Ureader.com  
Microsoft software help and Community
   home   |   control panel login   |   archive   |  
 
other
informationbridge
office.intranets
office.misc
office.setup
office.xml
officeupdate
onenote
photodraw.discussion
powerpoint
producer
proj.standard&server
project
project.developer
project.pro_and_serve
project.server
project.vba
project2000
publisher
publisher.prepress
publisher.programming
publisher.webdesign
visio
visio.createshapes
visio.database.modeling
visio.dev.diagrams
visio.dev.shapesheet
visio.dev.vba
visio.dev.vc
visio.developer
visio.general
visio.installation
visio.printing
visio.software.modeling
visio.troubleshoot
  
 
date: Fri, 10 Oct 2008 11:25:01 -0700,    group: microsoft.public.project.server        back       


Cannot access Project Server 2007 - HTTP 503 Service Unavailable   
My Project 2007 Server installation was done in a way so that it is accessed 
through an existing SharePoint site.  The site http://staff comes up 
beautifully with no issues and everything is functioning normally.  However, 
when I navigate to http://staff/project server, I receive the following 
errors:

Web:
Server Error in '/' Application.
--------------------------------------------------------------------------------

The request failed with HTTP status 503: Service Unavailable. 
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 503: Service Unavailable.

Source Error: 

The source code that generated this unhandled exception can only be shown 
when compiled in debug mode. To enable this, please follow one of the below 
steps, then request the URL:

1. Add a "Debug=true" directive at the top of the file that generated the 
error. Example:

  <%@ Page Language="C#" Debug="true" %>

or:

2) Add the following section to the configuration file of your application:

<configuration>
   <system.web>
       <compilation debug="true"/>
   </system.web>
</configuration>

Note that this second technique will cause all files within a given 
application to be compiled in debug mode. The first technique will cause only 
that particular file to be compiled in debug mode.

Important: Running applications in debug mode does incur a 
memory/performance overhead. You should make sure that an application has 
debugging disabled before deploying into production scenario.  

Stack Trace: 


[WebException: The request failed with HTTP status 503: Service Unavailable.]
   Microsoft.Office.Project.PWA.PJContext.AuthenticateUserForPWA(Boolean 
validateUser, String username, Boolean checkTimebomb) +1639
   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() +273
   ASP.DEFAULT_ASPX_529955207..ctor() +10
   
__ASP.FastObjectFactory_app_web_default_aspx_529955207_5zlr54aw.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.GetHandler(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.IExecutionStep.Execute() +120
   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& 
completedSynchronously) +155

Event Logs:
Event Type:	Warning
Event Source:	ASP.NET 2.0.50727.0
Event Category:	Web Event 
Event ID:	1309
Date:		10/10/2008
Time:		11:06:25 AM
User:		N/A
Computer:	PORTAL
Description:
Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 10/10/2008 11:06:25 AM 
Event time (UTC): 10/10/2008 6:06:25 PM 
Event ID: 5d8a48c1cd1f40eeb86120cf2115e449 
Event sequence: 4 
Event occurrence: 1 
Event detail code: 0 
 
Application information: 
    Application domain: /LM/W3SVC/308997166/Root-1-128681355695117864 
    Trust level: WSS_Minimal 
    Application Virtual Path: / 
    Application Path: C:\Inetpub\wwwroot\wss\VirtualDirectories\Staff80\ 
    Machine name: PORTAL 
 
Process information: 
    Process ID: 2560 
    Process name: w3wp.exe 
    Account name: ABR\administrator 
 
Exception information: 
    Exception type: WebException 
    Exception message: The request failed with HTTP status 503: Service 
Unavailable. 
 
Request information: 
    Request URL: http://staff/projectserver/default.aspx 
    Request path: /projectserver/default.aspx 
    User host address: 207.182.39.117 
    User: ABR\cdinsmore 
    Is authenticated: True 
    Authentication Type: NTLM 
    Thread account name: ABR\administrator 
 
Thread information: 
    Thread ID: 1 
    Thread account name: ABR\administrator 
    Is impersonating: True 
    Stack trace:    at 
Microsoft.Office.Project.PWA.PJContext.AuthenticateUserForPWA(Boolean 
validateUser, String username, Boolean checkTimebomb)
   at Microsoft.Office.Project.PWA.PJContext.AuthenticateUserForPWA(Boolean 
newCookie)
   at Microsoft.Office.Project.PWA.PJContext.GetContext(Boolean 
isWebServiceCall, Boolean newCookie, Guid siteId, Nullable`1 zone)
   at Microsoft.Office.Project.PWA.PJBaseWebPartPage..ctor()
   at ASP.DEFAULT_ASPX_529955207..ctor()
   at 
__ASP.FastObjectFactory_app_web_default_aspx_529955207_5zlr54aw.Create_ASP_DEFAULT_ASPX_529955207()
   at System.Web.Compilation.BuildResultCompiledType.CreateInstance()
   at 
System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath 
virtualPath, Type requiredBaseType, HttpContext context, Boolean 
allowCrossApp, Boolean noAssert)
   at System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, 
String requestType, VirtualPath virtualPath, String physicalPath)
   at 
System.Web.UI.PageHandlerFactory.System.Web.IHttpHandlerFactory2.GetHandler(HttpContext 
context, String requestType, VirtualPath virtualPath, String physicalPath)
   at System.Web.HttpApplication.MapHttpHandler(HttpContext context, String 
requestType, VirtualPath path, String pathTranslated, Boolean useAppConfig)
   at 
System.Web.HttpApplication.MapHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
   at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& 
completedSynchronously)
 
 
Custom event details: 

For more information, see Help and Support Center at 
http://go.microsoft.com/fwlink/events.asp.

Event Type:	Error
Event Source:	Office SharePoint Server
Event Category:	Office Server General 
Event ID:	7888
Date:		10/10/2008
Time:		11:06:25 AM
User:		N/A
Computer:	PORTAL
Description:
A runtime exception was detected. Details follow. 
Message: The request failed with HTTP status 503: Service Unavailable.

Techinal Details:
System.Net.WebException: The request failed with HTTP status 503: Service 
Unavailable.
   at 
Microsoft.Office.Project.Server.PSIAuth.Authentication.GetUserByName(Boolean 
isProjUser, String username)
   at Microsoft.Office.Project.PWA.PJContext.AuthenticateUserForPWA(Boolean 
validateUser, String username, Boolean checkTimebomb)

For more information, see Help and Support Center at 
http://go.microsoft.com/fwlink/events.asp.

Event Type:	Error
Event Source:	Office SharePoint Server
Event Category:	Office Server General 
Event ID:	7888
Date:		10/10/2008
Time:		11:06:25 AM
User:		N/A
Computer:	PORTAL
Description:
A runtime exception was detected. Details follow. 
Message: The request failed with HTTP status 503: Service Unavailable.

Techinal Details:
System.Net.WebException: The request failed with HTTP status 503: Service 
Unavailable.
   at 
System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall)
   at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String 
methodName, Object[] parameters)
   at 
Microsoft.Office.Project.Server.PSIAuth.Authentication.GetUserByName(Boolean 
isProjUser, String username)

For more information, see Help and Support Center at 
http://go.microsoft.com/fwlink/events.asp.


I can tell you that several account passwords were changed recently due to a 
security issue.  It appears that the project server worker threads do not 
have the correct password, but I have yet to find out where I should go to 
change those....  Any help would be greatly appreciated.
date: Fri, 10 Oct 2008 11:25:01 -0700   author:   Christianne

Re: Cannot access Project Server 2007 - HTTP 503 Service Unavailable   
Hi

Your Web server is currently unable to handle the HTTP request due to
a temporary overloading or maintenance of the server. The implication
is that this is a temporary condition which will be alleviated after
some delay. Some servers in this state may also simply refuse the
socket connection, in which case a different error may be generated
because the socket creation timed out.

Any client (e.g. your Web browser) goes through the following cycle
when it communicates with your Web server:

Obtain an IP address from the IP name of your site (your site URL
without the leading 'http://'). This lookup (conversion of IP name to
IP address) is provided by domain name servers (DNSs).
Open an IP socket connection to that IP address.
Write an HTTP data stream through that socket.
Receive an HTTP data stream back from your Web server in response.
This data stream contains status codes whose values are determined by
the HTTP protocol. Parse this data stream for status codes and other
useful information.
This error occurs in the final step above when the client receives an
HTTP status code that it recognises as '503'.

A typical workaroud in case of Project Server is to close the web
services and restart IIS. Hope, you have tried this out:)

Ajit
www.epmguru.com
date: Fri, 10 Oct 2008 18:20:58 -0700 (PDT)   author:   Aj

Re: Cannot access Project Server 2007 - HTTP 503 Service Unavailab   
Yes, I have closed web services and restarted IIS, but I am still receiving 
the same errors as above.
date: Mon, 13 Oct 2008 10:07:01 -0700   author:   Christianne

RE: Cannot access Project Server 2007 - HTTP 503 Service Unavailable   
> 
> 
> I can tell you that several account passwords were changed recently due to a 
> security issue.  It appears that the project server worker threads do not 
> have the correct password, but I have yet to find out where I should go to 
> change those....  Any help would be greatly appreciated.

hi Christianne,

have you been able to solve this yet? As you state that account passwords 
have changed, this would be your problem indeed. You can check this in IIS 
Manager. Expand the Local computer node and then select teh 'application 
pools'. You will probably see one or more application pool that is not on 
'running' state. Double click the pool name to check wich identity this pool 
runs on. Do not change it in this screen. It needs to be changed through 
sharepoint central administration or stsadm tool. 
First let us know how the situation is.

regards
Sander
date: Wed, 15 Oct 2008 05:26:00 -0700   author:   Sander

RE: Cannot access Project Server 2007 - HTTP 503 Service Unavailab   
No, I haven't found a way to resolve this issue as of yet.

The application pools are running with the correct identity.
date: Wed, 15 Oct 2008 10:10:15 -0700   author:   Christianne

RE: Cannot access Project Server 2007 - HTTP 503 Service Unavailab   
hmm... if all pools are still running, then there is need for more information.
Is the event log from the server giving any errors that connects with this?
Maybe also worth to have a look at
http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/55f71614-ef1b-4015-b9c8-a42c1e700c25.mspx?mfr=true

and see if there is some extra information on the error it self.

Sander

"Christianne" wrote:

> No, I haven't found a way to resolve this issue as of yet.
> 
> The application pools are running with the correct identity.
date: Thu, 16 Oct 2008 00:12:01 -0700   author:   Sander

RE: Cannot access Project Server 2007 - HTTP 503 Service Unavailab   
I have the same issue. My app pools are running. I get this if I go directly 
through our f5 pools. do you have any other info on this?

"Sander" wrote:

> hmm... if all pools are still running, then there is need for more information.
> Is the event log from the server giving any errors that connects with this?
> Maybe also worth to have a look at
> http://www.microsoft.com/technet/prodtechnol/WindowsServer2003/Library/IIS/55f71614-ef1b-4015-b9c8-a42c1e700c25.mspx?mfr=true
> 
> and see if there is some extra information on the error it self.
> 
> Sander
> 
> "Christianne" wrote:
> 
> > No, I haven't found a way to resolve this issue as of yet.
> > 
> > The application pools are running with the correct identity.
date: Mon, 3 Nov 2008 10:21:01 -0800   author:   Tim C. Tim

Google
 
Web ureader.com


    COPYRIGHT 2007, YARDI TECHNOLOGY LIMITED, ALL RIGHT RESERVE  |   contact us