Forums (Obsolete)

Member

tspring-allegra - 3/29/2010 4:13:27 AM

Site Export Error

Hi

We've recently moved our Kentico CMS over to a new server (Win2008 & IIS7) everything migrated ok but I’m having trouble backing-up (i.e. exporting) sites from the new server.

During an Export the process will start but during the 'copying files' section the following error occurs and the export is terminated.

Error: “Application has been restarted and the logging of the export process has been terminated. Please make sure that the export package has been created.”

If I look into the Event log, I can see the following error messages that are happening:

EventDescription: Message: Directory rename change notification for 'C:\inetpub\wwwroot\KenticoCMS'.
KenticoCMS dir change or directory rename
HostingEnvironment initiated shutdown
HostingEnvironment caused shutdown

EventDescription: Message: IIS configuration change
HostingEnvironment initiated shutdown
HostingEnvironment caused shutdown<br />
Shutdown stack: at System.Environment.GetStackTrace(Exception e, Boolean needFileInfo)

From the errors in the Event Log, something seams to be happening to cause the application to restart during the Export process.

Is there anything obvious that could be causing this? Could it be a file caching setting, either in the CMS or IIS? I’m not sure why the main KenticoCMS folder is getting a rename change notification. I tried googling the problem, and the File Change Notifications in IIS came up a few times, but I don’t know how to change or disable this.

Thanks,
Tim

Kentico Developer

kentico_helenag - 4/1/2010 9:53:24 AM

RE:Site Export Error

Hi Tim,

I found helpful article explaning the application shut downs: http://blogs.msdn.com/tess/archive/2006/08/02/asp-net-case-study-lost-session-variables-and-appdomain-recycles.aspx.

Except for import/export you can copy the database and project folder to deploy the site. Please see here: Deployment to live server documentation

Best regards,
Helena Grulichova

Member

tspring-allegra - 4/13/2010 9:39:48 AM

RE:Site Export Error

Hi

I've still not managed to solve this backup problem.

But I have noticed an even simpler proccess that creates the same Event Log error message.

If I do the folllowing:

1. Log into a sites CMSSitemanager
2. Navigate to the Administation tab, then Event Log and clear the log file
3. Navigate to the Sites tab
4. Click the Export icon for a site, so it loads the Step 1 page
5. Then without going any further though the export process, navigate back to the Administration tab and view the Event Log

I see the same error message in the fresh log file:

Directory rename change notification for 'C:\inetpub\wwwroot\KenticoCMS'.
KenticoCMS dir change or directory rename
HostingEnvironment initiated shutdown
HostingEnvironment caused shutdown

Why does even entering the first export process (i.e. only as far a loading the Step 1 page) cause this directory notification error? ...and is there any way to stop it?

I have no virus scanner or file indexing running on the folder, so I dont know why it should be being changed/renamed.

Thanks,
Tim


Member	andrew.risbey-cubicit.co - 4/14/2010 11:09:55 AM RE:Site Export Error I am getting similar errors in the log and have had a similar issue with exporting - and only since moving to IIS7. Think this is one for Kentico to take a proper look at.

Kentico Developer

kentico_helenag - 4/16/2010 7:10:43 AM

RE:Site Export Error

Hello,

Are you using any custom files e.g. in the App_Code folder? It is possible that when trying to export/import them, .Net framework is restarting the application.

If so, please uncheck the "Export global folders" box in the selection tree (it is on the "default" screen) when exporting the site. Then you will need to transfer your custom folders manually.

Please let us know if it helps.

Best regards,
Helena Grulichova

Member

JPK - 5/5/2011 12:24:34 PM

RE:Site Export Error

The export process for sites and webparts creates and then deletes folders under /App_Data/CMSTemp/. The modification of the folder structure is what causes the restart. According to Kentico Support:

"The explanation is that our Export module first checks whether there exists any temporary folder with export data from previous exports and optionally deletes it. Deleting a folder triggers application restart even in App_Data, so we're doing this before the export itself to prevent restarting after the export. Mainly because we offer the exported package as a link after successful export."

That also explains why the restart happens at the first export process for site exports.