Directory not Empty error when bulk uploading for Runway Gallery
Hi
I have a site I have been deveoping for a while and I decided I want to do a direct comparison between Runway Gallery and another Gallery Control for asp.net.
So I aded a new Gallery into the content and tried to bulk upload a zip file containing the same photos that I am using in the other asp site. The first problem that I ran into was that if I had more then 24 photographs in the .zip file I was trying to up load I got this error:
Server Error in '/' Application.
Maximum request length exceeded.
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.Web.HttpException: Maximum request length exceeded.
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.
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
With 24 or less photos the file uploaded OK when I clik=cked the save icon and I got a Content Saved Message. BUT, when I tried to Publish the page I get this error:
Server Error in '/' Application.
The directory is not empty.
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.IOException: The directory is not empty.
Source Error:
The source code that generated this unhandled exception can only be
shown when compiled in debug mode. To enable this, please follow one of
the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
Note that this second technique will cause all files within a given
application to be compiled in debug mode. The first technique will cause
only that particular file to be compiled in debug mode.
Important:
Running applications in debug mode does incur a memory/performance
overhead. You should make sure that an application has debugging
disabled before deploying into production scenario.
Wrote a little batch file so that I can use it for any site. Works a treat. Or at least it doesn't error when I upload the file!
Now when I attempt to publish the page I get the following if I just click 'Save and Publish":
Server Error in '/' Application.
Could not find file 'C:\UmbracoSites\JRBP1\media\7318\knowsley.zip'.
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.FileNotFoundException: Could not find file 'C:\UmbracoSites\JRBP1\media\7318\knowsley.zip'.
Source Error:
The source code that generated this unhandled exception can only be
shown when compiled in debug mode. To enable this, please follow one of
the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
Note that this second technique will cause all files within a given
application to be compiled in debug mode. The first technique will cause
only that particular file to be compiled in debug mode.
Important:
Running applications in debug mode does incur a memory/performance
overhead. You should make sure that an application has debugging
disabled before deploying into production scenario.
Stack Trace:
And this if I RightClick on the page node and select publish:
Server Error in '/' Application.
Could not find file 'C:\UmbracoSites\JRBP1\media\7318\knowsley.zip'.
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.FileNotFoundException: Could not find file 'C:\UmbracoSites\JRBP1\media\7318\knowsley.zip'.
Source Error:
The source code that generated this unhandled exception can only be
shown when compiled in debug mode. To enable this, please follow one of
the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
Note that this second technique will cause all files within a given
application to be compiled in debug mode. The first technique will cause
only that particular file to be compiled in debug mode.
Important:
Running applications in debug mode does incur a memory/performance
overhead. You should make sure that an application has debugging
disabled before deploying into production scenario.
If I upload a smaller file I still get my original error rather than "Could not find file":
Server Error in '/' Application.
The directory is not empty.
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.IOException: The directory is not empty.
Source Error:
The source code that generated this unhandled exception can only be
shown when compiled in debug mode. To enable this, please follow one of
the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
Note that this second technique will cause all files within a given
application to be compiled in debug mode. The first technique will cause
only that particular file to be compiled in debug mode.
Important:
Running applications in debug mode does incur a memory/performance
overhead. You should make sure that an application has debugging
disabled before deploying into production scenario.
Directory not Empty error when bulk uploading for Runway Gallery
Hi
I have a site I have been deveoping for a while and I decided I want to do a direct comparison between Runway Gallery and another Gallery Control for asp.net.
So I aded a new Gallery into the content and tried to bulk upload a zip file containing the same photos that I am using in the other asp site. The first problem that I ran into was that if I had more then 24 photographs in the .zip file I was trying to up load I got this error:
Server Error in '/' Application.
Maximum request length exceeded.
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.Web.HttpException: Maximum request length exceeded.
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.1
With 24 or less photos the file uploaded OK when I clik=cked the save icon and I got a Content Saved Message. BUT, when I tried to Publish the page I get this error:
Server Error in '/' Application.
The directory is not empty.
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.IOException: The directory is not empty.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
Help please!
Hi,
Your first error is because the page is timing out as it's taking a while to upload all the pics, you can increase the timeout to solve this by reading this thread http://our.umbraco.org/forum/using/ui-questions/7441-Another-uploading-large-files-and-zip-files-issue
Don't know about the second error, sorry.
Rich
Thanks Rich
Wrote a little batch file so that I can use it for any site. Works a treat. Or at least it doesn't error when I upload the file!
Now when I attempt to publish the page I get the following if I just click 'Save and Publish":
Server Error in '/' Application.
Could not find file 'C:\UmbracoSites\JRBP1\media\7318\knowsley.zip'.
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.FileNotFoundException: Could not find file 'C:\UmbracoSites\JRBP1\media\7318\knowsley.zip'.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
Stack Trace:
And this if I RightClick on the page node and select publish:
Server Error in '/' Application.
Could not find file 'C:\UmbracoSites\JRBP1\media\7318\knowsley.zip'.
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.FileNotFoundException: Could not find file 'C:\UmbracoSites\JRBP1\media\7318\knowsley.zip'.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
Stack Trace:
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
And indeed the zip file is not in the directory!!
But Why Not ? :(
I'm confused :(
If I upload a smaller file I still get my original error rather than "Could not find file":
Server Error in '/' Application.
The directory is not empty.
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.IOException: The directory is not empty.
Source Error:
The source code that generated this unhandled exception can only be shown when compiled in debug mode. To enable this, please follow one of the below steps, then request the URL:
1. Add a "Debug=true" directive at the top of the file that generated the error. Example:
<%@ Page Language="C#" Debug="true" %>
or:
2) Add the following section to the configuration file of your application:
<configuration>
<system.web>
<compilation debug="true"/>
</system.web>
</configuration>
Note that this second technique will cause all files within a given application to be compiled in debug mode. The first technique will cause only that particular file to be compiled in debug mode.
Important: Running applications in debug mode does incur a memory/performance overhead. You should make sure that an application has debugging disabled before deploying into production scenario.
Stack Trace:
Version Information: Microsoft .NET Framework Version:4.0.30319; ASP.NET Version:4.0.30319.1
Perhaps it is one of the zip files that failed?
Rich
@Rich: I can unzip the file(s) just fine and see all the images in the target directory.
is working on a reply...