Problems with JDBC probe via MID

[tomas_larsson]

We are currently troubleshooting a JDBC integration via MID to a database with user data. It worked before but now it seems that the JDBC probe does not even reach the database. All necessary FW-rules should be in place. The MID log show the following error:

09/20/11 10:39:10 (540) Probe: JDBCProbe:a516cb58fd199440fe078cc767963f84 SEVERE *** ERROR *** getRecords failed (Method failed: (https://XXXX.service-now.com/sys_data_source.do?SOAP&displayvalue=all&redirectSupported=true)HTTP/1.... 500 Internal Server Error with code: 500)09/20/11 10:39:10 (540) Probe: JDBCProbe:a516cb58fd199440fe078cc767963f84 DEBUG: Data source not founda516cb58fd199440fe078cc767963f8409/20/11 10:39:10 (540) Probe: JDBCProbe:a516cb58fd199440fe078cc767963f84 Enqueuing: D:\ServiceNow\XXXXXXX\agent\work\monitors\ECCSender\output\ecc_queue.cb178f58fd199440fe078cc767963f6c.xml09/20/11 10:39:10 (540) Probe: JDBCProbe:a516cb58fd199440fe078cc767963f84 Worker completed: JDBCProbe source: a516cb58fd199440fe078cc767963f84 time: 0:00:00.719

Does anyone have an idea of what the problem might be?

Thanks,
Tomas

[john_andersen]

Looks like there is a debug statement of "Data source note found". Can you verify that the data source referenced by the scheduled import still exists.

[shart]

We also had this issue, it looks like an ACL problem with June11. You should add mid_server to the ACL on sys_data_source read.

[tomas_larsson]

Yes, we exported the data and imported it manually yesterday.

/Tomas