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