Home Support Site Search Faq Register Login  
FileUp
Re: *.tmp files left behind in the upload folder FileUp 5.3.3 & Windows 2003

Thread Starter: Shibu   Started: 07-22-2014 1:11 PM   Replies: 5
  22 Jul 2014, 1:11 PM
Shibu is not online. Last active: 7/23/2014 12:43:24 PM Shibu

Top 10 Posts
Joined on 07-22-2014
Posts 4
*.tmp files left behind in the upload folder FileUp 5.3.3 & Windows 2003
We have recently upgraded FileUp 5.0.14 in our site to FileUp 5.3.3 and Net 3.5 SP1.  Since then we can see many tmp files are left behind in the uploads folder. These files are not getting cleaned up by FileUp automatically.

What could be the rot cause for this issue?
Can anyone please suggest a solution for this problem?


Thanks
  
  22 Jul 2014, 3:31 PM
StephanieR is not online. Last active: 9/23/2014 11:25:33 AM StephanieR

Top 10 Posts
Joined on 11-25-2013
Posts 14
Re: *.tmp files left behind in the upload folder FileUp 5.3.3 & Windows 2003
Are you using FileUpSE or FileUpEE? And if you are using FileUpEE are you using the resumable uploads feature?

Please let me know so I can investigate the cause.

  
  22 Jul 2014, 3:38 PM
Shibu is not online. Last active: 7/23/2014 12:43:24 PM Shibu

Top 10 Posts
Joined on 07-22-2014
Posts 4
Re: *.tmp files left behind in the upload folder FileUp 5.3.3 & Windows 2003
I'm using FileUP PE 5.3.3, fileup is installed in 2 servers. We have tmp issues with only only one server. I have noticed following message in application event logs (MS Event viewer) "A trappable error (C0000005) occurred in an external object. The script cannot continue running" is logged for every tmp file is this issue related to FileUp .tmp files?

This issue is impacting our production website as customers and customers cannot upload files.

please advice
  
  23 Jul 2014, 9:30 AM
StephanieR is not online. Last active: 9/23/2014 11:25:33 AM StephanieR

Top 10 Posts
Joined on 11-25-2013
Posts 14
Re: *.tmp files left behind in the upload folder FileUp 5.3.3 & Windows 2003
The trappable error in classic ASP is a generic error that says something went wrong in an external object, which could be any object that gets created with Server.CreateObject(). So that error may not necessarily be related to your temporary files issue.

Can you check to make sure the account the application is running under has full permissions on the folder where the temporary files are being created?

In addition, does this happen for every upload? The next step would be to see if this error occurs with the FileUp samples. If it does occur with the samples, then there is likely a configuration issue, and if it doesn't, then there is likely a problem with your code or web.config file.

Perhaps procmon can give you more information regarding why the file isn't being deleted. Read this article about how to collect logs with procmon.
http://blog.softartisans.com/2014/06/25/kb-using-process-monitor-procmon-to-troubleshoot-web-applications/

Please let me know what you find.
Thanks.


  
  23 Jul 2014, 12:24 PM
Shibu is not online. Last active: 7/23/2014 12:43:24 PM Shibu

Top 10 Posts
Joined on 07-22-2014
Posts 4
Re: *.tmp files left behind in the upload folder FileUp 5.3.3 & Windows 2003
The error and tmp file issue ar enot happening with every upload. Does the load on server cause FileUp to fail?

I will try FileUp sample and the procmon as you suggested and get back to you.


  
  23 Jul 2014, 12:26 PM
Shibu is not online. Last active: 7/23/2014 12:43:24 PM Shibu

Top 10 Posts
Joined on 07-22-2014
Posts 4
Re: *.tmp files left behind in the upload folder FileUp 5.3.3 & Windows 2003
I was looking at the installation steps you provided in the kb
http://support.softartisans.com/kbview.aspx?ID=1398#Samples

Why are you guys recommending "un check ASP.net solution" on windows 2003, I have not un checked this, does this cause any conflict or issue?
  
 Page 1 of 1 (6 items)
SoftArtisans Forums » SoftArtisans Products » FileUp » Re: *.tmp files left behind in the upload folder FileUp 5.3.3 & Windows 2003