server on xp pro

[chris leeds]

Hi all,
I've been using the server in xp pro lately to test things before
publishing. it's starting to fail. I get messages like:
The page cannot be displayed
The page cannot be displayed There are too many people
accessing the Web site at this time. Please try the following: Click
the Refresh button, or try again later. Open the home page, and then look
for links to the information you want. HTTP 403.9 - Access Forbidden: Too
many users are connected Internet Information Services Technical
Information (for support personnel) Background: This error can occur if
the Web server is busy and cannot process your request due to heavy traffic.
More information: Microsoft Support

Is there somewhere I could go to make sure I've got the proper updates and
that may give me some help in understanding how to use this thing without
pulling my hair out?
TIA

 

[Jon]

Chris,
This is going to happen - Pro is limited to 10 connections at a time. If
you're working fast and testing in your browser frequently sometimes you'll
hit the limit. The only answer, which you ain't going to like, is to develop
against a server OS either win2k or 2003

Jon
Microsoft MVP - FP

 

[chris leeds]

I was afraid of that. I've noticed that xp's server won't do stuff like
server.execute and various little things that are no sweat on my hosted
server.
I like asp (and asp.net for what I've learned) so obviously it's going to be
a Microsoft product. I guess I'll go about looking for a good deal on one
of them and maybe some reference material on how to set it up for testing
purposes etc. (I don't want to be a server admin but I would like a fairly
solid testing environment).
so if anyone has some good links or tips for someone in my situation I'd be
appreciative.
Thanks Jon and TIA to anyone else with something to add. ;-)
cl

 

[Jack Brewster]

chris,

The only time I run into to the too many clients issue is if I have multiple
browsers open and viewing sites on my XP "Server" (usually when testing CSS
layouts). The quick way to clear that is to simply start closing browsers
which, in most cases, appears to terminate the connection as well.

As for supporting Server.Execute/Transfer, I just whipped up a test file
that ran as expected. The only difference, to my knowledge, between Server
and XP IIS is the number of connections supported. Of course, I couldn't
find my ASP with both hands, so I could be wrong.

Maybe Jon knows?

 

[Jon]

server.execute/transfer should certainly work on XP Pro - I can't think of
anything that would cause it to fail other than perhaps a path issue, eg
/folder/file.asp would point to a different location on Win2000/2003 server
than on XP Pro.

Jon
Microsoft MVP - FP

 

[chris leeds]

I only had one browser open, I had FrontPage open on the
http://localhost..... so maybe that was it. I don't know but I think there
is a problem with my iis server in general. I may have to look for the
help/ detect and repair. ;-)

 

[Thomas A. Rowe]

Chris,

Why not create subweb on the host for testing?

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle,
MS KB Quick Links, etc.
==============================================

 

[chris leeds]

I usually do, or I'll do it in the root but just put up a default page to
stop people.
some stuff it's nicer to try locally and not publish etc. sometimes
constantly publishing is a hassle. ;-)
I think there's something wrong with the server. I have to look for a way
to "re-install" it.

 

[chris leeds]

OK, One last question from you learned gurus:
since I'm using this for testing I'm wondering if there is a big benefit to
use server 2003 or just get the server 2000. I'd like to, at some point in
the future, get into the .net stuff which I guess means sql server which I'm
not sure will work with server 2000.
sorry about the possibly "easy" question but I'd rather the quick and
worthwhile advice from you guys than spending hours researching and probably
still picking wrong. ;-)
TIA

 

[Thomas A. Rowe]

Chris, look into getting the Windows 2003 Server Web Edition, cost less than
Windows 2000 Server, and will work well as a testing environment.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle,
MS KB Quick Links, etc.
==============================================

 

[Jon]

only drawback is you can't put SQL Server on 2003 web edition - that only
runs on standard and up.

Jon
Microsoft MVP - FP

 

[Jon]

only drawback is you can't put SQL Server on 2003 web edition - that only
runs on standard and up.

Jon
Microsoft MVP - FP

 

[chris leeds]

I had a feeling it'd be that way. now the only question is whether I'll
ever break the dot net ice enough to require the sql server or if I'd never
get past the mde thingy from the aspnet matrix. ;-)

 

[chris leeds]

Thomas,
whether I take your advice or Jon's, wouldn't either of these have to be
installed as a whole OS and not as a component on my "regular" computer?
I'm just kind of thinking past the purchase of the software and to what I'll
have to do with it once I've got it in my hand. set up another computer I
guess?

TIA and sorry if it's a stupid question but besides the weak and sort of
built in server in xp it's the first time I've considered setting one up.

 

[Thomas A. Rowe]

Chris,

They are complete Server OSs and should be installed on a networked
computer.

The Web Edition doesn't support being a file/application server, only a web
application server.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle,
MS KB Quick Links, etc.
==============================================

 

[chris leeds]

well then, in the words of Special Ed of Crank Yanker fame...."I'm makin a
computer, yeaah!" now if I could only find my helmet. ;-)

 

[Jon]

Hi Chris,
it would make sense to keep your options open re SQL Server, would be a
shame to set yourself up with 2003 web edition then have to ditch it because
you want sql. Bear in mind also the dev edition of SQL Server is only
$49.95. You shouldn't need any fancy hardware to run this either - I've got
Windows 2003 standard and sql server 2000 enterprise edition running quite
nicely on an old p3 with 256mb ram

Jon

 

[chris leeds]

so is there a server 2003 that is reasonably priced that'll lace up with
that dev. edition sql server?

I think Microsoft may be taking a tip from grocery store vendors; so many
different products that it forces the competition to the bottom of the
shelves. ;-)

That's why there's so many different kinds of dog food, soda pop, whatever,
even within the brands.

 

[Thomas A. Rowe]

Lowest cost Windows 2003 Server, is the Standard 5 User License version.
whereas the Web Edition doesn't require user access licenses.

--

==============================================
Thomas A. Rowe (Microsoft MVP - FrontPage)
WEBMASTER Resources(tm)

FrontPage Resources, WebCircle,
MS KB Quick Links, etc.
==============================================