Dear Mr./Mrs Cooper, Since you asked I would be happy to reiterate the problem. (sorry if this is a little long but I wanted you to have all the details clearly)
STEP BY STEP: 1) I started the install and followed the instructions to shut down all Cold Fusion and IIS services (although the installer should do this for me IMHO). 2) Installer completes successfully. The installer did not tell me there was a problem -- everything went fine. It simply told me to go to the CF Admin page to finish the setup. I tried to go to the admin page via the recommended URL and I got an HTTP 500 error (Internal Server Error). Attempted to access other sites on my server - same error 500. Panic ensues. 3) Breathing heavily now, I looked at the services applet and noticed that the ODBC Services were not started. Tried to start them, they failed and stopped immediately (in other words, they could not be started). 4) To re-iterate **I cannot access the "next step" of the install (which is to access the admin page) because every site on the whole server (including admin) is getting a 500 error**. 5) Attempted reboot. Still get the 500 error on every site. Cursing fits begin. 6) Check event log and see that there is a GPF occurring in a exe from a Cold fusion folder (I figure this is probably why the ODBC services won't start - which *MIGHT* be the reason all my sites are getting a 500 error)... the error in the event log is: Reporting queued error: faulting application swagent.exe, version "1.93.0.0, faulting module unknown, version 0.0.0.0, fault address 0x00000000." At this point I call Macromedia - they tell me I will pay $500 to get some help with this. I say no. I write the awesome experts at houseoffusion list and within minutes am instructed to do a search for all INI files containing c:\Program Files\Merant and change it to c:\CfusionMX\db. I make this change, attempt to start the ODBC Services... magic! they start. I smile. Next step, I try to access my sites. Still get the 500 error. Reboot... still get the 500 error. I whimper. Another reply on houseoffusion advises me to retry running the IIS connector batch file. I do so and suddenly the world is right again. Everything works! MY BEST GUESS ON WHAT HAPPENED: During the install maybe the IIS Connector batch file failed for some reason but did not notify the installation of the failure. It may have failed because of this Marant path and when it was changed it could run again. Just a guess. ENVIRONMENT: Windows 2003 Server (latest updates applied) IIS6 Multiple sites on one server SQL Server 2000 SP3 installed on same server (yea yea I know) ASP.NET Enabled (not currently used however) Upgrading from Coldfusion MX 6.0 with latest updates applied. INSTALLER LOG SUMMARY: Install Begin: Tue Aug 05 15:52:46 PDT 2003 Install End: Tue Aug 05 15:57:06 PDT 2003 Created with Zero G's InstallAnywhere 5.0.7 Enterprise Build 1680 Summary ------- Installation: Successful. 56 SUCCESSES 0 WARNINGS 0 NONFATAL ERRORS 0 FATAL ERRORS Coldfusion seems to be running fine for now. Speed seems faster which is great! I sincerely hope this helps. -Dustin Snell Unisyn Software, LLC ----- Original Message ----- From: <[EMAIL PROTECTED]> To: "CF-Talk" <[EMAIL PROTECTED]> Sent: Tuesday, August 05, 2003 6:29 PM Subject: CF 6.1 upgrade causes sitewide 500 error!! Pain! > Let me re-iterate what seems to have happened here: > > 1) The Installer encountered a problem of some kind. It should have then told you this and what to do next. This caused the error when you tried to get to the websites. > > 2) The Config Wizard needs to be run after the Installer successfully completes. It normally kicks this off automatically at the end and finishes ODBC service setup. It automatically makes the corrections Michael described to the INI files. However, you didn't get this far because of #1. > > For #1, the Installer shold have described what went wrong and told you what to do. There should also be a log file in your install directory. > > > > > > This prevented you from getting > > 2) > > >Now if only Macromedia could stop hurting me with their upgrades :-) > > > >Dustin Snell > >Unisyn Software, LLC > >[EMAIL PROTECTED] > >----- Original Message ----- > >From: "Chris Kief" <[EMAIL PROTECTED]> > >To: "CF-Talk" <[EMAIL PROTECTED]> > >Sent: Tuesday, August 05, 2003 5:14 PM > >Subject: RE: CF 6.1 upgrade causes sitewide 500 error!! Pain! > > > > > >> 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 Get the mailserver that powers this list at http://www.coolfusion.com Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.4
