SGC-SCCM Integration failing on second run

[jobikunjumon]

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.

[Viraj Hudlikar]

@jobikunjumon 

See if below thread is helpfull for you.
SG Connector for SCCM - Last Run datetime - ServiceNow Community

SCCM Data Source 'Last Run Date Time' is Not Getting Updated. - Support and Troubleshooting

If my response has helped you hit helpful button and if your concern is solved do mark my response as correct.

Thanks & Regards
Viraj Hudlikar.

[vhiinnz1 · Accepted solution]

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

[Michael Conley]

The fix helped us, but only when we used the 'test load' from the data source. Once the scheduled import kicks off it replaces the 'SQL statement' on the data source record. You should use the SQL statement provided in KB1724482 but you should update the 'Custom SQL Statement' on the proper 'SCCM Instance Member' record detailed in the "Customize Instance Data source SQL statement" section of KB1001248.

[BhupeshG]

can you please post the article here. Many are not able to access the article

[learn nv]

Hi Bhupesh,

are you able to fix the issue? if so, could you please help me with the solution.

Thank you,

learn nv