'07 PWA Issue - 'unexpected error'

[GaRchitect]

Hello;

We are experiencing an interesting issue with our PWA site "suddenly". We
recently released a new QA install of Project Server 2007 w/MOSS 07 on a 4
server farm (two front-end, two back-end) to our applications group. The
site was functional at release time, but sometime between "then" and now, the
site has become unusable. When visiting the page, the generic "unexpected
error" catch-all page is displayed. Some digging into the logs garners me
the following.

02/26/2007 12:48:22.31 w3wp.exe (0x0950)
0x0770 Project Server Project Server - General
8mqe Exception System.Web.Services.Protocols.SoapException: Server was
unable to process request. ---> Object reference not set to an instance of an
object. 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)

This error repeats several times with no other information. There are no
known issues with any of the other Sharepoint sites (including Shared
Services admin, Central Admin, and the main string of sites and subsites that
have recently been created). The database server is available and I've
confirmed connectivity with the account that PWA uses. The error is
universal for every user that we've tried.

I'm continuing to dig (I'll probably turn on more verbose logging to see if
I can further isolate the issue), but if any of you good folks have
suggestions, they would be much appreciated.

I've googled it, searched here, and come up with nothing.

Thanks a ton for any insight.

--Brad Watson
Dematic Corp, Grand Rapids MI

 

[Boaz Lev [MSFT]]

Are you connecting to the page as a different user than you used to use? If
you can provide some more info on set up etc. that would be helpful

Thanks,

 

[GaRchitect]

All our QA users (confirmed with ~8 accounts) are getting the error and I am
not using a different user. Not sure what details you need, but here's a
quick run-down.

2 front-end servers for web access (I've taken it down to one to make sure
that we're isolating the problem)

2 back-end servers for Project applications

2 front-ends have MOSS Standard 07 loaded. 2 back-ends just have WSS 3.
The front-ends are "clustered" using WNLB.

All DB's are on a clustered SQL 2005, single instance.

All other Sharepoint sites are working fine (we have an intranet CMS and a
wiki mocked up).

Just not sure where to look next...

Thanks for the help.

--Brad

Are you connecting to the page as a different user than you used to use? If
you can provide some more info on set up etc. that would be helpful

Thanks,

Hello;

We are experiencing an interesting issue with our PWA site "suddenly". We
recently released a new QA install of Project Server 2007 w/MOSS 07 on a 4
server farm (two front-end, two back-end) to our applications group. The
site was functional at release time, but sometime between "then" and now,
the
site has become unusable. When visiting the page, the generic "unexpected
error" catch-all page is displayed. Some digging into the logs garners me
the following.

02/26/2007 12:48:22.31 w3wp.exe (0x0950)
0x0770 Project Server Project Server - General
8mqe Exception System.Web.Services.Protocols.SoapException: Server was
unable to process request. ---> Object reference not set to an instance of
an
object. 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)

This error repeats several times with no other information. There are no
known issues with any of the other Sharepoint sites (including Shared
Services admin, Central Admin, and the main string of sites and subsites
that
have recently been created). The database server is available and I've
confirmed connectivity with the account that PWA uses. The error is
universal for every user that we've tried.

I'm continuing to dig (I'll probably turn on more verbose logging to see
if
I can further isolate the issue), but if any of you good folks have
suggestions, they would be much appreciated.

I've googled it, searched here, and come up with nothing.

Thanks a ton for any insight.

--Brad Watson
Dematic Corp, Grand Rapids MI

 

[GaRchitect]

Hello Mr Lev;

I have identified what the issue was. I'm not sure why, but both the
"Draft" and "Published" databases were offline (all the others were online)
for that Project site. I brought them both back online and now the site
starts. Very odd problem and sorry for the bother, but it really should be
communicated to the devs that if databases are offline, a more descriptive
error would certainly be helpful (and stop folks like me from bothering folks
like you).

Thanks a lot for your time and hopefully this bit of info will help someone
else.

--Brad

Are you connecting to the page as a different user than you used to use? If
you can provide some more info on set up etc. that would be helpful

Thanks,

Hello;

We are experiencing an interesting issue with our PWA site "suddenly". We
recently released a new QA install of Project Server 2007 w/MOSS 07 on a 4
server farm (two front-end, two back-end) to our applications group. The
site was functional at release time, but sometime between "then" and now,
the
site has become unusable. When visiting the page, the generic "unexpected
error" catch-all page is displayed. Some digging into the logs garners me
the following.

02/26/2007 12:48:22.31 w3wp.exe (0x0950)
0x0770 Project Server Project Server - General
8mqe Exception System.Web.Services.Protocols.SoapException: Server was
unable to process request. ---> Object reference not set to an instance of
an
object. 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)

This error repeats several times with no other information. There are no
known issues with any of the other Sharepoint sites (including Shared
Services admin, Central Admin, and the main string of sites and subsites
that
have recently been created). The database server is available and I've
confirmed connectivity with the account that PWA uses. The error is
universal for every user that we've tried.

I'm continuing to dig (I'll probably turn on more verbose logging to see
if
I can further isolate the issue), but if any of you good folks have
suggestions, they would be much appreciated.

I've googled it, searched here, and come up with nothing.

Thanks a ton for any insight.

--Brad Watson
Dematic Corp, Grand Rapids MI

 

[Boaz Lev [MSFT]]

Folks like me at not too bothered by folks like you I am happy that you
solved your problem. There is one place I would suspect the proper error
message would be put, and that would be in the log files (not the event
viewer, but the log files that Project Server creates and dumps informationt
to). If you can't find the error message there, I will gladly take this
feedback and see if we can improve that (this, of course, is said with all
the legalese in place as I am, unfortunately, not the only one that decides
what will be available in the next release ).

Hello Mr Lev;

I have identified what the issue was. I'm not sure why, but both the
"Draft" and "Published" databases were offline (all the others were
online)
for that Project site. I brought them both back online and now the site
starts. Very odd problem and sorry for the bother, but it really should
be
communicated to the devs that if databases are offline, a more descriptive
error would certainly be helpful (and stop folks like me from bothering
folks
like you).

Thanks a lot for your time and hopefully this bit of info will help
someone
else.

--Brad

Are you connecting to the page as a different user than you used to use?
If
you can provide some more info on set up etc. that would be helpful

Thanks,

Hello;

We are experiencing an interesting issue with our PWA site "suddenly".
We
recently released a new QA install of Project Server 2007 w/MOSS 07 on
a 4
server farm (two front-end, two back-end) to our applications group.
The
site was functional at release time, but sometime between "then" and
now,
the
site has become unusable. When visiting the page, the generic
"unexpected
error" catch-all page is displayed. Some digging into the logs garners
me
the following.

02/26/2007 12:48:22.31 w3wp.exe (0x0950)
0x0770 Project Server Project Server - General
8mqe Exception System.Web.Services.Protocols.SoapException: Server was
unable to process request. ---> Object reference not set to an instance
of
an
object. 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)

This error repeats several times with no other information. There are
no
known issues with any of the other Sharepoint sites (including Shared
Services admin, Central Admin, and the main string of sites and
subsites
that
have recently been created). The database server is available and I've
confirmed connectivity with the account that PWA uses. The error is
universal for every user that we've tried.

I'm continuing to dig (I'll probably turn on more verbose logging to
see
if
I can further isolate the issue), but if any of you good folks have
suggestions, they would be much appreciated.

I've googled it, searched here, and come up with nothing.

Thanks a ton for any insight.

--Brad Watson
Dematic Corp, Grand Rapids MI

 

[GaRchitect]

Thanks. I wasn't able to find any exceptions in the logs for the
databases (the entry I found below was from the log files (not event viewer).
I even turned on more verbose logging for Project Server and the only thing
in the logs for Project was the error from my first post.

It's certainly possible that I'm missing something along the way (I have
been looking cross-eyed at this problem for a couple of days now), but in
depth searches of the logs have only turned up the single error, repeated
several times.

Thanks for the positive feedback and have a good week.

--Brad

Folks like me at not too bothered by folks like you I am happy that you
solved your problem. There is one place I would suspect the proper error
message would be put, and that would be in the log files (not the event
viewer, but the log files that Project Server creates and dumps informationt
to). If you can't find the error message there, I will gladly take this
feedback and see if we can improve that (this, of course, is said with all
the legalese in place as I am, unfortunately, not the only one that decides
what will be available in the next release ).

Hello Mr Lev;

I have identified what the issue was. I'm not sure why, but both the
"Draft" and "Published" databases were offline (all the others were
online)
for that Project site. I brought them both back online and now the site
starts. Very odd problem and sorry for the bother, but it really should
be
communicated to the devs that if databases are offline, a more descriptive
error would certainly be helpful (and stop folks like me from bothering
folks
like you).

Thanks a lot for your time and hopefully this bit of info will help
someone
else.

--Brad

Are you connecting to the page as a different user than you used to use?
If
you can provide some more info on set up etc. that would be helpful

Thanks,

Hello;

We are experiencing an interesting issue with our PWA site "suddenly".
We
recently released a new QA install of Project Server 2007 w/MOSS 07 on
a 4
server farm (two front-end, two back-end) to our applications group.
The
site was functional at release time, but sometime between "then" and
now,
the
site has become unusable. When visiting the page, the generic
"unexpected
error" catch-all page is displayed. Some digging into the logs garners
me
the following.

02/26/2007 12:48:22.31 w3wp.exe (0x0950)
0x0770 Project Server Project Server - General
8mqe Exception System.Web.Services.Protocols.SoapException: Server was
unable to process request. ---> Object reference not set to an instance
of
an
object. 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)

This error repeats several times with no other information. There are
no
known issues with any of the other Sharepoint sites (including Shared
Services admin, Central Admin, and the main string of sites and
subsites
that
have recently been created). The database server is available and I've
confirmed connectivity with the account that PWA uses. The error is
universal for every user that we've tried.

I'm continuing to dig (I'll probably turn on more verbose logging to
see
if
I can further isolate the issue), but if any of you good folks have
suggestions, they would be much appreciated.

I've googled it, searched here, and come up with nothing.

Thanks a ton for any insight.

--Brad Watson
Dematic Corp, Grand Rapids MI