Platespin Recon - Monitoring Stops and Options are Greyed Out

1.0 Overview

This Xtravirt hot tip outlines an issue where most of the options are greyed out in the Recon client GUI and monitoring stops. The following sysptoms are observed.

• Monitoring stops on all servers and most of the options are greyed out in the Recon client GUI including the License Manager option

• If using the PostGRE database the ‘PostgreSQL Database Server 8.x’ service may also be stopped

2.0 Cause

The PlateSpin_3x website within IIS Manager is configured to use ASP .NET version 1.1 instead of version 2.0 and/or the PostGRE database service, if used, has not started

3.0 Resolution

• Ensure the following Windows services are started:
  
  • PlateSpin Recon Monitoring Service 3.x
  • PlateSpin Recon Service 3.x
  • PostgreSQL Database Server 8.3 (If using PostGRE, if you are using an alternative database ensure that this is online and accessible)

If they are not started then ensure the ‘startup type’ is set to Automatic and try to manually start them. If this fails then check the service accounts which these services are using. The PostGRE service, for example, uses the Local PowerRecon user account which is created as part of the installation so ensure that this account is enabled. If you are using a different service account then check that this account is enabled and that it has the ‘Run as a service’ rights within Windows and that you don’t have any group policy settings overwriting this.

Also check the Windows System event log for any service startup errors and their cause.

• Go into IIS Manager (Start / Administrative Tools / Internet Information (IIS) Manager), expand ‘Web Sites / Default Web Site / Platespin_3x’ and within the Properties page check that the ASP.NET version is set to use version 2.0.x

4.0 Summary

During the installation of Recon a local user account is created by default named ’PowerRecon’. This account is used by the PostGRE database to logon and must have the “Login as a service” user right. Recon also requires ASP.NET version 2.0 or higher. If the PostGRE service cannot start or if the ASP .NET version is set to use version 1.1 then the symptoms highlighted will occur.

Note: On the surface, these symptoms may appear to be a licensing issue as many features are greyed out. However, if it were a license issue then the License Manager option would still be present.