Error when schedule a job in SQL 2005

Hi,

I have a SSIS package that contains an Execute DTS 2000 process. This DTS 2000 is calling a legacy package, which resides on the same server. The legacy package is just to import a flat file into the database. When i right click and execute this package, it runs perfectly without any errors. However, if i try to schedule this package as a job, it keeps failing.

I checked the flat file source for the permission, it does have the account of the executor of the package. In the view history, i didn't see any more information about why it is failing. It keeps saying "The job failed. The Job was invoked by Schedule 10...."

Does anyone have any ideas?

Did you try to turn on logging so you could get better error details?|||

Thanks, I turned on the log and it wrote to the application log events saying. Is there another log event in SQL 2005? I only saw it said "View History" in the scheduled job.

Status: Failed - Invoked on: 2006-11-06 13:56:00 - Message: The job failed. The Job was invoked by Schedule 24 (Test Schedule). The last step to run was step 1 (RUN ImportData)

|||See this KB about turning on logging and general troubleshooting of SSIS packages under Agent:
http://support.microsoft.com/kb/918760

error when running SSIS package as a job

I am running into an error when running a package using a scheduled job under SQL Server Agent account. I am getting following error:

Date 6/12/2007 4:19:15 PM
Log Job History (VistaODSFeed)

Step ID 0
Server 006-DEVSQL2005
Job Name VistaODSFeed
Step Name (Job outcome)
Duration 00:00:00
Sql Severity 0
Sql Message ID 0
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
The job failed. Unable to determine if the owner (ACI\snasir) of job VistaODSFeed has server access (reason: Could not obtain information about Windows NT group/user 'ACI\snasir', error code 0x6ba. [SQLSTATE 42000] (Error 15404)).

ACI\snasir is not the account under which SQL Server Agent service runs. However ACI\snasir has sa priveleges. not sure why am I getting ACI\snasir in the error and not the account under which sql server agent runs.

ideas?

Hi Shahab,

Is ACI\snasir hard-coded as the username in any of the connection managers?

Andy

Error when loading Package

Hi all,
I've finished an SSIS Package on my computer and want to move the project into production server. I was just copied the whole files and when I load the package from production server there was an error occured, the description is below :

Error 1 Error loading 'SC2DC_Regular.dtsx' : The package failed to load due to error 0xC0010014 "One or more error occurred. There should be more specific errors preceding this one that explains the details of the errors. This message is used as a return value from functions that encounter errors.". This occurs when CPackage::LoadFromXML fails. . e:\dw workplace\sc2dc_server\SC2DC_Regular.dtsx 1 1

What's the problem with my Package, I never met this error before with the same behaviour of moving SSIS project from one computer to another.
Thanks in advance

Is you production server 64-bit? If so, the problem may be that your scripts are not precompiled. Make sure your PreCompileScriptIntoBinaryCode is True (the default). Scripts are compiled when the script editor IDE is closed, so you may need to open and close the scripts (tasks and components) to get them to compile.
|||The property is True and like I wrote before I moved my previous project to that production server and it's work fine. Only this current project I got this error.|||Hi all,
Does anyone know what's the real problem with my package ?|||Hi,
after searching the answer for days I found this thread :

https://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=1244365&SiteID=1

no wonder there's no people here tried to answered my question ;p except JayH, thanks bro :-)

sql

Error when I try to copy components and tasks

Hi everyone,

Everything's fine or I think so but when I try to copy/cut components to another SSIS of to own.

I get this error:

Error al copiar objetos. El Dise?ador SSIS no pudo serializar los objetos de tiempo de ejecución de SSIS.

No se pudo copiar el objeto 'Tarea Secuencia de comandos ActiveX' al Portapapeles.

(Microsoft.DataTransformationServices.Design)

Tranlasted into English (more or less):

Error copying objetcts. SSIS designer was not able to serialize run-time SSIS objects

ActiveX Script task was not copied to clipboard

NOTE: this behaviour doesn't happen in the own server only from client (xp pros sp2). Nothing has been changed I don't know if install again or not.

Any help will be welcomed.

I thought it maybe something to do with the ActiveX Script Task since it is legacy, but that is rubbish. Not much help, but it seems to be something not right with your local installation.|||

Thanks Darren.

I suppose that for Integration Services' Microsoft developers keep up old COM schemes is a hell in a certain way.

I try to imagine Sql25k without any dependencies...

By the moment, I'll follow working via TS.

|||

Darren,

How odd! It happens with any component not only with VbScript task.

?

Error when doing fuzzy lookup

I am trying to run a SSIS package that contains a fuzzy lookup. I am using a flat file with about 7 million records as the input. The reference table has about 2000 records. The package fails after about 40,000 records with the following information:

Warning: 0x8007000E at Data Flow Task, Fuzzy Lookup [228]: Not enough storage is available to complete this operation.
Warning: 0x800470E9 at Data Flow Task, DTS.Pipeline: A call to the ProcessInput method for input 229 on component "Fuzzy Lookup" (228) unexpectedly kept a reference to the buffer it was passed. The refcount on that buffer was 2 before the call, and 1 after the call returned.
Error: 0xC0047022 at Data Flow Task, DTS.Pipeline: The ProcessInput method on component "Fuzzy Lookup" (228) failed with error code 0x8007000E. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.
Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0x8007000E.
Error: 0xC02020C4 at Data Flow Task, Flat File Source [1]: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.
Error: 0xC0047039 at Data Flow Task, DTS.Pipeline: Thread "WorkThread1" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown.
Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread1" has exited with error code 0xC0047039.
Error: 0xC0047038 at Data Flow Task, DTS.Pipeline: The PrimeOutput method on component "Flat File Source" (1) returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.
Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "SourceThread0" has exited with error code 0xC0047038.

-

I have tried many things - changing the BufferTempStoragePath path to a drive that has plenty space, changed the MaxInsertCommitSize to 5,000...

What else can I do?

Thanks!

Did you get this on a RTM build?

If yes, is it possible you apply SP1 to see whether that helps?

Thanks

wenyang

|||

Yes, it is on a RTM build.

The server does not have SP1 on it yet. Is there something else that I could try before that is installed?

Thanks!

|||

I know there was a memory issue got fixed in SP1 for FuzzyLookup, in which case the error looks very similar to yours, so I wanted you to try SP1.

For temp work arounds, you may also try one of the following two on your RTM

1) Increase your page file to >10GB

2) Mitigate the problem by splitting the input into smaller batches (e.g. 100k at a time) and tearing down the package in between each batch.

HTH

wenyang

|||

I have installed SP1, and am getting the same errors.

Any other suggestions other than the temp work arounds you mentioned? As I mentioned earlier, the process is stopping after only 40,000 records or so. This seems like a very small number and I'd hate to have to split the input up into smaller pieces than that.

Thanks!

|||

Does increase page file size help? If not, then we probably need to repro in house to investigate further.

Is it possible you log a bug with repro? (bug report place is http://lab.msdn.microsoft.com/productfeedback/default.aspx) We'll get back to you asap.

Thanks

Wenyang

|||

Sorry - I was told that SP1 had been installed before I wrote my previous message. It actually hadn't been installed at that point. Once that was successfully installed on Integration Services, the fuzzy lookup issues seem to have been resolved.

Thanks!

|||

Hi Wenyang,

I have installed SQL Server 2005 Service Pack 2 and unfortunately this error does not seem to have gone away.

Increasing my pagefile does not seemed to have helped the situation either ?

It seems to occur whenever I choose to perform a match on more than 10 columns within a Fuzzy Lookup ?

Can you please advise what I should do next/when this will be fixed ?

Many Thanks,

Gary

Error when doing fuzzy lookup

I am trying to run a SSIS package that contains a fuzzy lookup. I am using a flat file with about 7 million records as the input. The reference table has about 2000 records. The package fails after about 40,000 records with the following information:

Warning: 0x8007000E at Data Flow Task, Fuzzy Lookup [228]: Not enough storage is available to complete this operation.
Warning: 0x800470E9 at Data Flow Task, DTS.Pipeline: A call to the ProcessInput method for input 229 on component "Fuzzy Lookup" (228) unexpectedly kept a reference to the buffer it was passed. The refcount on that buffer was 2 before the call, and 1 after the call returned.
Error: 0xC0047022 at Data Flow Task, DTS.Pipeline: The ProcessInput method on component "Fuzzy Lookup" (228) failed with error code 0x8007000E. The identified component returned an error from the ProcessInput method. The error is specific to the component, but the error is fatal and will cause the Data Flow task to stop running.
Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0x8007000E.
Error: 0xC02020C4 at Data Flow Task, Flat File Source [1]: The attempt to add a row to the Data Flow task buffer failed with error code 0xC0047020.
Error: 0xC0047039 at Data Flow Task, DTS.Pipeline: Thread "WorkThread1" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown.
Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread1" has exited with error code 0xC0047039.
Error: 0xC0047038 at Data Flow Task, DTS.Pipeline: The PrimeOutput method on component "Flat File Source" (1) returned error code 0xC02020C4. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.
Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "SourceThread0" has exited with error code 0xC0047038.

-

I have tried many things - changing the BufferTempStoragePath path to a drive that has plenty space, changed the MaxInsertCommitSize to 5,000...

What else can I do?

Thanks!

Did you get this on a RTM build?

If yes, is it possible you apply SP1 to see whether that helps?

Thanks

wenyang

|||

Yes, it is on a RTM build.

The server does not have SP1 on it yet. Is there something else that I could try before that is installed?

Thanks!

|||

I know there was a memory issue got fixed in SP1 for FuzzyLookup, in which case the error looks very similar to yours, so I wanted you to try SP1.

For temp work arounds, you may also try one of the following two on your RTM

1) Increase your page file to >10GB

2) Mitigate the problem by splitting the input into smaller batches (e.g. 100k at a time) and tearing down the package in between each batch.

HTH

wenyang

|||

I have installed SP1, and am getting the same errors.

Any other suggestions other than the temp work arounds you mentioned? As I mentioned earlier, the process is stopping after only 40,000 records or so. This seems like a very small number and I'd hate to have to split the input up into smaller pieces than that.

Thanks!

|||

Does increase page file size help? If not, then we probably need to repro in house to investigate further.

Is it possible you log a bug with repro? (bug report place is http://lab.msdn.microsoft.com/productfeedback/default.aspx) We'll get back to you asap.

Thanks

Wenyang

|||

Sorry - I was told that SP1 had been installed before I wrote my previous message. It actually hadn't been installed at that point. Once that was successfully installed on Integration Services, the fuzzy lookup issues seem to have been resolved.

Thanks!

|||

Hi Wenyang,

I have installed SQL Server 2005 Service Pack 2 and unfortunately this error does not seem to have gone away.

Increasing my pagefile does not seemed to have helped the situation either ?

It seems to occur whenever I choose to perform a match on more than 10 columns within a Fuzzy Lookup ?

Can you please advise what I should do next/when this will be fixed ?

Many Thanks,

Gary

Error when deploy SSIS with Deployment Wizard

I've get error when I deploy SSIS package with Deployment wizard like this

===================================

Could not save the package "C:\Documents and Settings\aun\My Documents\Visual Studio 2005\Projects\ImportCommittee\ImportCommittee\bin\Deployment\IMPORT_FS_DATA.dtsx" to SQL Server "(local)". (Package Installation Wizard)

===================================

The SaveToSQLServer method has encountered OLE DB error code 0x80040E21 (Invalid character value for cast specification). The SQL statement that was issued has failed.

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)

===================================

The SaveToSQLServer method has encountered OLE DB error code 0x80040E21 (Invalid character value for cast specification). The SQL statement that was issued has failed.

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)

I've ever pass deploy wizard with test program (a little line of code) but when I've deploy with my real code it's return error I've show above

Thanks for your help

Pipope

Hi All -

I'm experiencing the same problem as well. Any solutions?

Thanks.

Error when deploy SSIS with Deployment Wizard

I've get error when I deploy SSIS package with Deployment wizard like this

===================================

Could not save the package "C:\Documents and Settings\aun\My Documents\Visual Studio 2005\Projects\ImportCommittee\ImportCommittee\bin\Deployment\IMPORT_FS_DATA.dtsx" to SQL Server "(local)". (Package Installation Wizard)

===================================

The SaveToSQLServer method has encountered OLE DB error code 0x80040E21 (Invalid character value for cast specification). The SQL statement that was issued has failed.

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.SavePackageToSqlServer(WizardInputs wizardInputs, String packagePassword, Boolean bUseSeverEncryption, String serverName, String userName, String password, String packageFilePath, List`1 configFileNames)
at Microsoft.SqlServer.Dts.Deployment.DtsInstaller.InstallPackagesToSqlServer(WizardInputs wizardInputs)

===================================

The SaveToSQLServer method has encountered OLE DB error code 0x80040E21 (Invalid character value for cast specification). The SQL statement that was issued has failed.

Program Location:

at Microsoft.SqlServer.Dts.Runtime.Wrapper.ApplicationClass.SaveToSQLServer(IDTSPackage90 Package, IDTSEvents90 pEvents, String ServerName, String ServerUserName, String ServerPassword)
at Microsoft.SqlServer.Dts.Runtime.Application.SaveToSqlServer(Package package, IDTSEvents events, String serverName, String serverUserName, String serverPassword)

I've ever pass deploy wizard with test program (a little line of code) but when I've deploy with my real code it's return error I've show above

Thanks for your help

Pipope

Hi All -

I'm experiencing the same problem as well. Any solutions?

Thanks.

Error when connecting to SSIS.

I just installed a default instance of SS 2005 and applied the most recent service pack, release date March 5th, SQLServer2005SP2-KB921896-x64-ENU.exe.

All services are running as localsystem. When I try to connect to SSIS through Management Studio on the local machine I receive the following error.

Any help would be appreciated.

TITLE: Connect to Server

Cannot connect to [server name].

ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Connect to SSIS Service on machine "[server name]" failed:
Error loading type library/DLL.
.

Connect to SSIS Service on machine "[server name]." failed:
Error loading type library/DLL.
.

BUTTONS:
OK

Do you have the SQL Server SSIS service started (running)?|||I do.|||

There was one thing that was a little weird. I tried re-installing the Service Pack and it did not recognize that the services were running or would interfere with the install.

The first time I installed SP2 it forced me to stop the services before installing, but the second time it did not. Seemed as if the install did not detect the services were running.

After installing the second time, I did a reboot to attempt to clear it up. SSIS still did not allow a connection and I received the same error.

|||Does this help? Are you also running SQL Server 2000?

http://sqljunkies.com/WebLog/knight_reign/archive/2005/06/08/15765.aspx|||No not running SQL 2000 on this computer. It is a brand new server.|||

I am looking at the link you sent, thought this may be relevant also.

There was a previous named instance that I uninstalled, before installing the default instance. There were no other instances on the computer after I uninstalled the named instance.

|||

Phil,

The xml ini file in the link appears to be correct on my server.

It shows the servername as <ServerName>.</ServerName>.

I appreciate the help, so does my client. ;)

|||

Phil,

The issue on the post at this site seems to be the same.

http://www.kbalertz.com/Feedback_926629.aspx

The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

|||Have you tried reinstalling the client tools?|||

SnoChoJoe wrote:

Phil,

The issue on the post at this site seems to be the same.

http://www.kbalertz.com/Feedback_926629.aspx

The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

I just read that myself. Are you on a 32 bit machine? The SP2 service pack you indicated is for 64 bit.|||No it is an X64 architecture.|||No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?|||

SnoChoJoe wrote:

No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?

Perhaps... Make sure you have a working installation before applying any service packs.|||

Ok, I am going to trouble shoot the client install.

I will advise if I determine the problem. Thanks Phil.

Error when connecting to SSIS.

I just installed a default instance of SS 2005 and applied the most recent service pack, release date March 5th, SQLServer2005SP2-KB921896-x64-ENU.exe.

All services are running as localsystem. When I try to connect to SSIS through Management Studio on the local machine I receive the following error.

Any help would be appreciated.

TITLE: Connect to Server

Cannot connect to [server name].

ADDITIONAL INFORMATION:
Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

Connect to SSIS Service on machine "[server name]" failed:
Error loading type library/DLL.
.

Connect to SSIS Service on machine "[server name]." failed:
Error loading type library/DLL.
.

BUTTONS:
OK

Do you have the SQL Server SSIS service started (running)?|||I do.|||

There was one thing that was a little weird. I tried re-installing the Service Pack and it did not recognize that the services were running or would interfere with the install.

The first time I installed SP2 it forced me to stop the services before installing, but the second time it did not. Seemed as if the install did not detect the services were running.

After installing the second time, I did a reboot to attempt to clear it up. SSIS still did not allow a connection and I received the same error.

|||Does this help? Are you also running SQL Server 2000?

http://sqljunkies.com/WebLog/knight_reign/archive/2005/06/08/15765.aspx|||No not running SQL 2000 on this computer. It is a brand new server.|||

I am looking at the link you sent, thought this may be relevant also.

There was a previous named instance that I uninstalled, before installing the default instance. There were no other instances on the computer after I uninstalled the named instance.

|||

Phil,

The xml ini file in the link appears to be correct on my server.

It shows the servername as <ServerName>.</ServerName>.

I appreciate the help, so does my client. ;)

|||

Phil,

The issue on the post at this site seems to be the same.

http://www.kbalertz.com/Feedback_926629.aspx

The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

|||Have you tried reinstalling the client tools?|||

SnoChoJoe wrote:

Phil,

The issue on the post at this site seems to be the same.

http://www.kbalertz.com/Feedback_926629.aspx

The cause is listed as "This problem occurs because the 32-bit Dts.dll file is unregistered when the 64-bit SSIS is installed as part of the hotfix.". Does this ring a bell?

I just read that myself. Are you on a 32 bit machine? The SP2 service pack you indicated is for 64 bit.|||No it is an X64 architecture.|||No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?|||

SnoChoJoe wrote:

No I have not, you know I get an error on the Client Tools Update when installing SP2. Could that be related?

Perhaps... Make sure you have a working installation before applying any service packs.|||

Ok, I am going to trouble shoot the client install.

I will advise if I determine the problem. Thanks Phil.

Error when changing the length on DataReader Source

Hi,
I am trying to import data from Oracle RDB into SQL Server 2005 using SSIS. Created a ODBC data source to connect to Oracle and used DataReader Source component and ADO.net to connect to the ODBC data source.

Under the Component properties tab, the SQL Command looks something like this.

Select ID, ADDRESS, REVISED from ADDRESS

The data type for the source columns are Integer, Varchar(30) and DATE VMS.

Now when I look at the Input and Output properties window,

The External columns has the following data types.

ID - four-byte signed integer [DT_I4]
ADDRESS - Unicode string [DT_WSTR], length = 0
REVISED - database timestamp [DT_DBTIMESTAMP]

The Output columns has the following data types

ID - four-byte signed integer [DT_I4]
ADDRESS - Unicode string [DT_WSTR], length = 0
REVISED - database timestamp [DT_DBTIMESTAMP]

When I tried to change the length of the ADDRESS on the output column, I get the following error.

Error at Data Flow Task [DataReader Source [1]]: The data type of output columns on the component "DataReader Source" (1) cannot be changed.

Error at Data Flow Task [DataReader Source [1]]: System.Runtime.InteropServices.COMException (0xC020837D)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.SetOutputColumnDataTypeProperties(Int32 iOutputID, Int32 iOutputColumnID, DataType eDataType, Int32 iLength, Int32 iPrecision, Int32 iScale, Int32 iCodePage)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostSetOutputColumnDataTypeProperties(IDTSManagedComponentWrapper90 wrapper, Int32 iOutputID, Int32 iOutputColumnID, DataType eDataType, Int32 iLength, Int32 iPrecision, Int32 iScale, Int32 iCodePage)

Is this the default length for the Unicode string type. I was not able to load the ADDRESS column as it gets truncated before I load it into destination. Even if I use Derived or Data Conversion transformation, the ADDRESS is getting truncated before it reaches this transformation.

Any thoughts.

Thanks,
SK

Did you try using a Data Conversion transformation?

Rafael Salas

|||

Hi,
I did try to use the Data Conversion transformation. But when I execute the package, I get the truncation error at the Data Source Reader itself.

Error: 0xC020902A at Data Flow Task, DataReader Source [1736]: The "component "DataReader Source" (1736)" failed because truncation occurred, and the truncation row disposition on "output column "ADDRESS" (2469)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.

Error: 0xC02090F5 at Data Flow Task, DataReader Source [1736]: The component "DataReader Source" (1736) was unable to process the data.

Error: 0xC0047038 at Data Flow Task, DTS.Pipeline: The PrimeOutput method on component "DataReader Source" (1736) returned error code 0xC02090F5. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.

Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "SourceThread0" has exited with error code 0xC0047038.

Error: 0xC0047039 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown.

Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0xC0047039

Thanks,
SK

|||

Hi,
Does anybody have inputs on this issue?

SK

|||

It sounds like the provider you are using is reporting the length of the string incorrectly as 0. I've seen that before with a provider, but I don't recall what one... Is there a different provider you can try?

Otherwise, you might try changing the select statement to cast the value explicitly to a string of length 30 and see if the DataReaderSrc correctly creates the column then.

|||

Unfortunately I can't use any other providers other than ADO.net as I have to use Oracle RDB ODBC to connect to RDB database.

Strangely, now the column is showing as text instead of Unicode string and I was able to use the data conversion transformation to convert back to Unicode String. Not sure what changed on the server. The only thing that I think of is we updated SQL Server with some updated from MS website.

Thanks,
SK

|||

We had the exact same problem trying to pull data from Oracle Rdb. I went round & round but eventually found the solution.

Basically we had to install SQL*Net for Rdb (or OCI Services for Rdb) on our VMS server to make our Rdb database look like an Oracle database. Then we had to install Oracle client software on our client machine. I've used both Oracle 9.2 client and ODAC 10.2. You then set up your client connection using the Oracle Net Manager.

After you've got client & server configured, set up an SSIS connection manager using .Net Providers for OleDb -> Oracle Provider for OLE DB.

It's kind of a hassle to set up but it seems to work just fine.

Regards, Pat

Error when changing the length on DataReader Source

Hi,
I am trying to import data from Oracle RDB into SQL Server 2005 using SSIS. Created a ODBC data source to connect to Oracle and used DataReader Source component and ADO.net to connect to the ODBC data source.

Under the Component properties tab, the SQL Command looks something like this.

Select ID, ADDRESS, REVISED from ADDRESS

The data type for the source columns are Integer, Varchar(30) and DATE VMS.

Now when I look at the Input and Output properties window,

The External columns has the following data types.

ID - four-byte signed integer [DT_I4]
ADDRESS - Unicode string [DT_WSTR], length = 0
REVISED - database timestamp [DT_DBTIMESTAMP]

The Output columns has the following data types

ID - four-byte signed integer [DT_I4]
ADDRESS - Unicode string [DT_WSTR], length = 0
REVISED - database timestamp [DT_DBTIMESTAMP]

When I tried to change the length of the ADDRESS on the output column, I get the following error.

Error at Data Flow Task [DataReader Source [1]]: The data type of output columns on the component "DataReader Source" (1) cannot be changed.

Error at Data Flow Task [DataReader Source [1]]: System.Runtime.InteropServices.COMException (0xC020837D)
at Microsoft.SqlServer.Dts.Pipeline.DataReaderSourceAdapter.SetOutputColumnDataTypeProperties(Int32 iOutputID, Int32 iOutputColumnID, DataType eDataType, Int32 iLength, Int32 iPrecision, Int32 iScale, Int32 iCodePage)
at Microsoft.SqlServer.Dts.Pipeline.ManagedComponentHost.HostSetOutputColumnDataTypeProperties(IDTSManagedComponentWrapper90 wrapper, Int32 iOutputID, Int32 iOutputColumnID, DataType eDataType, Int32 iLength, Int32 iPrecision, Int32 iScale, Int32 iCodePage)

Is this the default length for the Unicode string type. I was not able to load the ADDRESS column as it gets truncated before I load it into destination. Even if I use Derived or Data Conversion transformation, the ADDRESS is getting truncated before it reaches this transformation.

Any thoughts.

Thanks,
SK

Did you try using a Data Conversion transformation?

Rafael Salas

|||

Hi,
I did try to use the Data Conversion transformation. But when I execute the package, I get the truncation error at the Data Source Reader itself.

Error: 0xC020902A at Data Flow Task, DataReader Source [1736]: The "component "DataReader Source" (1736)" failed because truncation occurred, and the truncation row disposition on "output column "ADDRESS" (2469)" specifies failure on truncation. A truncation error occurred on the specified object of the specified component.

Error: 0xC02090F5 at Data Flow Task, DataReader Source [1736]: The component "DataReader Source" (1736) was unable to process the data.

Error: 0xC0047038 at Data Flow Task, DTS.Pipeline: The PrimeOutput method on component "DataReader Source" (1736) returned error code 0xC02090F5. The component returned a failure code when the pipeline engine called PrimeOutput(). The meaning of the failure code is defined by the component, but the error is fatal and the pipeline stopped executing.

Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "SourceThread0" has exited with error code 0xC0047038.

Error: 0xC0047039 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" received a shutdown signal and is terminating. The user requested a shutdown, or an error in another thread is causing the pipeline to shutdown.

Error: 0xC0047021 at Data Flow Task, DTS.Pipeline: Thread "WorkThread0" has exited with error code 0xC0047039

Thanks,
SK

|||

Hi,
Does anybody have inputs on this issue?

SK

|||

It sounds like the provider you are using is reporting the length of the string incorrectly as 0. I've seen that before with a provider, but I don't recall what one... Is there a different provider you can try?

Otherwise, you might try changing the select statement to cast the value explicitly to a string of length 30 and see if the DataReaderSrc correctly creates the column then.

|||

Unfortunately I can't use any other providers other than ADO.net as I have to use Oracle RDB ODBC to connect to RDB database.

Strangely, now the column is showing as text instead of Unicode string and I was able to use the data conversion transformation to convert back to Unicode String. Not sure what changed on the server. The only thing that I think of is we updated SQL Server with some updated from MS website.

Thanks,
SK

|||

We had the exact same problem trying to pull data from Oracle Rdb. I went round & round but eventually found the solution.

Basically we had to install SQL*Net for Rdb (or OCI Services for Rdb) on our VMS server to make our Rdb database look like an Oracle database. Then we had to install Oracle client software on our client machine. I've used both Oracle 9.2 client and ODAC 10.2. You then set up your client connection using the Oracle Net Manager.

After you've got client & server configured, set up an SSIS connection manager using .Net Providers for OleDb -> Oracle Provider for OLE DB.

It's kind of a hassle to set up but it seems to work just fine.

Regards, Pat

Error when attempting to use SQL Server Import and Export Wizard

I'm unable to use SSIS packages after installing SQL Server 2005. Specifically when I first loaded a new Integration Services project in SQL Server Business Intelligence Development Studio the default SSIS package could not load, I get Package.dtsx in my tabbed document view but in the body of this window is a error message: "Microsoft Visual Studio is unable to load this document. QI for IEnumVARIANT failed on the unmanaged server."

If I try to use the SQL Server Import and Export Wizard shortly after the window to select your data source I get a pop-up error message:

This wizard will close because it encountered the following error:

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.SqlServer.Management.UI.WizardFrameworkErrorSR&EvtID=UncaughtException&LinkId=20476

ADDITIONAL INFORMATION:

QI for IEnumVARIANT failed on the unmanaged server. (CustomMarshalers)

Anyone have any ideas on how I can resolve this?

I have experienced the same problem. Have you found a solution yet?

I found other users experiencing similar problems, but apparently not the same issue. I tried the fix at http://groups-beta.google.com/group/microsoft.public.dotnet.framework.setup/browse_thread/thread/a2ed96d68cb349f3/db810a1bcf8f66e4?q=qi+ienumvariant&_done=%2Fgroups%3Fhl%3Den%26lr%3Dlang_en%26safe%3Doff%26c2coff%3D1%26q%3Dqi+ienumvariant%26qt_s%3DSearch+Groups%26&_doneTitle=Back+to+Search&&d#db810a1bcf8f66e4

but had no luck.

Error when attempting to use SQL Server Import and Export Wizard

I'm unable to use SSIS packages after installing SQL Server 2005. Specifically when I first loaded a new Integration Services project in SQL Server Business Intelligence Development Studio the default SSIS package could not load, I get Package.dtsx in my tabbed document view but in the body of this window is a error message: "Microsoft Visual Studio is unable to load this document. QI for IEnumVARIANT failed on the unmanaged server."

If I try to use the SQL Server Import and Export Wizard shortly after the window to select your data source I get a pop-up error message:

This wizard will close because it encountered the following error:

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft%u00ae+Visual+Studio%u00ae+2005&ProdVer=8.0.50727.42&EvtSrc=Microsoft.SqlServer.Management.UI.WizardFrameworkErrorSR&EvtID=UncaughtException&LinkId=20476

ADDITIONAL INFORMATION:

QI for IEnumVARIANT failed on the unmanaged server. (CustomMarshalers)

Anyone have any ideas on how I can resolve this?

I have experienced the same problem. Have you found a solution yet?

I found other users experiencing similar problems, but apparently not the same issue. I tried the fix at http://groups-beta.google.com/group/microsoft.public.dotnet.framework.setup/browse_thread/thread/a2ed96d68cb349f3/db810a1bcf8f66e4?q=qi+ienumvariant&_done=%2Fgroups%3Fhl%3Den%26lr%3Dlang_en%26safe%3Doff%26c2coff%3D1%26q%3Dqi+ienumvariant%26qt_s%3DSearch+Groups%26&_doneTitle=Back+to+Search&&d#db810a1bcf8f66e4

but had no luck.

Error Type 'System.Xml.XmlTextWriter' is not defined

I use this Code in SSIS Destination Script Transforamtion:
Imports System
Imports System.Data
Imports System.Math
Imports Microsoft.SqlServer.Dts.Pipeline.Wrapper
Imports Microsoft.SqlServer.Dts.Runtime.Wrapper
Imports System.Xml

Public Class ScriptMain
Inherits UserComponent
Dim xWriter As XmlTextWriter
' get this Error: Type 'System.Xml.XmlTextWriter' is not defined

Public Overrides Sub Input0_ProcessInputRow(ByVal Row As Input0Buffer)
End Sub
End Class

Whats wrong ?

I use CTP Sept 2005 on Windows XP German.

Willfried

You need to add a reference to System.Xml in your script component

Go to Project|Add Reference... and select System.xml from the assembly list|||Thanks, i'm a fool |||Don't worry I just spent 30 minutes doing exactly the same thing

error trying to import packages to the MSDB

When I try import a SSIS package into the MSDB I get the following error message:

TITLE: Microsoft SQL Server Management Studio

Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum)

For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&LinkId=20476

ADDITIONAL INFORMATION:

The SQL server specified in SSIS service configuration is not present or is not available. This might occur when there is no default instance of SQL Server on the computer. For more information, see the topic "Configuring the Integration Services Service" in Server 2005 Books Online.

The .Net Framework OleDb Data Provider requires Microsoft Data Access Components(MDAC) version 2.6 or later. Version 2.12.4202.3 was found currently installed. (MsDtsSrvr)

BUTTONS:

OK

I do have default instance installed and the SSIS servie is running. When I look at the SSIS service configuration it shows a period for the server which I thought meant local host. Also I have MDAC 2.8 installed. What else do I need to look at?

Try the MDAC version checker just to be sure you have the correct version. http://support.microsoft.com/default.aspx?kbid=301202

As you can see from the error message this is more likely to be an MDAC issue than an SSIS issue per se, but let's see what the version says first.

Donald

|||The version checker shows that 2.8 is installed but the Registry setting shows 2.1. We had this issue before and just had to install 2003 OS Sp 1 again.|||

So you think you may be able to fix this again? If so, great. If not, I think the SQL Server Data Access forum would be the right place to get help.

thanks

Donald

|||

Phil,

Do you have multiple instances installed on your server? If not you might try hard coding your server name into your SSIS configuration file

<ServerName>my-server-01</ServerName>

I had the same error when I tried to view an SSIS package on my server with 2 instances but I had no default instance, so my case was a little different than yours. The way I resolved my problem was by hard coding both instances into my config file

<ServerName>my-server-01\instance1</ServerName>
<ServerName>my-server-01\instance2</ServerName>

If you have a default instance and a named instance you might try something like this:

<ServerName>my-server-01</ServerName>
<ServerName>my-server-01\instance1</ServerName>

This did the trick for me, hopefully it will work for you.

Error Starting Script Editor in SSIS

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

How odd! I havent' idea.. Maybe this is a stuff related with the own assembly?

Look at c:\windows\assembly and make sure that exists Microsoft.Vsa.Hosting.Design Time assembly.

I'm sorry

|||

reedcbr wrote:

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

does other control flow objects and data flow transformation experience the same

|||Those are the only two that I have noticed it in. Are there other objects that have Design Script buttons. If so, I will test them and reply with an answer.|||Yes, the assembly is there. Its' version is 8.0.0.0 and its' public key token is b03f5f7f11d50a3a|||Yes, the assembly is there. Its' version is 8.0.0.0 and its' public key token is b03f5f7f11d50a3a|||I am wondering if anyone is monitoring this forum, I posted answers to the questions that I was asked and haven't received any more responses.|||Well, perhaps a reinstall is in order... Nevermind... Just read the whole thread.|||I was just wondering if this could be happening because this desktop is running Windows XP Media Edition?|||

Do you have Visual Studio installed?

If yes, can you try and and run : Tools-> Macros-> Macros IDE... and see if that works?

Thanks,

Ovidiu

|||

hi,

Weird thing happen to SSIS when

the integration service does not have sufficient right

in the Box.

check to see if the integrarion service has sufficient rights

click start>run>type "service.msc"

look for the integration service and supply it with a powerful account in your box

perhaps an administrator account.

regards,

joey

|||

I'm having the same problem, except when I click the Design Script button nothing happens, I don't even get an error message. Has anyone been able to find the solution for this?

Tom

|||

(I think the underlying cause is something to do with .Net 3.0 install, Maybe the installation of SQL2005 SP2, or maybe the order of install between VS2005 and SSIS, but whatever the reason, there is a registry issue.

First, do make sure your SSIS service has appropriate login rights.

Also, navigate to the following folders:

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa

In each of those folders run this command to re-register everything in there.:

for %i in (*.dll) do RegSvr32 -s %i

You will be very pleased with the results I think. May be a little blunt, but it worked for me.

I had determined this was the issue from the detailed error message provided in the dialog, where it indicated the problem was the program Microsoft.VisualBasic.Vsa.Dt.get_extensibility.... blah blah, and another message saying "interface not registered". Putting 2 and 2 together, I did a search for that dll, and registered everything in that folder and the other one.

There are a few people on forums starting to post this issue, and there don't seem to be any responses, so tell everyone you know, because I'm sure it will be a common problem among SSIS developers who use scripting.

|||

Your idea is on the right path. My initial error pointed me to the DTS folder under C:\Program Files\Microsoft SQL Server\90\DTS\Binn. I registered what you did above, but it did not work. I decided, hey lets try the DTS\Binn folder. What do you know, I no longer get the error and can see all my work flow in SSIS. Thanks for the tip (it appears security does not have to be set to Local User, but rather a solid Admin account).

Thanks,

TR

Error Starting Script Editor in SSIS

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

How odd! I havent' idea.. Maybe this is a stuff related with the own assembly?

Look at c:\windows\assembly and make sure that exists Microsoft.Vsa.Hosting.Design Time assembly.

I'm sorry

|||

reedcbr wrote:

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

does other control flow objects and data flow transformation experience the same

|||Those are the only two that I have noticed it in. Are there other objects that have Design Script buttons. If so, I will test them and reply with an answer.|||Yes, the assembly is there. Its' version is 8.0.0.0 and its' public key token is b03f5f7f11d50a3a|||Yes, the assembly is there. Its' version is 8.0.0.0 and its' public key token is b03f5f7f11d50a3a|||I am wondering if anyone is monitoring this forum, I posted answers to the questions that I was asked and haven't received any more responses.|||Well, perhaps a reinstall is in order... Nevermind... Just read the whole thread.|||I was just wondering if this could be happening because this desktop is running Windows XP Media Edition?|||

Do you have Visual Studio installed?

If yes, can you try and and run : Tools-> Macros-> Macros IDE... and see if that works?

Thanks,

Ovidiu

|||

hi,

Weird thing happen to SSIS when

the integration service does not have sufficient right

in the Box.

check to see if the integrarion service has sufficient rights

click start>run>type "service.msc"

look for the integration service and supply it with a powerful account in your box

perhaps an administrator account.

regards,

joey

|||

I'm having the same problem, except when I click the Design Script button nothing happens, I don't even get an error message. Has anyone been able to find the solution for this?

Tom

|||

(I think the underlying cause is something to do with .Net 3.0 install, Maybe the installation of SQL2005 SP2, or maybe the order of install between VS2005 and SSIS, but whatever the reason, there is a registry issue.

First, do make sure your SSIS service has appropriate login rights.

Also, navigate to the following folders:

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa

In each of those folders run this command to re-register everything in there.:

for %i in (*.dll) do RegSvr32 -s %i

You will be very pleased with the results I think. May be a little blunt, but it worked for me.

I had determined this was the issue from the detailed error message provided in the dialog, where it indicated the problem was the program Microsoft.VisualBasic.Vsa.Dt.get_extensibility.... blah blah, and another message saying "interface not registered". Putting 2 and 2 together, I did a search for that dll, and registered everything in that folder and the other one.

There are a few people on forums starting to post this issue, and there don't seem to be any responses, so tell everyone you know, because I'm sure it will be a common problem among SSIS developers who use scripting.

|||

Your idea is on the right path. My initial error pointed me to the DTS folder under C:\Program Files\Microsoft SQL Server\90\DTS\Binn. I registered what you did above, but it did not work. I decided, hey lets try the DTS\Binn folder. What do you know, I no longer get the error and can see all my work flow in SSIS. Thanks for the tip (it appears security does not have to be set to Local User, but rather a solid Admin account).

Thanks,

TR

Error Starting Script Editor in SSIS

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

How odd! I havent' idea.. Maybe this is a stuff related with the own assembly?

Look at c:\windows\assembly and make sure that exists Microsoft.Vsa.Hosting.Design Time assembly.

I'm sorry

|||

reedcbr wrote:

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

does other control flow objects and data flow transformation experience the same

|||Those are the only two that I have noticed it in. Are there other objects that have Design Script buttons. If so, I will test them and reply with an answer.|||Yes, the assembly is there. Its' version is 8.0.0.0 and its' public key token is b03f5f7f11d50a3a|||Yes, the assembly is there. Its' version is 8.0.0.0 and its' public key token is b03f5f7f11d50a3a|||I am wondering if anyone is monitoring this forum, I posted answers to the questions that I was asked and haven't received any more responses.|||Well, perhaps a reinstall is in order... Nevermind... Just read the whole thread.|||I was just wondering if this could be happening because this desktop is running Windows XP Media Edition?|||

Do you have Visual Studio installed?

If yes, can you try and and run : Tools-> Macros-> Macros IDE... and see if that works?

Thanks,

Ovidiu

|||

hi,

Weird thing happen to SSIS when

the integration service does not have sufficient right

in the Box.

check to see if the integrarion service has sufficient rights

click start>run>type "service.msc"

look for the integration service and supply it with a powerful account in your box

perhaps an administrator account.

regards,

joey

|||

I'm having the same problem, except when I click the Design Script button nothing happens, I don't even get an error message. Has anyone been able to find the solution for this?

Tom

|||

(I think the underlying cause is something to do with .Net 3.0 install, Maybe the installation of SQL2005 SP2, or maybe the order of install between VS2005 and SSIS, but whatever the reason, there is a registry issue.

First, do make sure your SSIS service has appropriate login rights.

Also, navigate to the following folders:

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa

In each of those folders run this command to re-register everything in there.:

for %i in (*.dll) do RegSvr32 -s %i

You will be very pleased with the results I think. May be a little blunt, but it worked for me.

I had determined this was the issue from the detailed error message provided in the dialog, where it indicated the problem was the program Microsoft.VisualBasic.Vsa.Dt.get_extensibility.... blah blah, and another message saying "interface not registered". Putting 2 and 2 together, I did a search for that dll, and registered everything in that folder and the other one.

There are a few people on forums starting to post this issue, and there don't seem to be any responses, so tell everyone you know, because I'm sure it will be a common problem among SSIS developers who use scripting.

|||

Your idea is on the right path. My initial error pointed me to the DTS folder under C:\Program Files\Microsoft SQL Server\90\DTS\Binn. I registered what you did above, but it did not work. I decided, hey lets try the DTS\Binn folder. What do you know, I no longer get the error and can see all my work flow in SSIS. Thanks for the tip (it appears security does not have to be set to Local User, but rather a solid Admin account).

Thanks,

TR

Error Starting Script Editor in SSIS

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

How odd! I havent' idea.. Maybe this is a stuff related with the own assembly?

Look at c:\windows\assembly and make sure that exists Microsoft.Vsa.Hosting.Design Time assembly.

I'm sorry

|||

reedcbr wrote:

I am having a problem in the Business Intelligence Development Studio. When I add and try to edit a Script Task or a Script Component, I click on the Design Script button and get one of two errors. For the Script task I get an error that states:

Cannot show the editor for this task. (Microsoft Visual Studio)

For the Script component I get:

Cannot show Visual Studio for Applications editor. (Microsoft Visual Studio)

For some reason or another it just will not start Visual Studio for Applications. I have uninstalled an re-installed several times. I have also researched and discovered that there is a bug when C# tasks are include in the project. However, this is not the case. Please help!

does other control flow objects and data flow transformation experience the same

|||Those are the only two that I have noticed it in. Are there other objects that have Design Script buttons. If so, I will test them and reply with an answer.|||Yes, the assembly is there. Its' version is 8.0.0.0 and its' public key token is b03f5f7f11d50a3a|||Yes, the assembly is there. Its' version is 8.0.0.0 and its' public key token is b03f5f7f11d50a3a|||I am wondering if anyone is monitoring this forum, I posted answers to the questions that I was asked and haven't received any more responses.|||Well, perhaps a reinstall is in order... Nevermind... Just read the whole thread.|||I was just wondering if this could be happening because this desktop is running Windows XP Media Edition?|||

Do you have Visual Studio installed?

If yes, can you try and and run : Tools-> Macros-> Macros IDE... and see if that works?

Thanks,

Ovidiu

|||

hi,

Weird thing happen to SSIS when

the integration service does not have sufficient right

in the Box.

check to see if the integrarion service has sufficient rights

click start>run>type "service.msc"

look for the integration service and supply it with a powerful account in your box

perhaps an administrator account.

regards,

joey

|||

I'm having the same problem, except when I click the Design Script button nothing happens, I don't even get an error message. Has anyone been able to find the solution for this?

Tom

|||

(I think the underlying cause is something to do with .Net 3.0 install, Maybe the installation of SQL2005 SP2, or maybe the order of install between VS2005 and SSIS, but whatever the reason, there is a registry issue.

First, do make sure your SSIS service has appropriate login rights.

Also, navigate to the following folders:

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\common\

C:\Program Files\Common Files\Microsoft Shared\VSA\8.0\vsa

In each of those folders run this command to re-register everything in there.:

for %i in (*.dll) do RegSvr32 -s %i

You will be very pleased with the results I think. May be a little blunt, but it worked for me.

I had determined this was the issue from the detailed error message provided in the dialog, where it indicated the problem was the program Microsoft.VisualBasic.Vsa.Dt.get_extensibility.... blah blah, and another message saying "interface not registered". Putting 2 and 2 together, I did a search for that dll, and registered everything in that folder and the other one.

There are a few people on forums starting to post this issue, and there don't seem to be any responses, so tell everyone you know, because I'm sure it will be a common problem among SSIS developers who use scripting.

|||

Your idea is on the right path. My initial error pointed me to the DTS folder under C:\Program Files\Microsoft SQL Server\90\DTS\Binn. I registered what you did above, but it did not work. I decided, hey lets try the DTS\Binn folder. What do you know, I no longer get the error and can see all my work flow in SSIS. Thanks for the tip (it appears security does not have to be set to Local User, but rather a solid Admin account).

Thanks,

TR