SGC-SCCM Integration failing on second run

jobikunjumon
Tera Contributor

Hi Team,

 

SGC-SCCM works perfect when the Last run datetime is empty. However when that gets filled in after the 1st run it fails with import log as below.

 

MID Server reported error: SQLState: S0001
com.microsoft.sqlserver.jdbc.SQLServerException: Invalid column name 'TimeKey'.

 

TimeKey is standard SCCM column, nothing customized. This worked cool during dev phase, while we deployed this to prod, we see this behavior with error out.

1 ACCEPTED SOLUTION

vhiinnz1
Tera Expert

Hello - it will get fixed on the next upgrade 4.0. But please see the work around below that fixed it. Thanks

 

https://support.servicenow.com/kb?id=kb_article_view&sys_kb_id=0d66ef9a47879a5077748d01426d43a5

View solution in original post

12 REPLIES 12

use the old SQL statement which is there for time being. pls update it in instance sql and base sql both.

during upgrade to 4.0 revert to bases

Hi vhiinnz1,

Could you please paste the document here as don't have access to the article.

The issue stemmed from the SQL query introduced in the latest release—it was misconfigured. To resolve this, I copied the SQL statement from the KB Article (If I am not wrong, you can copy the SQL query from any SCCM instance where the plugin hadn’t been updated and the SQL statement is OOB ) and apply it to the OOB instance of SCCM Computer identity data sources .

To avoid the conflict during upgrade the Article suggested to make a change to the state of the update xml under versions. Hope this helps.