DTS Package Timeout Error

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

DKRReddy - 24 Oct 2005 01:13 GMT

I have two simple dts pacakges , DTS_Main and DTS_Sub.
DTS_Sub being called from DTS_Main.
When DTS_Main calls DTS_Sub getting the following timeout error while
calling the package not while executing.
Is there any settings I can set to increase the time out setting when
calling sub package.Both dts packages
exists in Same SQL server (SQL 2000 SP4 + Windows 2003), the server is 8
processor with 12 GB Ram.

Error: -2147467259 (80004005); Provider Error: 0 (0)
Error string: Timeout expired Error source: Microsoft OLE DB Provider
for SQL Server
Help file:
Help context: 0.
Process Exit Code 1. The step failed.

Please advise.

Reply to this Message

Myles.Matheson@gmail.com - 24 Oct 2005 06:22 GMT

Hello DK,

The error message seems to be more to do with connecting to your SQL
Server. First off are all the DTS packages on the same server?

If all DTS packages are on the same server try the following:

I would try and run the sub package independently of the main package.

Also I would test all the database connections in the DTS package.

Hope this helps,

Myles Matheson
Data Warehouse Architect
http://bi-on-sql-server.blogspot.com/

Reply to this Message

DKRReddy - 24 Oct 2005 07:47 GMT

Ran the main and sub packages individually they ran fine.
Both the packages are in the same server.I have tested all the connections
inside the packages.
I have changed the connection timeout for all connections to 600000

My question is while main package opening the sub package it's taking more
time, where I can change this
time out setting for opening dts packages..

> Hello DK,
>
[quoted text clipped - 12 lines]
> Data Warehouse Architect
> http://bi-on-sql-server.blogspot.com/

Reply to this Message

Myles.Matheson@gmail.com - 24 Oct 2005 11:38 GMT

Hello DK,

This could be a permissions problem. Did you manually run the sub
package or scheduled it?

If you manually ran the package your user context would have been used.
This may include all the aliases for databases connections. The timeout
error could have been trying to connect on a different port requiring
an alias.

Are you using server aliases for you db connections?

Try scheduling the sub package on its own to see if you get the same
error. Or logon under the SQL agent account and the sub package.

Myles Matheson
Data Warehouse Architect
http://bi-on-sql-server.blogspot.com/

Reply to this Message

Darren Gosbell - 24 Oct 2005 22:06 GMT

> Ran the main and sub packages individually they ran fine.

If the main package ran fine, does that mean it runs OK from the
designer, but not as a scheduled job? If this is the case the issue is
probably that the account that SQL Agent is running under does not have
permission to run the packages.

Signature

Regards
Darren Gosbell [MCSD]
<dgosbell_at_yahoo_dot_com>
Blog: http://www.geekswithblogs.net/darrengosbell

Reply to this Message

Thomas - 25 Oct 2005 22:51 GMT

Since the DTS packages are on the same server why not create a job and have
the pacakges executed as separate steps?

Signature

Thomas

> Hello DK,
>
[quoted text clipped - 12 lines]
> Data Warehouse Architect
> http://bi-on-sql-server.blogspot.com/

Reply to this Message

DKRReddy - 26 Oct 2005 07:27 GMT

i have many dts packages, so i want to include them in one package with
different conditions.

> Since the DTS packages are on the same server why not create a job and have
> the pacakges executed as separate steps?
[quoted text clipped - 15 lines]
> > Data Warehouse Architect
> > http://bi-on-sql-server.blogspot.com/

Reply to this Message