the resource monitor does use a soap connect over a named pipe to sapstart service to communicate with it (IsAlive/LoockAlive checks Online/Offline calls).
Device not found indicates that the named pipe of the service could'nt be contacted, because it was not created during startup?
A typical root cause for this is, if the Start-Profile of the service can't be read. In this case the service can't read his configration, which is stored in the start profile and will terminate or in older versions will start in an state, which is note usefull for anything.
You should see this (start profile can't be read) in the Windows Application Eventlog.
The Eventlog (System and Application) is one of the most important resources for error/trace information if the profile can't be read.
Profile can't be read typically has two flavors:
- Access to the profile is denied - in this situation analyze the ACLs of the profile path (network share, directory to the profile and profile) and compare with the account information (account, group membership of the account)
- Profile not found: path/filename are incorrect or missing on the device - or the device is not ready at the time the service was started (in a cluster: the dependency of the cluster resources is not correct)
regards
Peter