SCCM Import Fails with Error - MID Server reported error: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name ''Issue SCCM JDBC import fails with error as - MID Server reported error: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name <object _name>CauseThe issue occurs due to the specific object being deleted or renamed or removed from the SCCM Database. Resolution1. In this case customer was facing exact error as - 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:262) at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1624) at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteCursored(SQLServerStatement.java:2021) at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:844) at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:768) If we closely look at the error, the exception occurs at SCCM End. 2. The object for which the issue occurs here is - V_GS_SN_SAMP_ADD_REMOVE_PROGRAMS_EDITION. 3. When we check the data source for which the issue occurs is - SCCM 2016 Software Edition - https://<instance_name>.service-now.com/nav_to.do?uri=sys_data_source.do?sys_id=e5255c6887300300562e4127f5cb0bab 4. Check the SQL statement in the data source - SELECT product0 as Product, edition0 as Edition, version0 as Version, publisher0 as Publisher, timestamp, resourceID FROM V_GS_SN_SAMP_ADD_REMOVE_PROGRAMS_EDITION WHERE Edition0 IS NOT NULL AND Product0 IS NOT NULL AND Publisher0 IS NOT NULL AND Version0 IS NOT NULL 5. We can see the SQL statement is querying on the table - V_GS_SN_SAMP_ADD_REMOVE_PROGRAMS_EDITION. The issue occurs because the table/object has been renamed/modified/deleted from the SCCM database that is the reason the SQL statement fails to find the object. The customer further needs to work with SCCM Administrators and update the SQL statement in the JDBC data source.