500.0 - Internal Server Error

Question

1.00/5 (1 vote)

See more:

I have one site developped by MVC3 running by IIS 7.5 on win 2008 r2 Server Back End Oracle.When i run the application first page coming no problem but when i giving user name and password its showing this error:

HTTP Error 500.0 - Internal Server Error
The page cannot be displayed because an internal server error has occurred.

But the Application running smoothly on 2003 server.I made the 2008 server 32 bit true. How can I solve this big problem plz help me. Thanks in Advance...

Posted 9-Jul-12 9:35am

khosnur

Updated 9-Jul-12 9:42am

Karthik. A

v2

Add a Solution

Comments

Karthik. A 9-Jul-12 15:41pm

An internal server error could occur for numerous reasons like - incorrect database server, incorrect username / password etc etc. The best way to approach this would be to find out what's the actual error. You have said that you could see the 1st page, but the error happens after you enter the user name/ password. What type of authentication does your web application / site use ? See if it's setup correctly in IIS under the "Authentication" module. Also, go to the server and visit your page there, instead of from a machine that just acts as a client. If you use the server itself, it will give you much more information than a useless "500 internal server" error. If you could do that and see the actual error, it might be helpful If you have qns. post it here and one of us will help! Its difficult to help w/ just the general 500 error...

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

jkirkerx · Answer 1 · 2012-07-09T10:02:00

Solution 1

Sometimes you have to load your project on the web server, and debug it from there. Some things that work on Server 2003 don't work on Server 2008.

So you can take a stab in the dark, and pick out just the login page code to debug on the server.

You may have to setup a temp server at your shop, to test and debug on, before you deploy to a production server.

I ran into that the first time I deployed on Server 2008, mostly things like

Request.Server("some context") failed.
Get IP Address instead of GetUserHostAddress
Folder Security issues, incorrect permissions for writing to the disk drive

If there is a long pause, then the Server Unavailable error, probably folder permission.

Posted 9-Jul-12 10:02am

jkirkerx

Updated 9-Jul-12 10:06am

v2

Comments

khosnur 9-Jul-12 16:19pm

Thanks for your reply. Actually i didn't publish that site. i made two pages site without DB using MVC3 framework. I run on 2008 server but it was showing error. when i assigned the port number and publish it again now it runs. I what i am thinking i wanna collect the source code and assign the port number and will publish it again. I hope it will work what u r thinkikg i am in right way....

jkirkerx 9-Jul-12 16:47pm

Oh, so you had a problem with IIS7.5 Server, and did not make a bind on port 80 for that website. I think that should of resulted in a page not found error.

Well whatever. I read your words, you contacted the server, and the server replied with an error, so the port number must of been correct.

Good Luck.