DTLoggedExec Work Item Rss Feed

Commented Unassigned: is this working for 2012? [34070]

shrey_halani — Mon, 20 May 2013 06:39:02 GMT

Hi

Is this working same as Sql server 2012 ?
I tried but it's give me error like as below

OnError:
Package Name:
Object Type: ()
Description:
Object ID:
Container Name:
Container ID:
StartTime: 5/20/2013 12:06:46 PM
EndTime: 5/20/2013 12:06:46 PM
Message: Package migration from version 6 to version 3 failed with error 0xC0
01700A "The version number in the package is not valid. The version number cannot be greater than cu
rrent version number.".

Variables:
Expressions:
OnError:
Package Name:
Object Type: ()
Description:
Object ID:
Container Name:
Container ID:
StartTime: 5/20/2013 12:06:46 PM
EndTime: 5/20/2013 12:06:46 PM
Message: Error loading value "<DTS:Property xmlns:DTS="www.microsoft.com/SqlS
erver/Dts" DTS:Name="PackageFormatVersion">6</DTS:Property>" from node "DTS:Property".

Variables:
Expressions:

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
.

Error while loading Package.

Cannot load package.

C:\Users\user\Desktop\example\DTLoggedExec.vssscc\Samples>pause
Press any key to continue . . .

Thanks,
Shreyans
Comments: ** Comment from web user: shrey_halani **

Error IN 2012

Created Unassigned: is this working for 2012? [34070]

shrey_halani — Mon, 20 May 2013 06:38:02 GMT

Closed Issue: Exception when logging the POV & PRV events [25737]

manowar — Thu, 16 May 2013 08:04:22 GMT

Version: 0.2.3.0
The use of the POV and PRV switches fires an exception.

I tried with a fully empty package (no tasks) with neither loggging nor package configuration. The package only contains an oledb connection which uses a couple of expressions altering InitialCatalog and ServerName.
I cannot see any reason, but DTLoggedExec crashes only when the connection alters both the properties; if I change just InitialCatalog or ServerName it works...

C:\DTLoggedExec\DTLoggedExec\bin\Any\Release\DTLoggedExec.exe /FILE:CG_Test.dtsx /LE:POV,E
All the best
pf

EDIT: kindly read the "Events switches seem to alter the behaviour" ticket too as there's a common issue bound to connections.

Here below the exception when using POV:
Unhandled Exception: System.ArgumentException: An item with the same key has already been added.
at System.ThrowHelper.ThrowArgumentException(ExceptionResource resource)
at System.Collections.Generic.Dictionary`2.Insert(TKey key, TValue value, Boolean add)
at DTLoggedExec.LogProviders.CSVLogProvider.GetPropertiesWithExpressions(IDTSPropertiesProvider dpp)
at DTLoggedExec.LogProviders.CSVLogProvider.GetExpressions(Package package)
at DTLoggedExec.LogProviders.CSVLogProvider.LogEventData(String eventName, DtsObject dtsobj, String message)
at DTLoggedExec.CustomEventHandler.LogData(String eventName, DtsObject dtsobj) in C:\Work\SSIS Logging\DTLoggedExec\DTLoggedExec\CustomEventHandler.cs:line 250
at DTLoggedExec.CustomEventHandler.OnPreValidate(Executable exec, Boolean& fireAgain) in C:\Work\SSIS Logging\DTLoggedExec\DTLoggedExec\CustomEventHandler.cs:line 176
at Microsoft.SqlServer.Dts.Runtime.ReverseIDTSEventsWrapper.OnPreValidate(IDTSExecutable90 exec, Boolean& fireAgain)
at Microsoft.SqlServer.Dts.Runtime.DtsContainer.Execute(Connections connections, Variables variables, IDTSEvents events, IDTSLogging log, Object transaction)
at DTLoggedExec.Program.ExecutePackage(Package package, String[] configurations, String[] values, String[] rparams, CustomEventHandler customEventHandler) in C:\Work\SSIS Logging\DTLoggedExec\DTLoggedExec\Program.cs:line 278
at DTLoggedExec.Program.Main(String[] args) in C:\Work\SSIS Logging\DTLoggedExec\DTLoggedExec\Program.cs:line 149

Closed Issue: Events switches seem to alter the behaviour [25738]

manowar — Thu, 16 May 2013 08:04:21 GMT

SQL Server 9.0.4035 Standard
DTLoggedExec 0.2.3.0
I'm facing a weird behaviour with a script task, but I feel it's bound to db connections which are altered using expressions...

EDIT: I reach the idea it depends on the "expression" info DTLoggedExec reports when the "I" flag is used; I think there's something wrong in a routine and the issue gets out every time it's called to manage connections
(see my other error "Exception when logging the POV & PRV events Title is required")

Here we go with the long explanation (attached the dtsx I used for testing)

A) The package contains:
1) one variable
2) one script task which only prints the variable using Dts.Events.FireInformation
3) two ole db connection:
the first without any expressions is used for logging,
the latter, with two expressions (InitialCatalog and ServerName), is there just for forcing the error
4) full logging
5) no package configuration

A) w/o the Information switch (package with expressions)
DTLoggedExec.exe /FILE:C:\CG_Test.dtsx /LE:E
Package end.
Total warnings: 0
Total errors: 0
Elapsed time: 0,3437588 secs.
...Package Executed.
Result: Success
The original log in the SSIS shows the expected information (a bit edited): "OnInformation CG_Test 60953889-5E08-4F99-B8BE-2DAF42EC0911 2009-12-21 15:06:45.000 -1 0x pippo"

B) with the Information switch
DTLoggedExec.exe /FILE:C:\CG_Test.dtsx /LE:E,I

OnInformation: Script Task
OnError: Script Task
OnError: Script Task
OnError: Script Task
Package end.
Total warnings: 0
Total errors: 3
Elapsed time: 0,2031302 secs.
...Package Executed.
Result: Success

The original SSIS log still shows, as reported above, the expected information, but followed by a couple of errors:
"OnError CG_Test 1FB798F8-31A9-48A4-B125-47BC5B52A423 2009-12-21 15:08:42.000 2 0x The script threw an exception: Value does not fall within the expected range."
"5 0x The script files failed to load."
"-1073594108 0x The Execute method on the task returned error code 0x80070057 [...]. The Execute method must succeed, and indicate the result using an "out" parameter.

C) with the Information switch, BUT I MODIFIED THE PACKAGE TO REMOVE ONE OF THE EXPRESSIONS
DTLoggedExec.exe /FILE:C:\CG_Test.dtsx /LE:E,I

OnInformation: Script Task
Package Name: CG_Test
Task Type: ScriptTask (Microsoft.SqlServer.Dts.Tasks.ScriptTask.ScriptTask, Microsoft.SqlServer.ScriptTask, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91)
Description: Script Task
Object ID: {375E1F62-61C1-480E-898D-9D7BC74CE904}
Container Name: CG_Test
Container ID: {C05C08CC-45F0-47F4-9100-D21C6E4BA3DC}
StartTime: 21/12/2009 15:18:40
EndTime: 21/12/2009 15:18:41
Message: localhost
Variables:
\Package.Variables[User::ConfigCatalog] = msdb
\Package.Variables[User::ConfigServer] = localhost
Expressions:
\Package.Connections[OLEDB_Config].Properties[ServerName]: localhost

Package end.
Total warnings: 0
Total errors: 0
Elapsed time: 0,1718057 secs.
...Package Executed.
Result: Success

Closed Issue: ; missing in import-profile-data.sql [26479]

manowar — Thu, 16 May 2013 08:04:21 GMT

I'm investigating this for use in our company and I ran into a missing ; in the import-profile-data.sql script.
SQL gave an error when I ran the batch file saying
"Incorrect syntax near the keyword 'with'. If this statement is a common table expression or an xmlnamespaces clause, the previous statement must be terminated with a semicolon"

And that was just the case, just before the 'with cte as' there is a declare statement where the ; is missing at the end.

Commented Issue: Slow start from SQL Agent [33751]

miken175 — Sat, 09 Feb 2013 10:40:10 GMT

If you run DTLoggedExec from a SQL Job you could have 30s delay per step depending on your network configuration.

It not seems related to the executable itself, but to the CRL Certificate Revocation Check.

[See this article for more details](http://blogs.msdn.com/b/michen/archive/2007/07/29/network-causing-ssis-package-startup-delays.aspx)

In our production environment we have at least 60 steps, so I added a DTLoggedExec.exe.config file in the exe folder containing the following:

This has solved my problem.

Mik
Comments: ** Comment from web user: miken175 **

So here is the file...

Created Issue: Slow start from SQL Agent [33751]

miken175 — Sat, 09 Feb 2013 10:36:06 GMT

Created Issue: Dataflowprofiler not logging anything when SSIS packaged only was "Execute SQL" Tasks [31454]

Spurt — Wed, 14 Sep 2011 13:55:35 GMT

I running a statement like this
"C:\DTLoggedExec\X64\DTLoggedExec.exe" /SQL:"\SERVER\SSIS_package_ETL_load" /Server:"SERVER" /LE:E,I,PRE,POE /PDFN:"C:\DTLoggedExec\DataFlowProfile\{filename}_{date}_{time}"
And the package runs fine but the dataflowprofiler has almost no data (only the header) in the text log file.
I have no problems with normal tasks (OLEDB source and dest.)
I would like some logging of the time used in each "Execute SQL Task"

Closed Issue: different error and warning results [30687]

manowar — Wed, 18 May 2011 18:41:58 GMT

Message results differ from total warnings and total errors, see commandline display below

Executing...
[CSV Logger] 2011-05-12T19:00:30 PackageStart [\]
...
[CSV Logger] 2011-05-12T19:00:31 PackageEnd [\] <message><result>Failure</result>
<warnings>3</warnings><errors>2</errors></message>

Total warnings: 2
Total errors: 3
Elapsed time: 0,8418292 secs.
...Package Executed.

and differs from imported data in tables, see select ... from package_execution_results below

package_result load_result load_result warnings errors
-------------------------------------------------- -------------------------------------------------- -------------------------------------------------- ----------- -----------
Failure Success Success 3 2
Comments:

Problem fixed in version 1.1.2008.4

Commented Issue: different error and warning results [30687]

manowar — Wed, 18 May 2011 18:41:16 GMT

Perfect :)

Commented Issue: different error and warning results [30687]

Phil2011 — Tue, 17 May 2011 08:45:15 GMT

thanks, we have used an older version...

DTLoggedExec.LogProvidersCSVLogPovider.dll 1.0.0.2
Microsoft.SqlServer.DTSRuntimeWrap.dll 9.0.242.0
DTLoggedExec.exe 1.0.0.2

now it works fine...
DTLoggedExec.LogProvidersCSVLogPovider.dll 1.0.2008.0
Microsoft.SqlServer.DTSRuntimeWrap.dll 10.50.1600.1
DTLoggedExec.exe 1.1.2008.4

Commented Issue: different error and warning results [30687]

manowar — Sat, 14 May 2011 14:17:49 GMT

Hi, thanks for the feedback. I'm aware of this inconsistency and it should have been fixed in the latest version (1.1.2008.4). Which version of DTLoggedExec you're using?

Created Issue: different error and warning results [30687]

Phil2011 — Fri, 13 May 2011 09:16:25 GMT

Created Issue: Set Parameter value error when string has ';' [29408]

oszymczak — Fri, 12 Nov 2010 02:37:59 GMT

Hi,
If you are setting a string value that has a semicolon in it. The args parsing will fail. To fix this change the following line in the following method DTloggedExec.Program.cs

private static DTSExecResult SetPackageValues(Package package, string[] values, bool parseAsParameter)
{
...
...
...
else
{
//s = v.Split(';');
s = v.Split(new char[] { ';' }, 2);
valuePath = s[0];
}
...
...
}

Commented Issue: /CONNECTION parameter? [29374]

manowar — Mon, 08 Nov 2010 17:40:01 GMT

dtexec has some more parameters. I use the /CONNECTION (or /Connection) parameter frequently to run the same packages against different connections, but it is unrecognized by DTLoggedExec.
Is there a workaround?
Comments: ** Comment from web user: manowar **

You can change connection managers configuration using the /SET parameter, or you can use a configuration file for the same purpose

Commented Issue: Command Line Parameter Inconsistency [21510]

manowar — Mon, 08 Nov 2010 17:34:31 GMT

We use the SSIS Package Store for all out packages. If you click the Command Line tab in the job step and copy paste and run using DTLoggedExec, you will get paramater errors for every paramater. Why did you decide to make the command line paramaters parse differently then DTExec? I was expecting them to be parsed the same, but they are not. For example: DTExec accepts /SET "Property";"Value", but DTLoggedExec it must be /Set:"Property";"Value" otherwise you get an error. Also, why are the parameters case sensitive? On the wiki http://dtloggedexec.davidemauri.it/Command%20Line%20Parameters.ashx, it shows the parameters as upper case. But otherwise, great tool for troubleshooting without having to make any package changes. Awsome job!
Comments: ** Comment from web user: manowar **

@Germo
Not really. Do you need some parameter in particular that DTExec has and that is missing in DTLoggedExec?

Created Issue: /CONNECTION parameter? [29374]

Germo — Sun, 07 Nov 2010 14:57:00 GMT

Commented Issue: Command Line Parameter Inconsistency [21510]

Germo — Sun, 07 Nov 2010 14:52:37 GMT

is there any progress in extending the code to use the same parameters as in dtexec?

Created Issue: FileSystemTask (Move) not working inside event handler [27695]

raclede — Fri, 18 Jun 2010 09:05:43 GMT

I created a package that would process files in a certain directory using for each loop container. Then I've created an event handler
on the FELC in case there's an error, it has one File System Task on it, that is to move the file to a certain directory if exception
is thrown. I noticed that the file is not being moved once there's an error.

Attach is the simple package describing the issue and it consists of:

1) Script Task that throws an error
2) Event Handler for Script Task that contains 1 File System Task to move a certain file.

Executed with arguments: /FILE:"FileTaskInExceptionHandlerTest.dtsx" /LE:E,P,I,T,W

Commented Issue: Exception when logging the POV & PRV events [25737]

PGFIORE — Wed, 05 May 2010 09:44:28 GMT

The CG_Test.dtsx package is already attached to the other issue I opened, the #25738; it is exactly the same. Ciao pf