Showing results for 
Search instead for 
Do you mean 

SiteScope monitor error

Occasional Contributor

SiteScope monitor error

I'm using LoadRunner 9.50 + "SiteScope for Load Testing 11.00" (each running on a dedicated host) and I would like to add a SiteScope monitor to my scenario. Unfortunately when I try adding a new measure I get the following error in the “SiteScope Monitor Configuration” dialogue:

 

Parsing error.

Details: host c032036, port 8888, line: 11.

Reason: End tag 'HEAD' does not match the start tag 'META'.

.

Contents: <HTML>

<HEAD>

<meta http-equiv="Expires" content="0"/>

<meta http-equiv="Pragma" content="no-cache"/>

 

<META HTTP-EQUIV="Content-Type" CONTENT="text/html;CHARSET=Cp1252"/>

<META HTTP-EQUIV="Refresh" CONTENT="10; URL=/SiteScope/htdocs/SiteScope.html"...      [MsgId: MMSG-47587]

 

I attached two screenshots of the steps leading up to this error.


 I verified port 8888 is reachable from the controller and configured as the "Classic user interface" in the SiteScope config wizard. Also, SiteScope seems to run well otherwise (I can access the web UI from the controller machine without problem).

 

Any help is greatly appreciated.

 

4 REPLIES
HPE Expert

Re: SiteScope monitor error

Please try to add in this way while configuring the monitor

 

<hostname>:8080

<IP>:8080

 

Did you set any password for admin user?

Occasional Visitor

Re: SiteScope monitor error

KMadan are right.

admin user must have an empty password.

This error appears in case of admin password is not empty.
Member

Re: SiteScope monitor error

In order to use any SiteScope account you want, with any password you want, check this doc:
http://support.openview.hp.com/selfsolve/document/KM195182
Occasional Visitor

Re: SiteScope monitor error

[ Edited ]

I know this post is very old but just wanted to post a solution for people who run into this now.

 

Go to the server where Sitescope is installed and open the configuration manager console

Select change port

Note which port is used for the classic interface.  (Make sure the classic interface and the new interface are on 2 different ports)

Use that port with the server name in the controller

Example: click 'Add' and type <server name>:XXXX

 

Also try configuring as the new user interface but connecting with classic interface port from loadrunner controller as stated above.

 

That's what worked for me :)