Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 Cannot create COM Server

Author  Topic 

NickStan
Starting Member

36 Posts

Posted - 2008-11-20 : 05:32:07
Hi All

About once a week, we get the following error on our SQL Server:
Cannot create COM Server to load and execute DTS Package. Error -2147221008 (800401F0): CoInitialize has not been called.

We have the following database and OS: SQL Server 2000 SP4 and Windows Server 2003 Std Edition R2 SP2.

Now the only way I can get the error to stop is to re-boot our server (not ideal) and when this problem starts, it affects all DTS jobs that we have running until we reboot.

The first thing I did was to check Event Viewer -> System and on the day that we experianced problems, I can see an error:

Event Type: Error
Event Source: DCOM
Event Category: None
Event ID: 10016
Date: 14/11/2008
Time: 17:19:47
User: NT AUTHORITY\NETWORK SERVICE
Description:
The application-specific permission settings do not grant Local Activation permission for the COM Server application with CLSID
{0C0A3666-30C9-11D0-8F20-00805F2CD064} to the user NT AUTHORITY\NETWORK SERVICE SID (S-1-5-20). This security permission can be modified using the Component Services administrative tool.

Now the next thing I did was I went to regedit and looked up the CLSID 0C0A3666-30C9-11D0-8F20-00805F2CD064 and I can see 2 keys associated with this value: Machine Debug Manager and another one called AppID value {9209B1A6-964A-11D0-9372-00A0C9034910}.

I then went to Start -> Run -> dcomcnfg -> ComponentServices -> DCOM Config and found value {9209B1A6-964A-11D0-9372-00A0C9034910} which relates to Machine Debug Manager.

My question is where to from here?

I think that there could be a permissions issue with DCOM not initializing, but why intermittantly?

I changed the permissions on Machine Debug Manager in dcomcnfg (security -> Launch and Activate Permissions) and added Network Service to the list of users (but this did not help the problem).

Any suggestions welcome.

Thanks

Nick



   

- Advertisement -