Hi, I'm having a problem exporting a managed package to a file.  During the export, I get these notices:

I don't want to say I'm in a hurry to correct this, but I am!  :)

Subsequently, I get this error message after hitting OK:

I've tried logging on as "admin", and also using our other administrator account and I get the same error, whether it's a 32-bit or 64-bit export.

I've never had this problem trying to export a package before.

Anyone know what I can do to get this to export properly?

Thanks,
Dan

What's the exact SEPM version?

Can you check for a sem-iu.log file?

Hi,

Thank you for posting in Symantec community.

It was a known issue in the previous release of SEP.

Latest SEP release is SEP 12.1 RU4 (12.1.4013.4013)

What's the SEPM version?

To know more about SEP release details check this link: http://bit.ly/m0vOJp

Hi Brian and Chetan, the version is 12.1.1101.401.

create a new group in SEPM

Export policies from this particular group and export it.

Check if you have full permission on 

C:\Temp ( temp Environment variables)

C:\Program Files (x86)\Symantec\Symantec Endpoint Protection Manager\tomcat\Temp folder

I remember this happening a few versions back, any chance you can upgrade?

Nope, we're on a Production version.  No chance of updating to 12.1.4013.4013.

Did you find a sem-ui.log file?

I did a search for it, and couldn't find it.

Problem with export a new "All Content" package on SEP 12.1 and the export freezes

See this thread

http://www.symantec.com/connect/forums/package-export

What's the result if you try exporting an "unmanaged" client?

If all the above method fails then Call Support get the tool to delete the packages from DB

Then manually import the packages using this document, that should fix it 

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

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

What exactly will the upgrade.bat file do?  In a production environment, I don't want everyone's SEP client to be upgraded and be rebooted otherwise I'll be in big doo-doo.

It won't affect SEP clients. It's usually run if the SEPM install/upgrade does not complete properly. I'm not even sure this applies to you in this case.

Same result as the images above.

last one, try exporting an AV only package