Hello,

Two weeks ago we migrated our database to another server including our
DTS packages. We went in and replaced the Server connections with the
new server name where necessary including within Active X scripts where
a connection is declared. The problem is, now all of the packages I
run from my computer time out. The packages run successfully without
timing out when run from either of my colleague's computers. It makes
no sense to me...why would it work for the others? I haven't been able
to make any progress on any of the packages I was in the process of
building because it times out. I would really appreciate any help.
Here is a sample of some code where it times out:

Dim cnn

Set cnn = CreateObject("ADODB.Connection")
cnn.Provider = "sqloledb"

It times out here >> cnn.Open
"Server=FOG;Trusted_Connection=Yes;Database=IMPORT "

Does anybody have any idea why this would be occurring or what I can do
to fix it or where to look to find the problem?

An error would be helpful, but have you checked if you can resolve the name
FOG? What connection protocol are you using? Check the client Network
Utility.

I'd suggest using tcp, and then try a ping to FOG to check name resolution.
Can you use QA to open a connection from your machine? Try specifying the
full connection settings, e.g.

tcp:<ip>,<port>

If that works, work backwards, removing tokens until it fails.


--
Darren Green
http://www.sqldts.com
http://www.sqlis.com

"phantom" <phantomtoe (AT) yahoo (DOT) com> wrote

The error is fairly general:

"Microsoft OLE DB Provider for SQL Server: Timeout Expired"

I have no problem accessing Fog from QA or EM and it pings
successfully. We use TCP/IP. The network guy here is going to install
a new NIC card tomorrow, but that doesn't seem like the likely culprit
to me. My DTS packages started timing out immediately after migrating
the database to a new server. I changed the connection string to read:

oCnn.Open "Provider =sqloledb; Data Source = Fog; Initial Catalog =
Import; Integrated Security=SSPI"

It still times out here. Any other ideas?

Go into SQL Profiler and see if your connection is being attempted over
Named Pipes rather than TCP/IP. I have gotten these type of errors when
Named Pipes is the top most connection type defined at the server

-Mike Gercevich

--
Message posted via http://www.sqlmonster.com