HELP!! Project Pro 2003 to Project Server Error on Connection

[Chris Moran]

HELP!

I have seen several questions on this problem but no definate answers. Here
is the scenario:

Single Server Installation
Windows Server 2003
SQL 200 Sp3a
Project Server SP1
Sharepoint Services
MDAC 2.8

Client Machines are all Windows XP SP2, MDAC 2.8, Project Professional 2003
SP1.

Office is stateside, the remote office is in AK. Clients in the remote
office, when trying to log into the server through project professional
recieve the following error message after what appears to be a timeout on the
CLIENT SIDE:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

The server timeout is unlimitedm, and these same computers can log in
stateside just fine.

I have read and followed the instructions in the MS KB Article Article ID :
837653
http://support.microsoft.com/?scid=kb;en-us;837653&spid=2525&sid=216

I think that this is a client side timeout. Is there any fix for this.

My Anchorage people can't use this great system until I get this resolved.

 

[Earl Lewis]

It's often suggested to use Terminal Services for this kind of arrangement. It's a viable option that you might want to look at. Basically, clients in AK do a remote desktop connection to a machine at the home office that has project professional and terminal services installed on it. The terminal services machine talks locally to the project server installation and the remote clients only have to worry about being able to run a terminal session.

Another thing to think about is that these people are probably in different Windows domains, if they're in domains at all. This can cause problems. Here's a few things to check.

Make sure the project server URL is entered using a fully qualified domain name in the trusted sites list for the clients IE configuration.

Add an entry in the DNS suffix list of the IP configuration settings that will resolve the hostname to the home office domain, i.e. if the home office domain is the.company.com, add the.company.com to the DNS suffix list. This will allow the network names to resolve.

Let us know how you make out.

Earl


HELP!

I have seen several questions on this problem but no definate answers. Here
is the scenario:

Single Server Installation
Windows Server 2003
SQL 200 Sp3a
Project Server SP1
Sharepoint Services
MDAC 2.8

Client Machines are all Windows XP SP2, MDAC 2.8, Project Professional 2003
SP1.

Office is stateside, the remote office is in AK. Clients in the remote
office, when trying to log into the server through project professional
recieve the following error message after what appears to be a timeout on the
CLIENT SIDE:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

The server timeout is unlimitedm, and these same computers can log in
stateside just fine.

I have read and followed the instructions in the MS KB Article Article ID :
837653
http://support.microsoft.com/?scid=kb;en-us;837653&spid=2525&sid=216

I think that this is a client side timeout. Is there any fix for this.

My Anchorage people can't use this great system until I get this resolved.

 

[ddrhodes]

And, there is always a possibility that sql port 1433 is blocked at the
firewall level across domains. Therefore, use of a vpn tunneling software is
possible; however, using project pro with terminal services is your best
option.

It's often suggested to use Terminal Services for this kind of arrangement. It's a viable option that you might want to look at. Basically, clients in AK do a remote desktop connection to a machine at the home office that has project professional and terminal services installed on it. The terminal services machine talks locally to the project server installation and the remote clients only have to worry about being able to run a terminal session.

Another thing to think about is that these people are probably in different Windows domains, if they're in domains at all. This can cause problems. Here's a few things to check.

Make sure the project server URL is entered using a fully qualified domain name in the trusted sites list for the clients IE configuration.

Add an entry in the DNS suffix list of the IP configuration settings that will resolve the hostname to the home office domain, i.e. if the home office domain is the.company.com, add the.company.com to the DNS suffix list. This will allow the network names to resolve.

Let us know how you make out.

Earl


HELP!

I have seen several questions on this problem but no definate answers. Here
is the scenario:

Single Server Installation
Windows Server 2003
SQL 200 Sp3a
Project Server SP1
Sharepoint Services
MDAC 2.8

Client Machines are all Windows XP SP2, MDAC 2.8, Project Professional 2003
SP1.

Office is stateside, the remote office is in AK. Clients in the remote
office, when trying to log into the server through project professional
recieve the following error message after what appears to be a timeout on the
CLIENT SIDE:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

The server timeout is unlimitedm, and these same computers can log in
stateside just fine.

I have read and followed the instructions in the MS KB Article Article ID :
837653
http://support.microsoft.com/?scid=kb;en-us;837653&spid=2525&sid=216

I think that this is a client side timeout. Is there any fix for this.

My Anchorage people can't use this great system until I get this resolved.

--
Chris Moran
Operations Program Manager
TASMCO Communications
an ESSI Company

 

[Chris Moran]

I am seriously considering a Citrix server for this. I captured the packets
from both a successful remote and the clients in Anchorage and it looks like
the client is responding to the initial "handshake" of the login, but then
not responding to the sql server after the login. I am going to try adding
the dns suffix and using the fully qualified domain name for the enterprise
account on the client side today. I will let you know how it turns up.

Thanks for your help and if you have any other suggestions please let me know.

I wish there was a way to increase the timeout on the client side connection
within Project Pro.

Chris Moran

And, there is always a possibility that sql port 1433 is blocked at the
firewall level across domains. Therefore, use of a vpn tunneling software is
possible; however, using project pro with terminal services is your best
option.

It's often suggested to use Terminal Services for this kind of arrangement. It's a viable option that you might want to look at. Basically, clients in AK do a remote desktop connection to a machine at the home office that has project professional and terminal services installed on it. The terminal services machine talks locally to the project server installation and the remote clients only have to worry about being able to run a terminal session.

Another thing to think about is that these people are probably in different Windows domains, if they're in domains at all. This can cause problems. Here's a few things to check.

Make sure the project server URL is entered using a fully qualified domain name in the trusted sites list for the clients IE configuration.

Add an entry in the DNS suffix list of the IP configuration settings that will resolve the hostname to the home office domain, i.e. if the home office domain is the.company.com, add the.company.com to the DNS suffix list. This will allow the network names to resolve.

Let us know how you make out.

Earl

Chris Moran<[email protected]> 2/24/2005 1:47:03 PM >>>

HELP!

I have seen several questions on this problem but no definate answers. Here
is the scenario:

Single Server Installation
Windows Server 2003
SQL 200 Sp3a
Project Server SP1
Sharepoint Services
MDAC 2.8

Client Machines are all Windows XP SP2, MDAC 2.8, Project Professional 2003
SP1.

Office is stateside, the remote office is in AK. Clients in the remote
office, when trying to log into the server through project professional
recieve the following error message after what appears to be a timeout on the
CLIENT SIDE:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

The server timeout is unlimitedm, and these same computers can log in
stateside just fine.

I have read and followed the instructions in the MS KB Article Article ID :
837653
http://support.microsoft.com/?scid=kb;en-us;837653&spid=2525&sid=216

I think that this is a client side timeout. Is there any fix for this.

My Anchorage people can't use this great system until I get this resolved.

--
Chris Moran
Operations Program Manager
TASMCO Communications
an ESSI Company

 

[Earl Lewis]

Chris,

Citrix should work fine. There are some caveats to this configuration though. Remember there are 2 parts to the client solution, project pro and project web access. When the users run the citrix session they will need to get into the habit of using IE via Citrix instead of using a local IE installation, otherwise none of the project pro to project web access (and vice versa) will work.

This is just one of the major things we found with this configuration. I'm sure there are other "details" yet to be uncovered.

Earl
I am seriously considering a Citrix server for this. I captured the packets
from both a successful remote and the clients in Anchorage and it looks like
the client is responding to the initial "handshake" of the login, but then
not responding to the sql server after the login. I am going to try adding
the dns suffix and using the fully qualified domain name for the enterprise
account on the client side today. I will let you know how it turns up.

Thanks for your help and if you have any other suggestions please let me know.

I wish there was a way to increase the timeout on the client side connection
within Project Pro.

Chris Moran

And, there is always a possibility that sql port 1433 is blocked at the
firewall level across domains. Therefore, use of a vpn tunneling software is
possible; however, using project pro with terminal services is your best
option.

It's often suggested to use Terminal Services for this kind of arrangement. It's a viable option that you might want to look at. Basically, clients in AK do a remote desktop connection to a machine at the home office that has project professional and terminal services installed on it. The terminal services machine talks locally to the project server installation and the remote clients only have to worry about being able to run a terminal session.

Another thing to think about is that these people are probably in different Windows domains, if they're in domains at all. This can cause problems. Here's a few things to check.

Make sure the project server URL is entered using a fully qualified domain name in the trusted sites list for the clients IE configuration.

Add an entry in the DNS suffix list of the IP configuration settings that will resolve the hostname to the home office domain, i.e. if the home office domain is the.company.com, add the.company.com to the DNS suffix list. This will allow the network names to resolve.

Let us know how you make out.

Earl

Chris Moran<[email protected]> 2/24/2005 1:47:03 PM >>>

HELP!

I have seen several questions on this problem but no definate answers. Here
is the scenario:

Single Server Installation
Windows Server 2003
SQL 200 Sp3a
Project Server SP1
Sharepoint Services
MDAC 2.8

Client Machines are all Windows XP SP2, MDAC 2.8, Project Professional 2003
SP1.

Office is stateside, the remote office is in AK. Clients in the remote
office, when trying to log into the server through project professional
recieve the following error message after what appears to be a timeout on the
CLIENT SIDE:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

The server timeout is unlimitedm, and these same computers can log in
stateside just fine.

I have read and followed the instructions in the MS KB Article Article ID :
837653
http://support.microsoft.com/?scid=kb;en-us;837653&spid=2525&sid=216

I think that this is a client side timeout. Is there any fix for this.

My Anchorage people can't use this great system until I get this resolved.

--
Chris Moran
Operations Program Manager
TASMCO Communications
an ESSI Company

 

[Chris Moran]

I'm not trying to be a jerk or anything, but this error is really starting to
tick me off.

First of all, it has not begun to pop up on client machines in the immediate
area (same city) Now with the high speed connections that everyone has, I
don't see why they should be getting this error.

I have seen several posts on this error, and NO ONE seems to know.

I contacted Microsoft and PAID for support and after two weeks of making
useless changes and re-installing service packs, I HAVE THE SAME ISSUE.

Once again, another FINE product from microsoft.

I am seriously considering a Citrix server for this. I captured the packets
from both a successful remote and the clients in Anchorage and it looks like
the client is responding to the initial "handshake" of the login, but then
not responding to the sql server after the login. I am going to try adding
the dns suffix and using the fully qualified domain name for the enterprise
account on the client side today. I will let you know how it turns up.

Thanks for your help and if you have any other suggestions please let me know.

I wish there was a way to increase the timeout on the client side connection
within Project Pro.

Chris Moran

And, there is always a possibility that sql port 1433 is blocked at the
firewall level across domains. Therefore, use of a vpn tunneling software is
possible; however, using project pro with terminal services is your best
option.

It's often suggested to use Terminal Services for this kind of arrangement. It's a viable option that you might want to look at. Basically, clients in AK do a remote desktop connection to a machine at the home office that has project professional and terminal services installed on it. The terminal services machine talks locally to the project server installation and the remote clients only have to worry about being able to run a terminal session.

Another thing to think about is that these people are probably in different Windows domains, if they're in domains at all. This can cause problems. Here's a few things to check.

Make sure the project server URL is entered using a fully qualified domain name in the trusted sites list for the clients IE configuration.

Add an entry in the DNS suffix list of the IP configuration settings that will resolve the hostname to the home office domain, i.e. if the home office domain is the.company.com, add the.company.com to the DNS suffix list. This will allow the network names to resolve.

Let us know how you make out.

Earl



Chris Moran<[email protected]> 2/24/2005 1:47:03 PM >>>
HELP!

I have seen several questions on this problem but no definate answers. Here
is the scenario:

Single Server Installation
Windows Server 2003
SQL 200 Sp3a
Project Server SP1
Sharepoint Services
MDAC 2.8

Client Machines are all Windows XP SP2, MDAC 2.8, Project Professional 2003
SP1.

Office is stateside, the remote office is in AK. Clients in the remote
office, when trying to log into the server through project professional
recieve the following error message after what appears to be a timeout on the
CLIENT SIDE:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

The server timeout is unlimitedm, and these same computers can log in
stateside just fine.

I have read and followed the instructions in the MS KB Article Article ID :
837653
http://support.microsoft.com/?scid=kb;en-us;837653&spid=2525&sid=216

I think that this is a client side timeout. Is there any fix for this.

My Anchorage people can't use this great system until I get this resolved.

--
Chris Moran
Operations Program Manager
TASMCO Communications
an ESSI Company

 

[Gary L. Chefetz [MVP]]

Chris:

Thanks for your rant. If you need to solve this problem, some detail would
help.

I'm not trying to be a jerk or anything, but this error is really starting
to
tick me off.

First of all, it has not begun to pop up on client machines in the
immediate
area (same city) Now with the high speed connections that everyone has, I
don't see why they should be getting this error.

I have seen several posts on this error, and NO ONE seems to know.

I contacted Microsoft and PAID for support and after two weeks of making
useless changes and re-installing service packs, I HAVE THE SAME ISSUE.

Once again, another FINE product from microsoft.

I am seriously considering a Citrix server for this. I captured the
packets
from both a successful remote and the clients in Anchorage and it looks
like
the client is responding to the initial "handshake" of the login, but
then
not responding to the sql server after the login. I am going to try
adding
the dns suffix and using the fully qualified domain name for the
enterprise
account on the client side today. I will let you know how it turns up.

Thanks for your help and if you have any other suggestions please let me
know.

I wish there was a way to increase the timeout on the client side
connection
within Project Pro.

Chris Moran

And, there is always a possibility that sql port 1433 is blocked at the
firewall level across domains. Therefore, use of a vpn tunneling
software is
possible; however, using project pro with terminal services is your
best
option.

:

It's often suggested to use Terminal Services for this kind of
arrangement. It's a viable option that you might want to look at.
Basically, clients in AK do a remote desktop connection to a machine
at the home office that has project professional and terminal
services installed on it. The terminal services machine talks locally
to the project server installation and the remote clients only have
to worry about being able to run a terminal session.

Another thing to think about is that these people are probably in
different Windows domains, if they're in domains at all. This can
cause problems. Here's a few things to check.

Make sure the project server URL is entered using a fully qualified
domain name in the trusted sites list for the clients IE
configuration.

Add an entry in the DNS suffix list of the IP configuration settings
that will resolve the hostname to the home office domain, i.e. if the
home office domain is the.company.com, add the.company.com to the DNS
suffix list. This will allow the network names to resolve.

Let us know how you make out.

Earl



Chris Moran<[email protected]> 2/24/2005
1:47:03 PM >>>
HELP!

I have seen several questions on this problem but no definate
answers. Here
is the scenario:

Single Server Installation
Windows Server 2003
SQL 200 Sp3a
Project Server SP1
Sharepoint Services
MDAC 2.8

Client Machines are all Windows XP SP2, MDAC 2.8, Project
Professional 2003
SP1.

Office is stateside, the remote office is in AK. Clients in the
remote
office, when trying to log into the server through project
professional
recieve the following error message after what appears to be a
timeout on the
CLIENT SIDE:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen
(Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
exist or
access denied.

The server timeout is unlimitedm, and these same computers can log in
stateside just fine.

I have read and followed the instructions in the MS KB Article
Article ID :
837653
http://support.microsoft.com/?scid=kb;en-us;837653&spid=2525&sid=216

I think that this is a client side timeout. Is there any fix for
this.

My Anchorage people can't use this great system until I get this
resolved.

--
Chris Moran
Operations Program Manager
TASMCO Communications
an ESSI Company

 

[Earl Lewis]

Chris,

You never mentioned if you checked for port 1433/1434 blocking on your network between the two locations. Every network administrator in the world has blocked these ports from the outside since the Slammer worm hit over a year ago.

Also, the fact that you said the initial "handshake" seems to be acknowledged then it never seems that talk to the SQL server would elevate the likelihood of port blocking being a problem.

If 1433/1434 are blocked from outside you'll need to setup your AK people with a VPN client to connect back to home office so it looks like they're inside the home office network. Then 1433/1434 traffic should flow just fine, assuming your network admins didn't block it inside too.

BTW, I know the frustration you're feeling. I felt the same way back when the slammer originally hit. Good luck.

Have you looked into doing RDP (terminal services or Citrix)?

Earl
I'm not trying to be a jerk or anything, but this error is really starting to
tick me off.

First of all, it has not begun to pop up on client machines in the immediate
area (same city) Now with the high speed connections that everyone has, I
don't see why they should be getting this error.

I have seen several posts on this error, and NO ONE seems to know.

I contacted Microsoft and PAID for support and after two weeks of making
useless changes and re-installing service packs, I HAVE THE SAME ISSUE.

Once again, another FINE product from microsoft.

I am seriously considering a Citrix server for this. I captured the packets
from both a successful remote and the clients in Anchorage and it looks like
the client is responding to the initial "handshake" of the login, but then
not responding to the sql server after the login. I am going to try adding
the dns suffix and using the fully qualified domain name for the enterprise
account on the client side today. I will let you know how it turns up.

Thanks for your help and if you have any other suggestions please let me know.

I wish there was a way to increase the timeout on the client side connection
within Project Pro.

Chris Moran

And, there is always a possibility that sql port 1433 is blocked at the
firewall level across domains. Therefore, use of a vpn tunneling software is
possible; however, using project pro with terminal services is your best
option.

It's often suggested to use Terminal Services for this kind of arrangement. It's a viable option that you might want to look at. Basically, clients in AK do a remote desktop connection to a machine at the home office that has project professional and terminal services installed on it. The terminal services machine talks locally to the project server installation and the remote clients only have to worry about being able to run a terminal session.

Another thing to think about is that these people are probably in different Windows domains, if they're in domains at all. This can cause problems. Here's a few things to check.

Make sure the project server URL is entered using a fully qualified domain name in the trusted sites list for the clients IE configuration.

Add an entry in the DNS suffix list of the IP configuration settings that will resolve the hostname to the home office domain, i.e. if the home office domain is the.company.com, add the.company.com to the DNS suffix list. This will allow the network names to resolve.

Let us know how you make out.

Earl



Chris Moran<[email protected]> 2/24/2005 1:47:03 PM >>>
HELP!

I have seen several questions on this problem but no definate answers. Here
is the scenario:

Single Server Installation
Windows Server 2003
SQL 200 Sp3a
Project Server SP1
Sharepoint Services
MDAC 2.8

Client Machines are all Windows XP SP2, MDAC 2.8, Project Professional 2003
SP1.

Office is stateside, the remote office is in AK. Clients in the remote
office, when trying to log into the server through project professional
recieve the following error message after what appears to be a timeout on the
CLIENT SIDE:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

The server timeout is unlimitedm, and these same computers can log in
stateside just fine.

I have read and followed the instructions in the MS KB Article Article ID :
837653
http://support.microsoft.com/?scid=kb;en-us;837653&spid=2525&sid=216

I think that this is a client side timeout. Is there any fix for this.

My Anchorage people can't use this great system until I get this resolved.

--
Chris Moran
Operations Program Manager
TASMCO Communications
an ESSI Company

 

[Chris Moran]

Thanks for the help, aparently 1433 is being blocked somewhere along the way
bewteen our satellite office and the home offce. I had the local people make
a rule on the sonic firewall to allow 1433 and now when accessing remotely, I
get the folowing error:

Connection Failed:
SQLState: 'S1T00"
SQL Server Error: 0
Timeout Expired

I think it is still timing out on the client side. On the client "cliconfg"
settings, TCP is the only protocol, no aliases are set up. I wonder if you
can bypass the client timeout by creating an alias.

Chris,

You never mentioned if you checked for port 1433/1434 blocking on your network between the two locations. Every network administrator in the world has blocked these ports from the outside since the Slammer worm hit over a year ago.

Also, the fact that you said the initial "handshake" seems to be acknowledged then it never seems that talk to the SQL server would elevate the likelihood of port blocking being a problem.

If 1433/1434 are blocked from outside you'll need to setup your AK people with a VPN client to connect back to home office so it looks like they're inside the home office network. Then 1433/1434 traffic should flow just fine, assuming your network admins didn't block it inside too.

BTW, I know the frustration you're feeling. I felt the same way back when the slammer originally hit. Good luck.

Have you looked into doing RDP (terminal services or Citrix)?

Earl
I'm not trying to be a jerk or anything, but this error is really starting to
tick me off.

First of all, it has not begun to pop up on client machines in the immediate
area (same city) Now with the high speed connections that everyone has, I
don't see why they should be getting this error.

I have seen several posts on this error, and NO ONE seems to know.

I contacted Microsoft and PAID for support and after two weeks of making
useless changes and re-installing service packs, I HAVE THE SAME ISSUE.

Once again, another FINE product from microsoft.

I am seriously considering a Citrix server for this. I captured the packets
from both a successful remote and the clients in Anchorage and it looks like
the client is responding to the initial "handshake" of the login, but then
not responding to the sql server after the login. I am going to try adding
the dns suffix and using the fully qualified domain name for the enterprise
account on the client side today. I will let you know how it turns up.

Thanks for your help and if you have any other suggestions please let me know.

I wish there was a way to increase the timeout on the client side connection
within Project Pro.

Chris Moran

And, there is always a possibility that sql port 1433 is blocked at the
firewall level across domains. Therefore, use of a vpn tunneling software is
possible; however, using project pro with terminal services is your best
option.

:

It's often suggested to use Terminal Services for this kind of arrangement. It's a viable option that you might want to look at. Basically, clients in AK do a remote desktop connection to a machine at the home office that has project professional and terminal services installed on it. The terminal services machine talks locally to the project server installation and the remote clients only have to worry about being able to run a terminal session.

Another thing to think about is that these people are probably in different Windows domains, if they're in domains at all. This can cause problems. Here's a few things to check.

Make sure the project server URL is entered using a fully qualified domain name in the trusted sites list for the clients IE configuration.

Add an entry in the DNS suffix list of the IP configuration settings that will resolve the hostname to the home office domain, i.e. if the home office domain is the.company.com, add the.company.com to the DNS suffix list. This will allow the network names to resolve.

Let us know how you make out.

Earl



Chris Moran<[email protected]> 2/24/2005 1:47:03 PM >>>
HELP!

I have seen several questions on this problem but no definate answers. Here
is the scenario:

Single Server Installation
Windows Server 2003
SQL 200 Sp3a
Project Server SP1
Sharepoint Services
MDAC 2.8

Client Machines are all Windows XP SP2, MDAC 2.8, Project Professional 2003
SP1.

Office is stateside, the remote office is in AK. Clients in the remote
office, when trying to log into the server through project professional
recieve the following error message after what appears to be a timeout on the
CLIENT SIDE:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

The server timeout is unlimitedm, and these same computers can log in
stateside just fine.

I have read and followed the instructions in the MS KB Article Article ID :
837653
http://support.microsoft.com/?scid=kb;en-us;837653&spid=2525&sid=216

I think that this is a client side timeout. Is there any fix for this.

My Anchorage people can't use this great system until I get this resolved.

--
Chris Moran
Operations Program Manager
TASMCO Communications
an ESSI Company

 

[David H]

I'm seeing the exact error message on our new XP workstations which we just
installed. They can reach the web portion of project server but when they
attempt to launch Project Pro 2003 either from within Project Server or
Directly they receive the same error that Chris got followed by a SQL Server
Login box which just hangs.

What is strange that its only the brand new XPs that are having this problem
which makes me wonder if it is a subtle setup difference like the XP firewall
or Spyware Beta. As the older XP machines are on the same network it doesn't
suggest a timing issue.

As an aside, the RDC option is pretty cool. I use it with Rdestop for my
Penguins who need MS services and it works great.

 

[Mike Woffard]

I have a client who wants to use a third party vendor to host an application
server w/ Project Server 2003 and a SQL database server......accessing
through VPN. Are you aware of any known issues configuring project server in
this environment?

 

[Gary L. Chefetz [MVP]]

Use someone with experience:

http://www.epmsolutions.com
http://www.projectserverhosts.com
http://www.epi.com


--


Gary L. Chefetz, MVP
"We wrote the books on Project Server"
http://www.msprojectexperts.com

For Project Server FAQs visit
http://www.projectserverexperts.com

For Project FAQs visit
http://www.mvps.org/project

 

[Steve]

Chris,

I am seeing the exact same problem that you started with. Have you had any
results yet.

Thanks for the help, aparently 1433 is being blocked somewhere along the way
bewteen our satellite office and the home offce. I had the local people make
a rule on the sonic firewall to allow 1433 and now when accessing remotely, I
get the folowing error:

Connection Failed:
SQLState: 'S1T00"
SQL Server Error: 0
Timeout Expired

I think it is still timing out on the client side. On the client "cliconfg"
settings, TCP is the only protocol, no aliases are set up. I wonder if you
can bypass the client timeout by creating an alias.

Chris,

You never mentioned if you checked for port 1433/1434 blocking on your network between the two locations. Every network administrator in the world has blocked these ports from the outside since the Slammer worm hit over a year ago.

Also, the fact that you said the initial "handshake" seems to be acknowledged then it never seems that talk to the SQL server would elevate the likelihood of port blocking being a problem.

If 1433/1434 are blocked from outside you'll need to setup your AK people with a VPN client to connect back to home office so it looks like they're inside the home office network. Then 1433/1434 traffic should flow just fine, assuming your network admins didn't block it inside too.

BTW, I know the frustration you're feeling. I felt the same way back when the slammer originally hit. Good luck.

Have you looked into doing RDP (terminal services or Citrix)?

Earl

Chris Moran<[email protected]> 4/19/2005 4:28:02 PM >>>

I'm not trying to be a jerk or anything, but this error is really starting to
tick me off.

First of all, it has not begun to pop up on client machines in the immediate
area (same city) Now with the high speed connections that everyone has, I
don't see why they should be getting this error.

I have seen several posts on this error, and NO ONE seems to know.

I contacted Microsoft and PAID for support and after two weeks of making
useless changes and re-installing service packs, I HAVE THE SAME ISSUE.

Once again, another FINE product from microsoft.

I am seriously considering a Citrix server for this. I captured the packets
from both a successful remote and the clients in Anchorage and it looks like
the client is responding to the initial "handshake" of the login, but then
not responding to the sql server after the login. I am going to try adding
the dns suffix and using the fully qualified domain name for the enterprise
account on the client side today. I will let you know how it turns up.

Thanks for your help and if you have any other suggestions please let me know.

I wish there was a way to increase the timeout on the client side connection
within Project Pro.

Chris Moran

:

And, there is always a possibility that sql port 1433 is blocked at the
firewall level across domains. Therefore, use of a vpn tunneling software is
possible; however, using project pro with terminal services is your best
option.

:

It's often suggested to use Terminal Services for this kind of arrangement. It's a viable option that you might want to look at. Basically, clients in AK do a remote desktop connection to a machine at the home office that has project professional and terminal services installed on it. The terminal services machine talks locally to the project server installation and the remote clients only have to worry about being able to run a terminal session.

Another thing to think about is that these people are probably in different Windows domains, if they're in domains at all. This can cause problems. Here's a few things to check.

Make sure the project server URL is entered using a fully qualified domain name in the trusted sites list for the clients IE configuration.

Add an entry in the DNS suffix list of the IP configuration settings that will resolve the hostname to the home office domain, i.e. if the home office domain is the.company.com, add the.company.com to the DNS suffix list. This will allow the network names to resolve.

Let us know how you make out.

Earl



Chris Moran<[email protected]> 2/24/2005 1:47:03 PM >>>
HELP!

I have seen several questions on this problem but no definate answers. Here
is the scenario:

Single Server Installation
Windows Server 2003
SQL 200 Sp3a
Project Server SP1
Sharepoint Services
MDAC 2.8

Client Machines are all Windows XP SP2, MDAC 2.8, Project Professional 2003
SP1.

Office is stateside, the remote office is in AK. Clients in the remote
office, when trying to log into the server through project professional
recieve the following error message after what appears to be a timeout on the
CLIENT SIDE:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

The server timeout is unlimitedm, and these same computers can log in
stateside just fine.

I have read and followed the instructions in the MS KB Article Article ID :
837653
http://support.microsoft.com/?scid=kb;en-us;837653&spid=2525&sid=216

I think that this is a client side timeout. Is there any fix for this.

My Anchorage people can't use this great system until I get this resolved.

--
Chris Moran
Operations Program Manager
TASMCO Communications
an ESSI Company

 

[Raymond Chiu (gatorback]

Chris,

XP Remote Desktop can allow one user to remotely perform tasks, without
bandwidth latency problems. It can be thought of a watered down terminal
server.

The default port for RD
is 3389, which may already be allocated for TS. In this case, you may need
to configure RD for a port other than 3389.

RD ("server" side) can be setup via these instructions:
http://www.microsoft.com/windowsxp/using/mobility/getstarted/remoteintro.mspx

Client Side:
http://www.microsoft.com/WINDOWSXP/pro/using/howto/gomobile/remotedesktop/startremote.asp
Client Download (already built into XP: only for 2000 or less):
http://www.microsoft.com/windowsxp/pro/downloads/rdclientdl.asp

Thanks for the help, aparently 1433 is being blocked somewhere along the way
bewteen our satellite office and the home offce. I had the local people make
a rule on the sonic firewall to allow 1433 and now when accessing remotely, I
get the folowing error:

Connection Failed:
SQLState: 'S1T00"
SQL Server Error: 0
Timeout Expired

I think it is still timing out on the client side. On the client "cliconfg"
settings, TCP is the only protocol, no aliases are set up. I wonder if you
can bypass the client timeout by creating an alias.

Chris,

You never mentioned if you checked for port 1433/1434 blocking on your network between the two locations. Every network administrator in the world has blocked these ports from the outside since the Slammer worm hit over a year ago.

Also, the fact that you said the initial "handshake" seems to be acknowledged then it never seems that talk to the SQL server would elevate the likelihood of port blocking being a problem.

If 1433/1434 are blocked from outside you'll need to setup your AK people with a VPN client to connect back to home office so it looks like they're inside the home office network. Then 1433/1434 traffic should flow just fine, assuming your network admins didn't block it inside too.

BTW, I know the frustration you're feeling. I felt the same way back when the slammer originally hit. Good luck.

Have you looked into doing RDP (terminal services or Citrix)?

Earl

Chris Moran<[email protected]> 4/19/2005 4:28:02 PM >>>

I'm not trying to be a jerk or anything, but this error is really starting to
tick me off.

First of all, it has not begun to pop up on client machines in the immediate
area (same city) Now with the high speed connections that everyone has, I
don't see why they should be getting this error.

I have seen several posts on this error, and NO ONE seems to know.

I contacted Microsoft and PAID for support and after two weeks of making
useless changes and re-installing service packs, I HAVE THE SAME ISSUE.

Once again, another FINE product from microsoft.

I am seriously considering a Citrix server for this. I captured the packets
from both a successful remote and the clients in Anchorage and it looks like
the client is responding to the initial "handshake" of the login, but then
not responding to the sql server after the login. I am going to try adding
the dns suffix and using the fully qualified domain name for the enterprise
account on the client side today. I will let you know how it turns up.

Thanks for your help and if you have any other suggestions please let me know.

I wish there was a way to increase the timeout on the client side connection
within Project Pro.

Chris Moran

:

And, there is always a possibility that sql port 1433 is blocked at the
firewall level across domains. Therefore, use of a vpn tunneling software is
possible; however, using project pro with terminal services is your best
option.

:

It's often suggested to use Terminal Services for this kind of arrangement. It's a viable option that you might want to look at. Basically, clients in AK do a remote desktop connection to a machine at the home office that has project professional and terminal services installed on it. The terminal services machine talks locally to the project server installation and the remote clients only have to worry about being able to run a terminal session.

Another thing to think about is that these people are probably in different Windows domains, if they're in domains at all. This can cause problems. Here's a few things to check.

Make sure the project server URL is entered using a fully qualified domain name in the trusted sites list for the clients IE configuration.

Add an entry in the DNS suffix list of the IP configuration settings that will resolve the hostname to the home office domain, i.e. if the home office domain is the.company.com, add the.company.com to the DNS suffix list. This will allow the network names to resolve.

Let us know how you make out.

Earl



Chris Moran<[email protected]> 2/24/2005 1:47:03 PM >>>
HELP!

I have seen several questions on this problem but no definate answers. Here
is the scenario:

Single Server Installation
Windows Server 2003
SQL 200 Sp3a
Project Server SP1
Sharepoint Services
MDAC 2.8

Client Machines are all Windows XP SP2, MDAC 2.8, Project Professional 2003
SP1.

Office is stateside, the remote office is in AK. Clients in the remote
office, when trying to log into the server through project professional
recieve the following error message after what appears to be a timeout on the
CLIENT SIDE:

Connection failed:
SQLState: '01000'
SQL Server Error: 53
[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen (Connect())
Connection failed:
SQLState '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.

The server timeout is unlimitedm, and these same computers can log in
stateside just fine.

I have read and followed the instructions in the MS KB Article Article ID :
837653
http://support.microsoft.com/?scid=kb;en-us;837653&spid=2525&sid=216

I think that this is a client side timeout. Is there any fix for this.

My Anchorage people can't use this great system until I get this resolved.

--
Chris Moran
Operations Program Manager
TASMCO Communications
an ESSI Company