HI

We had our 3rd party design team make some changes to our masterpage and we are trying to create a design package to import into the other site collections. However when we try and create the package we get the following error:

in the logs we get this error

09/05/2013 09:22:33.68  w3wp.exe (0x06A8)                        0x1AA0 Web Content Management         Publishing                     ag7vj High     Design Package Export: an error occurred while exporting design 'XXXXXXXX' at web XXXXXXXX. Error: Error generating solution files in temporary directory. Stacktrace:    at Microsoft.SharePoint.SPSolutionExporter.ExportWebAsSolution()     at Microsoft.SharePoint.SPSolutionExporter.ExportWebToGallery(SPWeb web, String solutionFileName, String title, String description, ExportMode exportMode, Boolean includeContent, String workflowTemplateName, String destinationListUrl, Action`1 solutionPostProcessor, Boolean activateSolution)     at Microsoft.SharePoint.Publishing.DesignPackage.<>c__DisplayClassc.<Export>b__b()     at Microsoft.SharePoint.SPSecurity.<>c__DisplayClass5.<RunWithElevatedPrivileges>b__3()     at Microsoft.SharePoint.Utilities.SecurityContext.RunAsProcess(CodeToRunElev... 40f63f9c-c247-803d-353b-bf576c214fac

09/05/2013 09:22:33.68* w3wp.exe (0x06A8)                        0x1AA0 Web Content Management         Publishing                     ag7vj High     ...ated secureCode)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(WaitCallback secureCode, Object param)     at Microsoft.SharePoint.SPSecurity.RunWithElevatedPrivileges(CodeToRunElevated secureCode)     at Microsoft.SharePoint.Publishing.DesignPackage.Export(SPSite site, String packageName, Boolean includeSearchConfiguration)     at Microsoft.SharePoint.Publishing.Internal.CodeBehind.DesignPackageExport.<ButtonExport_Click>b__0(SPLongOperation longOperation) 40f63f9c-c247-803d-353b-bf576c214fac

They had previously made changes and created a package successfully twice before. But now it fails, we haven't made any changes to the server (apart from the last round of windows updates). Server is running Windows 2012.

thanks

Mark

Hi Mark,
According to your description, the design package cannot be created now after it was created successfully twice.

This failure is caused by corrupt permissions on the temporary directories.

Did you use the same account to create the design package?
I recommend to restore the directory permission or use another application service account which has been given the access to the temporary directory to see if the error still occurs.

Best regards.
Thanks

HI Victoria

The person trying to create the design package is the same person so yes using the same account.

I saw an article that that's the app pool account needs access to this folder, looking at effective access on the folder the app pool can create files /write data as has the user creating the package.

I've compared the permissions to our test box and they look identical so not sure if the permissions are corrupt or not.

Thanks

Hi Victoria

Continuing to look into this and I just noticed that when clicking create design package, it is trying to create the files in the c:\users\<app pool user>\AppData\Local\Temp folder, it creates two folders which then disappear.

The application pool user has full control over this folder so questioning whether it is a permissions issue.

thanks

Mark

Hi Mark,

Have you restore both the two temporary directories permission?

I recommend to restore permissions on both the two directories to see if the issue still occurs.

Best regards.

Thanks

HI Victoria

yes we have, I've also noticed that at the time we try and create the design packages we are getting the following error in the application event logs

An error occured in the blob cache.  The exception message was 'The system cannot find the file specified. (Exception from HRESULT: 0x80070002)'.

A bit of googling (or should that be binging too) suggested it could be a missing file/image referenced in the design package so we are getting that avenue checked out as well.

thank

we eventually discovered the problem, our designers had made a change to a couple of the search result page templates. once these had been sorted it worked fine.

• Marked as answer by cumbrianblues Tuesday, October 29, 2013 1:21 PM

Im having the same issu and i dont know how to fix it can u tell what kind of changes ?

HI Ahmed

The problem was because our designers had modified the search results page templates and left some hidden web parts (including a search box) that were referencing something that didn't exist. Once they had put them back to the defaults all worked fine.

thanks

Mark