Advanced Setting in Datasource Edit

[Sitaga214]

I am getting the following error when opening the Datasource Advanced Settings:

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.

It happens when adding a new Datasource or when editing an existing datasrouce.  Has anyone else seen this or know how to fix it?

This is Coldfusion 9 on Windows Server 2003.  Coldfusion was upgraded from CF8 right before this error started.

Thanks,

Bill

[Adam Cameron.]

Just to confirm, did you do an inline upgrade of the CF8 server?  It's a bit late now, but you really shouldn't upgrade a CF server, you should always set up a new CF instance and port the sites/applications across.  The reason being if you do an upgrade and it goes wrong (like it seems this one has), you're stuffed.

Did you do a back-up of your CF install before you did the upgrade?  The quickest thing might be to revert to that so you're up and running again, and start the migration again.

And... no... I have never seen that error.

--

Adam

[Sitaga214]

I believe it was an inline upgrade, however the CF8 install directory is still present.  This is on our development server, so I wasn't too concerned with down time.  Do you think an uninstall/reinstall of CF9 would correct the issue or should I restore a back up and try the upgrade again?

Thanks,

Bill

[Joshua_Cyr]

I would be interested to see the comparison of those files in cf 8 and cf 9.  Maybe install cf 9 locally fresh, then compare the files in question?  Perhaps a file permission issue caused the upgrade to miss or skip updating a few files?

[Sitaga214]

The file is a CF Template (part of the /CFIDE/Administrator folder), so I'm not sure how to compare them.  They are not flat text.  It could have been a file permission issue though - for instance if CF* Admin was open while CF9 was installing some of the files may have been locked.  I will try another install.

Thanks again,

Bill

[Adam Cameron.]

Hmmm.  It is one approach.  Often I am hesitant to try to work out what went wrong, in situations wherein there's not much to gain from knowing, and working this sort of thing out can take quite a bit of time.  If that makes sense.

If after doing a fresh CF9 install and porting the code (as per my preceding post) it still doesn't work, then I guess it's time to work out WTF.

--

Adam

[Sitaga214]

I uninstalled CF8 and CF9 and then reinstalled CF9 and the issue was corrected.

Thanks,

Bill

[TheRealAgentK]

Just saying - this topic bubbled up again and there is a solution:

http://forums.adobe.com/message/3221790#3221790

Cheers

Kai

[Adam Cameron.]

I would revert to a known-working CF8 environment before trying anything again.

Then install CF9 in a different location, export the settings from the CF8 server, import to the CF9 server, then copy the CFML files to the appropriate place for the CF9 server to serve them.

There's actually no problem having CF9 serving the same webroot as the CF8 server, so just leaving the source code where it is and set that to be CF9's webroot would be fine.

But back-up everything first.

--

Adam