Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Hresult: 0x80004005 Description: Expand / Collapse
Author
Message
Posted Tuesday, July 21, 2009 9:19 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, September 1, 2010 7:44 AM
Points: 176, Visits: 290
Hi,

Some time when my job run the SSIS package I am getting following error

Hresult: 0x80004005 Description:

some one can help me?

Thanks
MAK
Post #756684
Posted Tuesday, July 21, 2009 9:26 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Friday, May 30, 2014 6:27 PM
Points: 2,808, Visits: 7,175
Are there any other errors prior to this one in the error log?
Post #756692
Posted Tuesday, July 21, 2009 9:38 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, September 1, 2010 7:44 AM
Points: 176, Visits: 290
Thanks for replay, I am getting following error

Executed as user: PCA\svcSQLadm. ...sion 9.00.3042.00 for 32-bit Copyright (C) Microsoft Corp 1984-2005. All rights reserved. Started: 4:30:00 AM Error: 2009-07-20 04:30:47.81 Code: 0xC0202009 Source: LiveVoxImports Connection manager "de1clcrsql01.crs5_oltp.crsuser" Description: SSIS Error Code DTS_E_OLEDBERROR. An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Login timeout expired". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.". An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Named Pipes Pro... The package execution fa... The step failed.
Post #756706
Posted Tuesday, July 21, 2009 9:43 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, December 6, 2012 2:49 PM
Points: 140, Visits: 310
Looks like a connection failure, check if the users credentials who run the job are still the same or changed?.
Try manually executing the job with some valid connections and let us know the result.
Post #756715
Posted Tuesday, July 21, 2009 9:53 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, September 1, 2010 7:44 AM
Points: 176, Visits: 290
I ran is manually it work, and also my next schedule of same job ran fine, I want to know why this happened?
Post #756721
Posted Tuesday, July 21, 2009 9:55 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Thursday, December 6, 2012 2:49 PM
Points: 140, Visits: 310
There can be many reasons like
network glitch at that time, someone amended the pwd's, services restart etc.
Post #756725
Posted Tuesday, July 21, 2009 9:57 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, September 1, 2010 7:44 AM
Points: 176, Visits: 290
Thansk, but there is know why to know the exect cause of the problem
Post #756731
Posted Tuesday, July 21, 2009 12:33 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 4:59 PM
Points: 7,064, Visits: 15,278
That is the specific error. Looks like three warnings came up:

Login Timeout Error

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections.".

"Named Pipes Protocol is not enabled" (filled in for the truncation).


Something looks to have changed on the server.


----------------------------------------------------------------------------------
Your lack of planning does not constitute an emergency on my part...unless you're my manager...or a director and above...or a really loud-spoken end-user..All right - what was my emergency again?
Post #756864
Posted Tuesday, July 21, 2009 12:41 PM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, September 1, 2010 7:44 AM
Points: 176, Visits: 290
Thanks
Post #756868
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse