DTS Package Timeout Error

Tech-Archive recommends: Repair Windows Errors & Optimize Windows Performance

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.


.

Relevant Pages

  • DTS Package Timeout error
    ... 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 ...
    (microsoft.public.sqlserver.dts)
  • Remote Access Configuration Errors
    ... Calling CRRASCommit::ValidatePropertyBag ... Reading VPN Server Name returned OK ... Running IExpress to build the package returned OK ... Modifying client setup config.dat for provisioning returned OK ...
    (microsoft.public.windows.server.sbs)
  • RE: using an app.config of a referenced project
    ... the app.config it reference is the one of the ... be shared with calling application and be able to overwrite/customize them. ... To add/manage settings, ... Microsoft MSDN Online Support Lead ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: An mp3 epiphany
    ... thing works and what effect they have in given settings. ... There's a bunch more info on the Lame website, ... The options on the VBR and ABR tabs are still available to fiddle ... You're a *long* way behind on the state of current package management ...
    (uk.comp.sys.mac)
  • Re: java.lang vs java.util
    ... Let's make sure it's not really a package consisting entirely of utility ... in which case calling the package "util" is sensible. ... You may genuinely have some classes in there that _are_ utility classes: ...
    (comp.lang.java.programmer)