Showing posts with label configured. Show all posts
Showing posts with label configured. Show all posts

Wednesday, March 28, 2012

Problems in Loading configuration file

Hi,

We have configured package to load configurations from XML file.

But whenever we try to run the package, it throws below warning message

and continues to download the configuration file and finally ending up in low memory exception

The package is attempting to configure from the XML file "E:\Cybage\Deployment\MSCERT\MSCERT_MainPackgeConfig.dtsConfig".

I have made sure the file exists at the above location.

Please let me know if anyone have any solution on this.


Regards,

sachin

What exactly is the file name you are trying to supply? What are the machine specs where the package is running? What exactly is configured in the xml file?
|||

SachinS wrote:

The package is attempting to configure from the XML file "E:\Cybage\Deployment\MSCERT\MSCERT_MainPackgeConfig.dtsConfig".

That's an informational message. Where's the error/warning message? That message will occur every single time (and it is valid) that the package runs.|||

We are storing connection strings in this config file.

'Loading configuration settings from file' message gets repeated n number of times and it does not stop until it gets some memory exception

|||Do you have the same configuration file listed multiple times in the package configuration window?sql

Wednesday, March 21, 2012

problems connecting remotely to sql server 2005

hi. im still a bit new in handling SQL and im having problems connecting to a remote sql server 2005. i have already configured the surface area to accept remote connections and am using the connection string:

SqlConnection lasConnection = new SqlConnection("user id = sa;" +

"password = 12345; server = Naomi;" +

"Trusted_Connection = yes;" +

"database = LAS;" +

"connection timeout=30");

and it returns an error of "System.Data.SqlClient.SqlException: Login failed for user 'NAOMI\Guest' "

however, when i use the application on the same computer as the server, it has no problems connecting at all. could please point me to the right direction on how i should face this problem?

thanks in advance

hi. im still a bit new in handling SQL and im having problems connecting to a remote sql server 2005. i have already configured the surface area to accept remote connections and am using the connection string:

SqlConnection lasConnection = new SqlConnection("user id = sa;" +

"password = 12345; server = Naomi;" +

"Trusted_Connection = yes;" +

"database = LAS;" +

"connection timeout=30");

and it returns an error of "System.Data.SqlClient.SqlException: Login failed for user 'NAOMI\Guest' "

however, when i use the application on the same computer as the server, it has no problems connecting at all. could please point me to the right direction on how i should face this problem?

thanks in advance

|||

I merged these threads as they appear to be duplicates.

Are you using SSIS? If not, you might want to post in the SQL Server Data Access forum.

As a quick thought, you have the security set to a trusted connection, which means you don't have to specify a user id and password. You might want to take a look at http://www.connectionstrings.com/.

|||that was weird... when i tried a different connection string without the trusted connection then configured the surface area of the sql server for remote access it just connected like magic. hehe. sorry for being so bad at this btw. i already figured out how to connect to the server using the add data connection wizard in VS2K5 but i was wondering how do i access the data using this connection? how do i open it? coz in the old style we still need a manually configure a connection string, connect it and then do the queries.|||Still not clear on whether this is SSIS - in SSIS, you'd add a new connection manager (in the lower pane in the designer) to use a connection.

Problems Connecting Remotely - Integration Services

All,
We have a new install of SQL 2005 SP1 configured with a Navision
database restored and all client tests show no issues at moment. I am
able to connect remotely via SSMS (Management Studio) from my
workstation via TCP/IP. Also installed is Integration Services. I am
able connect to the service remotely to view the Stored Packages in the
File System but unable to view the MSDB contents. The error is below:
->Login timeout expired
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failue may be caused by the
fact that under the default settings SQL Server does not allow remote
connections.
TCP Provider: No connection could be made because the target machine
actively refused it. (Microsoft SQL Native Client)
No firewall exists on this server. Does anyone have insight to this
issue?
Thanks,
IanUpdate: Reviewing the Surface Area Configuration shows that Local and
remote connections are enabled for both TCP/IP and Named Pipes.
Connection via Named Pipes produced the similar error below:
->Login timeout expired
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failue may be caused by the
fact that under the default settings SQL Server does not allow remote
connections.
Named Pipes Provider: Could not open a connection to SQL Server [2].
(Microsoft SQL Native Client)
Regards,
Ian

Problems Connecting Remotely - Integration Services

All,
We have a new install of SQL 2005 SP1 configured with a Navision
database restored and all client tests show no issues at moment. I am
able to connect remotely via SSMS (Management Studio) from my
workstation via TCP/IP. Also installed is Integration Services. I am
able connect to the service remotely to view the Stored Packages in the
File System but unable to view the MSDB contents. The error is below:
->Login timeout expired
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failue may be caused by the
fact that under the default settings SQL Server does not allow remote
connections.
TCP Provider: No connection could be made because the target machine
actively refused it. (Microsoft SQL Native Client)
No firewall exists on this server. Does anyone have insight to this
issue?
Thanks,
IanUpdate: Reviewing the Surface Area Configuration shows that Local and
remote connections are enabled for both TCP/IP and Named Pipes.
Connection via Named Pipes produced the similar error below:
->Login timeout expired
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failue may be caused by the
fact that under the default settings SQL Server does not allow remote
connections.
Named Pipes Provider: Could not open a connection to SQL Server [2].
(Microsoft SQL Native Client)
Regards,
Iansql

Problems Connecting Remotely - Integration Services

All,
We have a new install of SQL 2005 SP1 configured with a Navision
database restored and all client tests show no issues at moment. I am
able to connect remotely via SSMS (Management Studio) from my
workstation via TCP/IP. Also installed is Integration Services. I am
able connect to the service remotely to view the Stored Packages in the
File System but unable to view the MSDB contents. The error is below:
->Login timeout expired
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failue may be caused by the
fact that under the default settings SQL Server does not allow remote
connections.
TCP Provider: No connection could be made because the target machine
actively refused it. (Microsoft SQL Native Client)
No firewall exists on this server. Does anyone have insight to this
issue?
Thanks,
Ian
Update: Reviewing the Surface Area Configuration shows that Local and
remote connections are enabled for both TCP/IP and Named Pipes.
Connection via Named Pipes produced the similar error below:
->Login timeout expired
An error has occured while establishing a connection to the server.
When connecting to SQL Server 2005, this failue may be caused by the
fact that under the default settings SQL Server does not allow remote
connections.
Named Pipes Provider: Could not open a connection to SQL Server [2].
(Microsoft SQL Native Client)
Regards,
Ian

Monday, March 12, 2012

problem: user account access (always uses the same account)

I've configured the IIS with only windows authentication, when i connect to
Reporting Server or Reporting Administrator uses the windows account, but
the security rules work different:
I have configured rules for two accounts: my windows account and
IUSR_machine.
When i try to connect to servers i put my windows account and goes ok, but
the security rules works with the rules assigned to the iusr_machine. Any
rule assigned to my user doesn't have effect, and all the changes makes in
the IUSR_machine's rules have effect.
I've configured restrict access to the iusr_machine and grant permission for
my windows account. When i connect with my windows account and i try to do
any task that iusr_machine haven't permission, the server response me that
the iusr_machine haven't permmission to do it.
Any idea?
thank you.
Oliver
"Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> escribió en el
mensaje news:OT0ifxqZEHA.212@.TK2MSFTNGP12.phx.gbl...
> Usually this is because anonymous is set on the IIS web site settings.
>
> --
> Brian Welcker
> Group Program Manager
> SQL Server Reporting Services
>
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> "oli" <oli1350@.hotmail.com> wrote in message
> news:eHPoJtZZEHA.3132@.TK2MSFTNGP10.phx.gbl...
> > Hi,
> > I'm having problem with the authentication in reports. When a user
sign
> > in to Report Administrator or Report Server validates with the IIS'
> > configuration. Onces inside always use the same user with the rules
> > security: IWAM_machine.
> > I need the account used inside of Reporting Server/Reporting
> > Administration
> > should be the same that the account used to validates with IIS.
> >
> > It's possible'
> >
> > Thank you in advanced.
> >
> > Oliver
> >
> >
>
>You have to disable anonymous access for both Reports and Reportserver
virtual directories.
--
Tudor Trufinescu
Dev Lead
Sql Server Reporting Services
This posting is provided "AS IS" with no warranties, and confers no rights.
"oli" <oli1350@.hotmail.com> wrote in message
news:#YUfIwBaEHA.212@.TK2MSFTNGP12.phx.gbl...
> I've configured the IIS with only windows authentication, when i connect
to
> Reporting Server or Reporting Administrator uses the windows account, but
> the security rules work different:
> I have configured rules for two accounts: my windows account and
> IUSR_machine.
> When i try to connect to servers i put my windows account and goes ok, but
> the security rules works with the rules assigned to the iusr_machine. Any
> rule assigned to my user doesn't have effect, and all the changes makes in
> the IUSR_machine's rules have effect.
> I've configured restrict access to the iusr_machine and grant permission
for
> my windows account. When i connect with my windows account and i try to do
> any task that iusr_machine haven't permission, the server response me
that
> the iusr_machine haven't permmission to do it.
> Any idea?
> thank you.
> Oliver
> "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> escribió en el
> mensaje news:OT0ifxqZEHA.212@.TK2MSFTNGP12.phx.gbl...
> > Usually this is because anonymous is set on the IIS web site settings.
> >
> > --
> > Brian Welcker
> > Group Program Manager
> > SQL Server Reporting Services
> >
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "oli" <oli1350@.hotmail.com> wrote in message
> > news:eHPoJtZZEHA.3132@.TK2MSFTNGP10.phx.gbl...
> > > Hi,
> > > I'm having problem with the authentication in reports. When a user
> sign
> > > in to Report Administrator or Report Server validates with the IIS'
> > > configuration. Onces inside always use the same user with the rules
> > > security: IWAM_machine.
> > > I need the account used inside of Reporting Server/Reporting
> > > Administration
> > > should be the same that the account used to validates with IIS.
> > >
> > > It's possible'
> > >
> > > Thank you in advanced.
> > >
> > > Oliver
> > >
> > >
> >
> >
>|||I uses the windows integrated authentication in both, but with the same
result: the rules works like if i authenticates with iwam_machine.
"Tudor Trufinescu (MSFT)" <tudortr@.ms.com> escribió en el mensaje
news:utWbctEaEHA.2792@.TK2MSFTNGP09.phx.gbl...
> You have to disable anonymous access for both Reports and Reportserver
> virtual directories.
> --
> Tudor Trufinescu
> Dev Lead
> Sql Server Reporting Services
> This posting is provided "AS IS" with no warranties, and confers no
rights.
> "oli" <oli1350@.hotmail.com> wrote in message
> news:#YUfIwBaEHA.212@.TK2MSFTNGP12.phx.gbl...
> > I've configured the IIS with only windows authentication, when i connect
> to
> > Reporting Server or Reporting Administrator uses the windows account,
but
> > the security rules work different:
> > I have configured rules for two accounts: my windows account and
> > IUSR_machine.
> >
> > When i try to connect to servers i put my windows account and goes ok,
but
> > the security rules works with the rules assigned to the iusr_machine.
Any
> > rule assigned to my user doesn't have effect, and all the changes makes
in
> > the IUSR_machine's rules have effect.
> >
> > I've configured restrict access to the iusr_machine and grant permission
> for
> > my windows account. When i connect with my windows account and i try to
do
> > any task that iusr_machine haven't permission, the server response me
> that
> > the iusr_machine haven't permmission to do it.
> >
> > Any idea?
> >
> > thank you.
> >
> > Oliver
> >
> > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> escribió en el
> > mensaje news:OT0ifxqZEHA.212@.TK2MSFTNGP12.phx.gbl...
> > > Usually this is because anonymous is set on the IIS web site settings.
> > >
> > > --
> > > Brian Welcker
> > > Group Program Manager
> > > SQL Server Reporting Services
> > >
> > > This posting is provided "AS IS" with no warranties, and confers no
> > rights.
> > >
> > > "oli" <oli1350@.hotmail.com> wrote in message
> > > news:eHPoJtZZEHA.3132@.TK2MSFTNGP10.phx.gbl...
> > > > Hi,
> > > > I'm having problem with the authentication in reports. When a
user
> > sign
> > > > in to Report Administrator or Report Server validates with the IIS'
> > > > configuration. Onces inside always use the same user with the rules
> > > > security: IWAM_machine.
> > > > I need the account used inside of Reporting Server/Reporting
> > > > Administration
> > > > should be the same that the account used to validates with IIS.
> > > >
> > > > It's possible'
> > > >
> > > > Thank you in advanced.
> > > >
> > > > Oliver
> > > >
> > > >
> > >
> > >
> >
> >
>|||sorry,
i wanted to say i uses only windows integrated authentication in both(not
uses anonymous access)
"oli" <oli1350@.hotmail.com> escribió en el mensaje
news:ub%23HEVLaEHA.3420@.TK2MSFTNGP12.phx.gbl...
> I uses the windows integrated authentication in both, but with the same
> result: the rules works like if i authenticates with iwam_machine.
>
> "Tudor Trufinescu (MSFT)" <tudortr@.ms.com> escribió en el mensaje
> news:utWbctEaEHA.2792@.TK2MSFTNGP09.phx.gbl...
> > You have to disable anonymous access for both Reports and Reportserver
> > virtual directories.
> >
> > --
> > Tudor Trufinescu
> > Dev Lead
> > Sql Server Reporting Services
> > This posting is provided "AS IS" with no warranties, and confers no
> rights.
> >
> > "oli" <oli1350@.hotmail.com> wrote in message
> > news:#YUfIwBaEHA.212@.TK2MSFTNGP12.phx.gbl...
> > > I've configured the IIS with only windows authentication, when i
connect
> > to
> > > Reporting Server or Reporting Administrator uses the windows account,
> but
> > > the security rules work different:
> > > I have configured rules for two accounts: my windows account and
> > > IUSR_machine.
> > >
> > > When i try to connect to servers i put my windows account and goes ok,
> but
> > > the security rules works with the rules assigned to the iusr_machine.
> Any
> > > rule assigned to my user doesn't have effect, and all the changes
makes
> in
> > > the IUSR_machine's rules have effect.
> > >
> > > I've configured restrict access to the iusr_machine and grant
permission
> > for
> > > my windows account. When i connect with my windows account and i try
to
> do
> > > any task that iusr_machine haven't permission, the server response me
> > that
> > > the iusr_machine haven't permmission to do it.
> > >
> > > Any idea?
> > >
> > > thank you.
> > >
> > > Oliver
> > >
> > > "Brian Welcker [MSFT]" <bwelcker@.online.microsoft.com> escribió en el
> > > mensaje news:OT0ifxqZEHA.212@.TK2MSFTNGP12.phx.gbl...
> > > > Usually this is because anonymous is set on the IIS web site
settings.
> > > >
> > > > --
> > > > Brian Welcker
> > > > Group Program Manager
> > > > SQL Server Reporting Services
> > > >
> > > > This posting is provided "AS IS" with no warranties, and confers no
> > > rights.
> > > >
> > > > "oli" <oli1350@.hotmail.com> wrote in message
> > > > news:eHPoJtZZEHA.3132@.TK2MSFTNGP10.phx.gbl...
> > > > > Hi,
> > > > > I'm having problem with the authentication in reports. When a
> user
> > > sign
> > > > > in to Report Administrator or Report Server validates with the
IIS'
> > > > > configuration. Onces inside always use the same user with the
rules
> > > > > security: IWAM_machine.
> > > > > I need the account used inside of Reporting Server/Reporting
> > > > > Administration
> > > > > should be the same that the account used to validates with IIS.
> > > > >
> > > > > It's possible'
> > > > >
> > > > > Thank you in advanced.
> > > > >
> > > > > Oliver
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>

Problem: SSIS, ODBC and Progress Database

Hi,

The project I′m working needs to import data from a Progress Database. I had configured my ODBC (MERANT 3.60 32-BIT Progress SQL92 v9.1D) driver and everything seems to be ok.

But when I tried to create a DataRearder Source pointing to my ODBC Data Source, and open the next tab I received this error message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Anyone can help ?

DataReaderSource requires a managed ADO.Net connection, so try to create a ADO.Net:ODBC connection first then point to that connection at DataReaderSrc.

Thanks

Wenyang

|||

Wenyang,

Since the first time I did what you said. I create a ADO.NET:ODBC connection and I received a successifull message.

But when I create create a DataReader Source and point to my ADO.NET:ODBC connection I receive this message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Appreciate your attencion.

[ ]′s

|||

um...normally this error is only seen when you use a wrong type of connection manager(e.g. a native one) at DataReaderSrc.

If you did use .Net provider for ODBC in your connection manager, did you see success when pushing the button "Test Connection" in your connection manager? We cast the connection to IDbConnection, I see no reason why you succeeded there but failed in DataReaderSrc on this error...

Thanks

Wenyang

|||

were you able to slove this problem..

I am also facing similar problems.

|||

Even i am facing similar kind of problem. But i my case i trying to connect to JDE through ODBC driver.

When i test the connection in connection manager, it succeds. but when i try to pull data using DataSource reader, it gives the same error,

"Error at DAta Flow Tast[DataReader Source [1]]: Cannot acquire a managed connection from the run-time connection manager."

Can any body help me ?

Regards,

Chetan

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

Hi, I am facing problem to connect to progress db in .net,

Would you please let me know of the connection string and other settings ,

I currently get connection string wrong format problem , but the weird part is when i test connection, it passes.

but then i get error when i try set anything else.

Thanking you.

|||

Problem solved

|||

Hi,

Could you please share your experience with us?

Thanks

Problem: SSIS, ODBC and Progress Database

Hi,

The project I′m working needs to import data from a Progress Database. I had configured my ODBC (MERANT 3.60 32-BIT Progress SQL92 v9.1D) driver and everything seems to be ok.

But when I tried to create a DataRearder Source pointing to my ODBC Data Source, and open the next tab I received this error message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Anyone can help ?

DataReaderSource requires a managed ADO.Net connection, so try to create a ADO.Net:ODBC connection first then point to that connection at DataReaderSrc.

Thanks

Wenyang

|||

Wenyang,

Since the first time I did what you said. I create a ADO.NET:ODBC connection and I received a successifull message.

But when I create create a DataReader Source and point to my ADO.NET:ODBC connection I receive this message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Appreciate your attencion.

[ ]′s

|||

um...normally this error is only seen when you use a wrong type of connection manager(e.g. a native one) at DataReaderSrc.

If you did use .Net provider for ODBC in your connection manager, did you see success when pushing the button "Test Connection" in your connection manager? We cast the connection to IDbConnection, I see no reason why you succeeded there but failed in DataReaderSrc on this error...

Thanks

Wenyang

|||

were you able to slove this problem..

I am also facing similar problems.

|||

Even i am facing similar kind of problem. But i my case i trying to connect to JDE through ODBC driver.

When i test the connection in connection manager, it succeds. but when i try to pull data using DataSource reader, it gives the same error,

"Error at DAta Flow Tast[DataReader Source [1]]: Cannot acquire a managed connection from the run-time connection manager."

Can any body help me ?

Regards,

Chetan

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

Hi, I am facing problem to connect to progress db in .net,

Would you please let me know of the connection string and other settings ,

I currently get connection string wrong format problem , but the weird part is when i test connection, it passes.

but then i get error when i try set anything else.

Thanking you.

|||

Problem solved

|||

Hi,

Could you please share your experience with us?

Thanks

Problem: SSIS, ODBC and Progress Database

Hi,

The project I′m working needs to import data from a Progress Database. I had configured my ODBC (MERANT 3.60 32-BIT Progress SQL92 v9.1D) driver and everything seems to be ok.

But when I tried to create a DataRearder Source pointing to my ODBC Data Source, and open the next tab I received this error message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Anyone can help ?

DataReaderSource requires a managed ADO.Net connection, so try to create a ADO.Net:ODBC connection first then point to that connection at DataReaderSrc.

Thanks

Wenyang

|||

Wenyang,

Since the first time I did what you said. I create a ADO.NET:ODBC connection and I received a successifull message.

But when I create create a DataReader Source and point to my ADO.NET:ODBC connection I receive this message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Appreciate your attencion.

[ ]′s

|||

um...normally this error is only seen when you use a wrong type of connection manager(e.g. a native one) at DataReaderSrc.

If you did use .Net provider for ODBC in your connection manager, did you see success when pushing the button "Test Connection" in your connection manager? We cast the connection to IDbConnection, I see no reason why you succeeded there but failed in DataReaderSrc on this error...

Thanks

Wenyang

|||

were you able to slove this problem..

I am also facing similar problems.

|||

Even i am facing similar kind of problem. But i my case i trying to connect to JDE through ODBC driver.

When i test the connection in connection manager, it succeds. but when i try to pull data using DataSource reader, it gives the same error,

"Error at DAta Flow Tast[DataReader Source [1]]: Cannot acquire a managed connection from the run-time connection manager."

Can any body help me ?

Regards,

Chetan

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

Hi, I am facing problem to connect to progress db in .net,

Would you please let me know of the connection string and other settings ,

I currently get connection string wrong format problem , but the weird part is when i test connection, it passes.

but then i get error when i try set anything else.

Thanking you.

|||

Problem solved

|||

Hi,

Could you please share your experience with us?

Thanks

Problem: SSIS, ODBC and Progress Database

Hi,

The project I′m working needs to import data from a Progress Database. I had configured my ODBC (MERANT 3.60 32-BIT Progress SQL92 v9.1D) driver and everything seems to be ok.

But when I tried to create a DataRearder Source pointing to my ODBC Data Source, and open the next tab I received this error message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Anyone can help ?

DataReaderSource requires a managed ADO.Net connection, so try to create a ADO.Net:ODBC connection first then point to that connection at DataReaderSrc.

Thanks

Wenyang

|||

Wenyang,

Since the first time I did what you said. I create a ADO.NET:ODBC connection and I received a successifull message.

But when I create create a DataReader Source and point to my ADO.NET:ODBC connection I receive this message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Appreciate your attencion.

[ ]′s

|||

um...normally this error is only seen when you use a wrong type of connection manager(e.g. a native one) at DataReaderSrc.

If you did use .Net provider for ODBC in your connection manager, did you see success when pushing the button "Test Connection" in your connection manager? We cast the connection to IDbConnection, I see no reason why you succeeded there but failed in DataReaderSrc on this error...

Thanks

Wenyang

|||

were you able to slove this problem..

I am also facing similar problems.

|||

Even i am facing similar kind of problem. But i my case i trying to connect to JDE through ODBC driver.

When i test the connection in connection manager, it succeds. but when i try to pull data using DataSource reader, it gives the same error,

"Error at DAta Flow Tast[DataReader Source [1]]: Cannot acquire a managed connection from the run-time connection manager."

Can any body help me ?

Regards,

Chetan

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

Hi, I am facing problem to connect to progress db in .net,

Would you please let me know of the connection string and other settings ,

I currently get connection string wrong format problem , but the weird part is when i test connection, it passes.

but then i get error when i try set anything else.

Thanking you.

|||

Problem solved

|||

Hi,

Could you please share your experience with us?

Thanks

Problem: SSIS, ODBC and Progress Database

Hi,

The project I′m working needs to import data from a Progress Database. I had configured my ODBC (MERANT 3.60 32-BIT Progress SQL92 v9.1D) driver and everything seems to be ok.

But when I tried to create a DataRearder Source pointing to my ODBC Data Source, and open the next tab I received this error message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Anyone can help ?

DataReaderSource requires a managed ADO.Net connection, so try to create a ADO.Net:ODBC connection first then point to that connection at DataReaderSrc.

Thanks

Wenyang

|||

Wenyang,

Since the first time I did what you said. I create a ADO.NET:ODBC connection and I received a successifull message.

But when I create create a DataReader Source and point to my ADO.NET:ODBC connection I receive this message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Appreciate your attencion.

[ ]′s

|||

um...normally this error is only seen when you use a wrong type of connection manager(e.g. a native one) at DataReaderSrc.

If you did use .Net provider for ODBC in your connection manager, did you see success when pushing the button "Test Connection" in your connection manager? We cast the connection to IDbConnection, I see no reason why you succeeded there but failed in DataReaderSrc on this error...

Thanks

Wenyang

|||

were you able to slove this problem..

I am also facing similar problems.

|||

Even i am facing similar kind of problem. But i my case i trying to connect to JDE through ODBC driver.

When i test the connection in connection manager, it succeds. but when i try to pull data using DataSource reader, it gives the same error,

"Error at DAta Flow Tast[DataReader Source [1]]: Cannot acquire a managed connection from the run-time connection manager."

Can any body help me ?

Regards,

Chetan

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

Hi, I am facing problem to connect to progress db in .net,

Would you please let me know of the connection string and other settings ,

I currently get connection string wrong format problem , but the weird part is when i test connection, it passes.

but then i get error when i try set anything else.

Thanking you.

|||

Problem solved

|||

Hi,

Could you please share your experience with us?

Thanks

Problem: SSIS, ODBC and Progress Database

Hi,

The project I′m working needs to import data from a Progress Database. I had configured my ODBC (MERANT 3.60 32-BIT Progress SQL92 v9.1D) driver and everything seems to be ok.

But when I tried to create a DataRearder Source pointing to my ODBC Data Source, and open the next tab I received this error message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Anyone can help ?

DataReaderSource requires a managed ADO.Net connection, so try to create a ADO.Net:ODBC connection first then point to that connection at DataReaderSrc.

Thanks

Wenyang

|||

Wenyang,

Since the first time I did what you said. I create a ADO.NET:ODBC connection and I received a successifull message.

But when I create create a DataReader Source and point to my ADO.NET:ODBC connection I receive this message:

“Error at Data Flow Task [DataReader Soucer [135]]: Cannot acquire a managed connection from the run-time connection manager”

Appreciate your attencion.

[ ]′s

|||

um...normally this error is only seen when you use a wrong type of connection manager(e.g. a native one) at DataReaderSrc.

If you did use .Net provider for ODBC in your connection manager, did you see success when pushing the button "Test Connection" in your connection manager? We cast the connection to IDbConnection, I see no reason why you succeeded there but failed in DataReaderSrc on this error...

Thanks

Wenyang

|||

were you able to slove this problem..

I am also facing similar problems.

|||

Even i am facing similar kind of problem. But i my case i trying to connect to JDE through ODBC driver.

When i test the connection in connection manager, it succeds. but when i try to pull data using DataSource reader, it gives the same error,

"Error at DAta Flow Tast[DataReader Source [1]]: Cannot acquire a managed connection from the run-time connection manager."

Can any body help me ?

Regards,

Chetan

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

I had a similar issue, the error I was getting:

"Error at Data Flow Tast[DataReader Source [35]]: Cannot acquire a managed connection from the run-time connection manager."

I changed to the ADO.NET ODBC as suggested above and it worked for me, THANKS for the tip!

Before changing it to ADO.NET ODBC it would work in the connection manager for the test but not the data read task. You would think Microsoft would either give better error messages or not allow the connection to be selected or something instead of just giving generic messages.

|||

Hi, I am facing problem to connect to progress db in .net,

Would you please let me know of the connection string and other settings ,

I currently get connection string wrong format problem , but the weird part is when i test connection, it passes.

but then i get error when i try set anything else.

Thanking you.

|||

Problem solved

|||

Hi,

Could you please share your experience with us?

Thanks

Problem: SQL Server does not accept TCP connections

Hi,
I have a W2k3 with SQL Server 2000 SP4. I have configured the server
to use named pipes and TCP on 1433 (at least that is what the registry
and server configuration tool say)
However the server does not accept tcp connections (i tried with
telnet, query analyzer, etc).
Log says the following:
2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
Named Pipes.
0
2007-01-03 19:12:55.85 server SQL Server is ready for client
connections
Is this a SQL Server BUG or i am doing something wrong?
Thanks,
Ezequiel Naftali
enaftali@.pisol.com.arIts not listening on TCP for some reason...verify that you have SQL Server
sp3 or higher (I know you say you have SP4) by looking at the file version
of sqlservr.exe on the server
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167922343.027575.146800@.6g2000cwy.googlegroups.com...
> Hi,
> I have a W2k3 with SQL Server 2000 SP4. I have configured the server
> to use named pipes and TCP on 1433 (at least that is what the registry
> and server configuration tool say)
> However the server does not accept tcp connections (i tried with
> telnet, query analyzer, etc).
> Log says the following:
> 2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
> Named Pipes.
> 0
> 2007-01-03 19:12:55.85 server SQL Server is ready for client
> connections
>
> Is this a SQL Server BUG or i am doing something wrong?
> Thanks,
> Ezequiel Naftali
> enaftali@.pisol.com.ar
>|||Hi Kevin,
The .exe version number is: 2000.080.0194.00
(8.0.0.194)
Is that what you were asking me?
Thanks for the answer.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Its not listening on TCP for some reason...verify that you have SQL Server
> sp3 or higher (I know you say you have SP4) by looking at the file version
> of sqlservr.exe on the server
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167922343.027575.146800@.6g2000cwy.googlegroups.com...|||Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server.
If you are sure you already did it, look for a file in C:\windows\sqlsp.log
which is the sp4 install log
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167924459.305986.118040@.q40g2000cwq.googlegroups.com...
> Hi Kevin,
> The .exe version number is: 2000.080.0194.00
> (8.0.0.194)
> Is that what you were asking me?
> Thanks for the answer.
> Ezequiel
>
> Kevin3NF ha escrito:
>
>|||Kevin
You are right, I installed again SP4 and everything is working right.
Thank you very much.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server
.
> If you are sure you already did it, look for a file in C:\windows\sqlsp.lo
g
> which is the sp4 install log
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167924459.305986.118040@.q40g2000cwq.googlegroups.com...

Problem: SQL Server does not accept TCP connections

Hi,
I have a W2k3 with SQL Server 2000 SP4. I have configured the server
to use named pipes and TCP on 1433 (at least that is what the registry
and server configuration tool say)
However the server does not accept tcp connections (i tried with
telnet, query analyzer, etc).
Log says the following:
2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
Named Pipes.
0
2007-01-03 19:12:55.85 server SQL Server is ready for client
connections
Is this a SQL Server BUG or i am doing something wrong?
Thanks,
Ezequiel Naftali
enaftali@.pisol.com.ar
Its not listening on TCP for some reason...verify that you have SQL Server
sp3 or higher (I know you say you have SP4) by looking at the file version
of sqlservr.exe on the server
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167922343.027575.146800@.6g2000cwy.googlegrou ps.com...
> Hi,
> I have a W2k3 with SQL Server 2000 SP4. I have configured the server
> to use named pipes and TCP on 1433 (at least that is what the registry
> and server configuration tool say)
> However the server does not accept tcp connections (i tried with
> telnet, query analyzer, etc).
> Log says the following:
> 2007-01-03 19:12:55.85 server SQL server listening on Shared Memory,
> Named Pipes.
> 0
> 2007-01-03 19:12:55.85 server SQL Server is ready for client
> connections
>
> Is this a SQL Server BUG or i am doing something wrong?
> Thanks,
> Ezequiel Naftali
> enaftali@.pisol.com.ar
>
|||Hi Kevin,
The .exe version number is: 2000.080.0194.00
(8.0.0.194)
Is that what you were asking me?
Thanks for the answer.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Its not listening on TCP for some reason...verify that you have SQL Server
> sp3 or higher (I know you say you have SP4) by looking at the file version
> of sqlservr.exe on the server
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167922343.027575.146800@.6g2000cwy.googlegrou ps.com...
|||Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server.
If you are sure you already did it, look for a file in C:\windows\sqlsp.log
which is the sp4 install log
Kevin Hill
3NF Consulting
http://www.3nf-inc.com/NewsGroups.htm
Real-world stuff I run across with SQL Server:
http://kevin3nf.blogspot.com
"Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
news:1167924459.305986.118040@.q40g2000cwq.googlegr oups.com...
> Hi Kevin,
> The .exe version number is: 2000.080.0194.00
> (8.0.0.194)
> Is that what you were asking me?
> Thanks for the answer.
> Ezequiel
>
> Kevin3NF ha escrito:
>
|||Kevin
You are right, I installed again SP4 and everything is working right.
Thank you very much.
Ezequiel
Kevin3NF ha escrito:
[vbcol=seagreen]
> Yes...that is the RTM version number, not sp4. Re-apply sp4 on the server.
> If you are sure you already did it, look for a file in C:\windows\sqlsp.log
> which is the sp4 install log
> --
> Kevin Hill
> 3NF Consulting
> http://www.3nf-inc.com/NewsGroups.htm
> Real-world stuff I run across with SQL Server:
> http://kevin3nf.blogspot.com
>
> "Ezequiel" <ezequiel.naftali@.gmail.com> wrote in message
> news:1167924459.305986.118040@.q40g2000cwq.googlegr oups.com...

Friday, March 9, 2012

Problem: DTS parallel tasks running sequentially

Hi

I have a SQL Server 2000 instance running on a Windows Server 2003 box with 4 processors. SQL Server is configured to use all 4 processors, and use all available processors for parallelism.

I have created a simple DTS package which has 2 "execute external process" tasks with no precedence constraints between them. There are no connections required or defined for the two tasks (sequential
processing is forced on tasks sharing connections). The DTS package
properties have the "limit the number of tasks to execute in parallel"
set to 4.

However, despite the above configuration, the two steps are never executed in parallel, but always sequentially.

Does anyone have any ideas as to why these tasks are not being executed in parallel?

Any suggestions welcome.

Thanks.My first guess would be that you've established a precedence between the tasks by creating either a success or a failure connector between them. This forces DTS to complete the first task in order to know if it succeeds or fails before it can start the second task. Remove the presedence, and they ought to run in parallel.

-PatP|||Pat

Thanks for the reply but as I stated in my original post, there are no precedent constraints in place.

I have subsequently done further testing and it seems related to the task type. I can successfully run external commands in parallel via the ActiveX script task shelling out to call the executables, but cannot acheive parallel running using the "Execute External Process" task type.