RM Service Host - Service not automatically starting

[BeardedTech]

Hello,

 

First time post so I apologize if this has already been covered by another post.

 

Has anyone found a fix to the RM Service Host not starting automatically? We have about 500 student computers and at least half of them don't start this service automatically.

I can manually start the service using a script but with how often this service stops running, I'm almost running it every other day.

 

We are currently running RM Console CC4.3.

 

Any help will be greatly appreciated.

 

Thank you,

 

BeardedTech

[the_wuigi]

Are your stations requiring any system updates? Usually visible in RMMC under the computers node

[BeardedTech]

@the_wuigi - I have a few needing system updates, however the ones which repeatedly get this problem aren't in this update list.

[Max_Power]

What happens if you rebuild the effected stations?

 

Do you get an error message within Event Logs or in the RM logs which gives details on service hosts failure to start?

[BeardedTech]

@Max_Power After a rebuild the effected machines work for a couple of days before they start to drop off again.

 

From the Event Viewer I get this error:-

_________________________________________________________________________

Log Name: System

Source: Service Control Manager

Date: 14/02/2017 07:40:06

Event ID: 7036

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Description: The RM Service Host Service entered the stopped state.

_________________________________________________________________________

_________________________________________________________________________

 

Log Name: Application

Source: RMServiceHost

Date: 14/02/2017 07:40:06

Event ID: 0

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: Generic Comp Name

Description:

Service cannot be started. System.ComponentModel.Win32Exception: Unable to log on user ---> System.ComponentModel.Win32Exception: Unable to logon user '[email protected]' due to error 1311

at RM.Networks.Comms.ServiceHost.LogonServiceHostUser(LauncherService service, Int32 bUpdateConfig, Void** phUserToken, Void** phUserProfile)

--- End of inner exception stack trace ---

at RM.Networks.Comms.ServiceHost.LauncherService.OnStart(String[] args)

at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

________________________________________________________________________

 

- - - Updated - - -

@Max_Power After a rebuild the effected machines work for a couple of days before they start to drop off again.

 

From the Event Viewer I get this error:-

_________________________________________________________________________

Log Name: System

Source: Service Control Manager

Date: 14/02/2017 07:40:06

Event ID: 7036

Task Category: None

Level: Information

Keywords: Classic

User: N/A

Description: The RM Service Host Service entered the stopped state.

_________________________________________________________________________

_________________________________________________________________________

 

Log Name: Application

Source: RMServiceHost

Date: 14/02/2017 07:40:06

Event ID: 0

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: Generic Comp Name

Description:

Service cannot be started. System.ComponentModel.Win32Exception: Unable to log on user ---> System.ComponentModel.Win32Exception: Unable to logon user '[email protected]' due to error 1311

at RM.Networks.Comms.ServiceHost.LogonServiceHostUser(LauncherService service, Int32 bUpdateConfig, Void** phUserToken, Void** phUserProfile)

--- End of inner exception stack trace ---

at RM.Networks.Comms.ServiceHost.LauncherService.OnStart(String[] args)

at System.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

________________________________________________________________________

[superaz300]

Hello,

 

Do you have an RM Support contact?

 

There has being a few updates on the RM website for the RM Service Host service, and I am wondering if maybe one of these updates may fix your problem.

 

Cheers

James

[Grazza]

Hi, have you got the latest Window Image on your system? DWN5028976 (32bit) and DWN2852249 (64bit)

Are you building Windows 7 or Windows 10 Machines?

Are you building 32 bit or 64 bit?

 

We only build Windows 7 64 bit SP1 workstations using the latest WIM Image and also have CC4 Updates on as there are quite a few that sort Service Host Problems.

[Max_Power]

Nothing specific on RM site with that event message.

 

Are the recovery settings setup on the stations? If you go to services -> RM Service Host ->Properties -> recovery -> first, second and subsequent failures set to restart the service? Could see if that helps.

 

Is the Blob Manager starting? That's a dependency for RM service host.

 

Other than that, probably best logging a call with RM.

[BeardedTech]

Hey, we are running the latest windows image for Windows 7 32 bit SP1.

Will check and see if we have any CC4 updates pending.

[BeardedTech]

Thanks foryour continued help Max_Power.

 

Wecurrently have the RM Service Host recovery options to attempt to restart theservice three times before failing and this is visible in the event viewer;

1-

 

Log Name: Application

Source: Comms (RM.Networks.Comms.ServiceHost.LauncherService) - Logged Event

Date: 15/02/2017 07:43:17

Event ID: 1

Task Category: None

Level: Error

 

Keywords: Classic

User: N/A

Computer: computer.internal

Description:

Comms(RM.Networks.Comms.ServiceHost.LauncherService) logged the following event at07:43:17

Unable to update configuration file due toexception RM.Networks.Comms.Data.DalException: No such host is known --->System.Net.Sockets.SocketException: No such host is known

 

2-

Log Name: Application

Source: RMServiceHost

Date: 15/02/2017 07:43:18

Event ID: 11111

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: computer.internal

Description:

Unable to log on user

 

3-

 

Log Name: Application

Source: RMServiceHost

Date: 15/02/2017 07:43:18

Event ID: 0

Task Category: None

Level: Error

Keywords: Classic

 

User: N/A

Computer: computer.internal

Description:

Service cannot be started.System.ComponentModel.Win32Exception: Unable to log on user --->System.ComponentModel.Win32Exception: Unable to logon user '[email protected]' due to error 1311

at RM.Networks.Comms.ServiceHost.LogonServiceHostUser(LauncherServiceservice, Int32 bUpdateConfig, Void** phUserToken, Void** phUserProfile)

---End of inner exception stack trace ---

atRM.Networks.Comms.ServiceHost.LauncherService.OnStart(String[] args)

atSystem.ServiceProcess.ServiceBase.ServiceQueuedMainCallback(Object state)

 

 

Thinkingit might be worth changing the last recovery for the RMServiceHost run a scriptto check if the RMBLOBManager is running and if not start it? Havent seen anyproblems with the RMDALConfigService yet, which is a dependant forRMServiceHost aswell.

From whatI can see RMBLOBManager is starting on these machines, I did find this eventlog but I'm not sure if this is a releveant problem as I get this message onmachines where the RMServiceHost is running ok.

 

Yes think it might be time to log a ticket with them.

[BeardedTech]

Hi superaz300,

 

Yeah we have a support contract with them. I will check that out and see if there has been any updates since my colleague last had a look.

 

Thanks,

 

BeardedTech

[DarrenBaberRM]

Hi BeardedTech,

 

The error above (1311) is a standard Windows error being thrown as the "RM Service Host" service starts-up. The error equates to "There are currently no logon servers available to service the logon request."

 

So it would appear that the computers are booting up and not seeing the domain – as such CC4’s RM Service Host cannot then start as the domain account used to launch the service cannot logon.

 

I would encourage you to log a support call with RM for this issue (and do mention that I've replied to this thread on EduGeek so that I can track this).

 

Regards,

Darren

[jonspurs]

Have you got SSDs?

What Darren said links up. PCs were booting too quick for RMSH.

After a support call, RM set a 'Delayed' start for the SH as well as delaying timeout for GPO settings to be applied.

This has fixed our issue.