Endpoint Protection

 View Only
Back to discussions
Expand all | Collapse all

Can't Export Client Packages in SEPM 11.0.6200.754

Migration User

Migration UserFeb 27, 2011 11:26 AM

 See attached log.
ℬrίαη

ℬrίαηFeb 27, 2011 01:02 PM

Please mark the post solved that helped you.

  • 1.  Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 26, 2011 12:45 PM

    I just migrated all of our content from one server to another using the documentation. That all went very well and everything was brought over successfully. I then upgraded from SEPM 11.0.4 to 11.0.6. I'm experiencing a few issues.

     

    The first and most important is I'm unable to export client packages. I receive the following error: "Error Happened" In the messages box is indicating it was preparing, then creating the export folder. It got to Retrieving the package data from server and stopped.

     

    The other issue I'm having while not as important at the moment will still be significantly important is the home, reports and Monitors screens aren't showing any content. The titles for each section is there, but no data. I thought it was a permissions issues but I put everyone FULL temporarily and tried it again and it still doesn't work.

     

    Any help would be greatly appreciated. Thanks in advance.



  • 2.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 26, 2011 01:09 PM

    Did you upgrade directly from 11.0.4 to 11.0.6200?



  • 3.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 26, 2011 09:48 PM

    run the upgrade.bat file again, seems like that packages are not added properly.if that does not work, do a repair from add/remove programs, once it puts the package you should be able to export without any problem...



  • 4.  RE: Can't Export Client Packages in SEPM 11.0.6200.754
    Best Answer

    Broadcom Employee
    Posted Feb 26, 2011 11:00 PM

    repair the SEPM, the SEPm package should be having the client packages while upgrading.



  • 5.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 27, 2011 08:52 AM

    Sorry for the late response, I subscribed but didn't get a nostice of replies. 

    I did upgrade directly from .4 to .6.

    I think I ran the upgrade.bat file again but I'll try once more. If that doesn't work I'll do a repair through add/remove programs as suggested. I'll post my results here. Thanks.



  • 6.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 27, 2011 09:14 AM

    It didn't work. I tried the upgrade.bat again and I tried the repair through add/remove programs. Both issues stille exist. 

    Where should the packages folder exist? Can I just manually copy the directory to it's location/



  • 7.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Broadcom Employee
    Posted Feb 27, 2011 10:23 AM

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

     

    could be helpful.



  • 8.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 27, 2011 10:38 AM

    When I attempted to follow those instructions it says the Package Already Exists and wont' let me add it. When I attempt to delete it so I can add it again it says I can't delete it. Below is a screenshot of the error I'm receiving while attempting to export the package.

     



  • 9.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Broadcom Employee
    Posted Feb 27, 2011 10:47 AM

    my apologies, are you not able to export the package?

    can you post the scm-server-0.log from the tomcat\logs folder of SEPM after you attempt to export the package?



  • 10.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 27, 2011 10:48 AM

    Another update. I went to the old installation that I migrated everything from as indicated in my original post. I copied the old packages folder over to the new server and created an install package from it. As a test I attempted to export it as well. Again the same error as before. So even a newly created package wouldn't export.



  • 11.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 27, 2011 10:53 AM

    Contents of log:

     

    2011-02-27 10:29:00.212 SEVERE: ================== Server Environment ===================
    2011-02-27 10:29:00.213 SEVERE: os.name = Windows Server 2008
    2011-02-27 10:29:00.214 SEVERE: os.version = 6.0
    2011-02-27 10:29:00.214 SEVERE: os.arch = x86
    2011-02-27 10:29:00.214 SEVERE: java.version = 1.6.0_14
    2011-02-27 10:29:00.215 SEVERE: java.vendor = Sun Microsystems Inc.
    2011-02-27 10:29:00.215 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2011-02-27 10:29:00.215 SEVERE: java.vm.version = 14.0-b16
    2011-02-27 10:29:00.238 SEVERE: java.home = D:\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2011-02-27 10:29:00.240 SEVERE: catalina.home = D:\Symantec\Symantec Endpoint Protection Manager\tomcat
    2011-02-27 10:29:00.240 SEVERE: java.user = null
    2011-02-27 10:29:00.240 SEVERE: user.language = en
    2011-02-27 10:29:00.240 SEVERE: user.country = US
    2011-02-27 10:29:00.241 SEVERE: scm.server.version = 11.0.6200.754
    2011-02-27 10:29:03.181 SEVERE: ================== StartClientTransport ===================
    2011-02-27 10:29:03.629 SEVERE: Schedule is started!


  • 12.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Broadcom Employee
    Posted Feb 27, 2011 11:03 AM

    the error has not been captured, please enable the logging to fine. Once enabled by following the URL , try exporting once again and then post the content of the scm-server-0.log

     

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



  • 13.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 27, 2011 11:07 AM

    Here is the output after following the instructions in the URL:

     

    2011-02-27 11:01:26.447 SEVERE: ================== Server Environment ===================
    2011-02-27 11:01:26.447 SEVERE: os.name = Windows Server 2008
    2011-02-27 11:01:26.462 SEVERE: os.version = 6.0
    2011-02-27 11:01:26.462 SEVERE: os.arch = x86
    2011-02-27 11:01:26.462 SEVERE: java.version = 1.6.0_14
    2011-02-27 11:01:26.462 SEVERE: java.vendor = Sun Microsystems Inc.
    2011-02-27 11:01:26.462 SEVERE: java.vm.name = Java HotSpot(TM) Server VM
    2011-02-27 11:01:26.462 SEVERE: java.vm.version = 14.0-b16
    2011-02-27 11:01:26.462 SEVERE: java.home = D:\Symantec\Symantec Endpoint Protection Manager\jdk\jre
    2011-02-27 11:01:26.462 SEVERE: catalina.home = D:\Symantec\Symantec Endpoint Protection Manager\tomcat
    2011-02-27 11:01:26.462 SEVERE: java.user = null
    2011-02-27 11:01:26.462 SEVERE: user.language = en
    2011-02-27 11:01:26.462 SEVERE: user.country = US
    2011-02-27 11:01:26.462 SEVERE: scm.server.version = 11.0.6200.754
    2011-02-27 11:01:26.493 INFO: Server startup
    2011-02-27 11:01:26.572 INFO: Server side cache PERCETAGE_OF_TOTAL_MEMORY=0.3  PERCETAGE_OF_MEMORY_TO_REMOVE=0.2
    2011-02-27 11:01:27.947 FINE: updProcessState: checking...
    2011-02-27 11:01:27.978 FINE: updProcessState: The process status has been checked.
    2011-02-27 11:01:27.978 FINE: updProcessState: checking...
    2011-02-27 11:01:27.993 FINE: updProcessState: The process status has been checked.
    2011-02-27 11:01:28.884 INFO: use transport url:http://localhost:8014/secars/secars.dll
    2011-02-27 11:01:28.884 SEVERE: ================== StartClientTransport ===================
    2011-02-27 11:01:29.384 FINE: Task scheduled
    2011-02-27 11:01:29.384 SEVERE: Schedule is started!
    2011-02-27 11:01:33.197 WARNING: Log property file does not exist.
    2011-02-27 11:01:33.884 FINE: Test db connection successfully.
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {ECCC5006-EF61-4c99-829A-417B6C6AD963}, sequenceNum= 2008021700
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {EA960B33-2196-4d53-8AC4-D5043A5B6F9B}, sequenceNum= 80820001
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {E5A3EBEE-D580-421e-86DF-54C0B3739522}, sequenceNum= 110225008
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {E5A3EBEE-D580-421e-86DF-54C0B3739522}, sequenceNum= 110224017
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {E5A3EBEE-D580-421e-86DF-54C0B3739522}, sequenceNum= 110223006
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {E1A6B4FF-6873-4200-B6F6-04C13BF38CF3}, sequenceNum= 110225008
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {E1A6B4FF-6873-4200-B6F6-04C13BF38CF3}, sequenceNum= 110224017
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {E1A6B4FF-6873-4200-B6F6-04C13BF38CF3}, sequenceNum= 110223006
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {DB206823-FFD2-440a-9B89-CCFD45F3F1CD}, sequenceNum= 80820001
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {D3769926-05B7-4ad1-9DCF-23051EEE78E3}, sequenceNum= 110225001
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {D3769926-05B7-4ad1-9DCF-23051EEE78E3}, sequenceNum= 110224001
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {D3769926-05B7-4ad1-9DCF-23051EEE78E3}, sequenceNum= 110223001
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {CC40C428-1830-44ef-B8B2-920A0B761793}, sequenceNum= 110225008
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {CC40C428-1830-44ef-B8B2-920A0B761793}, sequenceNum= 110224017
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {CC40C428-1830-44ef-B8B2-920A0B761793}, sequenceNum= 110223006
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 110226003
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 110225018
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C60DC234-65F9-4674-94AE-62158EFCA433}, sequenceNum= 110225003
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C25CEA47-63E5-447b-8D95-C79CAE13FF79}, sequenceNum= 80929016
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {C13726A9-8DF7-4583-9B39-105B7EBD55E2}, sequenceNum= 80820001
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {812CD25E-1049-4086-9DDD-A4FAE649FBDF}, sequenceNum= 110225008
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {812CD25E-1049-4086-9DDD-A4FAE649FBDF}, sequenceNum= 110224017
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {812CD25E-1049-4086-9DDD-A4FAE649FBDF}, sequenceNum= 110223006
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {4F889C4A-784D-40de-8539-6A29BAA43139}, sequenceNum= 101201096
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {4F889C4A-784D-40de-8539-6A29BAA43139}, sequenceNum= 91111048
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {4F889C4A-784D-40de-8539-6A29BAA43139}, sequenceNum= 91104048
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {42B17E5E-4E9D-4157-88CB-966FB4985928}, sequenceNum= 110226001
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {42B17E5E-4E9D-4157-88CB-966FB4985928}, sequenceNum= 110224001
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {42B17E5E-4E9D-4157-88CB-966FB4985928}, sequenceNum= 110223001
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 110226003
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 110225018
    2011-02-27 11:01:35.732 FINE: >> cleanupLuDownloadedContent: Keeping this content revision, clientMoniker= {1CD85198-26C6-4bac-8C72-5D34B025DE35}, sequenceNum= 110225003
    2011-02-27 11:01:43.279 FINE: Test db connection successfully.
    2011-02-27 11:01:43.435 INFO: LoginHandler->doLogin: version from database: 11.0.6.2
    2011-02-27 11:01:43.435 INFO: LoginHandler->doLogin: version from server: 11.0.6.2
    2011-02-27 11:01:43.435 INFO: LoginHandler->doLogin: version from template: 11.0.6.2
    2011-02-27 11:01:43.685 FINE: GetScmPropertiesHandler>> read scm properties from server: Done!
    2011-02-27 11:01:43.779 FINE: >>> GetObjectHandler: SemSite  D6840F06C0A801ED005E07B62D2D3D0D  1298822503779, duration: 0.015s (15.0)
    2011-02-27 11:01:43.873 FINE: >>> GetObjectHandler: SemConfigRoot  null  1298822503873, duration: 0.031s (31.0)
    2011-02-27 11:01:44.076 FINE: >>> GetObjectHandler: SemDomain  C1D6BA96C0A8010301AA167AF6C0CAAC  1298822504076, duration: 0.016s (16.0)
    2011-02-27 11:01:49.742 INFO: LoginHandler->doLogin: version from database: 11.0.6.2
    2011-02-27 11:01:49.742 INFO: LoginHandler->doLogin: version from server: 11.0.6.2
    2011-02-27 11:01:49.744 INFO: LoginHandler->doLogin: version from template: 11.0.6.2
    2011-02-27 11:01:53.276 FINE: Test db connection successfully.
    2011-02-27 11:01:54.340 FINE: >>> GetObjectHandler: LuDownloadedContentArray  6028C6E625754ECE4312D41CB963A039  1298822514340, duration: 0.01s (10.0)
    2011-02-27 11:01:54.626 FINE: >>> GetObjectHandler: SoftwarePackage  7A80D187F6EBF3B41E38D479BCBCC54A  1298822514626, duration: 0.011s (11.0)
    2011-02-27 11:01:54.771 FINE: >>> GetObjectHandler: SoftwarePackage  4209DCACED66213A52DB822FCD5D1C80  1298822514771, duration: 0.0080s (8.0)
    2011-02-27 11:01:54.867 FINE: >>> GetObjectHandler: SoftwarePackage  A11366A282A1CF210184BCB70538C85C  1298822514867, duration: 0.0050s (5.0)
    2011-02-27 11:01:54.955 FINE: >>> GetObjectHandler: SoftwarePackage  609D6B082D0AD1F060CD933BF2F6B77F  1298822514955, duration: 0.0060s (6.0)
    2011-02-27 11:01:55.317 FINE: >>> GetObjectHandler: SoftwarePackage  10DA470E1403BC65E1E2D21123CCE012  1298822515317, duration: 0.0070s (7.0)
    2011-02-27 11:01:55.408 FINE: >>> GetObjectHandler: SoftwarePackage  C54BC5064950603E696DA2E535B11ACB  1298822515408, duration: 0.0070s (7.0)
    2011-02-27 11:01:55.445 FINE: >>> GetObjectHandler: PhysicalFile  F94B0E2AC3B299FC281DB020B405D50E  1298822515445, duration: 0.0080s (8.0)
    2011-02-27 11:01:55.680 FINE: >>> GetObjectHandler: SoftwarePackage  8548C703048A939CAECFDB9C4C030E85  1298822515680, duration: 0.0060s (6.0)
    2011-02-27 11:01:55.717 FINE: >>> GetObjectHandler: PhysicalFile  CA94C6D35434FC8627D6DD0D55240584  1298822515717, duration: 0.0090s (9.0)
    2011-02-27 11:01:55.858 FINE: >>> GetObjectHandler: SoftwarePackage  410307F75CCEDCEDBB0C0BB5E77F3EEC  1298822515857, duration: 0.0060s (6.0)
    2011-02-27 11:01:55.892 FINE: >>> GetObjectHandler: PhysicalFile  BB68A58F248D6031C6EA6AE7381FD0EF  1298822515892, duration: 0.0080s (8.0)
    2011-02-27 11:01:56.350 FINE: >>> GetObjectHandler: SoftwarePackage  8D5F1CA44E2184F8698AF5442E6D06B1  1298822516350, duration: 0.0060s (6.0)
    2011-02-27 11:01:56.858 FINE: >>> GetGroupPathsByPackageIdHandler: [C54BC5064950603E696DA2E535B11ACB, null]  1298822516858, duration: 0.458s (458.0)
    2011-02-27 11:01:59.915 FINE: >>> GetObjectHandler: ClientInstallationSettings  1750BAB9C0A8010300F0CD6D8DDCBC3E  1298822519915, duration: 0.013s (13.0)
    2011-02-27 11:02:00.059 FINE: >>> GetObjectHandler: ClientInstallationSettings  AD922C13C0A8010301AD4242C85A5F65  1298822520059, duration: 0.03s (30.0)
    2011-02-27 11:02:00.569 FINE: >>> GetObjectHandler: ClientInstallationSettings  FBF9ECEEC0A8010300F9C26E40C70CA3  1298822520569, duration: 0.112s (112.0)
    2011-02-27 11:02:00.617 FINE: >>> GetObjectHandler: ClientInstallationSettings  44964ED0C0A801ED01EDA4016848808B  1298822520617, duration: 0.015s (15.0)
    2011-02-27 11:02:00.665 FINE: >>> GetObjectHandler: ClientInstallationFeatures  E8975108C0A8010300BB51F05A0A0A64  1298822520665, duration: 0.016s (16.0)
    2011-02-27 11:02:00.741 FINE: >>> GetObjectHandler: ClientInstallationFeatures  2C2BEEF7C0A8010301CED32DAD0EEAAF  1298822520741, duration: 0.037s (37.0)
    2011-02-27 11:02:00.791 FINE: >>> GetObjectHandler: ClientInstallationFeatures  7A6602D1C0A801030123113E170D677E  1298822520791, duration: 0.02s (20.0)
    2011-02-27 11:02:00.832 FINE: >>> GetObjectHandler: ClientInstallationFeatures  BCBC2C0DC0A8010301C4C85252522CC4  1298822520832, duration: 0.013s (13.0)
    2011-02-27 11:02:00.875 FINE: >>> GetObjectHandler: ClientInstallationFeatures  0D585274C0A8010300F9C26EF62900F0  1298822520875, duration: 0.015s (15.0)
    2011-02-27 11:02:00.929 FINE: >>> GetObjectHandler: SemClientGroupTree  8489C3C9C0A8010301852AFC74B4C7E0  1298822520928, duration: 0.0050s (5.0)
    2011-02-27 11:02:03.499 FINE: Test db connection successfully.
    2011-02-27 11:02:13.410 FINE: Test db connection successfully.
    2011-02-27 11:02:23.414 FINE: Test db connection successfully.
    2011-02-27 11:02:33.413 FINE: Test db connection successfully.
    2011-02-27 11:02:43.540 FINE: Test db connection successfully.
    2011-02-27 11:02:49.725 INFO: LoginHandler->doLogin: version from database: 11.0.6.2
    2011-02-27 11:02:49.725 INFO: LoginHandler->doLogin: version from server: 11.0.6.2
    2011-02-27 11:02:49.727 INFO: LoginHandler->doLogin: version from template: 11.0.6.2


  • 14.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Broadcom Employee
    Posted Feb 27, 2011 11:16 AM

    :-(, again, I could not get the error message from logs. I'm sorry, can you post the screen capture of the error message,please?



  • 15.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 27, 2011 11:18 AM

    The error message is in my post above. I'll enable the logging and try again.



  • 16.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 27, 2011 11:26 AM
      |   view attached

    See attached log.

    Attachment(s)

    txt
    err.txt   2.87 MB 1 version


  • 17.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 27, 2011 11:29 AM

    Remove IIS from the add/remove program, close the add/remove box, then re-install the IIS,

    Then run the reconfiguration wizard.

    if you are still unable to export the package, you may need to import them from the DVD source. Delete the current packages, and from the admin segment where you want to export the packages, you can find the import packages. Follow the instruction and check if it solves the issue.



  • 18.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 27, 2011 11:34 AM

    This is server 2008, it's a role, you don't remove it through add/remove programs.

    I can remove the role and run the wizard and try again.

    However, as to your information at the bottom of your post. I can't delete the packages. If I attempt it tells me I can't because they are the latest. And when I attempt to just add another package it tells me that package already exists. 



  • 19.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 27, 2011 12:56 PM

    Update, it's all working. I removed IIS, and SEPM and reinstalled it all. Everything seems to be fine, it even kept all of my database information. Thank you for all the assistance.



  • 20.  RE: Can't Export Client Packages in SEPM 11.0.6200.754

    Posted Feb 27, 2011 01:02 PM

    Please mark the post solved that helped you.