VPN and Scheduled Package

  • I currently have a package successfully executing on a set schedule with the job agent. I also have two batch files that the package calls that connect our cisco vpn client when the package starts, and disconnects when it is done. My problem comes in if the vpn connection is already established. If the connection already exists it throws a failure of the package and won't continue. So I have a two fold question:

    1. Is there a way that I can have the package detect an existing vpn connection on the machine?

    2. Is there a way I can have a conditional statement in the batch file that will return the expected code if the connection already exists?

    Thank you for any help you can provide.

  • Can you use a batch process to check the status of the connection? If so, use another batch file to check the status, force it to fail if the connection does not exist, and use a Precedence Constraint for the failure condition to your batch process to open the connection.

    If there is no way to check the status of the connection with a batch process, just set the FailTaskIfReturnCodeIsNotSuccessValue on your Execute Process task (that opens your connection) to False. That will allow your batch file to fail silently if the connection already exists, which will let your package continue to execute. Of course, you'll need to consider that a legitimate failure to connect to the VPN will also not be detected in your batch process, so you'll need to address this downstream in your package.

    hth,

    Tim

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

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