Ahhh - gotcha. Nice call then Michael. chris
>-----Original Message----- >From: Michael Dinowitz [mailto:[EMAIL PROTECTED] >Sent: Tuesday, August 05, 2003 5:23 PM >To: CF-Talk >Subject: Re: CF 6.1 upgrade causes sitewide 500 error!! Pain! > >Trust me, if the files in the cfusionmx/db directory say merant in them as >mentioned in the other post then there was an error on install and the >steps I >mentioned need to be made. If not, the migration wizard will not even work. >It's >super rare, but it does happen. > > >> The migration wizard manages the installation of the ODBC services. There >> should be no need to change files like you're suggesting. >> >> Before re-installing 6.1, try removing / re-installing the connectors to >> IIS. You can find bat files to handle this in >C:\CFusionMX\bin\connectors. >> >> If that fails, I would re-run the 6.1 installer and see if that clears >> things up. Be sure to rename the updater backup folder from your original >> CFMX installation (C:\CFusionMX\cfmx_updater\cfmx_61) so that rerunning >the >> installer doesn't overwrite those files. >> >> chris >> >> >> >> >-----Original Message----- >> >From: Michael Dinowitz [mailto:[EMAIL PROTECTED] >> >Sent: Tuesday, August 05, 2003 5:06 PM >> >To: CF-Talk >> >Subject: Re: CF 6.1 upgrade causes sitewide 500 error!! Pain! >> > >> >Glad the first issue could be resolved. The second one is probably what >the >> >other poster mentioned, which is that the migration tool has to be run. >> >Load up >> >this url: >> >http://127.0.0.1:8500/CFIDE/administrator/index.cfm >> >and let it run. If you get a 500 error on the url, then it's probable >that >> >the >> >update didn't finish or didn't install some needed connector. In that >case, >> >shut >> >down the IIS service, the CF service and SQL service (and any unneeded >> >service >> >like FTP, print spooling, etc.). Then re-run the 6.1 updater. After this >> >runs >> >and before doing anything else, make sure the ODBC is running (as you >did >> >before). If not, fix it. If so, then run the migration. It should all go >> >ok. >> >It's possible that the IIS running when the updater was installed >prevented >> >the >> >connector or something. As I don't use IIS, I can only speculate. >> > >> >> You were correct that the ODBC Services were not started and would not >> >start >> >> manually. I followed your instructions exactly and after doing this >the >> >> services started. That was exciting. Unfortunately the 500 error >> >persists. >> >> Tried restarting CF and IIS services: 500 error, tried server reboot: >500 >> >> error. Any other ideas? >> >> >> >> Thank you so much for trying to help me. >> >> >> >> Dustin Snell >> >> Unisyn Software, LLC >> >> [EMAIL PROTECTED] >> >> ----- Original Message ----- >> >> From: "Michael Dinowitz" <[EMAIL PROTECTED]> >> >> To: "CF-Talk" <[EMAIL PROTECTED]> >> >> Sent: Tuesday, August 05, 2003 4:35 PM >> >> Subject: Re: CF 6.1 upgrade causes sitewide 500 error!! Pain! >> >> >> >> >> >> > Go to the services and see if the 2 MX ODBC services are running. If >> >not, >> >> try to >> >> > start them. If they fail, then go to the cfusion/db dir and do a >search >> >> for any >> >> > *.ini with the words merant in them. Change all references to >> >c:\program >> >> > files\merant to c:\cfusionmx\db (assuming the cfusionmx is in c). >Then >> >> start the >> >> > ODBC services. >> >> > If that's not the problem, we'll go on from there. What webserver? >> >> > >> >> > >> >> > > Okay - hearing about all the great new stability enhancements in >6.1. >> >I >> >> > > immediately upgraded to eliminate a problem where the cold fusion >> >> service >> >> > > would stop responding until reboot about once a day at random >times. >> >Now >> >> > > immediately after upgrade, all sites on this multsite server are >> >> returning >> >> > > an Internal Error 500 to the browser. >> >> > > >> >> > > I am so sad about this and I can see no way to revert back to the >> >> orginal >> >> > > MX - with all its problems at least it worked for most of the day. >> >> > > >> >> > > Looked in the event log and I can see that a Coldfusion SQL agent >is >> >> GPFing >> >> > > Log folows: >> >> > > >> >> > > "Reporting queued error: faulting application swagent.exe, version >> >> 1.93.0.0, >> >> > > faulting module unknown, version 0.0.0.0, fault address >0x00000000." >> >> > > >> >> > > however I am not sure if the 500 problem is related because it >even >> >> happens >> >> > > when I access non-database related pages. I would try to change >the >> >> driver >> >> > > but I cannot access the web server without getting the 500 error - >> >not >> >> even >> >> > > the CF Administrator! No other interesting entries in the event >log. >> >> > > Everything worked before. >> >> > > >> >> > > Environment is: >> >> > > Windows 2003 Server >> >> > > SQL Server 2000 Latest SP >> >> > > CFMX 6.1 >> >> > > >> >> > > Help if you can please!!! Macromedia says they won't help me >unless I >> >> pay >> >> > > $500 >> >> > > >> >> > > >> >> > > >> >> > >> >> >> > >> > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Archives: http://www.houseoffusion.com/cf_lists/index.cfm?forumid=4 Subscription: http://www.houseoffusion.com/cf_lists/index.cfm?method=subscribe&forumid=4 FAQ: http://www.thenetprofits.co.uk/coldfusion/faq Your ad could be here. Monies from ads go to support these lists and provide more resources for the community. http://www.fusionauthority.com/ads.cfm Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
