The application has encountered an error.

Question

3.67/5 (3 votes)

See more:

I'm trying to add a page to an existing web site in its own sub-folder. When I try to browse to it, it gives me this error (and this is the only thing displayed on the page):

The application has encountered an error.

Things I've done:

0) I've tried commenting out all of the code behind.

1) I've tried creating a new master page for it (as opposed to using the one I original tried to use).

2) I verified that the code behind is okay by creating another web site project on my local box and it renders as expected.

3) I comment out EVERYTHING in the aspx file, and just had the following text, when rendered as expected:

<%=test%>

Due to security restrictions, I cannot remotely debug, and I can't change the web.config. I've google the error text itself, but haven't yet found anything that can help me through the problem.

How do I find out what I'm doing wrong?

EDIT ===============

If you're going to edit my qestion, tell me what you changed.

EDIT ===============

Why was this question down-voted? Sheesh...

Posted 19-May-11 5:09am

#realJSOP

Updated 19-May-11 9:42am

v4

Add a Solution

Comments

R. Giskard Reventlov 19-May-11 11:21am

Check the event log when you are able and see what the real error might be.
Is the path to the Master Page correct?
You can put some exception handling in Global.asax (Application_Error).

#realJSOP 19-May-11 12:16pm

I can't check the event log - no access. I assume the master page path is right because I chose it in the ide when I created the page. I'll ook into the global.asax thing.

#realJSOP 19-May-11 13:43pm

Well, I can't modify global.asax because it's read-only on the server (and of course, I don't have permissions to change it).

dan!sh 19-May-11 12:27pm

Is it like the new build (one with the new page) does not works on web server but works on the local box? How about adding tracing and creating log for everything on the server?

Update: Sorry, just noticed you cannot change web.config too. :doh:

[no name] 19-May-11 13:42pm

Is it perhaps a .net version issue? Your local has a different version than the server and different references in the web.config?

#realJSOP 19-May-11 13:45pm

Well, we're talking about a complete (LARGE) web site that uses authentication, versus a little off-the-cuff web site I used to verify the code behind was okay. The two can't possibly be compared. In the interest of completeness, the deployed web site is .Net 3.5, and the simple one is .Net 4, but I'm definitely not using any .Net4-specific code.

Ed Nutting 19-May-11 13:49pm

Aaah.. In that case I hit this problem just two days ago. The issue is that (assuming your using IIS), 'IIS cannot run two versions of the .Net Framework in the same service'. Basically, even though your not using .Net 4.0 specifc code, it's targeted at .Net 4.0 which causes IIS a problem. Try changing the simple site to 3.5 :) Should solve your problem, did for me :)

#realJSOP 20-May-11 5:55am

The simple site was not deployed - it was just to check the code behind. The problem is happening on the main site where I just uploaded a couple of files to a new folder. No web config to change (in the new folder), so no place to specify the .net version.

Ed Nutting 19-May-11 13:47pm

I've had this problem myself too but I can't remember how I solved it. I've an awful feeling I had to resort to deleting the new files and folder and recreating them under new names. Are you sure your page names don't cause conflicts? That' all I can suggest, recreation, sorry :/ (On a side note, I wonder if God considered 'recreation' ;P )

#realJSOP 19-May-11 13:59pm

I don't understand your question. There are four files in the folder right now - default.aspx (and its vb file), and masterpage.master (and its vb file). There's really nothing to conflict with those files since they live in their own sub-folder.

Ed Nutting 19-May-11 14:06pm

Meh.. all I know is that 1) Please see my other answer, it's more likely to be your problem - change the target framework and stuff :) 2) I just had to recreate folder and files (using Visual Studio) as something, unknown to me, had gone wrong with them :/

3 solutions

Solution 1

We randomly get this error on the form that generates pdf reports for us... the solution (for us) is to perform an iisreset, then it all magically works again... ymmv.

Posted 25-May-11 19:03pm

_Damian S_

Solution 3

go to visual studio command prompt

type devenv.exe/resetskippkgs

And then open your project again.

I hope this will help you.

Posted 29-Aug-11 2:23am

Yogesh Pednekar

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)

#realJSOP · Accepted Answer · 2011-08-29T02:07:00

We use VS2010 to write (VB) code now. VS2010 allows you to use .Net 4.0 constructs, even if the web site is specified to target .Net 2.0. This means that all of the stuff that was required (or not previously supported) in VB.Net 2.0 became optional in .Net 4.0, and since intellisense wasn't barking at me, some of the stuff I did wouldn't run on the web site because the server doesn't have .Net 4.0 on it. This caused the generic error described above to be displayed.

For the record, the most problematic item was the way ternary conditions were handled. .Net 2.0 requires Iif, but .Net 4.0 allows If.