ColdFusion Administrator issues after installing ColdFusion 10 Update 18 hotfix (APSB15-29)

Posted by Dan on Nov 18, 2015 @ 1:43 PM

While upgrading to ColdFusion 10u18 (APSB15-29) in my development environment, I immediately started having a problem with the CF Administrator. The topnav.cfm was generate errors (I wasn't seeing the normal icons at the top right) and any attempt to go to the Server Update > Updates page was throwing one of the following errors:

java.lang.NullPointerException
    at coldfusion.server.UpdateService.init(UpdateService.java:127)
    at coldfusion.server.UpdateService.<init>(UpdateService.java:118)
    at coldfusion.server.UpdateService.getInstance(UpdateService.java:179)
    at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
    at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
    at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
    at java.lang.reflect.Method.invoke(Method.java:497)
    at coldfusion.runtime.java.JavaProxy.invoke(JavaProxy.java:97)
    at coldfusion.runtime.CfJspPage._invoke(CfJspPage.java:2428)

or:

Element UPDATESETTINGS.UPDATESERVICE is undefined in a Java object of type class [Ljava.lang.String; referenced as ''

The error occurred in C:/work/cf10_final_hotfix/cfusion/wwwroot/CFIDE/administrator/updates/index.cfm: line 103
Called from C:/work/cf10_final_hotfix/cfusion/wwwroot/CFIDE/administrator/updates/index.cfm: line 52
Called from C:/work/cf10_final_hotfix/cfusion/wwwroot/CFIDE/administrator/updates/index.cfm: line 51
Called from C:/work/cf10_final_hotfix/cfusion/wwwroot/CFIDE/administrator/updates/index.cfm: line 1

-1 : Unable to display error's location in a CFML template.

After working with Adobe, it was determined that the {cf_install_home}/{instance_name}/lib/neo_updates.xml was corrupted and missing the <defaulturl> element. It appears this file was corrupted in the version of hotfix_018.jar that was originally available. I just re-downloaded the JAR file and the problem appears to be resolved, so I think they already fixed the problem.

The fix was to replace the neo_updates.xml with the following:

<?xml version="1.0" encoding="UTF-8"?>
<settings>
    <update autocheck="false" checkinterval="10" checkperiodically="false">
        <url>
            http://www.adobe.com/go/coldfusion-updates
        </url>
        <defaulturl>http://www.adobe.com/go/coldfusion-updates</defaulturl>
        <notification>
            <emaillist/>
        </notification>
    </update>
</settings>

And then restart the ColdFusion service.

Hopefully no one else runs into the issue, but if you do, hopefully this helps someone!

Categories: HTML/ColdFusion

2 Comments


Comments for this entry have been disabled.