0

Is it possible to debug (with VS 2008) a site at my host? I have no particular control of the server, I'm only allowed to upload my website files to the server. I can however upload .pdb files etc.

The reason for me wanting this is because the site works fine on my dev machine, but refuses to show even the first page when deployed on the server (404-error).

Improve this question
2
  • I don't want to sound patronising, but just to be doubly sure, is your host box a Windows server? Commented Jan 14, 2010 at 8:29
  • Oh, yes , it worked fine, and then I updated it, and this problem started. It's not easy to find out what changed exactly, since I've upgraded the MWPSK to a new version (codeplex.com/…) Commented Jan 14, 2010 at 8:34

2 Answers 2

Reset to default
1

Maybe a long-shot, but in my experience the "works-on-my-machine-but-returns-404-on-the-server" problem is often a consequence of that the WebServer Extension "ASP.NET v2.0.50727" is prohibited.

As Ganesh R points out, it may sound like your application never gets startet.

As for the debugging part, I don't think you would be able to pull that off...

Improve this answer
Sign up to request clarification or add additional context in comments.

9 Comments

Thanks for your answer. How can I find out if I'm using WebServer Extension "ASP.NET v2.0.50727"? The site is based on MWPSK, codeplex.com/…
Normally this could be checked in the IIS manager on the server. (Under Administrative Tools in the control panel). Directly beneath the server-node, you have a folder named "Web Service Extensions". In this folder you would find the "ASP.NET v2.0.50727" node (which has to be Allowed in your case, since you are running on this platform (the MWPSK is base on this). However, if you don't have any control over this server (maybe it it a 3rd party hosing site?), then you should make sure you have the proper rights to actually run an asp.net site in their environment.
I think that maybe something is configured wrong in web.config or some else place. The thing is that MWPSK worked fine in version 1.2.2 and this problem started when I upgraded to 1.3.0. I've made almost no code changes, and I also suspect that the code is not even executed. This error seem to occur before that (but I cant be sure).
OK, yes, I agree that none of your code is executed. What if you put a plain HTML page in your solution and try to access this...? Do you still the get 404-error? Also, try to access a specific aspx-page in your application? Do they all give you 404-errors?
Very interesting! I added a html-page, and that worked fine. Also, a few other aspx-pages worked (like Search.aspx and Login.aspx). When I've loaded for example Search.aspx, and I click the home-link, the 404 reappears.
|
1

Debugging requires that certain debugging components are installed and enabled on the server. This is highly unlikely to be the case on any production hosting platform.

Contact your hosting provider - they will usually be quite willing to help you diagnose the problem you are encountering.

Improve this answer

1 Comment

Try adding logging to your code. THis will help you to indirectly diagnose the issue. Also a 404 error means that most probabily, control never reaches your code.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.