Incorrect PageAudit

I've a database in SQLServer 2K Personal Edition. The database compatibility
level is set to 8. I was trying to create deployment package using Office 2K
Developer. I am using MSDE as my backend database manager.
Howerver when I try to attach my MDF in the MSDE, it gives me error as
follows:
"Invalid database page header. PageAudit Property is Incorrect"
Can anyone help me with this problem.
Thank you in advance
Dorji
hi Dorji,
Dorji wrote:
> I've a database in SQLServer 2K Personal Edition. The database
> compatibility level is set to 8. I was trying to create deployment
> package using Office 2K Developer. I am using MSDE as my backend
> database manager.
> Howerver when I try to attach my MDF in the MSDE, it gives me error as
> follows:
> "Invalid database page header. PageAudit Property is Incorrect"
Office 2000 provides MSDE 1.0 (based on SQL Server 7.0 code base)...
you can not restore/attach SQL Server 2000/MSDE 2000 databases on SQL Server
7.0/MSDE 1.0 intances..
you can perhaps download and use MSDE Rel A, updated at sp4 level from
http://www.microsoft.com/sql/msde/do...s/download.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hello Adrea,
Thank you so much for your kind response. But I still couldn't manage to
attach my database. In fact I've tried several of my databases from the same
source, none seem to work. I can attach exisitng databases (model etc) but no
mine.
What could it be?
Dorji
"Andrea Montanari" wrote:

> hi Dorji,
> Dorji wrote:
> Office 2000 provides MSDE 1.0 (based on SQL Server 7.0 code base)...
> you can not restore/attach SQL Server 2000/MSDE 2000 databases on SQL Server
> 7.0/MSDE 1.0 intances..
> you can perhaps download and use MSDE Rel A, updated at sp4 level from
> http://www.microsoft.com/sql/msde/do...s/download.asp
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Dorji,
Dorji wrote:
> Hello Adrea,
> Thank you so much for your kind response. But I still couldn't
> manage to attach my database. In fact I've tried several of my
> databases from the same source, none seem to work. I can attach
> exisitng databases (model etc) but no mine.
>
are you trying to attach SQL Server 2000/MSDE 2000 databases on MSDE 1.0?
again, if this is the case, this is not a supported option...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
It works now. I did not know that MSDE installs in Windows security mode by
default. So I had to change it to SQL and the connection works fine.
However I've another thing to ask if you don't mind. I've multiple instance
of SQL Server and MSDE 2000. How can I connect to a particular Instance for
instance from MS Access ADP file?.
I must thank you for the DbaManager utility that you have posted on your
website. It is a great tool for MSDE users. It really helped me with my
project.
Dorji
"Andrea Montanari" wrote:

> hi Dorji,
> Dorji wrote:
> are you trying to attach SQL Server 2000/MSDE 2000 databases on MSDE 1.0?
> again, if this is the case, this is not a supported option...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Dorji,
Dorji wrote:
> Hi Andrea,
> It works now. I did not know that MSDE installs in Windows security
> mode by default. So I had to change it to SQL and the connection
> works fine.
this should have little or nothing to do with the problem you reported...
changing the authentication supported mode to Mixed mode does not grant you
the option to attach invalid databases...
ok..

> However I've another thing to ask if you don't mind. I've multiple
> instance of SQL Server and MSDE 2000. How can I connect to a
> particular Instance for instance from MS Access ADP file?.
in the datalink dialog you have to select the server name...
the relative combo should be already populated with all available servers...
default instances will be in the form of "ComputerName", where named
instances will be listed as "ComputerName\InstanceName"...

> I must thank you for the DbaManager utility that you have posted on
> your website. It is a great tool for MSDE users. It really helped
> me with my project.
thank you for your interest in this prj of mine... and please feel free to
(privately) contact me for any question or concern about it, as long as for
suggestions and feedback
thank you
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Inconsistent package failures

I'm debugging my first SSIS package and is getting inconsistent results. The package does not always complete successfully. When the package does fail, it fails at different tasks that accquire database connections. Any of the following error message would show up:

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

[OLE DB Destination [6374]] Error: The AcquireConnection method call to the connection manager "FORGE.FMC" failed with error code 0xC0202009.

[Connection manager "FORGE.FMC"] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "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: 0x80004005Description: "Communication link failure". An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "Named Pipes Provider: No process is on the other end of the pipe. ".

I never experienced any connection error when executing query through management studio. It's only SSIS packages that fails to connect every now and then. Any help is appreciated.

Thanks.

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

-Jamie

|||

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.

|||

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.?

|||We are getting the same error - did you resolve this? if so, may we ask how?|||

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?

|||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.|||

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.

|||

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

|||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.|||

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.

|||

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

|||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!

|||

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

|||

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 interrupción de una conexión existente por el host remoto.

PLEASE SOMEONE!!!!!!

Inconsistent package failures

I'm debugging my first SSIS package and is getting inconsistent results. The package does not always complete successfully. When the package does fail, it fails at different tasks that accquire database connections. Any of the following error message would show up:

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

[OLE DB Destination [6374]] Error: The AcquireConnection method call to the connection manager "FORGE.FMC" failed with error code 0xC0202009.

[Connection manager "FORGE.FMC"] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "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: 0x80004005Description: "Communication link failure". An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "Named Pipes Provider: No process is on the other end of the pipe. ".

I never experienced any connection error when executing query through management studio. It's only SSIS packages that fails to connect every now and then. Any help is appreciated.

Thanks.

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

-Jamie

|||

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.

|||

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.?

|||We are getting the same error - did you resolve this? if so, may we ask how?|||

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?

|||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.|||

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.

|||

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

|||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.|||

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.

|||

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

|||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!

|||

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

|||

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 interrupción de una conexión existente por el host remoto.

PLEASE SOMEONE!!!!!!

Inconsistent package failures

I'm debugging my first SSIS package and is getting inconsistent results. The package does not always complete successfully. When the package does fail, it fails at different tasks that accquire database connections. Any of the following error message would show up:

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

[OLE DB Destination [6374]] Error: The AcquireConnection method call to the connection manager "FORGE.FMC" failed with error code 0xC0202009.

[Connection manager "FORGE.FMC"] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "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: 0x80004005Description: "Communication link failure". An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "Named Pipes Provider: No process is on the other end of the pipe. ".

I never experienced any connection error when executing query through management studio. It's only SSIS packages that fails to connect every now and then. Any help is appreciated.

Thanks.

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

-Jamie

|||

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.

|||

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.?

|||We are getting the same error - did you resolve this? if so, may we ask how?|||

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?

|||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.|||

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.

|||

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

|||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.|||

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.

|||

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

|||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!

|||

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

|||

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 interrupción de una conexión existente por el host remoto.

PLEASE SOMEONE!!!!!!

Inconsistent package failures

I'm debugging my first SSIS package and is getting inconsistent results. The package does not always complete successfully. When the package does fail, it fails at different tasks that accquire database connections. Any of the following error message would show up:

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

[OLE DB Destination [6374]] Error: The AcquireConnection method call to the connection manager "FORGE.FMC" failed with error code 0xC0202009.

[Connection manager "FORGE.FMC"] Error: An OLE DB error has occurred. Error code: 0x80004005. An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "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: 0x80004005Description: "Communication link failure". An OLE DB record is available.Source: "Microsoft SQL Native Client"Hresult: 0x80004005Description: "Named Pipes Provider: No process is on the other end of the pipe. ".

I never experienced any connection error when executing query through management studio. It's only SSIS packages that fails to connect every now and then. Any help is appreciated.

Thanks.

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

-Jamie

|||

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.

|||

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.?

|||We are getting the same error - did you resolve this? if so, may we ask how?|||

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?

|||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.|||

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.

|||

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

|||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.|||

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.

|||

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

|||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!

|||

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

|||

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 interrupción de una conexión existente por el host remoto.

PLEASE SOMEONE!!!!!!

Inconsistent DTS Error - Help please

I get an error every so often with a DTS package on SQL 7. Error as
follows.

The connection is currently being used by a task. The connection
cannot be
closed or re-used.

This doesn't happen all the time and I can sometimes (more often than
not) get the DTS package to complete in it's entirety.

To explain what the DTS package does...

Truncate tables in reporting environment(several in a batch)
Clear Transaction Logs
Copies data from live environment into CSV (for speed)
Copies data from CSV files into tables previously truncated.
Builds up a table based on the data copied (for reporting)
Clear Transaction logs

I'm using a pretty basic set up, Connection (1st DB) -> Transformation
to CSV -> Transformation to Connection (2nd DB). It seems to fail on
either the first or second transformation at random (?).

I've checked the transformations so that they close the connection
afterwards so it should in theory be releasing the CSV files for the
next step. I suspect that there is a timing issue with this. I can
copy the CSV files over, but this is a little sloppy and I would
prefer not to do it.

Any ideas how to find a tidy way to ensure these are closed both
before and afterwards ?

Thanks

Ryan"Ryan" <ryanofford@.hotmail.com> wrote in message
news:7802b79d.0402170522.6fdf7786@.posting.google.c om...
> I get an error every so often with a DTS package on SQL 7. Error as
> follows.
> The connection is currently being used by a task. The connection
> cannot be
> closed or re-used.
> This doesn't happen all the time and I can sometimes (more often than
> not) get the DTS package to complete in it's entirety.
> To explain what the DTS package does...
> Truncate tables in reporting environment(several in a batch)
> Clear Transaction Logs
> Copies data from live environment into CSV (for speed)
> Copies data from CSV files into tables previously truncated.
> Builds up a table based on the data copied (for reporting)
> Clear Transaction logs
> I'm using a pretty basic set up, Connection (1st DB) -> Transformation
> to CSV -> Transformation to Connection (2nd DB). It seems to fail on
> either the first or second transformation at random (?).
> I've checked the transformations so that they close the connection
> afterwards so it should in theory be releasing the CSV files for the
> next step. I suspect that there is a timing issue with this. I can
> copy the CSV files over, but this is a little sloppy and I would
> prefer not to do it.
> Any ideas how to find a tidy way to ensure these are closed both
> before and afterwards ?
> Thanks
> Ryan

I don't know of a specific solution to your problem, but you may be able to
use an ActiveX step to check the DTS Connection object's Connected property,
and call ReleaseConnection if necessary.

If that isn't helpful, you may want to post this in a more specialized
forum, such as microsoft.public.sqlserver.dts.

Simon|||That's done the trick. Thanks for the help. Used the following code :

Function Main()
Dim oPkg
Dim oConn

Set oPkg = DTSGlobalVariables.Parent
Set oConn = oPkg.Connections("myConnection")

oConn.ReleaseConnection
Main = DTSTaskExecResult_Success
End Function

"Simon Hayes" <sql@.hayes.ch> wrote in message news:<403274e9$1_3@.news.bluewin.ch>...
> "Ryan" <ryanofford@.hotmail.com> wrote in message
> news:7802b79d.0402170522.6fdf7786@.posting.google.c om...
> > I get an error every so often with a DTS package on SQL 7. Error as
> > follows.
> > The connection is currently being used by a task. The connection
> > cannot be
> > closed or re-used.
> > This doesn't happen all the time and I can sometimes (more often than
> > not) get the DTS package to complete in it's entirety.
> > To explain what the DTS package does...
> > Truncate tables in reporting environment(several in a batch)
> > Clear Transaction Logs
> > Copies data from live environment into CSV (for speed)
> > Copies data from CSV files into tables previously truncated.
> > Builds up a table based on the data copied (for reporting)
> > Clear Transaction logs
> > I'm using a pretty basic set up, Connection (1st DB) -> Transformation
> > to CSV -> Transformation to Connection (2nd DB). It seems to fail on
> > either the first or second transformation at random (?).
> > I've checked the transformations so that they close the connection
> > afterwards so it should in theory be releasing the CSV files for the
> > next step. I suspect that there is a timing issue with this. I can
> > copy the CSV files over, but this is a little sloppy and I would
> > prefer not to do it.
> > Any ideas how to find a tidy way to ensure these are closed both
> > before and afterwards ?
> > Thanks
> > Ryan
> I don't know of a specific solution to your problem, but you may be able to
> use an ActiveX step to check the DTS Connection object's Connected property,
> and call ReleaseConnection if necessary.
> If that isn't helpful, you may want to post this in a more specialized
> forum, such as microsoft.public.sqlserver.dts.
> Simon

Inconsistand execution of SISS Package

Hi

Can someone please help?

I have a small package that makes an OLDB connection to my local 2005 SQL server then does some processing and places the results in a text file as XML

I have created a stored proc that uses xp_cmdshell to call the package and pass a paramter to it.

It all works fine when I call it from the command line or execute the stored proc from SQL Management Studio or if I call it as part of a SQL Agent job, but when it is called from C# from an ASP page then it fails with a timeout error.

Even stanger is the fact that when there is no data there for it to process it runs OK so I dont think it is permissions but the size of the output file only has to be a couple of k for it to fail from the ASP page.

If we comment out some of the functions in the package then it will execute OK from ASP

Help Whats going on ?

Got a work around for it at the moment. I created an agent job which starts the package then used sp_start_job in my application to start the job and hence the package and it all works OK

Would like to know why I cant get it to work directly from the application though

Cheers

Including MSDE in Windows package, containing C# app

Hi,
I am trying to create a windows installer package, that will install:
- .NET framework
- MSDE
- My app..
Can anyone offer some advice, or point me in the right direction.
How would the package know if .NET framework is already installed, or if
MSDE is already installed.
Any advice appreciated
Thanks
Paul,
There is a deployment tool kit for MSDE.
http://www.microsoft.com/sql/msde/te...ployreskit.asp
If you use windows installer included with visual studio. It will
automatically add
an install dependency for the .net framework for a c# program.
Karl
"Paul Aspinall" wrote:

> Hi,
> I am trying to create a windows installer package, that will install:
> - .NET framework
> - MSDE
> - My app..
> Can anyone offer some advice, or point me in the right direction.
> How would the package know if .NET framework is already installed, or if
> MSDE is already installed.
> Any advice appreciated
> Thanks
>
>

In your opinion: what's the best book on DTS?

I need to build an extensive DTS package and my experience is with simple
DTS techniques only. I like books that start with simple but include
advanced.
What would you reccomend?
Thanks,
DarwinHave a look at the site we have a carousel that shows the books.
The book by Brian Knight et al is good as is the Peterson book
Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
www.SQLIS.com - You thought DTS was good. here we show you the new stuff.
www.konesans.com - Consultancy from the people who know
"Darwin Fisk" <Darwin@.DotNetDesigns.com> wrote in message
news:OJwl0vVBFHA.3644@.TK2MSFTNGP15.phx.gbl...
>I need to build an extensive DTS package and my experience is with simple
>DTS techniques only. I like books that start with simple but include
>advanced.
> What would you reccomend?
> Thanks,
> Darwin
>