Login Failed. Project could not connect to server

[Robert]

Hello,
Project Server 2007 SP1

I just installed the SP2 of Windows Server 2003: so now I'm not able to
connect Project Pro 2007 directly on the server. I get the message box :
"Login Failed. Project could not connect to server. Please check your
username and password and try again."

But I can connect from PWA without any problem. and while I'm connected via
PWA, The connection from Project Pro works fine too!!!!

Any idea ?

 

[Frank J.]

Have similar isse here.

I am set up as the administrator of Project Server (2007 w/SP1)

I can open up Project Pro on my local system and connect to the Project
Server.

I can open up PWA and see all projects and do admisistrative functions
(Server Settings).

However, if I try to open (edit) a project via the PWA interface I get same
message.

This just started this week.... will need to check with Technical team is
same patch was jus applied

Frank j.

 

[Brooks, Jason]

We just saw this too with a fresh install of Project Server 2007 on Server
2003 R2 SP2.

I can log in via web, but not via the Project Profession 2007 client. When
looking at the web server logs, all I see are 401s. I suspect there's
something AD related awry on the Project Server install - I see auth errors
in Event Viewer saying that the domain id doesn't exist.

Anything similar elsewhere on your end?

Jason

 

[Backtrack]

Hello,
we are facing the same problem.
Access via web PWA works fine but not via Project Professional 2007.
We have another instance of the PS with the same PS databses on a test
machine and there it works fine.
Can't figure out why.

Anybody found a solution?

Andrew

 

[Gérard Ducouret]

Hello,

I had the same problem. It was solved by the uninstall of Norton Internet
Security!

Gérard Ducouret

 

[Backtrack]

Thanks for answering!
fortunately we don't use Symantec products.
However I can't see as an antivirus/firewall problem.
Other instances of PS work fine.

 

[Backtrack]

I found the difference between the test installation and the live.
The first one uses ntlm the second one Kerberos.
So I guess the problem must reside in Kerberos authentication direction

 

[Backtrack]

we solved. after some testing.
it was not kerberos.
It was the SSL certificate, we were using an internally created one by our CA.
We tried with a real one, like Comodo and it worked.
damn it! how much wasted time!