qbvast
asked on
Cluster log entry "Startup routine for ResType MSMQ returned 21"
We had have som problem with SQL can´t handle sessions within a failover.
But I can find this entry in the eventlog that I can´t find why it appers. Resource monitor reports error.
MSMQ is not an enabled feuture of any of the nodes. Entry appears in both nodes log file when failover takes place.
Cluster log entry:
0000190c.000033ec::2013/01 /05-00:56: 04.166 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQ returned 21.'
00002ce4.0000353c::2013/01 /05-00:56: 04.166 WARN [RCM] Failed to load restype 'MSMQ': error 21.
00002ce4.0000353c::2013/01 /05-00:56: 04.166 WARN [RCM] rcm::RcmApi::ResTypeContro l: ResType MSMQ's DLL is not present on this node. Attempting to find a good node...
0000190c.000033cc::2013/01 /05-00:56: 03.168 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQ returned 21.'
0000190c.000033cc::2013/01 /05-00:56: 03.168 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQ returned 21.'
0000190c.000033cc::2013/01 /05-00:56: 03.168 ERR [RHS] s_RhsRpcCreateResType: ERROR_NOT_READY(21)' because of 'Startup routine for ResType MSMQTriggers returned 21.'
But I can find this entry in the eventlog that I can´t find why it appers. Resource monitor reports error.
MSMQ is not an enabled feuture of any of the nodes. Entry appears in both nodes log file when failover takes place.
Cluster log entry:
0000190c.000033ec::2013/01
00002ce4.0000353c::2013/01
00002ce4.0000353c::2013/01
0000190c.000033cc::2013/01
0000190c.000033cc::2013/01
0000190c.000033cc::2013/01
ASKER
Nope, no hyper-v. Have also seen that this occours when hyper-v is on but not in this case.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I start getting strange errors after adding Hyper-V role on one of two clusters where did it.