colleagues, are there anybody with ct for siebel experience? we have some strange problem at one of our customers' sites. there is s8300 cm3 switch, aes 3.1 and ct for siebel: driver version 2.0.1.7, applications version is release 1.1, version 1.0, service pack 1, db version is 1.1.000 (according to SCHEMAVER table). almost everything is working as expected, i.e. ct events are passed to siebel, screen pops are working, siebel cti panel is working but there's a problem with database call tracking. upon call arrival, its data is being inserted in db, we can confirm it in the db itself (calldata table) and in call service log files. but according to logs, the call data is not being updated with new information. there's an excerpt from call service log:
viewing db trace itself we can see that ct for siebel tries to execute the following two requests:
as far as i know anything about sql, second statement is meaningless and thus it is no wonder that sql server returns an error on it. anybody seen this problem before?
Code:
061907 17:46:03 INFO: Successful Insert of QueueTime data for UCID - 00001006401182275165
061907 17:46:07 INFO: Successful Insert of QueueTime data for UCID - 00001006411182275169
061907 17:46:19 ERROR: Unable to Update Queuetime record for UCID - 00001006411182275169
061907 17:46:26 ERROR: Unable to Update Queuetime record for UCID - 00001006401182275165viewing db trace itself we can see that ct for siebel tries to execute the following two requests:
Code:
UPDATE CALLDATA SET ENTRYDATETIME = () WHERE UCID = '00001006411182275169 ' and ITEMNAME = 'QueueTime'
select * from UPDATE CALLDATA SET ENTRYDATETIME = () WHERE UCID = '00001006411182275169 ' and ITEMNAME = 'QueueTime'as far as i know anything about sql, second statement is meaningless and thus it is no wonder that sql server returns an error on it. anybody seen this problem before?
