KNOWN ISSUE: Specific NSE files from clients are not processing. These NSE become stale and never process.

Article:TECH195347  |  Created: 2012-08-21  |  Updated: 2012-09-10  |  Article URL http://www.symantec.com/docs/TECH195347
Article Type
Technical Solution


Issue



Specific NSE files from clients are not processing. These NSE become stale and never process.

About 20 NSE files are not getting processed.  Newer NSE files will come in and get processed OK.  If we restart the NS Services, the files will process.  The same client can send in a basic inventory after the service is restarted and the new NSE from the network will often not process until we again restart the service.  We have waited for a couple days to see if these will process without any luck. 

In another scenario, periodically 3 or more NSEs would become stuck in the queue and not process for a very long time. New NSEs that come in would be processed but due to the thread pool being held by these static NSEs, it causes a clutter that leads to the excessive growth of the event queue which ends up causing performance issues and errors in the logs due to delayed replies from clients. Eventually the static NSEs will be processed with no reported errors and the queue will quickly process through the NSE backlog. However when these NSE's are 'stuck' they cause a large performance hit  on the NS environment as the NSE backlog builds up.

 

Error



Failed to process NSE invalid date. 

Must be between 1/1/1753 12:00:00 AM and 12/31/9999 11:59:59 PM

"Failed to move file from 'C:\ProgramData\Symantec\SMP\EventQueue\EvtQFast\1c4e66ba719d4895967d9e433c2885ca.nse'
to 'C:\ProgramData\Symantec\SMP\EventQueue\EvtQFast\Process\1c4e66ba719d4895967d9e433c2885ca.nse'. Exception details: System.IO.IOException: The process cannot access the file because it is being used by another process.
   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.File.Move(String sourceFileName, String destFileName)
   at Altiris.NS.EventRouter.MoveFile(String source, String destination, Int32 severity)","MoveFile","AeXSvc","559"


Environment



Symantec Management Platform 7.1 SP2, 7.1 SP2 Rollup v4


Cause



Known Issue


Solution



 

 This issue has been reported to the Symantec Development Team. A permanent fix will be provided in a later release (possibly SMP 7.5).

There is a pointfix for this issue available. There is a SMP 7.1 SP2 version, as well a SMP 7.1 SP2 Rollup v4 (HOWTO64113).

Pointfix for SMP 7.1 SP2 is called “Pointfix_eTrack2890116_SP2.zip“
Pointfix file for SMP 7.1 SP2 Rollup v4 is called “Pointfix_eTrack2890116_SP2v4.zip“

HOW TO INSTALL THIS POINTFIX: 

1.     Extract files from the pointfix zip archive to the SMP hard drive. Make sure PointFix is not extracted to Altiris install directory (or any subfolder to it).

2.     Execute PFInstaller.exe with administrative privileges (right-click > Run as administrator).

3.     Accept UAC (User Account Control) prompt, select Install Files.

4.     Old binaries will be automatically backuped to the same location where PFinstaller is and replaced with the new ones.

 

This hotfix has the following known issues:

None.

 

HOW TO UNINSTALL: 

1.    Make sure that Backup subfolder is located in PFinstaller’ directory.

2.    Execute PFInstaller.exe with administrative privileges (right-click > Run as administrator).

3.    Accept UAC (User Account Control) prompt, select Uninstall Files.


Attachments

Apply this version of the pointfix if only SP2 is installed without any pointfixes.
Pointfix_eTrack2890116_7_1_SP2.zip (1.3 MBytes)
Apply this version of the pointfix if SMP 7.1 SP2 Rollup v4 is installed. - Updated
Pointfix_eTrack2890116_7_1_SP2v4.zip (1.4 MBytes)




Supplemental Materials

SourceETrack
Value2799261


Article URL http://www.symantec.com/docs/TECH195347


Terms of use for this information are found in Legal Notices