Submit a ticketCall us

Don’t fall victim to a ransomware attack
Backups are helpful, but sometimes that’s not enough to protect your business against ransomware. At our live webcast we will discuss how to protect against ransomware attacks with SolarWinds® Patch Manager and how to leverage log data to detect ransomware. Register now for our live webcast.

Home > Success Center > Network Performance Monitor (NPM) > NPM 10.7 HotFix 1- Polling Issues due to Daylight Saving Time

NPM 10.7 HotFix 1- Polling Issues due to Daylight Saving Time

Table of contents
Created by Tiarnan Stacke, last modified by MindTouch on Jun 23, 2016

Views: 8 Votes: 0 Revisions: 4

Overview

This HotFix addresses an issue where polling stops before the shift to the daylight saving time due to the effects of the time change on scheduled polling jobs.

 

Environment

NPM version 10.7

Steps

SolarWinds NCM 7.2.x, NPM 10.7, SAM 6.1 HotFix 1
------------------------------------------------------------

This HotFix addresses an issue where polling stops before the shift to the daylight saving time due to the effects of the time change on scheduled polling jobs.

To determine if you are experiencing this issue, review the JobEngine.v2 log.

Notes:

  •  The default location of this file on Windows Server 2008 and 2012 is C:\ProgramData\Solarwinds\JobEngine.v2\Logs\.
  • The default location of this file on Windows Server 2003 is C:\Documents and Settings\All Users\Application Data\SolarWinds\JobEngine.v2\Logs\.

 

The error message indicating this issue is similar to the following:
The supplied DateTime represents an invalid time. For example, when the clock is adjusted forward, any time in the period that is skipped is invalid.

 

This issue may occur if you are running any of the following SolarWinds products:

  •  SolarWinds NCM 7.2.X (standalone, or together with any other modules, including NPM 10.6)
  •  NPM 10.7
  •  SAM 6.1

 

Notes:

  • If you are running a combination of the products listed above, install only one of the provided HotFix versions. It is not important which HotFix version you choose to install.
  • Install this HotFix even if you experience no problems to prevent the issue from occurring.
  • This HotFix must be installed on the main poller and on all additional pollers.
  • This HotFix contains the file JobEngine.v2.msi with JobEngine version 2.7.31.

 


To install this hotfix:
1. Log on as an administrator to the SolarWinds server hosting your Orion installation.

2. Using the Orion Service Manager, stop all SolarWinds services, as follows:
   a. Start the Orion Service Manager in your SolarWinds Orion program folder (SolarWinds Orion > Advanced Features >        Orion Service Manager).
   b. Click Shutdown Everything.

3. Rename the existing version of the JobEngine (JobEngine.v2.msi) to JobEngine.v2.msi.old.
Notes:

  • The default location of this file on Windows Server 2008 and 2012 is %ProgramData%\Solarwinds\Installers\.
  • The default location of this file on Windows Server 2003 is c:\Documents and Settings\All Users\Application Data\Solarwinds\Installers\.

4. Extract the file from this Hotfix (JobEngine.v2.msi) into the Installers folder.

Notes:

  • The default location of this folder on Windows Server 2008 and 2012 is %ProgramData%\Solarwinds\Installers\.
  • The default location of this folder on Windows Server 2003 is c:\Documents and Settings\All Users\Application Data\Solarwinds\Installers\.

5. Run the JobEngine installation from JobEngine.v2.msi.
6. In the Orion Service Manager, click Start Everything.

 


To uninstall this hotfix:

1. Log on as an administrator to the SolarWinds server hosting your Orion installation.

2. Using the Orion Service Manager, stop all SolarWinds services as follows:
   a. Start the Orion Service Manager in your SolarWinds Orion program folder (SolarWinds Orion > Advanced Features >        Orion Service Manager).
   b. Click Shutdown Everything.

3. Using Add or Remove Programs, uninstall the product SolarWinds Job Engine v2.7.31.

3. Delete JobEngine.v2.msi from the Installers folder. JobEngine.v2.msi.old.

Notes:

  • The default location of this file on Windows Server 2008 and 2012 is %ProgramData%\Solarwinds\Installers\.
  • The default location of this file on Windows Server 2003 is c:\Documents and Settings\All Users\Application Data\Solarwinds\Installers\.

4. Rename the JobEngine backup (JobEngine.v2.msi.old) as JobEngine.v2.msi.
Notes:

  • The default location of this file on Windows Server 2008 and 2012 is %ProgramData%\Solarwinds\Installers\.
  • The default location of this file on Windows Server 2003 is c:\Documents and Settings\All Users\Application Data\Solarwinds\Installers\.

5. Run the JobEngine installation from JobEngine.v2.msi.
6. Make a copy of JobEngine35 - Blank.sdf, and then rename it as JobEngine35.sdf.

Notes:

  • The default location of this file on Windows Server 2008 and 2012 is C:\ProgramData\SolarWinds\JobEngine.v2\Data\.
  • The default location of this file on Windows Server 2003 is C:\Documents and Settings\All Users\Application Data\SolarWinds\JobEngine.v2\Data\.

7. Right-click JobEngine35.sdf, as renamed in the previous step, click Properties, and then clear the Read-only option.

8. In the Orion Service Manager, click Start Everything.

 

 

 

Last modified
22:53, 22 Jun 2016

Tags

Classifications

Public