Hi All,

Just a quick question. I am trying to upload the SEP 12.1.4112.4156 client package but it is failing. I am using the instructions here http://www.symantec.com/docs/TECH122824 .

I am getting the below error message. Does anyone know if there are any logs for this process to hepl me trouble shoot this. I was initially trying from a UNC path but also tried a local path for the source. Both failed.

Any assistance is appreciated.

Thanks in advance.

Error message not visible can you attach again ?

Have you try restart SEPM service and again upload ?

Your attach error message is not be visible, please upload again.

Is the error viewable now?

Message Window has the following;

- Reading the package contents...
- Adding the package into the management server...
- Disabling cancel operation as updating server database...

Are you trying to import the package?

What SEPM version?

Run the upgrade.bat

Similar error

https://www-secure.symantec.com/connect/forums/sepm-mssql-cant-import-clients-packages

Hi,

SEPM version?

Are you trying to add latest client package to old SEPM?

If yes from the download package folder you can view the new packages copy all to the SEPM install location > under Tomcat> package folder

GO to SEPM install location again under bin , run upgrade.bat will update to your db.

Hello,

Please check the below threads.

https://www-secure.symantec.com/connect/forums/how-add-client-install-package-sepm-121

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

Cannot import new packages into SEPM

https://www-secure.symantec.com/connect/forums/cannot-import-new-packages-sepm

https://www-secure.symantec.com/connect/forums/package-import

Did you verify the checksums to ensure the package is not corrupt?

Hi all thanks for your feedback. To answer a few of your questions.

The SEPM version is 12.1.4104.4130.

We are trying to upload the 12.1.4112.4156 client installs. So I believe that there is no requirement to upgrade the SEPM.

Manipillai, I will give that a try.

.Brian, good point I will check the package checksums.

You can be restart the database service and try again

How to manually import client packages into Endpoint Protection Manager (SEPM)

If it can't be work then you can call to the symantec support, they can help to add the package.

Thread similar error solution

https://www-secure.symantec.com/connect/forums/sepm-1214-failed-add-package

How to create a new case in MySupport

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

Phone numbers to contact Tech Support:-

Regional Support Telephone Numbers:

• United States: https://support.broadcom.com (407-357-7600 from outside the United States)
• Australia: 1300 365510 (+61 2 8220 7111 from outside Australia)
• United Kingdom: +44 (0) 870 606 6000

Additional contact numbers: http://www.symantec.com/business/support/contact_techsupp_static.jsp

Well we have a resolution to the problem.

We found that the packages are stored in the SQL database table. When we enabled the 'finest' logging on the console we saw the following error.
 

"Could not allocate space for object 'dbo.BINARY_FILE' in database 'sem5' because the 'FG_CONTENT' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup." 

So we reduced the number of Packages and bingo we where able to upload the new version.

Maybe a takeway for Symantec here, the error messaging could be a little more informative.