SCCM-SNOW Integration error? view V_GS_SN_SAMP_ADD_REMOVE_PRORAMS_EDITION does not exist

sachin2085
Kilo Explorer

SCCM-Servicenow Integration

Integration with SCCM was working fine till SCCM version Microsoft SCCM 2012 v2. Post SCCM upgrade to 1702 SCCM integration has started failing with  error.Object V_GS_SN_SAMP_ADD_REMOVE_PRORAMS_EDITION" does not exist. 

I am not able to see this particular view listed in the docs which is used for SCCM integration in the DOCS.

https://docs.servicenow.com/bundle/jakarta-platform-administration/page/integrate/cmdb/reference/sccm-import-process-and-tables.html

https://docs.servicenow.com/bundle/kingston-platform-administration/page/integrate/cmdb/reference/how-sccm-integration-works.html

 

Has anyone faced this situation earlier or what could be the reason

 

 

 

 

 

 

9 REPLIES 9

sachin2085
Kilo Explorer

Hi Ashutosh,

 

Thanks for your reply. I know that this object does not exist in database.

 

but this view has no where been listed on servicenow docs in the list for views used for hardware inteventory by Servicenow SCCM.

Hi,

Can you clarify what exactly are you looking for.

 

Because this image which i can see is a screen which we get when we transform the data.


Thanks,
Ashutosh Munot

Mike W_
Tera Contributor

Was this issue ever resolved? I just hit it, too.  I think it might be related to SCCM being on the Current Branch versioning, whereas ServiceNow just supports the year numbered releases.

alexqx4
ServiceNow Employee
ServiceNow Employee

what's the latest on this, any fixes? I am running SCCM 2016 with Madrid were I see the same issue:

 

Data source: SCCM 2016 Software Edition
Error: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'V_GS_SN_SAMP_ADD_REMOVE_PROGRAMS_EDITION'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1515)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteCursored(SQLServerStatement.java:1879)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:766)
at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:689)
at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeQuery(SQLServerStatement.java:616)
at com.service_now.monitor.jdbc.JDBCRowSet.query(JDBCRowSet.java:64)
at com.service_now.mid.probe.JDBCProbe.doSelect(JDBCProbe.java:313)
at com.service_now.mid.probe.JDBCProbe.doQuery(JDBCProbe.java:199)
at com.service_now.mid.probe.JDBCProbe.doCountRows(JDBCProbe.java:167)
at com.service_now.mid.probe.JDBCProbe.probe(JDBCProbe.java:118)
at com.service_now.mid.probe.AProbe.process(AProbe.java:96)
at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:125)
at com.service_now.mid.queue_worker.AWorkerThread.run(AWorkerThread.java:20)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)

Frank1975
Kilo Guru

Hi all, 

i got rid of the error. I found the following Community thread as well as the Knowledge Article on High

I checked the community and noticed this article.

https://community.servicenow.com/community?id=community_question&sys_id=8e9c39f9dbcf23801089e15b8a96...

 

 

 

With a link to this KB on the HI Site.

https://hi.service-now.com/kb_view.do?sysparm_article=KB0721360

 

 

But even so , no error, also no data coming in from SCCM.

 

thanks

Frank