I've added a log provider to several packages, and for some reason, everytime I execute them, I end up with 2 log files. The first one is the right log file I was waiting for, and the second one is an almost empty file in my Desktop, that only contains this line
#Fields: event,computer,operator,source,sourceid,executionid,starttime,endtime,datacode,databytes,message
I would really appreciatte if anyone could tell me what am I possibly doing wrong.
Thanks.
Does the text log provider use a connection manager with dynamic connection string, e.g. a connection string which is an expression, or uses a value which changes during package lifetime (like the milliseconds of GETDATE()), or uses a variable which itself is an expression?
If the log name is dynamic to the point where it may change within the package lifetime itself (between the validation and execution times), its quite possible to end up with two files names.
Two files may be created because the log provider (at least the stock text log provider) writes to the connection manager's path once during validation, and a second time during execution. There is a sample log provider called the HtmlLogProvider in the SQL Server samples which writes the log file name during the log provider's CloseLog method, and so will produce a single file name. Other alternates to the text log provider include the stock SQL Server log provider, or simply capturing the output of dtexec, if the package is so executed.
|||Hi
I'm using an expression to build the connection string for the Text Log Provider. Something like:
@.[User::LogPath] + "logfilename.log"
The idea was to be able to dynamically change the path log files are going to be saved to, something I will probably never do. You know how these things are. I will check the sample log provider you mention.
Thanks a lot
|||Do you set the LogPath variable dynamically?|||Hi
If by dynamically you mean if I change its value during the package excution, the answer is no. The variable 'LogPath' holds the path where the log file will be created, and the LogProvider connection string is set using the expression in the previous post.
Cheers.
|||Hi jgomez,
1) Double click the SSIS Log Provider Connection Manager and check if it uses the Existing file or Creates a new File.
2) Assign the following expression for Connections String Property of SSIS Log Provider Connection Manager:
@.[User::LogPath] + Logfile.log
Thanks
Subhash Subramanyam
|||Hi
I think I know why I had this problem. I'm invoking several packages from my SSIS, using package configurations to set the value of the LogPath variable . Everytime a new package is invoked, using the parent package variable to create the log provider, I end up with 2 differents log files as previously stated.
So I guess jaegd and jwelch were right, and this behaviour is caused by the evaluation of the log path during validation and execution times.
Thank you
Cheers
|||Logging starts before parent package variable configurations are applied. So it would start the log with the original value (saved in the package at design time), then start a new log file when the parent package variable was applied.sql
