Normally deleting the app data TEMP folder is no problem and we do it a lot when copying websites to reset all temp files. Normally the TEMP folder will just recreate itself.
Now I deleted the folder in Umbraco 4.8.0.0 and when trying to publish any page recieved the following error. Does that mean that we can/should no longer delete the TEMP folder?
Could not find a part of the path 'D:\inetpub\wwwroot\planday.dk\www\App_Data\TEMP\ExamineIndexes\Internal\Index\'.
Description:An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.
Exception Details:System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\inetpub\wwwroot\planday.dk\www\App_Data\TEMP\ExamineIndexes\Internal\Index\'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Deleted App_Data\TEMP folder - Made Publish crash
Hi Guys,
Normally deleting the app data TEMP folder is no problem and we do it a lot when copying websites to reset all temp files. Normally the TEMP folder will just recreate itself.
Now I deleted the folder in Umbraco 4.8.0.0 and when trying to publish any page recieved the following error. Does that mean that we can/should no longer delete the TEMP folder?
Could not find a part of the path 'D:\inetpub\wwwroot\planday.dk\www\App_Data\TEMP\ExamineIndexes\Internal\Index\'.
Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.IO.DirectoryNotFoundException: Could not find a part of the path 'D:\inetpub\wwwroot\planday.dk\www\App_Data\TEMP\ExamineIndexes\Internal\Index\'.
Source Error:
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.272
Thanks
/Rune
Hey Rune,
Came accross this issue myself, I simply recycled the application pool of the website in IIS.
Then republished one page to get the indexs to regenerate, off the back of the publish event.
Thanks,
Will
is working on a reply...