January 30, 2006 at 9:02 am
I have installed SQL Server developer on my home pc running Windows XP Professional.
I get the following error message in job history:
The job failed. Unable to determine if the owner (ANTEC\Stefan) of job test has server access (reason: The server could not load DCOM. [SQLSTATE 42000] (Error 7404))
January 30, 2006 at 9:22 am
Hello Stefan,
Do you find any information in SQL Server Logs or Event Viewer?
What does the stored procedure do?
If you can provide more information, then we can go ahead investigating it in the right direction.
Thanks and have a nice day!!!
Lucky
January 30, 2006 at 9:38 am
This is a failing job, not a stored procedure. The error message in the Event Viewer is:
Event Type:Warning
Event Source:SQLSERVERAGENT
Event Category:Job Engine
Event ID:208
Date:30/01/2006
Time:16:20:39
User:N/A
Computer:ANTEC
Description:
SQL Server Scheduled Job 'test2' (0x33EE095F4BC451479C4903CDEE9B0D74) - Status: Failed - Invoked on: 2006-01-30 16:20:39 - Message: The job failed. Unable to determine if the owner (ANTEC\Stefan) of job test2 has server access (reason: The server could not load DCOM. [SQLSTATE 42000] (Error 7404)).
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
January 30, 2006 at 9:52 am
I also get a similar message when trying to create a new database in Enterprise manager:
Dialogue box:
Microsoft SQL-DMO (ODBC SQL State:42000)
Error 7404: The server could not load DCOM.
However after clicking OK on the dialogue box I can still create a database. I can also create a database from QA without any error.
January 30, 2006 at 10:23 am
Hello Stefan,
Can you check this information in Books Online -> Installing SQL-DMO
Check whether the said files are existing in the default location.
Thanks and have a nice day!!!
Lucky
January 31, 2006 at 10:38 am
Make sure that your windows firewall is disabled and that the services needed for DCom to work are running. I am not absolutely sure what the services are but the Remote Procedure Call (RPC) service and the COM+ Event system service should be running.
February 7, 2006 at 5:31 am
I've got exactly the same problem and I just can't find out what the issue is. If I try and create a database via Management Studio I get the above error. If I use TSQL it creates without any problems. Also if I connect to another SQL Server machine I can happily use Management Studio! So it seems it's having trouble communicating to the local server!!? I played around with every DCOM setting I can see, the firewalls been up and down and that doesn't seem to help. I'm totally stumped. HELP!
February 7, 2006 at 6:24 am
DCOM allows you to start com+ (activex) components executing on another pc or server, but you need to have the correct permission and it needs various services to be running on that server.
When you create a database in TSQL the command is actually executing on the server so it isn't using DCOM.
When you run a command in management studio it needs to start a com+ component on the remote (or local) server in order to do what it needs, but for some reason the com+ component won't start. Check the event log for error messages. Check the services that are running on the server you can link to (the com based ones and the remote connection ones).
The problem can also be security. You need to have the (windows) permission to start dcom components.
For interest, if you want to look at the authentication required for specific dcom components: on the server type in dcomcnfg (in START/run), then double click on component services and then Computers, then click on My computer and Dcom config. Enter yes to any messages that come up. Right click on the dcom component you are interested in and select properties.
Sorry, I don't know what dcom component management studio uses on the server.
Hope this points you in the right direction. i.e. look at the differences in the services and permissions you have to the problem server and the one that is OK.
Peter
February 13, 2006 at 8:06 am
Peter, thanks the message but WHICH component? In my case I can't create databases on the same server as tools but it WILL create databases on a remote server. I've tried enababling all sorts of things in DCOM, default/launch etc. One of the things I'm considering is that I don't run on a Domain (when it's local) and some of the DCOM stuff I've found seems to suggest that you need a domain user. Perhaps that's the issue, but I've no idea how to solve it since I don't have a domain controller on my own network. The other avenue is the COM SQLDOM objects, but I would imagine they'd be used to talk to a remote server.
July 2, 2007 at 6:19 pm
I am having a similar problem. I was trying to install a new piece of software (Journeyx Timesheet), and after the installation and upon rebooting, the following entries appear in my SQL Server Log:
Failed to Initialize COM (CoInitializeEx returned 80010106)
Heterogeneous Queries and Remote RPC will be disabled.
Using 'xpstar.dll' version '2000.80.760' to execute extended stored procedure 'sp_MSgetversion'.
And at this point, certain functions have stopped working. For example,
SELECT * FROM ::fn_helpcollations()
returns the following error message:
Server: Msg 7404, Level 16, State 2, Procedure fn_helpcollations, Line 9
The server could not load DCOM.
Likewise, attempting to add a new database prompts with "The server could not load DCOM" (which I suspect is because the New Database dialog box also displays the list of Collations in a drop-down box).
Prior logs do not show this error, and uninstalling the software and rebooting has not cleared up the problem.
Anyone have any ideas?
July 4, 2007 at 5:48 pm
I am having the same problem (error 7404) using SQL Server 2000. I am unable to add a database or view tables in a new linked server. I recently installed MDAC 2.8 and I believe the problem has started since then.... but that's just a guess.
I also see the following in event logs when starting up SQL Server:
17052 : Failed to Initialize COM (CoInitializeEx returned 80010106)
17052 : Heterogeneous Queries and Remote RPC will be disabled.
July 16, 2007 at 4:59 pm
A complete uninstall (including all previously created files) then a fresh install cured the problem for me.
April 24, 2009 at 9:52 am
On your client machine try registering SQL-DMO dlls:
regsvr32 atl.dll
regsvr32 sqldmo.dll
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply