segunda-feira, 7 de maio de 2012 18:43Dear Good afternoon.
I have following error when trying to connect the Client Project.
Can not connect
Microsoft Project was unable to connect to Microsoft Project Server selected. This can be caused by a loss of network connectivity, invalid user name or password, the lack of a global model of the company, problems with Microsoft Project Server or database or Microsoft Project Server enterprise resource has not enabled
Todas as Respostas
segunda-feira, 7 de maio de 2012 18:45
segunda-feira, 7 de maio de 2012 18:59
I have two Project Server 2003 environments:
1 - The first environment all users giving this problem is giving this problem of authentication.
2 - The second environment only a few users have this connection problem.
segunda-feira, 7 de maio de 2012 19:03
terça-feira, 8 de maio de 2012 05:06
Please see a below support article for PS2003 for the issue resolution:
Thanks, Amit Khare |EPM Consultant| Blog: http://amitkhare82.blogspot.com http://www.linkedin.com/in/amitkhare82
terça-feira, 8 de maio de 2012 13:19
With the admin user is running a perfect connection.
I'm doing some testing to see the problem and I am following with question marks:
It is worth noting again that the problem is happening with few users, the rest is OK.
But what draws the most attention is that if this user is having trouble accessing the PWA access it normally, if he log into another workstation normally connects the professional project, but the machine the person does not access the project professional.
And in other cases the user can also access the PWA, but can not connect to project server utlizando the professional project him at the station and not at another station.
Screenshot of error:
Test connection from the account of professional project in project server on the same machine with the same user of the previous message:
quarta-feira, 9 de maio de 2012 17:19Proprietário
If I understand correctly Hezequias you are saying that a user who cannot connect from his own machine can go to another machine and it works ok. This looks like all the permissions are OK in Project Server, but that for some reason the communication is not happening from specific computers. Could be a local firewall or perhaps some components have been updated? I think you would need to compare the machines to see what is different.
quarta-feira, 9 de maio de 2012 17:55
Thanks for the info.
I'll make that determination in the environment in 2003 and put the result here.
Thanks for the help.
quinta-feira, 10 de maio de 2012 11:39
Can you compare the software installed to see if both have SP3, Microsoft .NET Framework (1.1 , 2 , or above - this is visual studio components) ?
Ofir Marco , MCTS P.Z. Projects
quinta-feira, 10 de maio de 2012 11:49
Hello Marco good morning.
I'm with the necessary updates recommended by Microsoft properly installed including SP3.
I do not know if you ever run into this scenario.
Let me give the example of my username:
My user name is administrator of the domain, I access the project web access normally, but my professional project is experiencing the above mentioned error.
I testing the connection project professional 2003 and the same reports that the connection has been successfully tested as also the image of the previous post.
I created a test machine that is running windows xp professional 2003 and the project completely updated and the problem continues.
Permission at the firewall is not on the internal network because everyone has free access on this server.
I'm having difficulty solving the problem ...... as a test and I have created a server with the project approval, new installation and I can connect normally.
The worst thing is that this problem is occurring in a production environment
sexta-feira, 11 de maio de 2012 21:45Proprietário
We will be making different connections between Project Professional and the server than we do from just PWA - so it could still be a networking or firewall issue - potentially access to SQL Server. If your new test system worked OK then I would compare a netmon trace between your client and the new server to a trace between your client and the production server and see if that shows some blockage. Best to opena support incident with Microsoft if you need further assistance with this.
- Sugerido como Resposta PWMatherMVP domingo, 13 de maio de 2012 15:21
quarta-feira, 16 de maio de 2012 12:23
Can not resolve the problem, but more calmly analyzing it can be related to timeout.Vou redo the installation and once you have solve the problem but will open a new post.
Thank you all for your help.
- Marcado como Resposta Hezequias Vasconcelos quarta-feira, 16 de maio de 2012 12:24