/logger option

Hi,

I'm trying to use the below command to execute for generating the log file for SSIS package.

DTExec /FILE "C:\Documents and Settings\CP0808\My Documents\Test.dtsx" /logger "DTS.LogProviderTextFile;c:\log.txt"

But it got the error as below. Please advise.

Started: 10:03:20 AM
Error: 2006-10-06 10:03:21.15
Code: 0xC001000E
Source: Test
Description: The connection "c:\log.txt" is not found. This error is thrown b
y Connections collection when the specific connection element is not found.
End Error
Error: 2006-10-06 10:03:21.18
Code: 0xC001000E
Source: Test
Description: The connection "c:\log.txt" is not found. This error is thrown b
y Connections collection when the specific connection element is not found.
End Error
Error: 2006-10-06 10:03:21.21
Code: 0xC02020EA
Source: Test Log provider "{1AEAB490-1124-4A84-981F-7C1FDD80A721}"
Description: The connection manager "c:\log.txt" is not found. A component fa
iled to find the connection manager in the Connections collection.
End Error

Hi,

the logger option in DTEXEC specifies an already existing connection within the package. YOu will have to create a file location within the package to reference it.

Have a look here: http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=72104

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

Hi,

I still got the error as below.

DTExec /FILE "C:\Documents and Settings\CP0808\My Documents\Test.dtsx" /CONNECTION DestinationConnectionFlatFile;"c:\test.csv" /CONNECTION SourceConnectionOLEDB;"Data Source=test;User ID=user;Initial Catalog=DATA_CONV;Provider=SQLNCLI;Auto Translate=false;PASSWORD=password" /MAXCONCURRENT " -1 " /CHECKPOINTING OFF /REPORTING EWCDI /l "DTS.LogProviderTextFile;log.txt" /Set "\package.Connections[log.txt].Properties[ConnectionString];c:\log.txt"

Error: 2006-10-10 09:57:21.07
Code: 0xC001000E
Source: Test
Description: The connection "log.txt" is not found. This error is thrown by C
onnections collection when the specific connection element is not found.
End Error
Error: 2006-10-10 09:57:21.10
Code: 0xC001000E
Source: Test
Description: The connection "log.txt" is not found. This error is thrown by Connections collection when the specific connection element is not found.
End Error
Warning: 2006-10-10 09:57:21.14
Code: 0x8001F02F
Source: Test
Description: Cannot resolve a package path to an object in the package ".Connections[log.txt].Properties[ConnectionString]". Verify that the package path is valid.
End Warning
Warning: 2006-10-10 09:57:21.17
Code: 0x80012017
Source: Test
Description: The package path referenced an object that cannot be found: "\package.Connections[log.txt].Properties[ConnectionString]". This occurs when an attempt is made to resolve a package path to an object that cannot be found.
End Warning
DTExec: Could not set \package.Connections[log.txt].Properties[ConnectionString]
value to c:\log.txt.
Started: 9:57:20 AM
Finished: 9:57:21 AM
Elapsed: 0.5 seconds

.Net and SSIS

Hi,
Is there way I could pass on an object to an IS package from a .Net component? Basically I need to validate a file using c# and pass the valid records to an IS packet to be uploaded to the database. Is this possible without me writing the valid records to a file and using that as input for the IS packet?

I tried doing the validation on the IS side as well but seems extremly slow so going to try to get a c# program to do that for me.

Appreciate your help....If you want to reuse this code - write a custom data source component for data flow. If this is to be used once only - use a script component to create the source.|||Siv1 - if you're looking to programatically manipulate a SSIS package from c# code, check out the Microsoft.SqlServer.Dts.Runtime namespace. You'll need to import a reference to Microsoft.SQLServer.ManagedDTS.dll. You can load packages into .Net objects and manipulate from there (even run the package).|||

If you want to use the output of an existing .NET assembly within a package, then perhaps you'll prefer to approach things from the other end than Jeff suggested, and invoke your existing assembly from within a Script task or Script component (with the inconveniences around reusability that Michael mentioned).

However you can also do things the other way around, and run your package from a .NET application, and if the package terminates in a DataReader destination, load that DataReader output into your client app, as described in BOL.

-Doug

|||Thanks guys for giving me an idea on where to start...

...cannot be run because the SSIS subsystem failed to load....

Greetings all,

After moving all my packages to a new server, win2K3, SQL2k5, non of the SSIS packages run. They all ran fine on the other server.

The error is

"2006-03-07 13:09:38 - ! [LOG] Step 1 of job 'ExportXML' (0x4E0C7495EFE4034FA6EF94B7C7F77262) cannot be run because the SSIS subsystem failed to load. The job has been suspended"

These packages ran perfectly on the old system.

Running the package manually, using DTExec or from the Saved Packages tree in SQL is fine.

Package is saved in SQL.

Any ideas?

Do you have SSIS installed on that machine?

This isn't meant to be as patronising as it sounds, honest.

Its just that some people think installing BIDS constitutes installing SSIS and that isn't the case.

-Jamie

|||

Since your package works on the new server using DTExec (and the error indicates an agent subsystem failed to load) you might want to post this question to the agent forum since it sounds like an agent problem not an SSIS problem.

Thanks,

Matt

|||

Jamie,

It is installed.

I can run packages saved in msdb usiing dtexec with no problem.

Will post on the Agent group and see. Only a couple people had this problem it would seem.

Cheers,

** critical issue with SSIS ** Please help!

Hi all of you,

This post is related with this one, previously opened:

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=620243&SiteID=1

Moreover, this post is related too (IMHO) with

http://forums.microsoft.com/TechNet/ShowPost.aspx?PostID=430406&SiteID=17

Following with my research I've seen that DTS.DLL is installed on:

1)My root c:

2)%systemroot%\system32

2)c:\archivos de programa\...\90\

3)c:\archivos de programa\...\80\

It seems that BIDS is trying to call, at first, to this COM CCW component.

So that, all has been deleted phsyically from my workstation and unregistered.

Sql Server 2005 full installation again and... the problem lives yet.

I'm desperate

I'm afraid I cannot help, never seen this issue, but if it really is that important I'd strongly recomend you contact MS Support. It will be easier for them to diagnose a problem with you in real-time over forum posts.|||Thanks Darren