Unsolved
This post is more than 5 years old
5 Posts
0
7411
November 6th, 2013 02:00
nsrpsd stopped automatic, windows server 2012 error
In windows server 2012 errors are generated in the server manager when a service has start type 'Automatic' and the status 'Stopped'.
This seems to be the default for nsrpsd.
Services that handles this correctly has a start type of 'Automatic (Trigger Start)'. Shouldn't this service as well?
If you've come across this issue, how did you handle it?
No Events found!


ble1
6 Operator
•
14.4K Posts
•
56.2K Points
1
November 6th, 2013 03:00
I think "Automatic (Trigger Start)" should be ok for services "on demand". Not sure if nsrpsd is programmed that way, but you can check via sc qtriggerinfo nsrpsd (top of my head).
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
1
November 6th, 2013 04:00
I agree. I believe on older OS instance, it would be started as per demand which is pretty much what TriggerStart is, but EMC should set this during installation phase. On the other hand, you would use it only if using snapshotting so unless you don't use it - you can ignore that service.
azzid
5 Posts
0
November 6th, 2013 04:00
You could in theory set triggerinfo for the service, but the dependencies seem non-trivial and should probably be set up during client installation, and hence be specified by EMC.
azzid
5 Posts
0
November 6th, 2013 06:00
If you approach the issue the other way around, how do I turn this red green? I know I can ignore the issue, but I wan't the server manager to quit bothering me about it as well.
ble1
6 Operator
•
14.4K Posts
•
56.2K Points
0
November 6th, 2013 11:00
Ignore server manager too
I believe this is a question for EMC folks... I have couple of win2k12, but I use 8.0.2.x for them (so no nsrpsd). Where I use 8.1 (due to NMM 3.0), I do not use win2k12 so I have successfully escaped to this issue so far.