SCCM Integration fails on 1st attempt, successful on second attempt

Thought I’d share a strange SCCM Connection issue with the Ivanti Service Manager (HEAT ISM) Integration. Cloud, VPN, SCCM 2010

The 1st connection attempt fails with error: 40 – Could not open a connection to SQL Server

The 2nd connection attempt is successful (no changes made to settings)

This is an issue for scheduled SCCM imports that are set to nightly and the import shows as complete but actually fails with zero batches and records processed. 

Manually running the connection experiences similar symptoms and testing the connection sometimes gives an error the first time around but is ok the second time around.

HEAT Ivanti Service Manager (ISM) SCCM Integration Issue with VPN Workaround:

To overcome this SCCM Integration issue, at first I attempted creating a second schedule with the same SCCM Integration but didn’t seem to work and the SCCM Integration ran, showed as completed, but had zero bathes and records.

Then created a second dummy SCCM Integration, with a filter that produced zero records, and scheduled it 15 minutes prior to the actual SCCM Integration.

That seems to have been working so far.

Ivanti finally came back and recommended to look into the “keep alive” setting on the VPN, as it may be getting in the way .

Leave a Reply

Please log in using one of these methods to post your comment:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s