SCCM 2016 Software Edition Data Source Not working

[Santosh M1]

Hi Team,

Can anyone please explain, how sccm 2016 software Edition data source will work?

It is not fetching any data from sccm database.

OOB query:

/*Table name and the query below should not be considered as the final query that executes. The final table and query responsible for extracting data from SCCM is formed at Run-Time*/

SELECT 1 from v_GS_Add_Remove_Programs where 1=0

[Ashutosh Munot1]

HI,

We use this:

SELECT 1 from v_GS_Add_Remove_Programs where 1=0

Thanks,
Ashutosh

[Pat Slattery]

When you run "test data source connecitons" form the setup module under the 2016 SCCM application, do you receive a success or failure? 

Is this isolated to the removed software datasource or is it failing in the connections test?

[Santosh M1]

Hi pat,

We we run the test connection, it is successful. and also we are fetching the data from other data sources. Only software edition data source is not working. We are getting the below error.

MID Server reported 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.probe(JDBCProbe.java:124)
at com.service_now.mid.probe.AProbe.process(AProbe.java:103)
at com.service_now.mid.queue_worker.AWorker.runWorker(AWorker.java:122)
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)

[Pat Slattery]

Read through this knowledge article. It seems that it is similar to your issue and provides remediation. 

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

Specific to only failing with the software editions