This was a clean install of MX6.1, and then the updater, so presumably any com patch will have been included. It turned out that both the machines which didn't have com working had hung during install of MX at the "Installing ODBC services step". As http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_18800#hangs we had tweaked the cf_root\lib\adminconfig.xml file to set runsetupwizard=false. This meant CF admin would run, but com wasn't working. We then uninstalled, and added 127.0.0.1 to the local intranet zone as a trusted site (as per http://www.macromedia.com/cfusion/knowledgebase/index.cfm?id=tn_18800#win2003) then re-ran the installation. That seemed to fix the COM thing.
However, when the site was put back on the box MX was restaring itself every hour or so. This was the same site which ran happily for weeks on the same servere when it was win2000, and now after upgrading to 2003 its unusable, but i'm going to start a new thread cos the subject line is now wrong... Cheers Bert On Wed, 15 Dec 2004 07:19:38 -0500, SteveK <[EMAIL PROTECTED]> wrote: > Cf released a com patch awhile back. Try adding or removing the patch. > When we installed the patch it broke our com object. > > Steve > ----- Original Message ----- > From: "Bert Dawson" <[EMAIL PROTECTED]> > To: "CF-Server" <[email protected]> > Sent: Wednesday, December 15, 2004 6:51 AM > Subject: An exception occurred when instantiating a Com > > > I'm getting an error ("An exception occurred when instantiating a Com > > object, The cause of this exception was that: AutomationException: > > 0x80040154 - Class not registered") when trying to instantiate a COM > > object, but i only get it on some servers. > > > > My laptop works fine, as does the test server and a couple of the live > > servers. But the dev and a new live server are both giving the error > > above. > > (all are running CFMX6.1, with updater. > > And win2003, except the laptop which is XPpro SP1) > > > > a cfm file containing: > > CreateObject("COM", "InternetExplorer.Application"): > > throws the error on some of the servers (as listed above) > > > > a .vbs file containing > > Set o = CreateObject("InternetExplorer.Application") > > doesn't throw an error on any servers. (if i change the object name > > then it does throw an error) > > > > Any ideas why creating COM objects in CF would work on some servers > > and not on others? > > > > Cheers > > Bert > > > > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~| Special thanks to the CF Community Suite Silver Sponsor - New Atlanta http://www.newatlanta.com Message: http://www.houseoffusion.com/lists.cfm/link=i:10:5073 Archives: http://www.houseoffusion.com/cf_lists/threads.cfm/10 Subscription: http://www.houseoffusion.com/lists.cfm/link=s:10 Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=11502.10531.10 Donations & Support: http://www.houseoffusion.com/tiny.cfm/54
