November 5, 2008 at 3:21 pm
[font="Courier New"]PS SQLSERVER:\SQL\WS453VM1\DEFAULT\databases> cd \
PS SQLSERVER:\> cd sql
PS SQLSERVER:\sql> cd MySS2KMachine
PS SQLSERVER:\sql\MySS2KMachine> cd default
PS SQLSERVER:\sql\MySS2KMachine\default> cd Databases
PS SQLSERVER:\sql\MySS2KMachine\default\Databases> dir[/font]
and I see a list of all databases on the default (SS2K) instance
[font="Courier New"]PS SQLSERVER:\sql\MySS2KMachine\default> cd ..
PS SQLSERVER:\sql\MySS2KMachine> dir
Instance Name
-------------
DEFAULT
MSSQL2005[/font]
As you can see from the above, there is also a SQL Server 2005 instance installed on the MySS2KMachine.
Now, if I try the same thing for an Sql Server 2000 instance on a server (Windows 2003 R2 with SP1) with no SQL Server installed on the machine I get the error below:
[font="Courier New"]PS SQLSERVER:\> cd sql
PS SQLSERVER:\sql> cd MyPureSS2KMachine[/font]
WARNING: Could not obtain SQL Server Service information. An attempt to connect
to WMI on 'MyPureSS2KMachine' failed with the following error: SQL Server WMI provider is
not available on MyPureSS2KMachine. --> Invalid namespaceSet-Location : Cannot find path 'SQLSERVER:\sql\MyPureSS2KMachine' because it does not exist.
At line:1 char:3 + cd <<<< MyPureSS2KMachine
PS SQLSERVER:\sql>
So it seems that the machine where some Sql Server 2005 was installed has something that the other one is missing and which causes the error above.
So, did anyone have this problem and solved it? What is that minimum required to be able to contact a SS2K instance from SS2K8 PowerShell?
Any help wil be greatly appreciated.
November 5, 2008 at 3:26 pm
Sorry, there waqs a typo in my initial message:
For the second example it should read:
"with no SQL Server 2005 or higher installed on the machine I get the error below:"
instead of
"with no SQL Server installed on the machine I get the error below:"
Gabriela
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply