Service Graph Connector for SCCM Authentication Issue

Community Alums
Not applicable

I am attempting to configure the Service Graph Connector for SCCM but I am running into some strange authentication errors.  I am wondering if anyone else has encountered a similar error.  I have set up the integration to use integrated authentication with our MID server.  I have granted the account that is running the MID server the needed access to the SCCM database, so I would expect the integration to work.  However, when I use the "Test Load 20 Records" feature, I see the error: MID Server reported error: java.sql.SQLException: com.microsoft.sqlserver.jdbc.SQLServerException: Login failed for user

 

The user it says that the login failed for is NOT the user that is running the MID server, but the name of the server itself.  Since the server is not an account, obviously the integration fails.  I just can't seem to figure out why the integration is attempting to authenticate using the name of the server rather than the user.  I have tried changing the "Run Scheduled Import As" user to my own user ID just to test, and it still shows the server name as the failed login.  

 

One thing I found in a KB article is this line:

  1. Verify the Log On account/password are a Windows user with access to the SQL SCCM tables.

When I looked at this on the MID server, the Log On section is blank and it instead says it is using the local account which would be the right account for what I am trying to accomplish.  I can't set that Log On section because the password for the account gets rotated frequently and so it would be impossible to keep that up-to-date.

 

Does anybody know what the issue here might be or have any ideas on things to try in order to resolve this?

1 REPLY 1

ersureshbe
Giga Sage
Giga Sage

Hi, I believe the mid server is configured with the hosted machine. The service account is not having the admin role then you will face the mentioned error. 

Service Account should contain the right role. Test purpose configures the admin role.

Regards,
Suresh.