This content has been marked as final. Show 3 replies
"Active X component can't create object" means com+ was not able to instantiate the object. Usually it occurs because either
a) the component is not installed/registered, so install it, or
b) you're using a 64 bit process, and have the 32 bit component registered (so ultimately, it's still "not registered" as far as 64 bit goes, because it simply doesn't exist)
If using vbscript, you'll need to invoke the vbs file with the 32bit vbscript or cscript.exe (ie, c:\windows\syswow64\cscript.exe) , and then it should work.
You're right that it's not supported. 32 bit oo4 on 64 bit OS does seem to work fine though, based on my limited testing. It's not something we can help with if you encounter a problem in that config, but if just getting it to work is good enough, you may want to try it.
32 bit OLEDB IS supported on x64, if you want to change from OO4O to ADO.
Due to other software requirements on the web server, we were stuck using the x64 Oracle client. Althought I read you could have both x64 and x32 installed - we opted to go with OleDB and got it working.
As opposed to using:
Set dbSession = CreateObject("OracleInProcServer.XOraSession")
Set dbsession = Server.CreateObject("ADODB.Connection")
dbsession.Open "Provider=OraOLEDB.Oracle.1;Password=abc123;Persist Security Info=True;User ID=generic_user;Data Source=tnsnames_alias"