PTC MKS Toolkit Knowledge Base

Section:IO
Product:MKS AlertCentre (None)
Version:
OS:All
Keywords:user account, permissions, remote access, schedule
Category:General/Knowledge Base


My monitor runs fine when tested but as soon as I schedule it I get "Rasman" failed and directory not found errors?


The following error description happens when I set up and schedule AlertCentre monitors:

    I am using AC and have two monitors, a disk monitor and a windows service monitor. I add the monitors and "test" them and they work fine but when I schedule them I get the following errors:

    This is the text of the error message I receive from the Windows Service Monitor:

    10554 08 Aug 2003 11:45:04 Failed Service "RasMan" failed on REMOTEIN. No attempt to restart "RasMan" o (more...) Service "RasMan" failed on REMOTEIN. No attempt to restart "RasMan" on REMOTEIN. The monitor failed.

    This is the text of the error message I receive from the Disk Space Monitor:

    Run Number Run Time Run Status Run Result
    10577 08 Aug 2003 12:00:07 Failed couldn't stat file system for "//wsa_main/d$" Filesystem 1024-blocks (more...) couldn't stat file system for "//wsa_main/d$" Filesystem 1024-blocks Used Available Capacity Mounted on Failure due to any of the following: — cannot access filename — cannot access device — device is not a device

    The Monitors report successes when I browse into our AlertCenter server and run the "test" on each one. But when I schedule it, I get the above errors.

The problem is the user that the schedule is run as. The default is the system account. This needs to be changed to an account that has permissions to the machine that is being monitored. Typically this is the domain administrator account. When you run test a monitor, you are testing it with the account you are logged in as and it works. When it runs as a schedule it runs as the system account and fails.