Troubleshooting SiteScope Resource Monitor Connectivity from LoadRunner Enterprise/Performance Center

Disclaimer: The information provided in this article is for general informational purposes only. The author and the publisher do not guarantee the accuracy, completeness, or reliability of the information. The techniques and suggestions mentioned may cause harm if not implemented correctly. The author and the publisher are not liable for any damages resulting from the use or misuse of the information. Use your own judgment and exercise caution when applying the suggestions in this article. Always consult official documentation and experts, and test changes in a controlled environment before applying them to production systems. By using this information, you agree to hold the author and the publisher harmless from any liability or claim.

Applies To:

1. LoadRunner Enterprise (LRE) / Performance Center (PC)
2. Micro Focus SiteScope (all versions where resource monitoring integration is used)
3. SiteScope installations with SSL or hardened security settings
4. Environments where SiteScope and LRE/PC are installed on separate servers
5. Windows servers running SiteScope and LRE/PC

Issue:

When attempting to set up a SiteScope Resource Monitor from within the LRE/PC controller, the connection fails at the stage where existing monitors should be retrieved. The user is unable to proceed beyond the initial SiteScope connection step in the monitor configuration UI.

Even though SiteScope itself is working and monitors are correctly configured there, the PC/LRE host cannot connect to retrieve them.

Cause:

This issue is commonly caused by:

1. Disabled or incorrect ports: The default SiteScope ports (8080 for UI, 8888 for communication) are disabled due to SSL configuration or hardening.
2. Incorrect port configuration in PC/LRE: The new secure ports (e.g., 8443 for UI, 8899 for data) were not used during the monitor setup.
3. Misunderstanding between “Account Name” and “User Name” in SiteScope, leading to authentication issues.
4. Improper or missing entries in SiteScope’s internal configuration files, which link user credentials with account IDs.

Steps:

1. Confirm SiteScope Ports

On the SiteScope host:

• Run the following to check port listening:

netstat -an | findstr LISTENING

• Or from PC/LRE host, run:

Test-NetConnection -ComputerName <SiSHost> -Port 8899

Make sure port 8899 (secure monitor port) is open and listening.

2. Understand Secure Port Mapping

If you've disabled default ports (8080/8888), note the equivalents:

• UI Access Port: 8443
• Monitor Communication Port: 8899 These must be used when configuring the SiteScope monitor in PC.

3. Identify Correct SiteScope Account Name

SiteScope uses an internal Account ID that differs from the User Name shown in the UI.

To find the Account Name:

• Go to:

<SiteScopeInstallDir>\groups

• Open user.config in a text editor (do not save changes).
• Locate the section for your user (e.g., _login=pc_sisadmin)
• A few lines above it, locate _id=... → This is your Account Name.

In this example:

• Account Name: login2
• User Name: pc_sisadmin

 4. Test SiteScope Connectivity via URL

From the SiteScope host and then from the PC/LRE host, access:

http://<SiteScopeHost>:8899/SiteScope/cgi/go.exe/SiteScope?page=topaz&account=<AccountName>

• Enter the User Name and Password when prompted
• You should see an XML output indicating a successful login

5. Configure SiteScope Monitor in PC

When adding the SiteScope monitor in the PC console:

• Server: SiteScope server hostname
• Port: 8899
• Use HTTPS: ✅ (Yes)
• Account Name: (from Step 3)
• User Name: (e.g., pc_sisadmin)
• Password: Corresponding password

Then click Get Counters to retrieve monitor list.

Additional Info:

1. Account Name vs. User Name:
   • Account Name = Internal SiteScope ID
   • User Name = Login used in the UI
2. Do not confuse the SSL UI port (8443) with the monitor communication port (8899).
3. If URL tests fail but ports are open, check for firewalls or proxy rules that may affect traffic between PC and SiteScope.
4. Always confirm user permissions: the SiteScope service account should have the necessary privileges to access remote systems being monitored.

We hope this article provided you with the assistance you needed. If you would like to find out more regarding the Services and Support Offerings we provide, please reach out to our Sales Team.