This post is more than 5 years old
142 Posts
0
3629
NMM .. Exchange2010 Shell Exception State of runspace is not valid for this operation. in function GetDBServers
Hi All,
I am using NMM - 2.4.1build122, Exhange 2010 DAG, Networker Server 8.0.1.1 build.132.
I sometimes get "NMM .. Exchange2010 Shell Exception State of runspace is not valid for this operation. in function GetDBServers" on running nsrsnap_vss_save -v -?
I get this message before each of the valid savesets, at the end I get "68150:nsrsnap_vss_save:nsrsnap_vss_save: Exiting with success."
Running the same command the very next time gives the desired result i.e the list of savesets.
Corresponding to first run below is what i get in nmm.raw
"
NSRcitical NMM .. Exchange2010 Shell Exception Processing data for a remote command failed with the following error message: The client cannot connect to the destination specified in the request. Verify that the service on the destination is running and is accepting requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig". For more in function CheckDBExists
"
I am trying to understand why does this happen sometime. I came across https://emc--c.na5.visual.force.com/apex/KB_BreakFix_1?id=kA1700000000lSH, but I am not sure if the problem at hand and the KA are related.
The backup is running fine, my query is only related to sometime out of line output of nsrsnap_vss_save -v -?
Regards
tech88kur
CarlosRojas
1.7K Posts
1
January 16th, 2014 07:00
Did you re-register the DLL?
If you are getting the same error even after re-registering it then this could be a temporary communication issue.
Also, have you checked the Application and System event logs to find out more about why this error is coming up?
Thank you,
Carlos
tech88kur
142 Posts
0
January 15th, 2014 08:00
Hi All,
Eagerly waiting to hear from you.
Regards
tech88kur
tech88kur
142 Posts
0
January 16th, 2014 04:00
Hi Carlos,
I get this randomly. The answer to all other questions is no.
Regards
tech88kur
CarlosRojas
1.7K Posts
1
January 16th, 2014 04:00
Hi tech88kur,
Is there any backup/restore running when you run nsrsnap_vss_save -v -?
Is there any Exchange maintenance running when you ran that command?
Was the Exchange server busy at the time you ran the command?
Are you getting that error always or randomly?
Thank you,
Carlos
tech88kur
142 Posts
0
January 16th, 2014 09:00
Dear Carlos,
I did not re-register DLL. (I do not know what it is? appreciate if you could enlighten here)
I missed to check App and SYS logs.
I understand it could be a temporary communication issue, as you said.
Regards
tech88kur
CarlosRojas
1.7K Posts
0
January 16th, 2014 10:00
Hi,
Plase see below the Steps to re-register EMC PowerShell library for Exchange:
In Cmd Prompt, type:
Cd C:\Windows\Microsoft.NET\Framework64\v4.0.30319
regasm "C:\Program Files\EMC NetWorker\nsr\bin\libnmexchmgmt.dll"
Replace \nsr\bin path with actual \nsr\bin
Also about re-registering dll's check this link:
windows - What does registering a DLL do? - Stack Overflow
Thank you,
Carlos