Log Folder Creation

My Log file connection is set to "Create Folder". According to BOL, this seems to indicate that the folder(s) that the log file will reside in will be created if they do not already exist. Yet I am receiving a package validation error when I execute the package. The full error is:

The SSIS logging provider has failed to open the log. Error code: 0x80070003
The system cannot find the path specified.

As a side note, I thought that setting the connection to "Create File" would recreate the log file each time it ran but that does not seem be the case. Instead, the file gets appended.

The type (FileUsageType) property does not do anything itself, as connections do not really do anything. It is up to the consumer of the connection to validate the usage type and act according to their function.

The type indicates to the consumer what it is dealing with, as the connection UI validates that for you, but the consumer does not have to act on it all, but it would normally at least validate this. If I wrote a task that read data from a file, I would validate the file connection type was file exists, anything else would not make sense.

I don't think the log provider should accept a type of create folder, it really requires a file. It would make sense for it to overwrite the file if using create file.

|||

In my opinion, any process that needed to create a file should ALSO create the folder structure if it does not exist. (Especially loggers...)

If I log to \\MySystem\Packages\Logging\20060607\mylog.xml I should not have to create the "Logging" and "20060607" folders. In the case of SSIS and logging, you CANNOT create the folders since you would need a task to create the folders and logging starts BEFORE the tasks...

(I also think it is silly when a function that creates folders cannot create the entire tree but instead I have to call it separately for each level... but that is a horse of a different color...)

And I agree Darren, if set to Create File it should overwrite the file instead of appending it.

Log File path in Configuration file does not work.

Hi,

I cannot get the log file path read from the configuration.

If the path in the Connection Manager is invalid, package throws an error "SSIS logging provider has failed to open the log" instead of reading it from the config.file. What am I doing wrong?

Here is the portion of the config file. Everthing else is read from the config file correctly.

- <Configuration ConfiguredType="Property" Path="\Package.Connections[SalesforceConnectLog].Properties[ConnectionString]" ValueType="String"> ConfiguredValue>D:\APPS\BACIAR\SalesforceConnect\SalesforceConnect.log</ConfiguredValue>

</Configuration>

Appreciate a help.

Gulden

I'm not sure about this but it COULD be that the log fails validation before the config gets applied. Try setting it in the package to c:\temp\SalesforceConnect.log or something similar and see what happens.

-Jamie

|||

Jamie,

It worked..

I gather from here then, the path in the Connection Manager should be valid for the target environment. Only then, the real path is being read from the config file.

Thanks a lot....

Gulden

|||

Yeah, sort of. Its an unfortunate consequence of the order in which things occur when the package spins up. It seems the log file location needs to be a valid "place" even though its never actually used - that's why I suggested something as arbitrary as "c:\temp".

-Jamie

|||

What is interesting is, I have Excel file connections in the same package with paths invalid for the target environment. Those work fine... Valid paths are read from the config.

Thanks again..

Gulden

|||

Gulden wrote:

What is interesting is, I have Excel file connections in the same package with paths invalid for the target environment. Those work fine... Valid paths are read from the config.

Thanks again..

Gulden

Yeah but that's not really comparing apples with apples. A connection manager used by a logfile is used differently (i.e. alot more) than others. Also its a different type of connection manager.

I haven't given a very good answer to this thread because frankly, I don't know what the proper answer is. At least it works now anyway.

-Jamie

Log file cant acquire connection while working offline

hi

As I trun Work offline - true, my connection manager for log file says-it cant acquire connection while work offline is true.Where as other oledb connections work fine.

Even it tried to get around by putting DelayValidation as true, but didnt work.

Is there is anyother setting that has be set.

Thanks and Regards

Rahul Kumar

Hello, are you referring to messages you see when you open the package with 'Work Offline'=true?

When you say "work fine" do you mean you can open the package and do not see any messages related to the OLEDB connections?

Thank you

|||

Are there any tasks using the connection managers that apparently don't throw any errors?

-Jamie

|||

I think this thread is related... I think the error is received while executing the package:

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

|||

Hi Craig,

I mean, when i run the package without having log file connection(which uses file connection) and work offline-true,delayvalidation-true with oledb connections, package returns no error and does the purpose.

Where as if i use log file with file connectin manager with above conditions as true,this file connection manager throws the error that it cant acquire connection.

Now if oledb connections can acquire connection,why does file connection manager fails.

Thanks and Regards

Rahul Kumar

|||

hi jamie

yes other which donot throw errors are olddb connections for my source and destination.

Thanks and regards

Rahul Kumar

|||

yes Rafaels

Both are on similar lines.But fact is problem still exists and i have given it many tests.

Log file cant acquire connection while working offline

hi

As I trun Work offline - true, my connection manager for log file says-it cant acquire connection while work offline is true.Where as other oledb connections work fine.

Even it tried to get around by putting DelayValidation as true, but didnt work.

Is there is anyother setting that has be set.

Thanks and Regards

Rahul Kumar

Hello, are you referring to messages you see when you open the package with 'Work Offline'=true?

When you say "work fine" do you mean you can open the package and do not see any messages related to the OLEDB connections?

Thank you

|||

Are there any tasks using the connection managers that apparently don't throw any errors?

-Jamie

|||

I think this thread is related... I think the error is received while executing the package:

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

|||

Hi Craig,

I mean, when i run the package without having log file connection(which uses file connection) and work offline-true,delayvalidation-true with oledb connections, package returns no error and does the purpose.

Where as if i use log file with file connectin manager with above conditions as true,this file connection manager throws the error that it cant acquire connection.

Now if oledb connections can acquire connection,why does file connection manager fails.

Thanks and Regards

Rahul Kumar

|||

hi jamie

yes other which donot throw errors are olddb connections for my source and destination.

Thanks and regards

Rahul Kumar

|||

yes Rafaels

Both are on similar lines.But fact is problem still exists and i have given it many tests.