"project creation error" with Ivolva Component Wizards for Integration Services

Hi,

I'm just getting started with SSIS and want to create a custom data flow component. I found the Ivolva Digital "Component Wizards for Integration Services" which says it make starting your own custom task or data flow component a snap by providing a functional base project for your task or component.

Therefore I installed the Component Wizards for Integration Services and everything seemed to install ok - when I started Visual Studio I had the "Custom Data Flow Component" and "Custom Task" templates available in the New Projects dialog.

However, when I try to create a project of either of these types I get the message "Creating project 'CustomTask1'...project creation error" in the status bar, and can't get past the New Project dialog. (I can create all other project types ok, though).

Can anyone offer any advice that might help me out here?

Thanks in advance,
Lawrie.

You might contact Oleg who created the wizards. His contact information is on the website ivolva.com.

As this isn't a Microsoft product, we don't support it.

On the other hand, creating custom tasks is really quite simple and BOL gives solid recommendations on how to do it. The wizard didn't do that much other than set up a class library, add the imports/references and derive from a task. All stuff you can do in a matter of a minute or two.

K

"Network general error"....

Hi Guys,

I have a problem with my application.when i try to run it to a network pc, show me this message "Network general error". But if i run it to simple pc everything ok.

Database is local. SQL Express agent running locally.Also all protocols for sql server is enebled.

Any ideas,,,,

COuld it be that the firewall is enabled or not configured for accessing the computer on this specific port ?

HTH, jens Suessmeyer.

http://www.sqlserver2005.de

"Attempted to read or write protected memory error" in SSIS

I'm trying to import data from a Sybase ASE 12.0 database called "OurTestDatabase" into MS SQL Server 2005. I started SSIS Wizard and indicated "Sybase ASE OLEDB Provider" as a source and SQL Native Client as the target. I'm gettign the following error message:

--

Cannot get supported data types from the database connection

"Provider=Sybase.ASEOLDEDBProvider;Password=;Persist Security Info=True;User ID=sa;Data Source=sybase;Initial Catalog=OurTestDatabase"

Additional information

|_ Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (System.Data)

--

The same data source worked with DTS when we thought we'd convert to MS SQL Server 2000. Is this a bug in SSIS? What can be done? Using ".Net Framework Provider for ODBC" is not a good option because this doesn't allow me to choose any tables from the Sybase source.

Any help is greatly appreciated.

Hi,

Did you get the chance ti figure out what was the problem. I do get the similar error while accessing AS400 database.

its fail in :

// Summary:

// Fixes any errors identified during design-time validation that result in

// the component returning Microsoft.SqlServer.Dts.Pipeline.Wrapper.DTSValidationStatus.VS_NEEDSNEWMETADATA.

void ReinitializeMetaData();

where its suppose to identify the errors in metadata it seems.

I still am investigating my metadata for AS400 tables.

Hope This helps you.

|||

I'm not sure that we can help debug in detail - we have not tested the Sybase drivers and don't know what behaviour they typically report.

However, most likely the issue arises because the Sybase provider does not support methods we are calling to get data types for columns. I have seen similar issues with the Sybase provider and linked servers. You may want to check with Sybase to see if they have tested their provider with SSIS.

The .Net provider for ODBC may be a workaround in terms of getting column level metadata. You are right that in the present version you cannot browse tables or views. However, although the provider does not list tables, it is still possible to access them, but you need to write the query yourself.

Donald

|||The same error came up when I used the ODBC drivers to access Sybase ASE|||

That sounds like a Sybase issue, then. Have you checked with them, or tested the same calls to the driver with other clients?

Donald

"Attempted to read or write protected memory error" in SSIS

I'm trying to import data from a Sybase ASE 12.0 database called "OurTestDatabase" into MS SQL Server 2005. I started SSIS Wizard and indicated "Sybase ASE OLEDB Provider" as a source and SQL Native Client as the target. I'm gettign the following error message:

--

Cannot get supported data types from the database connection

"Provider=Sybase.ASEOLDEDBProvider;Password=;Persist Security Info=True;User ID=sa;Data Source=sybase;Initial Catalog=OurTestDatabase"

Additional information

|_ Attempted to read or write protected memory. This is often an indication that other memory is corrupt. (System.Data)

--

The same data source worked with DTS when we thought we'd convert to MS SQL Server 2000. Is this a bug in SSIS? What can be done? Using ".Net Framework Provider for ODBC" is not a good option because this doesn't allow me to choose any tables from the Sybase source.

Any help is greatly appreciated.

Hi,

Did you get the chance ti figure out what was the problem. I do get the similar error while accessing AS400 database.

its fail in :

// Summary:

// Fixes any errors identified during design-time validation that result in

// the component returning Microsoft.SqlServer.Dts.Pipeline.Wrapper.DTSValidationStatus.VS_NEEDSNEWMETADATA.

void ReinitializeMetaData();

where its suppose to identify the errors in metadata it seems.

I still am investigating my metadata for AS400 tables.

Hope This helps you.

|||

I'm not sure that we can help debug in detail - we have not tested the Sybase drivers and don't know what behaviour they typically report.

However, most likely the issue arises because the Sybase provider does not support methods we are calling to get data types for columns. I have seen similar issues with the Sybase provider and linked servers. You may want to check with Sybase to see if they have tested their provider with SSIS.

The .Net provider for ODBC may be a workaround in terms of getting column level metadata. You are right that in the present version you cannot browse tables or views. However, although the provider does not list tables, it is still possible to access them, but you need to write the query yourself.

Donald

|||The same error came up when I used the ODBC drivers to access Sybase ASE|||

That sounds like a Sybase issue, then. Have you checked with them, or tested the same calls to the driver with other clients?

Donald

"Additional information: System error" message

Hello,
I needed to look at some .BCP files, so I thought I'd create a small tool for that.
I decided to create a temporary DB, attach empty mdf, ldf files with predefined structure and then insert the BCP files, so I can view the data as DB tables .

Here is the procedure I follow:
1) I drop the existing (if exists) DB ("Drop DBName") - to be prepared for the next set of .BCP files.
2) Then I create a new DB using sp_attach_db,
3) Then I populate the db via "Bulk Insert".

1st time this works just fine, but when I try to execute step 1 (drop DB) after step 3 I get a message that there is still open connection and the DB can't be dropped.

Here I can do two different things:
1) Find the SPID of the open connection to my DB and KILL the process or
2) Instead of killing the process, set the DB to "SINGLE_USER WITH ROLLBACK IMMEDIATE" and then drop the DB.

In both cases I was able to Drop the DB and attach the new one, however the Bulk Insert (via ExecuteNonQuery() ) for some reason closes the current connection and brakes with the "System Error" message.

I simulated this procedure on Query Analyser and on SQL Server Studio Express, but everything worked just fine there.

The VB code is a little complicated with using app.config to open so many network drives and folders, but if anybody is interested I'll post it.

To make it short, here is the SQL Query procedure (which worked, though):

USE Master
if exists
(select name
from master.dbo.sysdatabases
where has_dbaccess(name)=1 and name='MyDB')
BEGIN
Drop database MyDB
END
exec sp_who2

-- Before the next command I have to manually restore the .ndf, .ldf files, deleted by the "Drop DB" command

sp_attach_db @.dbname = N'MyDB',
@.filename1 = N'D:\CurrSchema\DB_Patient.ndf',
@.filename2 = N'D:\CurrSchema\DB_Definitions.mdf',
@.filename3 = N'D:\CurrSchema\DB_Log.ldf',
@.filename4 = N'D:\CurrSchema\DB_Data.ndf'
exec sp_who2

-- WAITFOR DELAY '00:00:04'
-- need to wait manually here. Waitfor won't work with "USE DB"

USE MyDB
BULK INSERT CAL
FROM '\\srv\D$\CurrFiles\CAL.bcp'
WITH (DATAFILETYPE='native',KEEPIDENTITY,KEEPNULLS)

BULK INSERT CAP
FROM '\\srv\CurrFiles\CAP.bcp'
WITH (DATAFILETYPE='native',KEEPIDENTITY,KEEPNULLS)
exec sp_who2

Has anybody seen something like this?

Thank you.

Haven't seen it personally. However, I suggest you insert a 'go' between each command to seperate them into batches. Also, be sure to change the database to 'master' for your connection before sending/executing 'drop db'.|||

Yes, Thank you - you were right. I did not need the 'GO', but the change to 'master' was the key. I should have been more careful when using somebody else's code - no matter how encapsulated, it's never context-free - in my case I had to add context switching with 'USE master'.

George.

|||

Hi... you mentioned you had the below source sample...

The VB code is a little complicated with using app.config to open so many network drives and folders, but if anybody is interested I'll post it.

Can you please post or sent to billbbellevue@.hotmail.com

Kind regards,

Bill Bezick

"Additional information: System error" message

Hello,
I needed to look at some .BCP files, so I thought I'd create a small tool for that.
I decided to create a temporary DB, attach empty mdf, ldf files with predefined structure and then insert the BCP files, so I can view the data as DB tables .

Here is the procedure I follow:
1) I drop the existing (if exists) DB ("Drop DBName") - to be prepared for the next set of .BCP files.
2) Then I create a new DB using sp_attach_db,
3) Then I populate the db via "Bulk Insert".

1st time this works just fine, but when I try to execute step 1 (drop DB) after step 3 I get a message that there is still open connection and the DB can't be dropped.

Here I can do two different things:
1) Find the SPID of the open connection to my DB and KILL the process or
2) Instead of killing the process, set the DB to "SINGLE_USER WITH ROLLBACK IMMEDIATE" and then drop the DB.

In both cases I was able to Drop the DB and attach the new one, however the Bulk Insert (via ExecuteNonQuery() ) for some reason closes the current connection and brakes with the "System Error" message.

I simulated this procedure on Query Analyser and on SQL Server Studio Express, but everything worked just fine there.

The VB code is a little complicated with using app.config to open so many network drives and folders, but if anybody is interested I'll post it.

To make it short, here is the SQL Query procedure (which worked, though):

USE Master
if exists
(select name
from master.dbo.sysdatabases
where has_dbaccess(name)=1 and name='MyDB')
BEGIN
Drop database MyDB
END
exec sp_who2

-- Before the next command I have to manually restore the .ndf, .ldf files, deleted by the "Drop DB" command

sp_attach_db @.dbname = N'MyDB',
@.filename1 = N'D:\CurrSchema\DB_Patient.ndf',
@.filename2 = N'D:\CurrSchema\DB_Definitions.mdf',
@.filename3 = N'D:\CurrSchema\DB_Log.ldf',
@.filename4 = N'D:\CurrSchema\DB_Data.ndf'
exec sp_who2

-- WAITFOR DELAY '00:00:04'
-- need to wait manually here. Waitfor won't work with "USE DB"

USE MyDB
BULK INSERT CAL
FROM '\\srv\D$\CurrFiles\CAL.bcp'
WITH (DATAFILETYPE='native',KEEPIDENTITY,KEEPNULLS)

BULK INSERT CAP
FROM '\\srv\CurrFiles\CAP.bcp'
WITH (DATAFILETYPE='native',KEEPIDENTITY,KEEPNULLS)
exec sp_who2

Has anybody seen something like this?

Thank you.

Haven't seen it personally. However, I suggest you insert a 'go' between each command to seperate them into batches. Also, be sure to change the database to 'master' for your connection before sending/executing 'drop db'.|||

Yes, Thank you - you were right. I did not need the 'GO', but the change to 'master' was the key. I should have been more careful when using somebody else's code - no matter how encapsulated, it's never context-free - in my case I had to add context switching with 'USE master'.

George.

|||

Hi... you mentioned you had the below source sample...

The VB code is a little complicated with using app.config to open so many network drives and folders, but if anybody is interested I'll post it.

Can you please post or sent to billbbellevue@.hotmail.com

Kind regards,

Bill Bezick