SG-SCCM v3.6.0 Missing Data Source using guided setup

[Phillip1]

Using the guided setup after installing the 3.6.0 SG-SCCM plugin and creating the JDBC Connection, the next step is to validate the Data Source using the newly created JDBC connection. I manually tested the SCCM connection traditionally and via the connection alias to prove there are no issues with connectivity via port 1433 and that the credentials are working as expected; checks out okay. However, when making it to the guided step Validate Data Source, the guide takes you to a filtered Data Sources list with this embedded query: app_scope=9a2ce8f60f80001067ae409dc4767e6f^nameLIKESG-SCCM Computer Identity^name!=SG-SCCM Computer Identity.

The result is no Data Source being listed unless you remove the last filter ^name!=SG-SCCM Computer Identity. 

In doing so, I can then see the SG-SCCM Computer Identity and attempt to load 20 records, using the new JDBC connection method.

Unfortunately, the MID Server throws the following error:

java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: The TCP/IP connection to the host localhost, port 1433 has failed. Error: "Connection refused: no further information. Verify the connection properties. Make sure that an instance of SQL Server is running on the host and accepting TCP/IP connections at the port. Make sure that TCP connections to the port are not blocked by a firewall.".

Has anyone encountered the issue of the missing data source or the fact that the job is trying to connect to the "localhost", which I presume it's attempting to connect to the MID server on port 1433, when it should be attempting to connect to the SCCM server on port 1433, which we know already does work?

[JonSNow1967]

I am encountering this issue now with the SGC for SCCM (3.4.2) in our DEV instance.  We currently have the SGC successfully configured and executing in our PROD instance.  I have attempted to setup DEV equal to PROD, but this has not brought any success.  I am about to submit a support request for this.

[Phillip1]

Tera, we ended up logging a HI ticket and support fixed it. Said there were issues on the back end of the platform due to customizations and multiple failed installed previously attempted that we were not aware of. In short, I have no idea what fixed it other than the wizard behind the curtain that pulled some levers.