PageRequestManagerServerErrorException: 401

I wrote some server code that work fine in VWD 2008 Express Edition. When I uploaded the page to my site (including the dll that my code uses), I get the following error:

Sys.WebForms.PageRequestManagerServerErrorException: An unknown error occured while processing the request on the server. The status code returned by the server was: 401. How can I find out where the problem is comming from?

Thanks,
Yoni

Server Error 401 is an "Unauthorized" error.

And how can I find out which peace of code is giving me this error?

Thanks,
Yoni

It's probably going to be something where it is trying to access a page, database, etc. that it doesn't have permissions to. I would set breakpoints and just see how far the code is getting.

Thats a problem. As I said, the page and code work fine on my computer - only when I move it to my site I get an error. How do I insert breakpoints? Do you mean I should use "return" statements in diff places until I find where the error originates?

Thanks,
Yoni

On the server you couldn't use breakpoints. I personally am a fan of just putting an extra blank <asp:Label> on the page and writing things to it to see values and my progress. Place occasional "I got to ____ function" statements in the label's text.

I wouldlove to do that: I have tried it, but it doesn't work. My server code takes about 10 seconds - 5 minutes to run and during that time I can't post nothing to the page... I asked how to do this in another forum, but I was given extremely complicated ways of doing this, that I could not do. Do you know how I can change a label while my server code is running?

Hi,

Thank you for your post!

Check out the following link:

http://blogs.msdn.com/david.wang/archive/2005/07/14/HOWTO_Diagnose_IIS_401_Access_Denied.aspx, David Wang said in this article:

One of the most common questions asked about IIS on the newsgroups as well as Microsoft Product Support is "why am I getting 401 Access Denied"?

There are many, many possible causes and variations, but from the IIS perspective, the top-level, logical categories are fixed. This information can help dramatically narrow down the scope of any investigation, but unfortunately, few people know to take advantage of this information. This is what I am going to address with this entry - how to use and diagnose the 401.x error codes on IIS.

Step 1: Determine the SubStatus Code

Step 2: Determine Course of Action

401.1 Denied by Invalid User Credentials

401.2 Denied by Server Configuration

401.3 Denied by Resource ACL

401.4 Denied by Custom ISAPI Filter

401.5 Denied by Custom ISAPI/CGI Web Application

Conclusion

401.1 through 401.3 errors are associated with IIS request processing and allow the logical interpretations and assumptions that I listed above.

Meanwhile, the 401.4 and 401.5 errors are the most arbitrary to diagnose since custom ISAPI DLLs and CGI EXE can cause IIS to behave in non-obvious manners. Thus, much of the logical assumptions about 401.x do not apply.

I hope that this information has been useful in deciphering theh 401.x errors from IIS. If you have additional questions, feel free to post a comment or post a private question via the "contact" link.

Recently, we have also released a tool,AuthDiag, to help troubleshoot IIS access denied issues. You can download it fromthis location. In particular, it has a feature to hook in to various failure points in IIS and directly troubleshoot what is failing on a given request - you need to see and try it out!

If you have further questions, let me know.

Best Regards,

Parser Error I got from the server

The website worked on my machine, but after I uploaded it to the server, I get the following error.

Server Error in '/' Application.

---

Parser Error

Description:Anerror occurred during the parsing of a resource required to servicethis request. Please review the following specific parse error detailsand modify your source file appropriately.
Parser Error Message:Could not load file or assembly 'Microsoft.Web.Atlas' or one of its dependencies. The system cannot find the file specified.
Source Error:

[No relevant source lines]

Source File: none Line: 0
Assembly Load Trace: The following information can be helpful to determine why the assembly 'Microsoft.Web.Atlas' could not be loaded.

WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].

---

Version Information: Microsoft .NET Framework Version:2.0.50727.42; ASP.NET Version:2.0.50727.42
--
Does anyone have some idea for this?
Thanks
I get this same error. What could it possibly be?

This is with the new December release. I double checked all my files are on the server, and correct. It is an asp.net 2.0 server.

I'm confused.
Here is the reason for these issues, although different AJAX implementations will give different errors.

I emailed godaddy.com, and sitepuppy.com (which i think is just another frontend for godaddy.), and got this reply from them:

Thank you for contactingCustomer Support. Unfortunately, we do not support the use of the AJAXhandler bundle, although we do have some limited capacity to allow theuse of java scripting. If you need to be able to use AJAX, might Irecommend the dedicated or virtual dedicated server options which wouldallow you to install whatever you like onto the operating system of theserver box. We have to keep the shared hosting servers relativelysimplified for the sake of the many different customers they each hold.We apologize for the inconvenience. Please let us know if we can helpyou in any other way.

Make sure you contact whoever it is you want to have host your sites before you try any implementation of AJAX to play around with.

I have tested, and godaddy does not work with AJAX.NET, and any others (including ATLAS).

(this is with shared hosting, btw).

It should run fine on your server, as long as you also upload Microsoft.Web.Atlas.dll. It doesn't need to be in the GAC (Global Assembly Cache) nor do you need to install anything else outside your webapplication. Just make sure you upload the Microsoft.Web.Atlas.dll inside the /bin directory in the root of your site.
I have a working version ofhttp://how2xbox.com/xbox using swirlhost's AJAX driven chatroom. It works well for the most part and it is on a go daddy hosting account.