Missing connections not causing a job failure

  • Hello

    I have a package that logs using Configure SSIS Logs: Logging

    It logs to a database (log)

    I've set up a new connection to the DB and called this log

    I've created a config file and added log to this:

    <Configuration ConfiguredType="Property" Path="\Package.Connections[log].Properties[InitialCatalog]" ValueType="String">
    <ConfiguredValue>log</ConfiguredValue>
    </Configuration>

    So, if I create a job that runs the package and uses the config file, all works well and it logs

     

    Now, if I change the name of the connection to logdb (for example), the job still works but it does not log

    NOTE: I also amend the connection string to something that is wrong as this seems to take presedence over the config file

     

    If I look at job history, it shows an error:

    Log provider "SSIS log provider for SQL Server" Description: SSIS Error Code DTS_E_CANNOTACQUIRECONNECTIONFROMCONNECTIONMANAGER. The AcquireConnection method call to the connection manager "logdb" failed with error code 0xC0202009 ...

     

    Why does the job still succeed?

    Ideally, in this situation, I want the job to fail as it cannot acquire a connection and cannot log

     

    Thanks

     

    Damian.

     

    - Damian

  • Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

Viewing 2 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply