Project Pro 2003 Unable to Create Connection

M

Matt Goldencrown

Hi all - I've got an install of Project Server 2003. When I try to
connect with Project Pro 2003 I get "Client failed to create
connection". By following some previous posts, I've determined that
the Named Pipes is the problem (see below). I'm able to work around
the issue by creating a TCP/IP connection to the server on the client
machine with ODBC. MSProjectUser (as is MSProjectServerUser) is a
user in SQL Server with default Project Server installation values.

I've read that if the machine is unable to create a connection to via
Named Pipes (using ODBC) but is able to connect via TCP/IP that it's a
Windows User rights issue. I get the same error from ODBC as Project
Pro when I try to create a connection with Named Pipes using ODBC.

I'm wondering what I can do so I don't have to create a connection on
every client machine via TCP/IP.

Thanks,
Matt
 
M

Matt Goldencrown

One thing I forgot to mention was that this is happening on multiple
machines, not an isolated issue.
 
D

David Gage - Project MVP

Try running cliconfg.exe (no i in config) on the clients and servers, delete
named pipes, and make sure TCP/IP is the only item. Also, make sure TCP/IP
is using the same port number, which is 1433 by default. I believe that
will work as it has for me in the past
 
M

Matt Goldencrown

Dave - The cliconfg worked exactly as described, thank you very much.

Matt
 
Top