dbTalk Databases Forums  

Timeout expired, Error code: 80004005

microsoft.public.sqlserver.dts microsoft.public.sqlserver.dts


Discuss Timeout expired, Error code: 80004005 in the microsoft.public.sqlserver.dts forum.



Reply
 
Thread Tools Display Modes
  #1  
Old   
James Ma
 
Posts: n/a

Default Timeout expired, Error code: 80004005 - 04-25-2005 , 11:39 AM






Hi all,

I have a bunch of DTS packages to load our data warehouse periodcally.
Recently it often invokes the "timeout expired" error. Sometime in this
package, sometime in another one. I also find the error always occur when
loading the package, namely not in a "bad" T-SQL.

Can anyone here give me some advice?

Thanks in advance.
James

Reply With Quote
  #2  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Timeout expired, Error code: 80004005 - 04-25-2005 , 02:21 PM






This error code 80004005 generally signals some kind of logon failure or failure to connect. Could this be possible in your
situation?

--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - SQL Server 2005 Integration Services.
www.Konesans.com


"James Ma" <JamesMa (AT) discussions (DOT) microsoft.com> wrote

Quote:
Hi all,

I have a bunch of DTS packages to load our data warehouse periodcally.
Recently it often invokes the "timeout expired" error. Sometime in this
package, sometime in another one. I also find the error always occur when
loading the package, namely not in a "bad" T-SQL.

Can anyone here give me some advice?

Thanks in advance.
James



Reply With Quote
  #3  
Old   
James Ma
 
Posts: n/a

Default Re: Timeout expired, Error code: 80004005 - 04-25-2005 , 08:59 PM



Maybe. But the critical point is: it isn't that it cannot always logon
(namely the security configuration is fine), but it cannot logon when some
other unknown factors are involved. Here we have another test server that
does the same thing as that production server, and it never fails.

Is it possible that it happened to run out of all connections due to the SQL
server licence limit? Or the disk system has some defects?


Still thanks for your reply.
James

"Allan Mitchell" wrote:

Quote:
This error code 80004005 generally signals some kind of logon failure or failure to connect. Could this be possible in your
situation?

--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - SQL Server 2005 Integration Services.
www.Konesans.com


"James Ma" <JamesMa (AT) discussions (DOT) microsoft.com> wrote

Hi all,

I have a bunch of DTS packages to load our data warehouse periodcally.
Recently it often invokes the "timeout expired" error. Sometime in this
package, sometime in another one. I also find the error always occur when
loading the package, namely not in a "bad" T-SQL.

Can anyone here give me some advice?

Thanks in advance.
James




Reply With Quote
  #4  
Old   
Allan Mitchell
 
Posts: n/a

Default Re: Timeout expired, Error code: 80004005 - 04-26-2005 , 12:53 AM



Which licensing model are you running?

I would have expected the error to be different.

The error also means that the server you seek could not be found which could be because of a whole raft of things

Is there anything in the SQL Server event for the connection excess theory?

--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - SQL Server 2005 Integration Services.
www.Konesans.com


"James Ma" <JamesMa (AT) discussions (DOT) microsoft.com> wrote

Quote:
Maybe. But the critical point is: it isn't that it cannot always logon
(namely the security configuration is fine), but it cannot logon when some
other unknown factors are involved. Here we have another test server that
does the same thing as that production server, and it never fails.

Is it possible that it happened to run out of all connections due to the SQL
server licence limit? Or the disk system has some defects?


Still thanks for your reply.
James

"Allan Mitchell" wrote:

This error code 80004005 generally signals some kind of logon failure or failure to connect. Could this be possible in your
situation?

--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - SQL Server 2005 Integration Services.
www.Konesans.com


"James Ma" <JamesMa (AT) discussions (DOT) microsoft.com> wrote

Hi all,

I have a bunch of DTS packages to load our data warehouse periodcally.
Recently it often invokes the "timeout expired" error. Sometime in this
package, sometime in another one. I also find the error always occur when
loading the package, namely not in a "bad" T-SQL.

Can anyone here give me some advice?

Thanks in advance.
James






Reply With Quote
Reply




Thread Tools
Display Modes

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off



Powered by vBulletin Version 3.5.3
Copyright ©2000 - 2012, Jelsoft Enterprises Ltd.