Unexpected Server Response

[Charlie]

I give up folks ... I have gone step by step through the single computer
installation guide and ... I received NO errors during the install process.
Still, when all is said and done, I get the following when trying to connect
from MS Project Professional:

"Unexpected Server response.

Project Server has returned an unexpected response. Click the view button to
view the server response as an error page in your browser"

The resultant web page shows this:

"You are not authorized to view this page
You do not have permission to view this directory or page using the
credentials that you supplied because your Web browser is sending a
WWW-Authenticate header field that the Web server is not configured to
accept. "

HTTP error 4.012

Anybody got any ideas?

 

[Scott m Wagner - EPM Consulting Services]

Charlie,

Please try this:
In IIS go to the default web site
Then navigate to the name of the project server web site.
Right click and go to properties.
Go to the security tab and check the box for basic authentication.

Make sure that you have added the project server url to you trusted sites
within Internet Explorer as well.

Let me know if that helps,
Scott

 

[Charlie]

Scott ... thanks for replying, but no it didn't help.

Here's the odd part ... I CAN upload projects (as well as other types of
files) to my sharepoint document share site and it will even let me launch
them with MS Project Pro.

So, I know the intranet site is working. But when I try to collaborate or
publish from Project (after having made changes to the file) I keep getting
the error I mentioned.

It's too bad because I think we could really use this stuff but eventually
my boss is going to pull the plug because I can't deploy the damned thing.
:-(

 

[Scott m Wagner - EPM Consulting Services]

Charlie,

Another thing that I should always check is, what version on Project Server
(sp1, sp2, no service pack?) and what is on the client (SP1, SP2, No service
pack). Note: They must match sp1 for sp1 or sp2a sever for sp2 of client.

A note for your boss, this is a complex system but if you are willing to
take the time to learn and use the system (Or spend the money on a
consultant) its benefits can be extraordinary. I have personally seen how a
small company with 5 PM's has grown to a large company with over 50 PM's and
they attribute much of their success to the EPM Solution.

Scott

 

[Charlie]

Thanks, Scott ... no they match. SP2a on the server copy & sp2 on the client.

My boss is well aware of the benefits but we've got 89 friggin' projects and
a very tiny staff.

Damn, I can feel that I'm close but I just can't get Sharepoint and Project
to "talk" to each other. :-(

 

[JDG]

Hi:

We have had the same problem but with a different twist. This problem
occured after a user had changed their password. MS Project and PWA
didn't recognize their new password. This is what we did:

1. Have the user reboot their P/C.
2. Right after the user logons on have them change their password.
3. Have them open MS Project.

This may not work, but worth a try.

Also did you check to see that in the IE settings under Security that
for the different zones the User Authentication is set to "Automatic
logon with current username and password"

Also you might try lowering the Custom Security settings.

JDG

 

[Charlie]

Thanks for the input ... will try all and get back to you.

 

[Gary L. Chefetz [MVP]]

Charlie:

First, let me re-emphasize Scott's point about professional services. You
don't pull the plug on a technology because an untrained person is failing
to install it correctly. Wait until you get to configuration and use. If you
think a lack of training is difficult now...

With that said, did you install Project Server and WSS both to the default
web site? If so, did you install WSS first or second? If the latter is true,
did you add Project Server to the excluded list in SharePoint's managed
paths?

 

[Charlie]

WSS went in 1st and no I didn't add Project Server to the excluded paths --

Thanks! Will try and this and post here.

By the way, it's not that we are abandoning the technology, it's just that
we've got a million things to do. In all likelihood someone (me) will wind up
at a training course to install this on a large scale.

We just figured we could do the single computer install to check it out ...
kind of quick & dirty.

On the bright side, Sharepoint is working very well and those that have seen
it really like it.
CEL

Charlie:

First, let me re-emphasize Scott's point about professional services. You
don't pull the plug on a technology because an untrained person is failing
to install it correctly. Wait until you get to configuration and use. If you
think a lack of training is difficult now...

With that said, did you install Project Server and WSS both to the default
web site? If so, did you install WSS first or second? If the latter is true,
did you add Project Server to the excluded list in SharePoint's managed
paths?

 

[Charlie]

OK Gary ... now HERE's a gem for you.

I've uploaded various documents to the Shared Documents folder on the
SharePoint site. Excel, Word, Project, you name it.

ALL of the documents can be edited AND saved to that Sharepoint site,
including MS-Project. So that's good.

Now, when I load MS-Project Pro and try to use either the collaborate or
test the Enterprise Options, I continue to receive the "unexpected server
response" message.

Clearly, I am able to communicate with Sharepoint or how would I edit and
save there? I'm beginning to think my problem is on the SQL side now.
Afterall, if I can launch a single MPP from SharePoint, edit it with
MS-Project, then resave ... but can't collaborate, my guess is that my
connection between Project Server and SQL is fubar.

Do I sound like I'm reading this right and ... more importantly ... do you
have any thoughts?

Thanks!
--
CEL

Charlie:

First, let me re-emphasize Scott's point about professional services. You
don't pull the plug on a technology because an untrained person is failing
to install it correctly. Wait until you get to configuration and use. If you
think a lack of training is difficult now...

With that said, did you install Project Server and WSS both to the default
web site? If so, did you install WSS first or second? If the latter is true,
did you add Project Server to the excluded list in SharePoint's managed
paths?

 

[Gary L. Chefetz [MVP]]

Charlie:

In the current iteration of Project Server, SharePoint is an adjunct
technology. Your post makes it sound like you believe that it's the core of
Project Server, which is incorrect. Please read the following FAQ:

http://www.projectserverexperts.com/Shared Documents/CreatePMLoginAccount.htm

Let us know if you've done this already. This is the first step you need to
take before you can access Project Server after you install it. I also
suggest that you look at our upcoming on-line classes listed on the home
page. These will surely help you through the DIY process.

 

[Charlie]

Thanks again ... very helpful ... I appreciate it.

 

[Bruce]

We are currently having the same issue on our project server if we use
any other group then "authenticated users" on the "C:\ProjServ\IIS
Virtual Root" folder. Changing it back to "authenticates users"