Inconsistent package failures

Inconsistent package failures

• vnswathi

  For those still having problem with issue 1 above you might want to check the following link. I just read it and working to recreate the problem so as to see if I can solve apply the solution.

  http://lab.msdn.microsoft.com/productfeedback/viewfeedback.aspx feedbackid=c1394ab2-7e90-47de-a057-d2d183da74a2

  
  
  

• bassock

  I have also designed one package and i am getting the same type of error inconsistently.

  [Execute SQL Task] Error: Failed to acquire connection "server.database.username". Connection may not be configured correctly or you may not have the right permissions on this connection.

  [Connection manager "server.database.username".]Error: An OLE DB error has occurred. Error code: 0x80040E4D. An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Login failed for user 'user'."

  but whenever i test my connection it works fine,i try to change the connection with new connectionstring but with same parameters in all the component ,then it worked.But the package fails after creating the deployment package.what will be reason.

  
  

• pauleley

  You must have misconfigured your connection manager. What is the connection string (i.e. the ConnectionString parameter of the connection manager)

  -Jamie

  
  
  

• chakru

  I'm getting the same errors

  An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Communication link failure".

  An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80004005 Description: "Shared Memory Provider: No process is on the other end of the pipe.".

  I'm using OLE DB, Native SQL driver and just added the failing package to a Sequence task with required DTC transactions.

  Any one have a cure Also the passwords keep getting deleted behind the scenes in the connection managers and config file.

  thank you!

  
  

• Gauguin

  I use OLE DB and still get the message noted in the original post and shown below. I do not get it when I set the transactionOption = supported but do get it when I set it = required. Unfortunately, I need to have the package option required. I've checked and both the client running SSIS and all the db servers (2) have the DTC running.

  [Execute SQL Task] Error: Failed to acquire connection "Data_Source". Connection may not be configured correctly or you may not have the right permissions on this connection.

  
  

• Ronald Tan

  I have been getting similar messages all day. After I deploy and install my package to another server(either to file system or SQl server) and run it through schedule job, I get similar error. When I run it by right clicking it on MSDB or file system on SSIS, it works fine.
  the two errors I am getting are:

  [Execute SQL Task] Error: Failed to acquire connection "server.database.username". Connection may not be configured correctly or you may not have the right permissions on this connection.

  The variable "System::LocaleID" is already on the read list. A variable may only be added once to either the read lock list or the write lock list.

  Anyone out there who has a solution

  
  
  

• HarishLalwani

  Has anyone heard anything about this problem yet The way I am working around the two issues are listed below.

  1. The variable "System::LocaleID" is already on the read list. A variable may only be added once to either the read lock list or the write lock list.

  Workaround: I create a new control flow and copy all the dataflow from the one I am getting the error. Then delete it. This works fine but I shouldn't have to do this. This is the third time I have done this. Is this a bug or what

  2. Execute SQL Task] Error: Failed to acquire connection "server.database.username". Connection may not be configured correctly or you may not have the right permissions on this connection.

  Workaround: I have three connections. Two OLEDB and one ADO.NET. I found out that only the ADO.NET is giving me this error. I disabled the Execute SQL Task that is using this ADO.NEt and I was able to run my package successfully using my SQLAgent. I need that process as part of my complete package and would be glad if a solution is forth coming.

  
  
  

• Confuzed VB Guy....

  Hey Microsoft - WTF Can we please get someone to examine this issue I'm sure we are doing something wrong, but it does seem like a common error.
  

• scourge

  I have the same issue.
  Does anybody has solution for this issue

  
  
  

• tcpsoft

  I changed the provider to OLE DB. My package has been working fine for over a month in debug mode and as part of a job. The connection error appears to occur for SQL Native Client connections only... but that's only my theory.
  

• Andy Kwok

  omhoge wrote:

  I'm getting the same errors Also the passwords keep getting deleted behind the scenes in the connection managers and config file.

  That's by design. You can store passwords in the package in an encrypted fashion by changing the ProtectionLevel property of the package.

  -Jamie

  
  
  

• Mowali

  ConnectionString is connecting to a remote server:

  <Configuration ConfiguredType="Property" Path="\Package.Connections[FMC].Properties[ConnectionString]" ValueType="String">

  <ConfiguredValue>Data Source=ServerName;Initial Catalog=DBName;Provider=SQLNCLI.1;Integrated Security=SSPI;Auto Translate=False;

  </ConfiguredValue>

  </Configuration>

  If the connection string is misconfigured, shouldn't the package consistently fail at the same point My package sometimes fail at package validation, sometimes at different steps during execution, and sometimes complete with no error.

  Thanks in advance.

  
  

• Rusty01

  HI, I’M HAVING THE SAME PROBLEMS.. DO WE HAVE ANY SOLUTIONS OR WHAT

  Error: 0xC0202009 at Package, Connection manager "NAME X": An OLE DB error has occurred. Error code: 0x80040E4D.

  An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "Communication link failure".

  An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E4D Description: "TCP Provider: Se ha forzado la interrupcion de una conexion existente por el host remoto.

  PLEASE SOMEONE!!!!!!

  
  
  

• Dude1

  We are getting the same error - did you resolve this if so, may we ask how
  
• Inconsistent package failures