August 18, 2014 at 7:58 am
HI Experts,
I am getting below error when ran an SSIS package as job
Source: ABC_2 5_DCC_3 0_Sync v6 Connection manager "DestinationSCODatabase"
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 Server Native Client 11.0" Hresult: 0x80004005 Description: "Login timeout expired".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "A network-related or instance-specific error has occurred while establishing a connection to SQL Server. Server is not found or not accessible. Check if instance name is correct and if SQL Server is configured to allow remote connections. For more information see SQL Server Books Online.".
An OLE DB record is available. Source: "Microsoft SQL Server Native Client 11.0" Hresult: 0x80004005 Description: "Named Pipes Provider: Could not open a connection to SQL Server [2]. ".
End Error
Error: 2014-08-18 09:50:30.70
Code: 0xC020801C
Source: (0) Update Configuration Names Lookup [2]
Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "DestinationSCODatabase" failed with error code 0xC0202009. There may be error messages posted before this with more information on why the AcquireConnection method call failed.
End Error
Error: 2014-08-18 09:50:30.70
Code: 0xC0047017
Source: (0) Update Configuration Names SSIS.Pipeline
Description: Lookup failed validation and returned error code 0xC020801C.
End Error
Error: 2014-08-18 09:50:30.70
Code: 0xC004700C
Source: (0) Update Configuration Names SSIS.Pipeline
Description: One or more component failed validation.
End Error
Error: 2014-08-18 09:50:30.70
Code: 0xC0024107
Source: (0) Update Configuration Names
Description: There were errors during task validation.
End Error
DTExec: The package execution returned DTSER_FAILURE (1).
Started: 9:50:14 AM
Finished: 9:50:30 AM
Elapsed: 16.125 seconds
Please help
TIA
August 18, 2014 at 8:05 am
check your source Login credentials, as its unable to login to sql server. try to connect to the user login and password which are configured for this SSIS Package.
August 18, 2014 at 8:29 am
Thanks for the reply..
The job is run under SA account.
config file is using windows authentication only.
August 18, 2014 at 8:36 am
Strange thing is that the same run without any issue in a default instance and have issue with named instance.
August 18, 2014 at 8:37 am
Ratheesh.K.Nair (8/18/2014)
Thanks for the reply..The job is run under SA account.
config file is using windows authentication only.
you need to check this server 'DestinationSCODatabase'. try to login into the sql server using that window user from SSMS. See if you are unable to login then that window user do not have permission to connect to the sql server. if possible try any other user like 'SA' to connect because there might be a case that sql server is down.
August 18, 2014 at 8:40 am
Thanks twin.devil.
Both the databases are in same server.
August 18, 2014 at 8:51 am
Ratheesh.K.Nair (8/18/2014)
Strange thing is that the same run without any issue in a default instance and have issue with named instance.
have u tried IP ?
August 18, 2014 at 8:52 am
Look at the properties of the connection manager DestinationSCODatabase. What is the name of the server? What authentication mode does it use? If it uses Windows authentication, does the SQL Server Agent account of the server on which you're running the job have permission to log on to that first mentioned server? If it uses SQL authentication, are the credentials provided valid on the server? Is the SQL Server Browser service running?
John
August 18, 2014 at 9:06 am
twin.devil (8/18/2014)
Ratheesh.K.Nair (8/18/2014)
Strange thing is that the same run without any issue in a default instance and have issue with named instance.have u tried IP ?
Yes
August 18, 2014 at 9:09 am
John Mitchell-245523 (8/18/2014)
Look at the properties of the connection manager DestinationSCODatabase. What is the name of the server? What authentication mode does it use? If it uses Windows authentication, does the SQL Server Agent account of the server on which you're running the job have permission to log on to that first mentioned server? If it uses SQL authentication, are the credentials provided valid on the server? Is the SQL Server Browser service running?John
Thanks John
Server name is :MALINF\SQL001
Package uses windows authentication. Created the job on same server where these databases resides. The Agent logon account is windows account so cant check that.
August 19, 2014 at 12:15 am
Ratheesh.K.Nair (8/18/2014)
Strange thing is that the same run without any issue in a default instance and have issue with named instance.
can you elaborate this in detail?
August 21, 2014 at 4:34 am
twin.devil (8/19/2014)
Ratheesh.K.Nair (8/18/2014)
Strange thing is that the same run without any issue in a default instance and have issue with named instance.can you elaborate this in detail?
The server where i got error is a named instance but when i create the same job in a default instance it works well.
The SSIS package we used inside the job is 2008 version and SQL Server is 2012,can this be a reason?
August 21, 2014 at 5:18 am
Ratheesh.K.Nair (8/21/2014)
twin.devil (8/19/2014)
Ratheesh.K.Nair (8/18/2014)
Strange thing is that the same run without any issue in a default instance and have issue with named instance.can you elaborate this in detail?
The server where i got error is a named instance but when i create the same job in a default instance it works well.
The SSIS package we used inside the job is 2008 version and SQL Server is 2012,can this be a reason?
you need to migrate your 2008 package to 2012. you can do in SSDT(SQL Server Data Tools) previously known as BIDS.
once done try to execute the package from the SSDT if its run ok then attach this package with the sql job.
Viewing 13 posts - 1 through 12 (of 12 total)
You must be logged in to reply to this topic. Login to reply