MS SQL Enterpise Manager 2005
Hi,
I am sequencing MS SQL Enterpise Manager 2005 application using AppV 4.6. Its working fine except one shortcut i.e SQL Server Manager confugration. When I launch the shortcut throwing the error saying "Canot connect to WMI Provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager. Invalid namespace [0x8004100e]. I searched for it, but didnt get any solution.
Thanks in advance.
Ravi
I am sequencing MS SQL Enterpise Manager 2005 application using AppV 4.6. Its working fine except one shortcut i.e SQL Server Manager confugration. When I launch the shortcut throwing the error saying "Canot connect to WMI Provider. You do not have permission or the server is unreachable. Note that you can only manage SQL Server 2005 servers with SQL Server Configuration Manager. Invalid namespace [0x8004100e]. I searched for it, but didnt get any solution.
Thanks in advance.
Ravi
0 Comments
[ + ] Show comments
Answers (2)
Please log in to answer
Posted by:
Rheuvel
13 years ago
Hi Ravi,
This doesn't sound like a problem with the sequence at all, but more of a problem with the application itself. The most common solution to this seems to be the fix described here
Try that after launching the sequence with a cmd prompt and if it works, upgrade the sequence and try to fix it during monitoring. If that doesn't work, have the OSD run the command inside the sequence on startup.
This doesn't sound like a problem with the sequence at all, but more of a problem with the application itself. The most common solution to this seems to be the fix described here
Try that after launching the sequence with a cmd prompt and if it works, upgrade the sequence and try to fix it during monitoring. If that doesn't work, have the OSD run the command inside the sequence on startup.
Posted by:
kewl.ravs
13 years ago
Hello,
I also got the same error while launching the sequenced SQL Server Manager Configuration of SQL 2005. I tried to apply the given fix, but it wont work. does anyone get resolved this issue.
I also got the same error while launching the sequenced SQL Server Manager Configuration of SQL 2005. I tried to apply the given fix, but it wont work. does anyone get resolved this issue.
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.
