Error in Admin after Upgrade to CF9

[The_ScareCrow]

Hi All,

I have upgraded to cf9 as per the online docs (multi server)

Made a copy of the neo files and the cfide

Uninstalled cf8

deleted jrun folder

rebooted

installed cf9

stopped services

copied neo files

replaced neo files with old cf8 neo files

started services

All went well except for the following error.

With the existing sql server datasources and when I try to create a new one I get the following error under the advanced section

Element DISABLE_AUTOGENKEYS is undefined in STDSN.

The error occurred in _cfsettings.cfm: line 95 Called from sqlserver.cfm: line 723 Called from sqlserver.cfm: line 1

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

So, I need to know how to fix this.  (re-install is not feasible)

Any ideas anyone....

Note:

If I check the checkbox next to the error and save the datasource.  When I open the datasource to edit it the error is gone.

Regards

Ken

[TheRealAgentK]

Hey Ken,

I don't really know what's causing it, but there's been a thread on this topic before where the person solved it by re-installing:

http://forums.adobe.com/thread/563849

stDSN is the internal struct that holds the datasource settings within the admin resp. on the page. It seems to be an issue with the CFadmin forms.

Cheers

K

[The_ScareCrow]

Thanks for the reply TheRealAgentK

Well after some research and a lot of debugging, I found the problem and thus the solution.

As I said I did this upgrade as per the online docs intructions.

In those it said to copy all the neo*.xml files from the web-inf/cfusion/lib folder from the existing instal.

After installing cf 9 the instructions then said to replace the noe*.xml files with the ones copied from the previous install.

The problem with this is that in cf 9 the sql server driver has a new attribute and thus the neo-drivers.xml file is different than the one in cf 8.

So, this file should not be replaced with the one from the previous version.

Luckily I copied the neo-*.xml files from the new install, so I just copied this file back, restarted the coldfusion service and all is well.

Regards

Ken

[TheRealAgentK]

Thx! I looged this as bug #84730 - prob. just a documentation unclarity that needs to be cleaned up then.

Cheers

Kai