clear log: ssis

Showing posts with label ssis. Show all posts

Wednesday, March 28, 2012

how to connect to ssis service - The RPC server is unavailable err

Hi
I am trying to connect to ssis service on remote machine using the sql 2005
management studio
I get the following error :
TITLE: Connect to Server
Cannot connect to <servername>.
Connect to SSIS Service on machine "<servername>" failed:
The RPC server is unavailable.
What do I miss please help
Best regards
Meron FridmanDid you figure out a solution ' I have the same problem
--
homebre
----
homebrew's Profile: http://www.dbtalk.net/m5
View this thread: http://www.dbtalk.net/t29008|||I've got the same problem in a two-node active/active environment.
Anyone got any further info?
"homebrew" wrote:
> Did you figure out a solution ' I have the same problem.
>
> --
> homebrew
> ---
> homebrew's Profile: http://www.dbtalk.net/m55
> View this thread: http://www.dbtalk.net/t290084
> .
>|||I found out that one of our developers (developer #1) wasn't having an
problems, and that he had used a different disk to install on hi
desktop. So then developer #2 used his disk, and her problem went away
I had already put in a call to Microsoft, and we tested my RPC port
and they seemed fine. So I think I got a bad disk ... perhaps som
file is corrupted ?
Then he had another utility for me to try, but I haven't bothered yet
since I'm pretty sure it's the disk, and not something on my desktop
--
homebre
----
homebrew's Profile: http://www.dbtalk.net/m5
View this thread: http://www.dbtalk.net/t29008sql

how to connect to ssis service - The RPC server is unavailable err

Hi
I am trying to connect to ssis service on remote machine using the sql 2005
management studio
I get the following error :
TITLE: Connect to Server
Cannot connect to <servername>.
Connect to SSIS Service on machine "<servername>" failed:
The RPC server is unavailable.
What do I miss please help
Best regards
Meron FridmanDid you figure out a solution ' I have the same problem.
homebrew
---
homebrew's Profile: http://www.dbtalk.net/m55
View this thread: http://www.dbtalk.net/t290084|||I found out that one of our developers (developer #1) wasn't having any
problems, and that he had used a different disk to install on his
desktop. So then developer #2 used his disk, and her problem went away.
I had already put in a call to Microsoft, and we tested my RPC ports
and they seemed fine. So I think I got a bad disk ... perhaps some
file is corrupted ?
Then he had another utility for me to try, but I haven't bothered yet,
since I'm pretty sure it's the disk, and not something on my desktop.
homebrew
---
homebrew's Profile: http://www.dbtalk.net/m55
View this thread: http://www.dbtalk.net/t290084

Wednesday, March 21, 2012

How to connect ExecuteSQLTask with data flow task

Hi, there;
I am doing my first SSIS project that moves data from dbf file to SQL2005.
What I did here is that I created a dataflow task (move data)with ASP.NET successfully (Very happy!). Now I want to create an ExecuteSQLTask that runs before data flow runs. This ExecuteSQLTask is used used to create a table if there is no destination table in the SQL2005.
This can be done easily in SSIS design mode, just need to connect those two box with a green line: )
I had a look example from MS website, but I didn't find a code example to connect this two task.
Does anybody know how to resolve this or have any link with sample code?

Big thanks here.

Not sure what the issue is. Just drag the green line to the data flow task.|||

I am creating SSIS package from C# manully, not using the SQL Server Business Intelligence Development Studio at all. So I'd like to know how to connect these two task using C# code.

Thanks.

|||

Try this:

.....

//Create the package
Package pkg = new Package();

//Add the tasks
TaskHost sqlTask = (TaskHost)pkg.Executables.Add("STOCK:SQLTask");
TaskHost pipelinetask = (TaskHost)pkg.Executables.Add("STOCK:PipelineTask");

//Add the PrecedenceConstraint
PrecedenceConstraint pc = pkg.PrecedenceConstraints.Add(sqltask, pipelinetask);
pc.Value = DTSExecResult.Success;

.....

HTH,
Ovidiu Burlacu

Monday, March 12, 2012

How to Configure DSN with DataReader Source

Hi
I am not able configure DSN in SSIS, I tired with DataReader Source but its given error
" Check SQL Command Property"
Appriciate to you for Help

Errr....try checking the SQLCommand property. What is it set to?
What is a DSN in SSIS?

You have to provide more specific info if you really want people to help.

-Jamie|||

Hi Jamie

I made one DSN which pointing Excel Driver, But when Create Connection Manager for these DSN by using ADO.NET Connection Manager.
When i configure this connection manager in DataReader Source its give as error "check SQL Command property"
Here I am ot able to set SQL Commmand property
so please Help me to set the property with any example

|||If you are connecting to Excel, why give yourself the added grief of maintaining an external DSN? Use the OLE DB Provider for Jet and a file path. ODBC simply adds one more unnecessary layer of DLLs in the background.

-Doug|||Thanks Doug
I got it from OLE DB,Thanks again for your help

Friday, March 9, 2012

How to compose the connection String of a SSIS package that execute another package?

Dear All,

I now have two SSIS package, "TESTING" and "LOADING". The "TESTING" package have an execute package task that call the "LOADING" package. When I want to execute the TESTING package, how can I setup the connection string so that I can edit the password of the database connected by the "LOADING" package?

Regards,

Strike

You should use configurations to achieve this. There's plenty of material out there about SSIS configurations if you google it.

-Jamie

|||How about if I want to create a command file so that I can input the password externally in the command prompt?|||

You can pass values into a package via the command-line using the /SET option of dtexec.

If the package that you call is a parent package then you can pass the value through to the child using a parent package configuration.

-Jamie

|||

Hi Jamie,

I would like to know how can I setup the command line in the SQL Server Job Agent for executing the two packages mentioned above? I have already configured the parent variable for the child package. However, I have encountered some errors when executing the job, and I don't know how to set up the path for the child package in the command line as both of the packages are loaded from the SQL server, not from the file system.

Thank you very much!!

Strike Wong

|||For help building command lines, try DTExecUI.exe. Set the options you want, and then look at the Command Line page. You can copy the command from there. Obviously you can execute the package from there as well to check the validity of the command you have built.|||

Is this included in the MS SQL Server 2005?
I can't found it in the directories

|||

Yes -

How to: Run a Package Using the DTExecUI Utility
(http://msdn2.microsoft.com/en-us/library/d827d7b2-2eb6-4f4a-a775-ab00c444c0dd.aspx)

It should be available from a command prompt or the Run dialog, as the Bin folder were it lives should be on your PATH, set as part of the SQL 2005 install.

How to compile/translate a SSIS package in Japanese

Hi,

I have a requirement to do a data migration work for a Japanese client. The problem is I don't know Japanese and the client SME does not know English. So, my requirement is, I should be able to create a SSIS package in English and then should be able to compile or translate it into Japanese so that my Japanese SME can understand the package. Is it possible to do? If so, how can I do it?

Thanks in advance.

I'm not aware of any existing tool to do the translation. You can either do "bi-lingual package", e.g. use English task and components names, and the translator can add Japanese task and component descriptions. Or you can create a tool yourself using SSIS object model - it is easy to enumerate the tasks and components and rename them based on some dictionary previously created by translator.|||Thanks Michael.

Sunday, February 19, 2012

How to check whether SSIS is installed

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Please rerun the setup. In one of the first screens the setup program asks which components to installs, there are 5 checkboxes total: SQL/SSAS/SSRS/SSIS and Workstation components. Please make sure the SSIS check box is checked.

|||"Integration Services" is greyed-out as an installation option, I'm guessing, because I'm running XP. It seems odd that I can install Management Studio but cannot use the import-export wizard. Is this right? IS is not considered to be a "client tool" which the documentation says can be installed on XP?|||

Thanks for reporting this problem, it seems like we have a bug here.

Some components of SSIS (e.g. designer) are installed and work with 'Workstation Components' install. Other components of SSIS (e.g. service, dtexec, and dtexecui) require installation of 'Integration Services'.

In current build the wizard can't execute the package it created without 'Integration Services' installation, which for Enterprise Edition means you need Server OS. You can still save the package and run or schedule it on machine with SSIS installed.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

|||I got around the problem (hope I haven't created any others) by uninstalling Enterprise Edition and installing Developer Edition which allows all installation options. I added IS to the install and then successfully ran the import/export wizard.|||

I ran into the same thing in September CTP with an attempted import of an Excel 2003 spreadsheet. I had installed SSIS and was consistently running numerous fairly sophisticated ETL packages between MSSQL Server 2005, MSSQL Server 2000, Oracle and other sources. It does not appear that the error is related to SSIS not being installed.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

I'm getting this same error when using the RTM release of the SQL Management Studio Import wizard to import data from Excel into SQL 2000. Does anyone know how to fix this?
TITLE: SQL Server Import and Export Wizard

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

|||I also get this error with the RTM release of Management Studio. It seems ridiculous that the Import/Export wizard can't be run on a machine with just the workstation tools installed. I really don't want to install Developer Edition on all of the machines here. Is there no other workaround? Import/Export seems to be a natural function of a client-only installation.

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

|||I would really like to see this available as a hotfix before a service pack. Our company does a lot of data loading utilizing the Import/Export wizard and this issue will prevent us from upgrading to SQL Server 2005.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

How to check whether SSIS is installed

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Thanks for reporting this problem, it seems like we have a bug here.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

|||I too am experiencing this same problem. I am using the standard version of SQL Server Management Studio that I obtained for free at the SQL Server 2005 launch party in San Francisco. I am running Windows XP. I have tried to migrate tables from my remote SQL Server 2000 DB without success. Exporting to Access was successful, but when I import to the new DB I get the following errors:
- Pre-execute (Error)
Messages
Error 0xc0202009: Data Flow Task: An OLE DB error has occurred. Error code: 0x80040E21.
An OLE DB record is available. Source: "Microsoft SQL Native Client" Hresult: 0x80040E21 Description: "Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done.".
(SQL Server Import and Export Wizard)
Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)
Error 0xc004701a: Data Flow Task: component "Destination - flo_layouts" (46) failed the pre-execute phase and returned error code 0xC0202025.
(SQL Server Import and Export Wizard)
I just wanted to weigh in and say that it would seem like this would be important enough for a quick 'hotfix'. Ease of migration using these tools is by far the most important reason I switched from MySQL to SQL Server and with these functions not working it is a real bummer.
Can anyone suggest a temporary work-aruond?
-Damien
|||Damien, your problem is completely unrelated to "product level" issue. I would suggest starting another thread specific to your issue, so that someone who knows this area might notice and help.|||We are having the same problem, only we get it on the server that SQL is installed on. We are running the 64bit RTM version downloaded from MSDN, with all options installed. I get the same errors, if I try to import from Excel, csv and sometimes from other tables on the same 2005 database. This last one is only sometimes.

How to check whether SSIS is installed

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Thanks for reporting this problem, it seems like we have a bug here.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

How to check whether SSIS is installed

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Thanks for reporting this problem, it seems like we have a bug here.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

How to check whether SSIS is installed

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Thanks for reporting this problem, it seems like we have a bug here.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

How to check whether SSIS is installed

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Thanks for reporting this problem, it seems like we have a bug here.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

How to check whether SSIS is installed

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Thanks for reporting this problem, it seems like we have a bug here.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

How to check whether SSIS is installed

I'm using the import wizard to create a new table from a flat file source. The table gets created but no data gets copied. What's wrong? Here's the report:

Operation stopped...

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Error)
Messages
* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - inSsrc_txt" (1).
(SQL Server Import and Export Wizard)

* Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Data Conversion 1" (43).
(SQL Server Import and Export Wizard)

- Prepare for Execute (Stopped)

- Pre-execute (Stopped)

- Executing (Success)

- Copying to [BayadaPortal].[dbo].[inSsrc] (Stopped)

- Post-execute (Stopped)

- Cleanup (Stopped)

Please see this thread:
http://forums.microsoft.com/msdn/ShowPost.aspx?PostID=110020

SSIS ships as part of SQL 2005, but the setup give you a choice of whether to install it or not.

Thanks for reporting this problem, it seems like we have a bug here.

We will fix this problem for SP1 release, the wizard should be able to run the package with just 'Workstation Components' install. Unfortunately, we missed this problem.

Thanks,
Michael.

Thanks.

|||And BTW - I immediately got it to work after importing the sheet into MS Access, and then using MS Access as the import source for MSSQL Server 2005 ...

Thanks.|||

Error 0xc00470fe: Data Flow Task: The product level is insufficient for component "Source - AgentDirectoryDownload$" (1).

Sean Carpenter|||

We've reconsidered this issue, and will be providing a fix for SP1 release.

For now, you need to install SSIS to run the package in the wizard.

Sean Carpenter|||

If this is blocking your move to 2005, you should consider opening a case with customer support, reviewing with them the content of this thread, and pressing for the hotfix.

With few exceptions, hotfixes are issued in response to escalated customer support calls.

jkh

Error 0xc0202025: Data Flow Task: Cannot create an OLE DB accessor. Verify that the column metadata is valid.
(SQL Server Import and Export Wizard)

How to check whether an SSIS package is executing

I have scheduled an SQL Job to run every 15 mins. This runs an SSIS package. But sometimes my package might execute for more than 15 mins. In this case, a second instance of the package would start. I don't want this to happen. So is there any way I can check whether the package is already running before I continue the execution of the same. Right now I am using a mutex to handle this problem. Are there any problems using the mutex and is there a better way to handle this?

Thanks in advance.

Sumesh

have you tried using the sql server profiler?|||Actually the entire process is an automated process. I want my SSIS or the SQL job to check whether an instance it has initiated earlier is not running when the next instance has to be started.|||

Interesting problem. There is no way that I know of to check whether a package is already executing or not. A good way of getting around this is to disable the Agent job at the start of the package and then re-enable it again at the end. I would probably do this even if I *could* check if a package was running or not.

-Jamie

|||Thank you Jamie! But if I disable the job and then re-enable it after the execution of my package, won't the agent wait for another 15 mins before it starts the next execution of the package?|||i recently heard in an msdn webcast that package execution can be monitored in the sql server management studio object explorer, but i haven't tried this.|||

Hi Sumesh,

I think you could use a scripting task and SMO to extract the current run status of the job:

http://msdn2.microsoft.com/en-us/library/microsoft.sqlserver.management.smo.agent.job.currentrunstatus.aspx

cheers,
Markus

Wednesday, March 28, 2012

how to connect to ssis service - The RPC server is unavailable err

how to connect to ssis service - The RPC server is unavailable err

how to connect to ssis service - The RPC server is unavailable err

Wednesday, March 21, 2012

How to connect ExecuteSQLTask with data flow task

Monday, March 12, 2012

How to Configure DSN with DataReader Source

Friday, March 9, 2012

How to compose the connection String of a SSIS package that execute another package?

How to compile/translate a SSIS package in Japanese

Sunday, February 19, 2012

How to check whether SSIS is installed

How to check whether SSIS is installed

How to check whether SSIS is installed

How to check whether SSIS is installed

How to check whether SSIS is installed

How to check whether SSIS is installed

How to check whether SSIS is installed

How to check whether SSIS is installed

How to check whether an SSIS package is executing

clear log

Blog Archive

About Me