• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 545
  • Last Modified:

ASP Upload IIS 6.0

This is in refrence to Windows 2003 Server running IIS 6.0

I have a web application that uploads files via an ASP script, and I am aware of the fact that in stock form IIS 6.0 will not accept uploads via asp larger than 200k. To fix this, I editted the MetaBase.xml and adjusted the "AspMaxRequestEntityAllowed" value to "1073741824"

I then restarted the server.

It seems that still, if I attempt to upload a file larger than 200k, it still fails, and I get a 500 error. I'm confused, I've run this web application on numerous other IIS 6.0 servers without a problem assuming I've made this edit.

Is there something I'm missing? URLscan is NOT on the box, and I already placed a "*" in the mime types to accept all file types. The problem seems to be completley size related.
0
jschweg
Asked:
jschweg
  • 3
  • 2
1 Solution
 
meverestCommented:
Hi,

does it look like it is sending the whole file (ie does it take longer to error when sending a 2meg file than when sending a 500K file?  A long shot, but doesn;t seem to be anything else to guess on for this one.

If so, could it have something to do with disk space or access permission?

cheers.
0
 
jschwegAuthor Commented:
No, it doesn't begin uploading the file, it fails immediatley with a 500. I was actually hoping that it was a permissions or file extension problem, but obviously this isn't the case being that I can upload ANY file smaller than 200K without a problem.
0
 
meverestCommented:
Very interesting - that would suggest that it is baulking after just reading the http header, which suggests that it is very much a server side configuration issue.

Can you double check what you have done with the metabase?  Maybe you have inadvertently changed the setting for something other than the particular web site running that application.

Cheers.
0
Efficient way to get backups off site to Azure

This user guide provides instructions on how to deploy and configure both a StoneFly Scale Out NAS Enterprise Cloud Drive virtual machine and Veeam Cloud Connect in the Microsoft Azure Cloud.

 
jschwegAuthor Commented:
The only thing different about this server is that it is a virtual server (running vmware). I would think that this shouldn't make any difference however. The metabase setting I changed affects IIS as a whole, for all the websites on the box.
0
 
jschwegAuthor Commented:
We ended up figuring out that it was a firewall problem. The firewall was blocking cross-site scripting. All is well now.
0
 
ee_ai_constructCommented:
Question answered by asker or dialog valuable.
Closed, 500 points refunded.
ee_ai_construct (replacement part #xm34)
Community Support Admin
0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

  • 3
  • 2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now