Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Server Error in '/' Application. The request failed with HTTP status

  Asked By: Nagendra    Date: Dec 26    Category: MOSS    Views: 4929

I have 3 project web sites on medium size SharePoint 2007 farm. On
each of them the default.aspx page is displaying this error:
____________________________________________________________
Server Error in '/' Application.
The request failed with HTTP status 401: Unauthorized.
Description: An unhandled exception occurred during the execution of
the current web request. Please review the stack trace for more
information about the error and where it originated in the code.

Exception Details: System.Net.WebException: The request failed with
HTTP status 401: Unauthorized.
_________________________________________________________________

I can hit other pages in the SharePoint site.

I cannot connect to the Project Server with a client.
_________________________________________________________________

The web front end is displaying this error from the server
application log file:

Event Type: Warning
Event Source: ASP.NET 2.0.50727.0
Event Category: Web Event
Event ID: 1309
Event code: 3005
Event message: An unhandled exception has occurred.
__________________________________________________________
STACK TRACE (from web page):
[WebException: The request failed with HTTP status 401: Unauthorized.]
Microsoft.Office.Project.PWA.PJContext.AuthenticateUserForPWA
(Boolean validateUser, String username, Boolean checkTimebomb) +1659
Microsoft.Office.Project.PWA.PJContext.AuthenticateUserForPWA
(Boolean newCookie) +877
Microsoft.Office.Project.PWA.PJContext.GetContext(Boolean
isWebServiceCall, Boolean newCookie, Guid siteId, Nullable`1 zone)
+368
Microsoft.Office.Project.PWA.PJBaseWebPartPage..ctor() +285
ASP.DEFAULT_ASPX_529955207..ctor() +10

__ASP.FastObjectFactory_app_web_default_aspx_529955207_jejodxir.Create
_ASP_DEFAULT_ASPX_529955207() +20
System.Web.Compilation.BuildResultCompiledType.CreateInstance() +49
System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath
(VirtualPath virtualPath, Type requiredBaseType, HttpContext context,
Boolean allowCrossApp, Boolean noAssert) +115
System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext
context, String requestType, VirtualPath virtualPath, String
physicalPath) +31

System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHa
ndler(HttpContext context, String requestType, VirtualPath
virtualPath, String physicalPath) +40
System.Web.HttpApplication.MapHttpHandler(HttpContext context,
String requestType, VirtualPath path, String pathTranslated, Boolean
useAppConfig) +139

System.Web.MapHandlerExecutionStep.System.Web.HttpApplication.IExecuti
onStep.Execute() +128
System.Web.HttpApplication.ExecuteStep(IExecutionStep step,
Boolean& completedSynchronously) +161

Share: 

 

5 Answers Found

 
Answer #1    Answered By: Arti Patel     Answered On: Dec 26

Please check with your permission levels with in the
sharepoint site .I meant to say whether are you adminstrator of the site or
full control over the site .

 
Answer #2    Answered By: Claire May     Answered On: Dec 26

I am a full control administer on the
SharePoint Portal and on the Project Site, and within the Project
administration settings.

The sites  were all working for about 2 months, and then mysteriously
started failing with this error.

The Web server  Application log error  indicates the service account
for the SSP application  pool:

Trust level: Full
Application Virtual Path: /
Application Path: C:\Inetpub\wwwroot\wss\VirtualDirectories\tmss\
Machine name: %frontendwebserver%

Process information:
Process ID: 2692
Process name: w3wp.exe
Account name: %applicationPoolAcct%

 
Answer #3    Answered By: Dan Dickerson     Answered On: Dec 26

Is it possible that one of your service accounts on the farm may in
fact have a password that expired? That would account why life was
good for 2 months then it died. I am thinking of farm accounts, search
accounts, etc.

 
Answer #4    Answered By: Phenil Poriya     Answered On: Dec 26

Check to make sure the application  pools are running correctly and that
those accounts have the necessary permissions

 
Answer #5    Answered By: Dante Parsons     Answered On: Dec 26

Additionally, where there any funky or custom web  parts added to the default
page or perhaps the master.default page? You may have to open the default
page in maintenance mode and close the offending webpart or remove any
custom code. It could also be a file permission issue (i.e.
inpub/wwwroot/virtualdirectories/wss/80/) or an IIS specific setting.

Check the IIS logs in c:\windows\system32\logfiles\<id number of your moss
site> and see what it says.

 




Tagged: