Video Screencast Help
Search Video Help Close Back
to help
New in the Rewards Catalog: Vouchers for "Symantec Technical Specialist" and "Symantec Certified Specialist" exams.

Error Exporting Installer Package

Updated: 21 May 2010 | 12 comments
FisherJ's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

 I have recently installed Endpoint Protection on my network.  Everything has worked fine with the exception of creating 32bit Installer Packages. When I try to export the Client Install Package it errors out with the following error:

"The Symantec client software package does not exist in the source folder that you have entered; type a valid source folder."

Endpoint Error.jpg
Endpoint Error.jpg

I have successfully created and deployed 64bit packages but cannot export the 32bit packages.  I am new to using Endpoint and am trying to find a solution to this problem without uninstalling. Any help is appreciated.

Comments

Prachand's picture
26
Nov
2009
0 Votes 0
Login to vote

Please run a repair for SEPM

Please run a repair for SEPM and then try to install/create  the pacakge

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

FisherJ's picture
26
Nov
2009
0 Votes 0
Login to vote

 I ran a repair earlier but

 I ran a repair earlier to see if it would fix the issue but to no avail. I still receive the same error message.

Prachand's picture
26
Nov
2009
0 Votes 0
Login to vote

Try to add the package

Try to add the package manually

How to import install packages manually into the Endpoint Protection Manager:

Select SAV32.info and click the Select button

Log into the SEPM

Click Admin

Click Install Packages

Click Add Client Install Package... under Tasks

Name the package and click the Browse... button

Navigate to CD1\SEPM\PACKAGES\ in the directory where the MR2 installation is located

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

Vikram Kumar-SAV to SEP's picture
26
Nov
2009
0 Votes 0
Login to vote

Make sure program

Make sure program files\Symantec...manager folder has permission Authenticated users and System ( full access )..and replace permission on child obejects.. 

FisherJ's picture
26
Nov
2009
0 Votes 0
Login to vote

 When I try and create

 When I try and create another package it errors out saying that the package already exists.  So I am unable to create a new package.

As for the permissions I did as you said and it still gives me the same error when trying to export.

Prachand's picture
27
Nov
2009
0 Votes 0
Login to vote

Try to see if you can create

Try to see if you can create the package through the migration and deployment wizard

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

FisherJ's picture
27
Nov
2009
0 Votes 0
Login to vote

 When I try and create an

 When I try and create an Install Package through the Migration Wizard I get the following error:

Failed to create a 32-bit package for "Group Name"
Error code: 7


Vikram Kumar-SAV to SEP's picture
27
Nov
2009
0 Votes 0
Login to vote

Run Dbvalidator and check if

Run Dbvalidator and check if Database is still working or has gone corrupt.

in SEPm create a new group--go to Details and check if you see the Group ID for it.. and the same folder being created in
program files\symantec...manager\data\outbox\agent

if no then it means Database has become corrupt. 

Prachand's picture
27
Nov
2009
0 Votes 0
Login to vote

There as a same issue in

There as a same issue in SEP MR2 and that  was fixed in SEP MR2MP2 , There is  a possiblity that the databse is corrupt.

If you have not deplyoed many client in the network , then just uinstall and reinstall the SEPM and see if that works

Prachand Kumar MCSE-2003 Symantec Technical Specialist (SCTS)

FisherJ's picture
27
Nov
2009
0 Votes 0
Login to vote

 Database validation passed

 Database validation passed and I tested creating a group to see if it created the associated file and it did that as well.

I guess I will try and re-install SEPM to see if that solves the issue. Thanks for all of the help guys.

FisherJ's picture
27
Nov
2009
0 Votes 0
Login to vote

 Re-installed and received

 Re-installed and received the same error. I am now thinking it is my media that is corrupt. Re-downloading and am going to try it again.

FisherJ's picture
27
Nov
2009
0 Votes 0
Login to vote

That was the fix. My first

That was the fix. My first download must have been corrupt which was causing the error. I re-downloaded SEP and re-installed and everything worked this time.

Again thanks for everyones help on trying to figure this out.