Symantec Endpoint Protection Integration::Failed to create package and Failed to create a command line for the package.

Article:TECH152293  |  Created: 2011-01-31  |  Updated: 2011-01-31  |  Article URL http://www.symantec.com/docs/TECH152293
Article Type
Technical Solution


Issue



Symantec Endpoint Protection Integration::Failed to create package and Failed to create a command line for the package.


Error



Symantec Endpoint Protection Integration::Failed to create a command line for the package.
( Exception Details: System.IO.IOException: Logon failure: unknown user name or bad password.

   at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access, FileShare share, Int32 bufferSize, FileOptions options, String msgPath, Boolean bFromProxy)
   at System.IO.FileStream..ctor(String path, FileMode mode)
   at Altiris.EndpointProtectionIntegration.Web.SepPackage.CreateSepPackage.GetCommandLine(String strName, String strNSPath, String strExeName, String strType) )

-------------------------------------------------------------

Symantec Endpoint Protection Integration::Failed to create package 'package name'
( Exception Details: Altiris.NS.Exceptions.AeXItemImportException: Item Import exception : 159627fc-9511-4c0d-8d19-67f7d99d1e7c = Altiris.SoftwareManagement.Resources.SoftwareReleaseResource(b6fe92fd-d5ac-4dc2-a023-a56c2973a413) ---> Altiris.NS.Exceptions.AeXException: An unexpected exception has occured in OnImport callback for Item ""Altiris.SoftwareManagement.Resources.SoftwareReleaseResource"". ---> Altiris.NS.Exceptions.AeXItemImportException: You must supply a valid installation file name in order to import components using this configuration method.  Software can also be defined manually in configuration files.
   at Altiris.SoftwareManagement.Resources.SoftwareComponentResource.OnImport(XmlNode itemNode)
   at Altiris.NS.ItemManagement.Item.Import(XmlNode itemNode)
   --- End of inner exception stack trace ---
   at Altiris.NS.ItemManagement.Item.Import(XmlNode itemNode)
   at Altiris.NS.ItemManagement.Item.ImportItem(XmlNode itemNode)
   --- End of inner exception stack trace ---
   at Altiris.NS.ItemManagement.Item.ImportItem(XmlNode itemNode)
   at Altiris.NS.ItemManagement.Item.ImportItem(String itemXml)
   at Altiris.EndpointProtectionIntegration.Web.SepPackage.CreateSepPackage.CreatePackage(String strName, String strType, String strExePath) )


Environment



Symantec Management Platform 7.0 SP5

SEP Integration Component 7.0 SP2


Cause



The SEP Integration Component uses the "SOFTWARE\Altiris\eXpress\Notification Server\", "PreferredNSHost" registry key to access the share where the SEP Client package will be placed.

Example:

\\<Value of the PreferredNSHost>\NSCap\bin\Win32\X86\Symantec Endpoint Protection\Install Package\<package name>


Solution



Make sure that the value of the "SOFTWARE\Altiris\eXpress\Notification Server\", "PreferredNSHost" registry key is present and correct.

Double check if the \\<Value of the PreferredNSHost>\NSCap\bin\Win32\X86\Symantec Endpoint Protection\Install Package\ UNC share is accessible using the Altiris Application Service account.




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


Terms of use for this information are found in Legal Notices