Endpoint Protection

 View Only
Expand all | Collapse all

Creating Client Package Error

  • 1.  Creating Client Package Error

    Posted Dec 04, 2013 05:26 PM

    After upgrading from 12.1.3 to 12.1.4 everything looked good, except the only new client packages that was automatically created was the version for the MAC.  In attempting to create a new Windows 32 and 64 bit package I did the following...

    1. From the Admin tab I selected Install Packages then Add a Client Install Package...
    2. I specificed the package name and browsed to the location of SAV32.info file located in the SEPM/Packages folder and clicked OK

    The package begain to build for about minute or two, then it gave the following error.

    Error Happened_1.jpg

    Any assistance in resolving this issue is appreciated.



  • 2.  RE: Creating Client Package Error

    Posted Dec 04, 2013 05:52 PM

    During the upgrade, did the DB properly update and did it also show that all packages were added correctly? No errors given during this stage of the upgrade?



  • 3.  RE: Creating Client Package Error

    Posted Dec 04, 2013 06:05 PM

    No errors during the upgrade, rather I received a successful message.



  • 4.  RE: Creating Client Package Error

    Posted Dec 04, 2013 06:11 PM

    In the SEPM, check the System/Administrative logs to see if they give further detail on the error message.



  • 5.  RE: Creating Client Package Error

    Posted Dec 04, 2013 11:41 PM

    Call Support they have a tool to delete the corrupt package once thats deleted you will be able to add.



  • 6.  RE: Creating Client Package Error

    Posted Dec 05, 2013 06:01 AM

    Hello,

    is there any disk space issue? If you are using a SQL DB, do you have the autogrow limited for the CONTENT file group?



  • 7.  RE: Creating Client Package Error
    Best Answer

    Posted Dec 05, 2013 03:04 PM

    I checked the admin logs on the SEPM and there were no errors present.  I also had over 5 GB of free space.

    Without making any changes to the environment I tried to create a 64 BIT package today and it was successful.  I then attempted a 32 BIT package and it worked also.  I'm not sure what was the difference today, but my issue seems to have resolved itself.

     



  • 8.  RE: Creating Client Package Error

    Posted Dec 06, 2013 07:52 AM

    I have got the same problem, but it doesn't fixed itself by trying to import the 32bit version.

    I tried to import this package with sepm version 1.12.3. After failing several times I updated sepm to version 1.12.4. The update went good but the package import failed for 32bit and 64bit in the process. I tried to import the package manually with the same error as descriped in post one. after importing the package the scm-ui log file wrote following:

    06.12.2013 12:58:00  STDOUT: CurrentPackagePanel>> valueChanged: m_curSelectedRow=0
    06.12.2013 12:58:00  STDOUT: Password safe on for domain : default
    06.12.2013 12:58:00  STDOUT: Password safe on for domain : default
    06.12.2013 12:58:00  STDOUT: A background query operation was cancelled by user.
    06.12.2013 12:58:00  STDOUT: >>> getGroupPathsMapByPackageId: [5BF3430CFDE673C1A5609D05C2A3F07D, null]  Duration: 0.038s (38.0ms)
    06.12.2013 12:58:00  STDOUT: >>> getGroupPathsMapByPackageId: [5BF3430CFDE673C1A5609D05C2A3F07D, null]  Duration: 0.037s (37.0ms)
    06.12.2013 12:58:43  STDOUT: OK clicked, validating user selected file or dir...
    06.12.2013 12:58:43  STDOUT: CreateNewSoftwareDlg>> isValidate()-> dirName D:\Symantec_CLIENTS\Source\part1\NEU\SEPM\Packages\SAV64.infois validated
    06.12.2013 12:58:43  STDOUT: Password safe on for domain : default
    06.12.2013 12:58:43  STDOUT: CreateNewPackageWorker>> doWork-> Source dir is...D:\Symantec_CLIENTS\Source\part1\NEU\SEPM\Packages\SAV64.info
    06.12.2013 12:58:43  STDOUT: CreateNewPackageWorker>> doWork-> Reading meta data...
    06.12.2013 12:58:43  STDOUT: Checking binary file integrity...file=D:\Symantec_CLIENTS\Source\part1\NEU\SEPM\Packages\SAV64.dat
    06.12.2013 12:58:43  STDOUT: Checking binary file integrity...Done
    06.12.2013 12:58:43  STDOUT: SoftwarePackageHandler>> addPackage: Begin...
    06.12.2013 12:58:43  STDOUT: Software Package Handler.isPackageExisted  newBinaryFileID>> 04D51F79BFFEF3DE733D1159688A29AC
    06.12.2013 12:58:43  STDOUT: Software Package Handler.isPackageExisted  newBinaryFileID>>       04D51F79BFFEF3DE733D1159688A29AC
    06.12.2013 12:58:43  STDOUT: Existing LUcontent array size:3
    06.12.2013 12:58:43  STDOUT: SoftwarePackageHandler>> addPhysicalFile: Begin...
    06.12.2013 12:58:43  STDOUT:     Begin to add PhysicalFile Data (remote): 04D51F79BFFEF3DE733D1159688A29AC, D:\Symantec_CLIENTS\Source\part1\NEU\SEPM\Packages\SAV64.dat
    06.12.2013 12:59:36  STDOUT: PackageWorker>> construct: Done!
    06.12.2013 12:59:36  STDOUT: Done PackageWorker!
    06.12.2013 13:04:06  STDOUT: is Export Request: false
    06.12.2013 13:04:06  STDOUT: PackageWorker>> after dlg, isAllDone=false

    Is there anyone who knows how to fix that? I need the new version asap because it fixes a huge problem with symantec and roaming profiles.



  • 9.  RE: Creating Client Package Error

    Posted Dec 06, 2013 08:40 AM

    Did you try the above solution?

    If that did not work, you can call support and they can provide you with a tool to remove any corrupt packages, allowing you to start fresh.



  • 10.  RE: Creating Client Package Error

    Posted Dec 06, 2013 08:49 AM

    As mentioned above, the "solution" to import another package did not work.

    I'm trying to call the support but until now without luck, thats why I'm asking here for help. Do you know this "tool" ?



  • 11.  RE: Creating Client Package Error

    Posted Dec 06, 2013 08:51 AM

    It's not publicly available, unfortunately. Try creating a web case, they usually send login info to download and instructions on how to use it.

    How to create a new case in MySymantec

    http://www.symantec.com/docs/TECH58873
     



  • 12.  RE: Creating Client Package Error

    Posted Dec 06, 2013 10:56 AM

    It seems the operation of importing the packages into the DB was not completed yet, hence a bit of patience was the solution for your issue :)



  • 13.  RE: Creating Client Package Error

    Posted Dec 23, 2013 08:05 AM

    Just for the record.

    I talked with the support and gave them the SEPM Logfiles and they redirected me to that article:

    http://www.symantec.com/business/support/index?page=content&id=TECH106075

     

    This solved my problem. We have 30 Revisions, but the Filegroup needed more space than 20k MB. We set it to 30k MB, now everything works again.