Page History

...

• If this is the first time you are installing Precise, install Precise 10.1 as described in Clean installation of the Precise Frameworkframework.
• If Precise version 10.0 is currently installed, upgrade directly to version 10.1 as described in Upgrading Precise.

...

• You must restart the Precise Focal Point after an upgrade if you are using remote instances. You also must start the SQL agents after the Focal Point restart.

• When an Oracle monitoring instance is created immediately after framework installation, errors can occur in Oracle warehouse processes located under Adminpoint > Warehouse Processes. In such cases, restart the Oracle Focal Point and PMDB focal point to resolve the problems.

• After a fresh install or upgrade, you must restart the Precise GUI service before using the Custom Portal.

• There is an issue with injdn.dll and injdn_x64.dll on Windows Server 2008 R2 with .NET monitoring. When a .NET instance is installed on Windows Server 2008 R2, a “Bad Image” error occurs. You can resolve this problem by installing the following Windows Security Update on the machine: https://technet.microsoft.com/en-us/library/security/3033929.aspx

• Some of the binaries from the Precise 10.0 installer appear as a threat under AVG antivirus. This is a false positive with AVG and does not cause any problems. You may want to whitelist when using AVG as antivirus.

• The first time you access the Precise custom portal (ASD) after a fresh Precise install or upgrade, it may fail to load. As a workaround, a one-time restart of the Precise GUI tomcat is required.
  Use the following steps as a work around: 

  1. Stop the Precise FW services

     1. On UNIX machines
        ./<precise_dir>/psin_stop_i3.sh

     2. On Windows machines
        .\<precise_dir>\infra\bin\psin_infra -multi-service stop

  2. Start the Precise FW services

     1. On UNIX machines
        ./<precise_dir>/psin_start_i3.sh

     2. On Windows machines
        .\<precise_dir>\infra\bin\psin_infra -multi-service start

  3. Clear the browser cache.

  4. Access the custom portal using url http://<hostname>:<port>/asd.

     Info
     If the issue still persists please contact Precise Support.