By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
457,759 Members | 1,273 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 457,759 IT Pros & Developers. It's quick & easy.

I'm totally stumped - IIS not working on two separate machines - 500 Internal Server Error

P: n/a
Hello - I'm having a serious problem with IIS on Windows XP pro.

Whenever I try to run ASP pages, I get

HTTP 500 - Internal server error

This behaviour happens identically, on two 'totally independent' machines. I
am trying to run Visual Studio 2003, however, the problem occurs before any
of this development software (or the CLR) is even installed.

Both machines are 'fully patched' via windows update. The problem however
occurs before and after patching.

I'm very surprised that I can't find any information on technet etc. The
fact that the two machines are exhibiting identical behaviour seems very
strange to me.

If anyone can point me in the right direction, I'd be most grateful. My
deadline is fast approaching for this site and, if I can't resolve this soon
I'll have to look at (shudder) other web servers.

Cheers
DS
Nov 18 '05 #1
Share this Question
Share on Google+
6 Replies


P: n/a
First, I wish to clarify whether you mean ASP or ASP.NET pages as they
require different component and setting to run.

Second, have you had your virtual directory being properly set up?

"Damien Sawyer" <da**********@yahoo.com.au> ???
news:d8**************************@posting.google.c om ???...
Hello - I'm having a serious problem with IIS on Windows XP pro.

Whenever I try to run ASP pages, I get

HTTP 500 - Internal server error

This behaviour happens identically, on two 'totally independent' machines. I am trying to run Visual Studio 2003, however, the problem occurs before any of this development software (or the CLR) is even installed.

Both machines are 'fully patched' via windows update. The problem however
occurs before and after patching.

I'm very surprised that I can't find any information on technet etc. The
fact that the two machines are exhibiting identical behaviour seems very
strange to me.

If anyone can point me in the right direction, I'd be most grateful. My
deadline is fast approaching for this site and, if I can't resolve this soon I'll have to look at (shudder) other web servers.

Cheers
DS

Nov 18 '05 #2

P: n/a
Make sure the extensions have been registered with your IIS server. Have you
installed the .Net Framework 1.1 to your IIS web server?

Check under services and make sure everything relating to web services is
running. Make sure IIS is running (you wouldn't believe how many times
people forget this one). Ensure the location of the ASP files have proper
permissions. ASP.NET folders need each folder to be Configured under
Application settings.

Did you have IIS running before you installed Visual Studio 2003 to your
machine. If not, uninstall VS.net, get IIS running properly and then install
VS.NET.

Please note that IIS on an XP Pro machine can handle only 10 concurrent
users. If you plan to have more users, then you will need to get the server
version.

--
G Vaught
"Damien Sawyer" <da**********@yahoo.com.au> wrote in message
news:d8**************************@posting.google.c om...
Hello - I'm having a serious problem with IIS on Windows XP pro.

Whenever I try to run ASP pages, I get

HTTP 500 - Internal server error

This behaviour happens identically, on two 'totally independent' machines. I am trying to run Visual Studio 2003, however, the problem occurs before any of this development software (or the CLR) is even installed.

Both machines are 'fully patched' via windows update. The problem however
occurs before and after patching.

I'm very surprised that I can't find any information on technet etc. The
fact that the two machines are exhibiting identical behaviour seems very
strange to me.

If anyone can point me in the right direction, I'd be most grateful. My
deadline is fast approaching for this site and, if I can't resolve this soon I'll have to look at (shudder) other web servers.

Cheers
DS

Nov 18 '05 #3

P: n/a
WJ
"Damien Sawyer" <da**********@yahoo.com.au> wrote in message
news:d8**************************@posting.google.c om...
Hello - I'm having a serious problem with IIS on Windows XP pro.

Whenever I try to run ASP pages, I get

HTTP 500 - Internal server error
"500 series" is Server side error. This means somethings erratic happening
on the IIS server. Does you page interact with any Database such as
SQL/Server ? Check to make sure SQL is up and running and your ASP page or
the account login has proper access right.
This behaviour happens identically, on two 'totally independent' machines. I am trying to run Visual Studio 2003, however, the problem occurs before any of this development software (or the CLR) is even installed.
Both machines are 'fully patched' via windows update. The problem
however occurs before and after patching.

For a developer PC (XP), I always follow the order of installations below:

1. Install XP and IIS at the same time.
2. Enable the Default site that came with the IIS to make sure that your IIS
is operational. If it does not, stop here and try to make the default
website work 1st before you move on. Because at this point your system is
still very simple (XP & IIS).

3. Install .NetFW 1.1.
4. Install MS/SQL Server (developer edition if you have)
5. Install Office Products if you have
6. Install Windows Security patches, SQL Service pack(s) if you have, and
Office Patches (if any)
7. Install VS.Net 2003.
8. At this point, check to make sure Windows/ASPNet account is created along
with the local group "VS Developers" created.
9. Inspect your Local Security Policy (user's right POL).
10. Check SQL Server Service to ensure if SQL is running (if you have it)
11. Reboot
12. Try out your site.

The 500 is very common error. Mostly related to database is not running and
or invalid database specification or bad logon credential. However, a 500
error means that your IIS is operational because it responds with 500. This
means you have successfully installed IIS Server on your box. Don't forget
that if you run the IIS Lock down tool, this could introduce 500 series too.

Good luck to you,

John
..
Nov 18 '05 #4

P: n/a
Can you tell us more about what you do to see the 500 error? Does this
happen on the first request to http://localhost ?

On 7 Jul 2004 19:33:24 -0700, da**********@yahoo.com.au (Damien
Sawyer) wrote:
Hello - I'm having a serious problem with IIS on Windows XP pro.

Whenever I try to run ASP pages, I get

HTTP 500 - Internal server error

This behaviour happens identically, on two 'totally independent' machines. I
am trying to run Visual Studio 2003, however, the problem occurs before any
of this development software (or the CLR) is even installed.

Both machines are 'fully patched' via windows update. The problem however
occurs before and after patching.

I'm very surprised that I can't find any information on technet etc. The
fact that the two machines are exhibiting identical behaviour seems very
strange to me.

If anyone can point me in the right direction, I'd be most grateful. My
deadline is fast approaching for this site and, if I can't resolve this soon
I'll have to look at (shudder) other web servers.

Cheers
DS


--
Scott
http://www.OdeToCode.com
Nov 18 '05 #5

P: n/a
In addition, you can flag IE to give you a message that means something.
View the "Advanced" tab in the IE options dialog. Toggle the "Show friendly
HTTP error messages" checkbox. Then try to access your sight. You should
be given a more descriptive error.

"GVaught" <gl****************@hotmail.com> wrote in message
news:uO**************@TK2MSFTNGP10.phx.gbl...
Make sure the extensions have been registered with your IIS server. Have you installed the .Net Framework 1.1 to your IIS web server?

Check under services and make sure everything relating to web services is
running. Make sure IIS is running (you wouldn't believe how many times
people forget this one). Ensure the location of the ASP files have proper
permissions. ASP.NET folders need each folder to be Configured under
Application settings.

Did you have IIS running before you installed Visual Studio 2003 to your
machine. If not, uninstall VS.net, get IIS running properly and then install VS.NET.

Please note that IIS on an XP Pro machine can handle only 10 concurrent
users. If you plan to have more users, then you will need to get the server version.

--
G Vaught
"Damien Sawyer" <da**********@yahoo.com.au> wrote in message
news:d8**************************@posting.google.c om...
Hello - I'm having a serious problem with IIS on Windows XP pro.

Whenever I try to run ASP pages, I get

HTTP 500 - Internal server error

This behaviour happens identically, on two 'totally independent' machines.
I
am trying to run Visual Studio 2003, however, the problem occurs before

any
of this development software (or the CLR) is even installed.

Both machines are 'fully patched' via windows update. The problem

however occurs before and after patching.

I'm very surprised that I can't find any information on technet etc. The
fact that the two machines are exhibiting identical behaviour seems very
strange to me.

If anyone can point me in the right direction, I'd be most grateful. My
deadline is fast approaching for this site and, if I can't resolve this

soon
I'll have to look at (shudder) other web servers.

Cheers
DS


Nov 18 '05 #6

P: n/a
I think Lau's probably right and it's something to do with your
virtual directory settings. But just in case it's not, I've had
problems in the past with my realtime AV software - some realtime
scanners conflict directly with asp.net. Each time asp.net tries to
compile for first time use, the realtime scanner thinks that the file
has changed and needs scanning. And when it tries to scan it, asp.net
thinks it needs recompiling...and so on.

This makes the file pretty much inaccessibly by asp.net and it throws
a 500 error. If this was the case, you'd need to either exclude the
physical directory which contains your web application from the
realtime scanner or exclude the aspnet_wp process.
"Lau Lei Cheong" <le****@yehoo.com.hk> wrote in message news:<uV**************@TK2MSFTNGP10.phx.gbl>...
First, I wish to clarify whether you mean ASP or ASP.NET pages as they
require different component and setting to run.

Second, have you had your virtual directory being properly set up?

"Damien Sawyer" <da**********@yahoo.com.au> ???
news:d8**************************@posting.google.c om ???...
Hello - I'm having a serious problem with IIS on Windows XP pro.

Whenever I try to run ASP pages, I get

HTTP 500 - Internal server error

This behaviour happens identically, on two 'totally independent' machines.

I
am trying to run Visual Studio 2003, however, the problem occurs before

any
of this development software (or the CLR) is even installed.

Both machines are 'fully patched' via windows update. The problem however
occurs before and after patching.

I'm very surprised that I can't find any information on technet etc. The
fact that the two machines are exhibiting identical behaviour seems very
strange to me.

If anyone can point me in the right direction, I'd be most grateful. My
deadline is fast approaching for this site and, if I can't resolve this

soon
I'll have to look at (shudder) other web servers.

Cheers
DS

Nov 18 '05 #7

This discussion thread is closed

Replies have been disabled for this discussion.