Recently we have migrated the datawarehouse server to windows 2003 server
from windows 2000 server.
Since then all dts packages are getting timedout with the following error.

Step Error Source: Microsoft OLE DB Provider for SQL Server
Step Error Description:Timeout expired
Step Error code: 80004005
Step Error Help File:
Step Error Help Context ID:0


The new server is very high end server which has 8 processors and 12GB RAM,
and All dts packages are having simple deletes and data transfer tasks.

Daily updatestats was running during off hours and proper indices are
there.
Ran the checkdb on all dbs, found no errors.

I never seen these kind of erros on windows2000 and sql 2000 ee sp3.

Is there any reason that sql2000 EE SP3 is not fully supported by Windows
2003 server.

I have verified the query timeout settings on source and destination server
which is 0 (unlimited)

Please let me know if settings need to be checked.



(Migration : dettahed the databases from windows 2000 server and sql200 EE
sp3 and attached to the windows2003 server and Sql 200 EE sp3)


If any queries that were run from query analyzer are failing with the
following error afetr few minutes :

[Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionRead (WrapperRead()).
Server: Msg 11, Level 16, State 1, Line 0
General network error. Check your network documentation.
Connection Broken

Info :

No new logins, all jobs are using "sa" login.
Recreated the jobs and dts packages on the new server.

Only user databases were dettached and attached and ran the checkdb against
all dbs found no errors.


"DKRReddy" <dkrreddy (AT) hotmail (DOT) com> wrote

One more thing

My Main dts package calls many other simple dts packages.
When my main dts package calls other dts packages getting timeout
immediately.

Is there any settings at package level to increase the timeout.


"DKRReddy" <dkrreddy (AT) hotmail (DOT) com> wrote

The error would suggest that either there is a permissions issue or that
the new 2003 box cannot see one of the datasources. The fact that the
packages were built on a different OS is unlikely to mean anything here.

Are you also saying that a query in QA is also not working?

Is this a query against the local server or a remote server?

Did you service Pack SQL Server on 2003?

Check with your Server team to make sure that nothing emanating from the
SQL Server is being blocked from leaving the box.

Allan



"DKRReddy" <dkrreddy (AT) hotmail (DOT) com> wrote

Thanks for the reply.

All jobs are running under "sa" login.
But the packaes were created under my nt account.
source and destination servers are in same domain .


The main dts packages is calling few dts packages.
While main package calling the dts pacckage itself getting the timeout, it's
running the package .
just while calling the pacckage itself getting timeout.

if I run the same package from enterprise manager running fine without
issues.




"Allan Mitchell" <allan (AT) no-spam (DOT) sqldts.com> wrote

DKRReddy,

See if the following applies:
http://support.microsoft.com/default...b;en-us;293318

Ilya

"DKRReddy" <dkrreddy (AT) hotmail (DOT) com> wrote