SiteScope monitor often encounters “System error 1219” for Windows Remote

System error 1219 is from Windows OS, not SiteScope error. That means, Multiple connections to a server or shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again.

When user configures Windows Remote and some monitors(i.e. CPU, Logfiles), user may encounter the 1219 error by perfex.

Here is a sample.

18:03:04 12/20/2011 good group.25 CPU_monitor no data due to Error: CPU Monitor error for machine \\, exit code: 1219 3:19 n/a

This is one of the examples,

a. Customer configured Domain Administrator user as SiteScope Service account.


b. Customer configured local administrator user as Windows Remote in SiteScope.\administrator

Since the SiteScope service runs as Domain Administrator user, the SiteScope may access to remote shared resource by the account.

CPU, Memory and Disk monitors used perfex command to monitor the remote server.

The credential is based on Windows Remote configuration in SiteScope.

To avoid this issue, we have two solution.

1. Using alias hostname for each monitored servers.

1-1. Add alias hostname to C:\Windows\System32\drivers\etc\hosts

i.e. host-A host-A1

1-2. Edit Remote Server configuration in SiteScope


Server: host-A1

Credentials: host-A1\administrator

SiteScope can access to Windows Remote server by using alias hostname instead of original configuration(i.e. IP address, original hostname).

Since SiteScope uses the alias name for perfex connection, the user never conflict.


2. Using -optionalSetupConnection as perfex option.

2-1. Add the follosing optin in \SiteScope\groups\master.config file


2-2. Restart SiteScope service

It was recommended that SiteScope monitor uses Remote Windows servers configuration instead of running the service as a specific user. This works fine for most cases.

However, user will need to check the credential if all kind of monitor can work.

Leave a Comment