UNSOLVED
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?
1879
1
Posted 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.
1879
0
Posted November 6th, 2013 04:00
C:\Windows\system32>sc qtriggerinfo nsrpsd
[SC] QueryServiceConfig2 SUCCESS
The service nsrpsd has not registered for any start or stop triggers.
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.
C:\Windows\system32>sc triggerinfo
DESCRIPTION:
Changes the trigger parameters of a service.
USAGE:
sc triggerinfo [service name] ...
OPTIONS:
start/device/UUID/HwId1/...
specified device interface class UUID
string with one or more hardware ID
strings and/or compatible ID strings>
start/custom/UUID/data0/..
event from the specified custom ETW
provider UUID string with one or more
binary data items in hexadecimal
string format such as ABCDABCD to
set 4 byte data>
stop/custom/UUID/data0/...
event from the specified custom ETW
provider UUID string with one or more
binary data items in hexadecimal
string format such as ABCDABCD to
set 4 byte data>
start/strcustom/UUID/data0/..
event from the specified custom ETW
provider UUID string with one or more
optional string data items>
stop/strcustom/UUID/data0/..
event from the specified custom ETW
provider UUID string with one or more
optional string data items>
start/lvlcustom/UUID/data0/..
event from the specified custom ETW
provider UUID string with level higher
or equal to the data items in
hexadecimal number format such as
0x01>
stop/lvlcustom/UUID/data0/..
event from the specified custom ETW
provider UUID string with level higher
or equal to the data items in
hexadecimal number format such as
0x01>
start/kwanycustom/UUID/data0/..
event from the specified custom ETW
provider UUID string with keyword that
matches any of the bits in the data
items in hexadecimal number format
such as 0x0A03>
stop/kwanycustom/UUID/data0/..
event from the specified custom ETW
provider UUID string with keyword that
matches any of the bits in the data
items in hexadecimal number format
such as 0x0A03>
start/kwallcustom/UUID/data0/..
event from the specified custom ETW
provider UUID string with keyword that
matches all of the bits in the data
items in hexadecimal number format
such as 0x0A03>
stop/kwallcustom/UUID/data0/..
event from the specified custom ETW
provider UUID string with keyword that
matches all of the bits in the data
items in hexadecimal number format
such as 0x0A03>
start/networkon
stop/networkoff
start/domainjoin
stop/domainleave
start/portopen/parameter
a network port. The parameter is of the
semi-colon delimited form
portnumber;protocolname;imagepath;
servicename>
stop/portclose/parameter
a network port. The parameter is of the
semi-colon delimited form
portnumber;protocolname;imagepath;
servicename>
start/machinepolicy
policy changes or is present at boot>
start/userpolicy
policy changes or is present at boot>
start/rpcinterface/UUID
arrives at the RPC Endpoint Mapper for
the given interface>
start/namedpipe/pipename
arrives for the specified named pipe.
Do not include the "\\.\pipe\" portion
of the pipe's name>
delete
1879
0
Posted 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.
1879
0
Posted 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.
ble1
6 Operator
•
14354 Posts
•
56186 Points
1879
1
Posted 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).