Can''t Aquire connections because OfflineMode is true

I am designing a SSIS package (source=Flat files,, destination =OLEDB) which is executing fine on my system but when I try to execute it on Server 2003 (x64)
it says Error: The AcquireConenction method call to connection manager "name of conn" failed with error code 0xC0014019 and
it says can't Aquire Connections because OfflineMode is true, while as I checked several times while saving the package it is set to false...

One of our developers had the same problem today... try this technet article. I think there are two places where you can set it. A config file and the project settings themselves.

http://technet.microsoft.com/en-us/library/ms137749.aspx

|||Error says OfflineMode is true, but actually it is not..
|||

One of my collegues ran into the same issue some time ago. After contacting MSF support and several rounds of troubleshooting, I think he ended up re-installing SSIS and the problem went away...Sorry, but I don't have more details.

|||

We encountered this issue some time ago. We incurred this error when trying to execute the 32bit DTEXEC (Program Files (x86)) on a 64bit machine.

As Rafael mentioned after contacting Microsoft support we simply reinstalled the client tools for SSIS and the problem was resolved. We were unable to identify the specific cause of the issue. I believe this is another very similar thread that was discussed a while back: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1557996&SiteID=1

|||I resolved the issue, I changed the connection settings and executed it using 64-bit dtexec from command prompt

Can''t Aquire connections because OfflineMode is true

I am designing a SSIS package (source=Flat files,, destination =OLEDB) which is executing fine on my system but when I try to execute it on Server 2003 (x64)
it says Error: The AcquireConenction method call to connection manager "name of conn" failed with error code 0xC0014019 and
it says can't Aquire Connections because OfflineMode is true, while as I checked several times while saving the package it is set to false...

One of our developers had the same problem today... try this technet article. I think there are two places where you can set it. A config file and the project settings themselves.

http://technet.microsoft.com/en-us/library/ms137749.aspx

|||Error says OfflineMode is true, but actually it is not..
|||

One of my collegues ran into the same issue some time ago. After contacting MSF support and several rounds of troubleshooting, I think he ended up re-installing SSIS and the problem went away...Sorry, but I don't have more details.

|||

We encountered this issue some time ago. We incurred this error when trying to execute the 32bit DTEXEC (Program Files (x86)) on a 64bit machine.

As Rafael mentioned after contacting Microsoft support we simply reinstalled the client tools for SSIS and the problem was resolved. We were unable to identify the specific cause of the issue. I believe this is another very similar thread that was discussed a while back: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1557996&SiteID=1

|||I resolved the issue, I changed the connection settings and executed it using 64-bit dtexec from command prompt

Can''t Aquire connections because OfflineMode is true

I am designing a SSIS package (source=Flat files,, destination =OLEDB) which is executing fine on my system but when I try to execute it on Server 2003 (x64)
it says Error: The AcquireConenction method call to connection manager "name of conn" failed with error code 0xC0014019 and
it says can't Aquire Connections because OfflineMode is true, while as I checked several times while saving the package it is set to false...

One of our developers had the same problem today... try this technet article. I think there are two places where you can set it. A config file and the project settings themselves.

http://technet.microsoft.com/en-us/library/ms137749.aspx

|||Error says OfflineMode is true, but actually it is not..
|||

One of my collegues ran into the same issue some time ago. After contacting MSF support and several rounds of troubleshooting, I think he ended up re-installing SSIS and the problem went away...Sorry, but I don't have more details.

|||

We encountered this issue some time ago. We incurred this error when trying to execute the 32bit DTEXEC (Program Files (x86)) on a 64bit machine.

As Rafael mentioned after contacting Microsoft support we simply reinstalled the client tools for SSIS and the problem was resolved. We were unable to identify the specific cause of the issue. I believe this is another very similar thread that was discussed a while back: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1557996&SiteID=1

|||I resolved the issue, I changed the connection settings and executed it using 64-bit dtexec from command prompt

Can''t Aquire connections because OfflineMode is true

I am designing a SSIS package (source=Flat files,, destination =OLEDB) which is executing fine on my system but when I try to execute it on Server 2003 (x64)
it says Error: The AcquireConenction method call to connection manager "name of conn" failed with error code 0xC0014019 and
it says can't Aquire Connections because OfflineMode is true, while as I checked several times while saving the package it is set to false...

One of our developers had the same problem today... try this technet article. I think there are two places where you can set it. A config file and the project settings themselves.

http://technet.microsoft.com/en-us/library/ms137749.aspx

|||Error says OfflineMode is true, but actually it is not..
|||

One of my collegues ran into the same issue some time ago. After contacting MSF support and several rounds of troubleshooting, I think he ended up re-installing SSIS and the problem went away...Sorry, but I don't have more details.

|||

We encountered this issue some time ago. We incurred this error when trying to execute the 32bit DTEXEC (Program Files (x86)) on a 64bit machine.

As Rafael mentioned after contacting Microsoft support we simply reinstalled the client tools for SSIS and the problem was resolved. We were unable to identify the specific cause of the issue. I believe this is another very similar thread that was discussed a while back: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1557996&SiteID=1

|||I resolved the issue, I changed the connection settings and executed it using 64-bit dtexec from command prompt

Can''t Aquire connections because OfflineMode is true

I am designing a SSIS package (source=Flat files,, destination =OLEDB) which is executing fine on my system but when I try to execute it on Server 2003 (x64)
it says Error: The AcquireConenction method call to connection manager "name of conn" failed with error code 0xC0014019 and
it says can't Aquire Connections because OfflineMode is true, while as I checked several times while saving the package it is set to false...

One of our developers had the same problem today... try this technet article. I think there are two places where you can set it. A config file and the project settings themselves.

http://technet.microsoft.com/en-us/library/ms137749.aspx

|||Error says OfflineMode is true, but actually it is not..
|||

One of my collegues ran into the same issue some time ago. After contacting MSF support and several rounds of troubleshooting, I think he ended up re-installing SSIS and the problem went away...Sorry, but I don't have more details.

|||

We encountered this issue some time ago. We incurred this error when trying to execute the 32bit DTEXEC (Program Files (x86)) on a 64bit machine.

As Rafael mentioned after contacting Microsoft support we simply reinstalled the client tools for SSIS and the problem was resolved. We were unable to identify the specific cause of the issue. I believe this is another very similar thread that was discussed a while back: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1557996&SiteID=1

|||I resolved the issue, I changed the connection settings and executed it using 64-bit dtexec from command prompt
sql

Can''t Aquire connections because OfflineMode is true

I am designing a SSIS package (source=Flat files,, destination =OLEDB) which is executing fine on my system but when I try to execute it on Server 2003 (x64)
it says Error: The AcquireConenction method call to connection manager "name of conn" failed with error code 0xC0014019 and
it says can't Aquire Connections because OfflineMode is true, while as I checked several times while saving the package it is set to false...

One of our developers had the same problem today... try this technet article. I think there are two places where you can set it. A config file and the project settings themselves.

http://technet.microsoft.com/en-us/library/ms137749.aspx

|||Error says OfflineMode is true, but actually it is not..
|||

One of my collegues ran into the same issue some time ago. After contacting MSF support and several rounds of troubleshooting, I think he ended up re-installing SSIS and the problem went away...Sorry, but I don't have more details.

|||

We encountered this issue some time ago. We incurred this error when trying to execute the 32bit DTEXEC (Program Files (x86)) on a 64bit machine.

As Rafael mentioned after contacting Microsoft support we simply reinstalled the client tools for SSIS and the problem was resolved. We were unable to identify the specific cause of the issue. I believe this is another very similar thread that was discussed a while back: http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1557996&SiteID=1

|||I resolved the issue, I changed the connection settings and executed it using 64-bit dtexec from command prompt

cant aquire a managed connection, SSIS

HI I am creating an integration service and have created a connection
manager. I tested it and the connection passed. I then wend to the data
flow source and added a data reader source but get the error , cannot aquire
a managed connection from the runtime connection manager. I am trying to
create a simple package that will read data from a database using a query and
then write it out to an excel file. I am familiar with the old 2000 DTS
package development.
thanks.
--
Paul G
Software engineer.Paul,
I'm in the same boat and ended up having to go buy the Microsoft Press SSIS
book. I'm still going through it.
You probably will have to do the same as SSIS help seems to be limited in
here.
Good luck,
Jay
"Paul" <Paul@.discussions.microsoft.com> wrote in message
news:722EC193-D7B7-4B20-AB4F-1303F4AB625C@.microsoft.com...
> HI I am creating an integration service and have created a connection
> manager. I tested it and the connection passed. I then wend to the data
> flow source and added a data reader source but get the error , cannot
> aquire
> a managed connection from the runtime connection manager. I am trying to
> create a simple package that will read data from a database using a query
> and
> then write it out to an excel file. I am familiar with the old 2000 DTS
> package development.
> thanks.
> --
> Paul G
> Software engineer.|||Hi Jay I was able to get it working. I now have an Integrated Services
packages that moves data from one database to another and if successful
updates a table in the original database. Also if successful I have it write
out in a message box using vbscript. Also if it fails I have it wright out
an error message in a message box.
If I remember correctly I selected the connection from the properties of the
dataflow task. Also on the connection I used the ADO.net. In addition I
changed the authentication mode to mixed (this is in the properties of the
database). Hope this helps.
--
Paul G
Software engineer.
"Jay" wrote:
> Paul,
> I'm in the same boat and ended up having to go buy the Microsoft Press SSIS
> book. I'm still going through it.
> You probably will have to do the same as SSIS help seems to be limited in
> here.
> Good luck,
> Jay
> "Paul" <Paul@.discussions.microsoft.com> wrote in message
> news:722EC193-D7B7-4B20-AB4F-1303F4AB625C@.microsoft.com...
> > HI I am creating an integration service and have created a connection
> > manager. I tested it and the connection passed. I then wend to the data
> > flow source and added a data reader source but get the error , cannot
> > aquire
> > a managed connection from the runtime connection manager. I am trying to
> > create a simple package that will read data from a database using a query
> > and
> > then write it out to an excel file. I am familiar with the old 2000 DTS
> > package development.
> > thanks.
> > --
> > Paul G
> > Software engineer.
>
>

Cannot run report on the report server with ssis as a datasource

Helo All,

I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:

An error has occurred during report processing.

Cannot create a connection to data source 'DataSource1'.

is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.

My connection string looks something like this:

="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"

Could any please help me out of this?

Note: SSIS is parameterized here!

Regards,

Raju

Does it work if you remove the parameter?

Also, enable logging in the package so you can tell if SSRS is actually executing it.

|||

Hi,

I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.

The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.

|||

Yes, it is likely that account that SSRS is running under can't access the database. Can you change to use a SQL Server login to connect to the data source?

|||

Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.

Thanks for your help...

|||Did you restart all the services (SSIS, SSRS, etc)? You have to restart the services for them to pick up new env. variables.|||

I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .

Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.

|||What data source are you using? Does it have a 64-bit driver?|||

Hello All,

The issue got resolved. I was having windows sp2 and sql sevrer sp1 on my server. After installing sp2 sql server the issue got resolved and seems to be running fine.

Thanks to you all.

Raju

Cannot run report on the report server with ssis as a datasource

Helo All,

I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:

An error has occurred during report processing.

Cannot create a connection to data source 'DataSource1'.

is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.

My connection string looks something like this:

="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"

Could any please help me out of this?

Note: SSIS is parameterized here!

Regards,

Raju

Does it work if you remove the parameter?

Also, enable logging in the package so you can tell if SSRS is actually executing it.

|||

Hi,

I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.

The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.

|||

Yes, it is likely that account that SSRS is running under can't access the database. Can you change to use a SQL Server login to connect to the data source?

|||

Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.

Thanks for your help...

|||Did you restart all the services (SSIS, SSRS, etc)? You have to restart the services for them to pick up new env. variables.|||

I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .

Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.

|||What data source are you using? Does it have a 64-bit driver?|||

Hello All,

The issue got resolved. I was having windows sp2 and sql sevrer sp1 on my server. After installing sp2 sql server the issue got resolved and seems to be running fine.

Thanks to you all.

Raju

Cannot run report on the report server with ssis as a datasource

Helo All,

I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:

An error has occurred during report processing.

Cannot create a connection to data source 'DataSource1'.

is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.

My connection string looks something like this:

="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"

Could any please help me out of this?

Note: SSIS is parameterized here!

Regards,

Raju

Does it work if you remove the parameter?

Also, enable logging in the package so you can tell if SSRS is actually executing it.

|||

Hi,

I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.

The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.

|||

Yes, it is likely that account that SSRS is running under can't access the database. Can you change to use a SQL Server login to connect to the data source?

|||

Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.

Thanks for your help...

|||Did you restart all the services (SSIS, SSRS, etc)? You have to restart the services for them to pick up new env. variables.|||

I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .

Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.

|||What data source are you using? Does it have a 64-bit driver?|||

Hello All,

The issue got resolved. I was having windows sp2 and sql sevrer sp1 on my server. After installing sp2 sql server the issue got resolved and seems to be running fine.

Thanks to you all.

Raju

Cannot run report on the report server with ssis as a datasource

Helo All,

I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:

An error has occurred during report processing.

Cannot create a connection to data source 'DataSource1'.

is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.

My connection string looks something like this:

="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"

Could any please help me out of this?

Note: SSIS is parameterized here!

Regards,

Raju

Does it work if you remove the parameter?

Also, enable logging in the package so you can tell if SSRS is actually executing it.

|||

Hi,

I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.

The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.

|||

Yes, it is likely that account that SSRS is running under can't access the database. Can you change to use a SQL Server login to connect to the data source?

|||

Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.

Thanks for your help...

|||Did you restart all the services (SSIS, SSRS, etc)? You have to restart the services for them to pick up new env. variables.|||

I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .

Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.

|||What data source are you using? Does it have a 64-bit driver?|||

Hello All,

The issue got resolved. I was having windows sp2 and sql sevrer sp1 on my server. After installing sp2 sql server the issue got resolved and seems to be running fine.

Thanks to you all.

Raju

Cannot run report on the report server with ssis as a datasource

Helo All,

I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:

An error has occurred during report processing.

Cannot create a connection to data source 'DataSource1'.

is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.

My connection string looks something like this:

="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"

Could any please help me out of this?

Note: SSIS is parameterized here!

Regards,

Raju

Does it work if you remove the parameter?

Also, enable logging in the package so you can tell if SSRS is actually executing it.

|||

Hi,

I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.

The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.

|||

Yes, it is likely that account that SSRS is running under can't access the database. Can you change to use a SQL Server login to connect to the data source?

|||

Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.

Thanks for your help...

|||Did you restart all the services (SSIS, SSRS, etc)? You have to restart the services for them to pick up new env. variables.|||

I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .

Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.

|||What data source are you using? Does it have a 64-bit driver?|||

Hello All,

The issue got resolved. I was having windows sp2 and sql sevrer sp1 on my server. After installing sp2 sql server the issue got resolved and seems to be running fine.

Thanks to you all.

Raju

Cannot run report on the report server with ssis as a datasource

Helo All,

I have report which uses an ssis package as a datasource. when I develop the report on the visual studio seems like it runs fine. But when I deployed the same report on to the server (report server 64 bit machine) it is throwing me an error:

An error has occurred during report processing.

Cannot create a connection to data source 'DataSource1'.

is not a valid Win32 application. (Exception from HRESULT: 0x800700C1)

I have both sql sever and reporting server on the same machine and using windows credentials for both the servers(sql and reporting).Then I believe there is no credential issue.

My connection string looks something like this:

="/FILE C:\NTSDW\KPI\KPI_SSIS\NTSKPICCA_DATA_RECON_DELIVERY.dtsx /SET \Package.Variables[User::V_SSRS_PARAM].Properties[Value];" & """" & Parameters!V_SETT_DATE.Value & """"

Could any please help me out of this?

Note: SSIS is parameterized here!

Regards,

Raju

Does it work if you remove the parameter?

Also, enable logging in the package so you can tell if SSRS is actually executing it.

|||

Hi,

I am using ssis logging and found there is a connectivity issue. I am able to connect to the source systems but not able to connect to the target(dwh) system. But I am able to run the package with the same configuration( configurations stored in xml file on the drive ) . I am using windows authentication to connect to the target systems.

The report manager also runs on the windows authentication mode. I am not sure where exctly the issue is. I think there is some authentication(ASP NET user) issue with report manager connecting to the target system.

|||

Yes, it is likely that account that SSRS is running under can't access the database. Can you change to use a SQL Server login to connect to the data source?

|||

Yes, it worked with SQL login, but with direct XML configuration type. It did not work with Indirect configuration using the environment variable. What could be the reason? Any solution for this? This will cause our build/deployment to QA and Prod difficult.

Thanks for your help...

|||Did you restart all the services (SSIS, SSRS, etc)? You have to restart the services for them to pick up new env. variables.|||

I did start the SSRS and SSIS services, the issue is the report server is not able to call the package itself.I found that the package is not invoked as i have enabled the logging. No log file is wirtten.It gives me the same old error "Not a valid win32 application" .

Note: The same package is running fine on all the 32 bit machines , but not on the 64 bit machines.

|||What data source are you using? Does it have a 64-bit driver?|||

Hello All,

The issue got resolved. I was having windows sp2 and sql sevrer sp1 on my server. After installing sp2 sql server the issue got resolved and seems to be running fine.

Thanks to you all.

Raju

Cannot run Datamining query task in standard edition of Integration Services

Hi

We are using SQL Server 2005 Standard Edition. I have SSIS package which uses 'Data Mining Query Task'. I am using this task to run the predictions using the mining model I have deployed. When I run this SSIS package from IDE , everything is fine. But I deployed this SSIS to msdb, and when I right click on the package and run it from MSDB I get error message saying ,

'Cannot run this task in this edition of Integration Services. It requires higher level edition'.

Altimately we want to execute this SSIS from an API which is written in C#. Can you please suggest any workaround for doing so?

Thanks,

Vikas

You should be able to use the Data Mining Query Task in SQL Server Standard Edition - the Data Mining Query Transform is only available in Enterprise Edition. This may be an issue with running from msdb - I'm assuming the DB server is SE and not Workgroup or Express?

Regarding running a package stored in a DB from C#, please ask on the Integration Services forum.