CreateObject Failure! What to do!

[chefquix]

I've recently been thrust into the role of setting up a Windows 2000 Advanced Server, and am having an interesting problem that I really hadn't noticed until today. Basically, we have an in-house developed COM object (a shopping cart) that we're using on several webpages. I thought that I had everything set up properly, as when I test it, everything functions as it should. However, for the last two weeks I've been setting it up directly logged in as Administrator... when I log out as Administrator, the webpages and everything still work, but any asp pages that use the shopping cart object give an error like this:

Failure to Create Object error - non-existent SQL server or invalid username and password (or something to that effect).

The funny part is that I get the same problems even if I log in as Administrator through the terminal server.. the shopping cart only works if I'm logged in as Administrator directly. I've gone into the oleview and set the launch and access permissions on the object to Everyone, but that didn't do anything either. Basically I'm stumped and looking for some advice.

 

[mattKnight]

Sounds to me more like an issue with SQL Security... Can you post more info?

are you using SQL or (trusted) NT/2000 authentication to SQL server?
Are you using OLEDB or ODBC -
if ODBC, is the DSN a system wide one?
just soem thoughts, buit more info needed ithink!

Matt

 

[chefquix]

Ok, I'm a little new at all this unfortunately, so how can I figure out these things? I believe it's ODBC, but of course I'm not sure... I had to set it up in a bit of a hurry...

 

[chefquix]

I'm not entirely convinced that the problem lies in the SQL Server, and the reason for that is because if I log into the machine directly as Administrator, launch oleview, and double click on the object, it opens up properly showing the interfaces etc... However, if I log out of the machine and remote log in with terminal services, and do the same thing, I get the following error:

CoGetClassObject failed.
The server process could not be started because the configured identity is incorrect.
Check the username and password.
severity: SEVERITY_ERROR, facility: FACILITY_NULL ($8000401A)

Of course, after looking at this, it could very well be SQL Server isn't set up properly after all. Je suis confuse!

 

[mattKnight]

First post

Failure to Create Object error - non-existent SQL server or invalid username and password (or something to that effect).

second post

CoGetClassObject failed.
The server process could not be started because the configured identity is incorrect.
Check the username and password.
severity: SEVERITY_ERROR, facility: FACILITY_NULL ($8000401A)

The mention of Non-existent SQL server misled me...

Have you tried setting the launch permissions & identity in DCOMCNFG to a fixed user and then using that acct?

After that, I am a little stupmed myself!

Matt