QMAD2003 sync error - Cisco UCCX - WFO

[mattlewis1]

The sync.log and sync.dbg are showing the following errors. We noticed the resources modified in UCCX GUI, do not sync over to WFO - monitoring and recording administration. Attempting to manually use the synchronize database, provides a QMAD2003 error (see attachment). This error is not the common one seen regarding database lowercase name structure or the uccxworkforce password.

Anyone experience something similar? As far as I can tell nothing has changed on the database side.

Sync.log

2015-06-08 10:58:11,884 INFO  SYNC0000 Initiating scheduled batch synchronization.

2015-06-08 10:58:12,025 INFO  SYNC0000 Synchronizing [com.calabrio.qm.sync.QmAcdSourceFactory$1@a00185 to com.calabrio.qm.sync.target.AgentTargetDao@c3c315 using com.calabrio.qm.sync.target.AgentSynchronizer@3c9c31].

2015-06-08 10:58:12,025 INFO  SYNC0000 Getting agents...

2015-06-08 10:58:12,447 INFO  SYNC0000 Retrieved 390 agents.

2015-06-08 10:58:12,494 INFO  SYNC0000 Synchronizing [com.calabrio.qm.sync.QmAcdSourceFactory$3@1758500 to com.calabrio.qm.sync.target.TeamTargetDao@6ed322 using com.calabrio.qm.sync.target.TeamSynchronizer@1e78c96].

2015-06-08 10:58:12,494 INFO  SYNC0000 Getting teams...

2015-06-08 10:58:12,884 INFO  SYNC0000 Retrieved 26 teams.

2015-06-08 10:58:12,884 INFO  SYNC0000 Synchronizing [com.calabrio.qm.sync.QmAcdSourceFactory$2@1884a40 to com.calabrio.qm.sync.target.SupervisorTargetDao@c2ee15 using com.calabrio.qm.sync.target.SupervisorSynchronizer@19cd75a].

2015-06-08 10:58:12,884 INFO  SYNC0000 Getting supervisors...

2015-06-08 10:58:13,275 INFO  SYNC0000 Retrieved 42 supervisors.

2015-06-08 10:58:13,603 ERROR SYNC2001 Synchronization failed with exception.

Sync.dbg

Caused by: java.sql.SQLException: Subquery returned more than 1 value. This is not permitted when the subquery follows =, !=, <, <= , >, >= or when the subquery is used as an expression.

                at net.sourceforge.jtds.jdbc.SQLDiagnostic.addDiagnostic(SQLDiagnostic.java:367)

                at net.sourceforge.jtds.jdbc.TdsCore.tdsErrorToken(TdsCore.java:2816)

                at net.sourceforge.jtds.jdbc.TdsCore.nextToken(TdsCore.java:2254)

                at net.sourceforge.jtds.jdbc.TdsCore.getMoreResults(TdsCore.java:631)

                at net.sourceforge.jtds.jdbc.JtdsStatement.processResults(JtdsStatement.java:584)

                at net.sourceforge.jtds.jdbc.JtdsStatement.executeSQL(JtdsStatement.java:546)

                at net.sourceforge.jtds.jdbc.JtdsPreparedStatement.executeUpdate(JtdsPreparedStatement.java:505)

                at com.calabrio.qm.sync.target.AbstractQmSynchronizer.executeUpdateAndClose(AbstractQmSynchronizer.java:34)

                at com.calabrio.qm.sync.target.AgentSynchronizer$4.execute(AgentSynchronizer.java:286)

                at com.calabrio.qm.sync.target.QmSyncOperation.execute(QmSyncOperation.java:35)

[mattlewis1]

anyone else who gets this issue. I had to delete all my inactive resources in UCCX. Once this was done, syncing started to work again.

[cperez0011 · Accepted solution]

Hello.

I had the same problem an hour ago. I solved the problem by checking the sync.dbg file, one of the Resources had a bad config, you can notice that in the file, there's a part where it say "DB Transaction Failed, rolling back." 3 lines above there's the name of the Resource, you have to delete the resource from Call Manager and then add again

Regards.

[prathmesh.bhurke@i-karma.on]

What you mean by delete resource from call manager. You mean delete user profile or remove them from app user and add again.