Win6 Coldfusion DSNs

Stephen

Stephen

US Operations
Staff member
We are restoring neo-query.xml from yesterdays backups, which we are extracting now.

The new hsphere did not resolve the problems with creating DSNs properly.
 
This issue is resolved. We once again had to disabled DSN creation on this account.

If you were the one needing a CF DSN on the win6 server that prompted this change in the last 24-48 hours, please submit a ticket and we will create the DSN for you.
 
OK, I am sorry, it is NOT resolved, it seems Coldfusion is storing some queue to edit from hsphere and within 30 seconds or so if fixing, it drops back to corrupting!
 
CF is now up, but DSNs and other user specific settings have not been restored, as the CF IIS connectors are still running during install process.
 
Well, we have been battling with the neo-query file and the ColdFusion issues. The neo-query file has been corrupted and our attempts to repair it have failed.

The only advice Macromedia has given us is to reinstall ColdFUsion and recreate the DSNs. Apart from that, their support is useless.

We request all Win6 ColdFusion users to resubmit their DSNs to us in a ticket so that we can recreate it. We would need the following information:

1) DSN Name

If MySQL, MSSQL or PostgreSQL
2) Database Name
3) Database Server
4) Database username
5) Database password

if MS Access
2) Database path
3) User/Password if any

We have disabled the ability to create DSNs through HSphere so please do not attempt to create DSNs through HSphere. We believe Hsphere is partly responsible for the ColdFusion issues as well as the poorly designed neo-query file by Macromedia. Ever since CFMX, Macromedia chose to use its own internal DSN system instead of relying on System DSNs created in Windows. This has been creating problems not only for us but other hosts especially when datasource related issues arise
 
You must log in or register to reply here.
Back
Top