Server Busy Errors (Full Version)

All Forums >> [Web Development] >> Server Issues



Message

xx75vulcan -> Server Busy Errors (5/14/2007 16:05:32)

I've read all of this group's posts about Server Time Outs, and have not found any postings that have a working solution that fixes my "Server Timed Out" errors.

I have a Windows Server 2003 Enterprise box running IIS 6.0 and Frontpage Extensions.
I have Service Pack 1 installed.
I have the site broken down into 30 subwebs and each are relatively small.
Under the "Server EXtensions 2002" Tab in IIS it says:
Microsoft Share Point is installed on this Web Site
Version 5.0.2.6738
Click "settings" to view and set Share Point and FrontPage Server Extenstion properties and to choose administration commands.

Just recently (I have no idea what changed) my users started getting "Server Busy" and "Server Timed Out" errors when they try to upload files to their subwebs. They can successfully log into their sub webs, and can modify/save html pages, but can not upload new files into the sub. (Ex. they can not upload a PDF or new JPG files).

I am an admin on the box (and sitting in the DMZ) can upload an unlimited file size, and have not experienced a "server busy" error. I have traveled to a machine that is on the regular network, and have witnessed this "server busy" error, so I know the users are not making this up. :)

Users systems range from:
Win NT with Front Page 2000
Win XP with Front Page 2000
Win XP with Front Page 2003
and all seem to experience this issue.

I've read many posts talking about deleting the service.lck and frontpg.lck files. I have deleted these files and it still does not eliminate the "server busy" error.

I have run the "Fix FP Extensions" through IIS and it hasn't helped either.

I'm sure I have left out some specs that someone needs to know to help me solve this great mystery, so please ask. I'd love nothing more than to solve this, and let this post be an "end all" to the "server busy" error so many of us seem to be experiencing.

Sincerely,
Chris



coreybryant -> RE: Server Busy Errors (5/15/2007 5:41:31)

it could potentially be on their side as wel. I am guessing you have rebooted the server as well.

A couple of things to suggest to them is slow / failed publishing or Frontpage Cleaner Utility to see if this is the problem.

If you deleted any files, hopefully you recalculated the web to fix the issues.



xx75vulcan -> RE: Server Busy Errors (5/29/2007 15:06:08)

So here's the newest:

We've discovered it's not a permissions issue. I have traveled to the user's location, and logged in as admin into frontpage, and I myself get a server timed out error.

I've discovered that it's not related to uploading a specific file type, but rather file size. Anything bigger than 0.18 MB will generate an instant server timed out error.

I did some more research, because I have two seperate web servers located in my DMZ, and they are both giving this error. This leads me to think that it's not the servers themself, but somehow, somewhere, an issue on the microsoft network we're running or even the PIX Controller.

When using Frontpage to upload files from home (or anywhere not on the network) users can upload several hundred MB w/o any issues. Seems odd you got to leave the network to run smoothly?!?!



rdouglass -> RE: Server Busy Errors (5/29/2007 15:30:24)

Are you in-house-ing your DNS or externally? With the combo of the PIX and external DNS, I have seen that issue before. The theory is that the PIX keeps trying to send to an external address and gets caught in a loop. Especially when trying to re-send packets. That has been my experience with a PIX 515e anyways.

A quick check would be to hard-code the IP address for those web server domains in the users 'host' file. You should only have to do 1 or 2 domains to test this theory.

If that works, I'd consider implementing in-house DNS. Either that or stick with the host file solution (which is a pain IMO).

Hope that helps.



xx75vulcan -> RE: Server Busy Errors (5/29/2007 17:04:57)

We used to have an external DNS, but is now in-house.

Here's something interesting though....I've noticed that online forms that submit data through e-mail have stopped working. (at the same time uploading starting giving server time out errors).

I double checked the IP of the Exchange Mail server, and it's good.

Just for kicks, I've switched the server's SMTP Mail settings to point to the internal IP of our exchange server, and *poof* the online forms started working again.

In theory, a machine in the DMZ isn't supposed to be on the inside network, rather, is supposed to be sitting outside the network, using all external IP's right?

(We've ALWAYS used external IP for the mail server in the past)

What's going on!?
I'm so confused now.



rdouglass -> RE: Server Busy Errors (5/29/2007 17:52:32)

quote:

We used to have an external DNS, but is now in-house.


How'd I guess...[;)]

I think the key is right there. Just make sure you have A records and pointer (PTR)records using the appropriate address from an 'inside-the-lan' perspective. That worked for me in almost all situations like that.

If that doesn't work, make sure you have appropriate host interfaces and NAT tables in your PIX. The way the PIX uses it's NAT tables and interface assignments can be tricky sometimes.

Hope some of that helps.



Page: [1]

Valid CSS!




Forum Software © ASPPlayground.NET Advanced Edition 2.4.5 ANSI
0.0625