This is a continously updated list of known issues for released versions of Performance Guard. The list contains all issues that we think are of special interest to our customers and partners.

Version 5.2.32

Agent

PG-4300 SQL server traffic generates false response times in agent

TCP Keep-alive traffic may cause the agent to measure false response times.

Server

PG-4299 Dashboard history update button does not work

Problem: When clicking the Dashboard history link beneath the Dashboard you enter the Dashboard history page. The "Update" button does not seem to work.

PG-4324 HTTP error code 404 when clicking on Performanceguard icon at top left

Problem: Anywhere within the help desk wizard, if you press on the PerformancGuard icon (top left) to go to the dashboard, you will get a 404 error

PG-4323 IE Transactions graph - Missing data in Requests subgraph

Problem: In the Time View -> Transactions graph when choosing an IE-filter the requests graph will be empty.

PG-4307 Administration -> system status -> log files - uppercase/lowercase problem

Problem: If you do not enter the value of "Monitor log folders" under the menu item Administration -> PGUARD Configuration -> Display in correct case then when you go to Administration -> system status -> log files, and click on a logfile, then you might get this error:

java.io.FileNotFoundException: C:\WINDOWS\TEMP\F:\PerformanceGuard\collector\logs\stderr.log (The filename, directory name, or volume label syntax is incorrect)
java.io.FileInputStream.open(Native Method)
java.io.FileInputStream.<init>(FileInputStream.java:106)
com.premitech.e2edisplay.servlet.TempFileServlet.showFile(TempFileServlet.java:85)
com.premitech.e2edisplay.servlet.TempFileServlet.copyFileToStream(TempFileServlet.java:78)
com.premitech.e2edisplay.servlet.TempFileServlet.doGet(TempFileServlet.java:196)
com.premitech.e2edisplay.servlet.TempFileServlet.doPost(TempFileServlet.java:46)
javax.servlet.http.HttpServlet.service(HttpServlet.java:709)
javax.servlet.http.HttpServlet.service(HttpServlet.java:802)

Report archiving - week 1 is not generated when overlapping with previous year

Problem: If week #1 of the year starts in the previous year weekly generated reports for week #1 are lost.

510to520post.sql is not executed when upgrading

Problem: When upgrading from PG version 5.1 to 5.2 the SQL server upgrade script 510to520.cmd executes the file "..\510to520post.sql" instead of correctly "510to520post.sql"

Solution: Correct the file 510to520.cmd before executing or execute the SQL file 510to520post.sql manually after the upgrade.

Version 5.1.44

Agent

PG-4165 Agent icon process consuming 100% of one CPU after install (since 5.1.36)

See description below: #PG-4165 Agent icon process consuming 100% of one CPU after install

PG-4203 Agent Icon consumes 100% CPU on Microsoft Terminal Servers (since 5.1.36)

See description below: #PG-4203 Agent Icon consumes 100% CPU on Microsoft Terminal Servers

Server

PG-4158 Server/Port graph heading is empty when selection agent super group

Problem: When selecting an agent super group in the Server/Port graph the graph heading does not contain the agent super group name but is empty.

Solution: There's no work around. Wait for a later version of Performance Guard.

PG-4157 Server/Agent graph does not work when agent super groups are selected

Problem: When selecting agent super groups in the Server/Agent graph the graph will most likely be empty.

Solution: There's no work around. Wait for a later version of Performance Guard.

PG-4054 Execution of DeleteDeadAgents may lock up the PG database on Citrix installations (since 5.1.36)

See description below: #PG-4054 Execution of DeleteDeadAgents may lock up the PG database on Citrix installations

Version 5.1.36

Agent

PG-4089 Agent icon cannot be removed

Problem: The agent icon does not disappear even you disable the "Enable Task Bar Icon" setting in the agent configuration.

Solution: A workaround to the problem could be to execute the following command after the installation of the agent:

c:\Program Files\Premitech\PErformance Guard Agent\guardagent.exe -ug

The above command removes the following entry in the registry which prevents the agent icon from starting up when the users logs in.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"GuardAgentGui"="\"C:\\Program Files\\Premitech\\Performance Guard Agent\\GUARDagent.exe\" -gui"

PG-4165 Agent icon process consuming 100% of one CPU after install

Problem: In certain situations the agent icon process uses 100% of the CPU resources (or 50% on dual core systems) just after being installed. Apparently this may happen if a user logs in to the machine right after the agent is installed by a software distribution tool or by using Group Policy Objects in Active Directory. The problem can be identified by the fact that 3 guardagent processes will be present in the task manager process list and one of them will be using excessive CPU. Rebooting the machine causes the problem to disappear. This is a serious issue to address when installing the agent on production servers.

Solution: Schedule a reboot just after the agent installation.

PG-4203 Agent Icon consumes 100% CPU on Microsoft Terminal Servers

Problem: The agent icon uses all available CPU resources for each terminal services session.

Solution: On Microsoft Terminal Servers you need to remove the agent icon completely by executing the following command after the installation:

c:\Program Files\Premitech\PErformance Guard Agent\guardagent.exe -ug

The above command removes the following entry in the registry which prevents the agent icon from starting up when the users logs in.

[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Run]
"GuardAgentGui"="\"C:\\Program Files\\Premitech\\Performance Guard Agent\\GUARDagent.exe\" -gui"

PG-4129 Agent uninstall does not remove PGExtHelper.dll

Problem: When uninstalling the agent, the file c:\windows\system32\PGExtHelper.dll is left behind on the system.
Solution: Don't do anything. The file does not harm your system and if you later install another version of the Performance Guard agent it will be overwritten with the correct version of the file..

Server

PG-4003 Upgrade of BTM v1. data is not correct

Problem: When upgrading from previous versions of Performance Guard and you are using the Business Transaction Monitor module, the data is not upgraded correctly.

Solution: Do not upgrade to this version. If you already have upgraded then please contact a Premitech consultant.

PG-4035 Citrix trend graph - Can not select empty ICA client group

Problem: In the Citrix trend graph it is not possible to select ICA Client Groups that have no agents installed.

Solution: Upgrade to a later version or disable the setting "Hide empty groups" in the menu Administration -> PGUARD Configuration on the Display tab.

PG-4054 Execution of DeleteDeadAgents may lock up the PG database on Citrix installations

Problem: If you have Performance Guard agents installed on Citrix servers and one of these agents is an old entry and is scheduled to be removed by the "DeleteDeadAgents" stored procedure, then the execution of the "DeleteDeadAgents" stored procedure may lock up the Performance Guard database.

Solution: Disable the stored procedure by replacing it with an empty procedure that does nothing or put a "RETURN" statement at the top of the stored database procedure "DeleteDeadAgents".

PG-4117 Collector refresh command throws runtime exception

Problem: Issuing the "refresh" command in the collector telnet interface causes the collector to throw a runtime exception and does not do a refresh.

Solution: If you need to refresh the collector please restart the collector service.

PG-4166 HelpDesk Wizard step 3 does not show a graph when no compare group is selected.

Problem: In step 3 of the Help Desk Wizard you will not see a response time graph unless you select an agent group to compare with.

Solution: Select "All agents" or any other agent group in the "Select group" drop down box to the left.