Connection fails for SQL Server 2005

I have SQLServer2k5 on a WinXP Pro PC. I am having extraordinary difficulty
in getting any of the instances to start. Within Computer Management, the SQ
L
Server Configuration Manager reports "Cannot connect to WMI provider. You do
not have permission or the server is unreachable. etc, etc. Access is
denied.[0x80070005]".
I have been tearing my hair out all day trying to work out why I cannot get
this to start. Can anyone here give me some pointers as to what to do?
--
--
Chris JonesTry:
http://blogs.msdn.com/echarran/arch.../03/509061.aspx
-oj
"Chris Jones" <ChrisJones@.discussions.microsoft.com> wrote in message
news:01E31AE4-A7E3-4DE9-8EF9-154E2B214AC4@.microsoft.com...
>I have SQLServer2k5 on a WinXP Pro PC. I am having extraordinary difficulty
> in getting any of the instances to start. Within Computer Management, the
> SQL
> Server Configuration Manager reports "Cannot connect to WMI provider. You
> do
> not have permission or the server is unreachable. etc, etc. Access is
> denied.[0x80070005]".
> I have been tearing my hair out all day trying to work out why I cannot
> get
> this to start. Can anyone here give me some pointers as to what to do?
> --
> --
> Chris Jones
>|||oj
I already tried that. The response from the command was:-
Microsoft (R) 32-bit MOF Compiler Version 5.1.2600.2180
Copyright (c) Microsoft Corp. 1997-2001. All rights reserved.
Parsing MOF file: sqlmgmprovider.mof
MOF file has been successfully parsed
Storing data in the repository...
An error occurred while opening the namespace for object 1 defined on lines
4 - 7:
Error Number: 0x80070005, Facility: Win32
Description: Access is denied.
Compiler returned error 0x80070005
Lines 4-7 read:
Instance of __Namespace
{
Name = "Microsoft";
};
Any ideas, anyone?
--
--
Chris Jones
"oj" wrote:

> Try:
> http://blogs.msdn.com/echarran/arch.../03/509061.aspx
> --
> -oj
>
> "Chris Jones" <ChrisJones@.discussions.microsoft.com> wrote in message
> news:01E31AE4-A7E3-4DE9-8EF9-154E2B214AC4@.microsoft.com...
>
>|||Chris,
WMI works over dcom. Run "Dcomcnfg" (component sercies -> computers -> righ
t click on my computer to access the properties page) and make sure that dis
tributed com is on, plus, the access and launch permission is set correctly
for your system.
"
a.. Under Default Access Permissions click Edit Default. Make sure SYSTEM, I
NTERACTIVE, NETWORK, and the user whose authentication credentials will be u
sed to access the COM application all have Local and Remote Access permissio
ns.
a.. Under Default Access Permissions click Edit Limits. Service Pack 2 comes
with the following default values: ANONYMOUS LOGON (Local Access) and Every
one (Local and Remote Access). Make sure these values are listed, and then a
dd the user whose authentication credentials will be used to access the COM
application. Allow this user to have Local and Remote Access permissions.
a.. Under Default Launch Permissions click Edit Default. Make sure SYSTEM, I
NTERACTIVE, NETWORK, and the user whose authentication credentials will be u
sed to access the COM application all have Local and Remote Launch permissio
ns, as well as Local and Remote Activation permissions.
a.. Under Default Launch Permissions click Edit Limits. Service Pack 2 comes
with the following default values: MACHINE\Administrators (Local and Remote
Launch, Local and Remote Activation) and Everyone (Local Launch and Local A
ctivation). Make sure these values are listed, and then add the user whose a
uthentication credentials will be used to access the COM application. Allow
this user to have Local and Remote Launch permissions, as well as Local and
Remote Activation permissions.
"
Additional info on dcom vs winxp firewall setting can be found here:
http://www.microsoft.com/technet/pr...n/sp2netwk.mspx
--
-oj
"Chris Jones" <ChrisJones@.discussions.microsoft.com> wrote in message news:D8F5C485-6131-4B4
6-A637-86643F23D32F@.microsoft.com...[vbcol=seagreen]
> oj
>
> I already tried that. The response from the command was:-
> Microsoft (R) 32-bit MOF Compiler Version 5.1.2600.2180
> Copyright (c) Microsoft Corp. 1997-2001. All rights reserved.
> Parsing MOF file: sqlmgmprovider.mof
> MOF file has been successfully parsed
> Storing data in the repository...
> An error occurred while opening the namespace for object 1 defined on line
s
> 4 - 7:
> Error Number: 0x80070005, Facility: Win32
> Description: Access is denied.
>
> Compiler returned error 0x80070005
>
> Lines 4-7 read:
>
> Instance of __Namespace
> {
> Name = "Microsoft";
> };
>
> Any ideas, anyone?
> --
> --
> Chris Jones
>
>
>
> "oj" wrote:
>|||Oj
Thanks for the response. Unfortunately, this was too late to prevent me
re-installing XP. The original install of XP was an upgrade from Win2k Pro
and clearly had significant issues with all sorts of things that effectively
STOPPED SQL Server (and one or two other applications) from working.
I will bear your response in mind if I get any issues with SQL Server 2k5
when I install it later.
Thanks
--
--
Chris Jones
"oj" wrote:

> Chris,
> WMI works over dcom. Run "Dcomcnfg" (component sercies -> computers -> ri
ght click on my computer to access the properties page) and make sure that d
istributed com is on, plus, the access and launch permission is set correctl
y for your system.
> "
> a.. Under Default Access Permissions click Edit Default. Make sure SYSTEM,
INTERACTIVE, NETWORK, and the user whose authentication credentials will be
used to access the COM application all have Local and Remote Access permiss
ions.
> a.. Under Default Access Permissions click Edit Limits. Service Pack 2 comes with
the following default values: ANONYMOUS LOGON (Local Access) and Everyone (Local and
Remote Access). Make sure these values are listed, and then add the user whose auth
ent
ication credentials will be used to access the COM application. Allow this user to have Loca
l and Remote Access permissions.
> a.. Under Default Launch Permissions click Edit Default. Make sure SYSTEM, INTERAC
TIVE, NETWORK, and the user whose authentication credentials will be used to access
the COM application all have Local and Remote Launch permissions, as well as Local a
nd
Remote Activation permissions.
> a.. Under Default Launch Permissions click Edit Limits. Service Pack 2 comes with
the following default values: MACHINE\Administrators (Local and Remote Launch, Local
and Remote Activation) and Everyone (Local Launch and Local Activation). Make sure
the
se values are listed, and then add the user whose authentication credentials will be used to
access the COM application. Allow this user to have Local and Remote Launch permissions, as
well as Local and Remote Activation permissions.[vbcol=seagreen]
> "
> Additional info on dcom vs winxp firewall setting can be found here:
> [url]http://www.microsoft.com/technet/prodtechnol/winxppro/maintain/sp2netwk.mspx[/ur
l]
>
> --
> -oj
>
> "Chris Jones" <ChrisJones@.discussions.microsoft.com> wrote in message news
:D8F5C485-6131-4B46-A637-86643F23D32F@.microsoft.com...