OfficeTalk gateway hanging

  1. Home
  2. Knowledge Base
  3. Softalk
  4. OfficeTalk
  5. OfficeTalk gateway hanging

More Info

Important: This procedure involves editing the database and therefore assumes knowledge of SQL. Please make sure that all data are backed up before undertaking this procedure. This procedure currently only assumes an ASA database; the process is similar for a JET and MS-SQL database.

There are 2 main raw queues in OfficeTalk.

The Received queue is made up of the following tables: RcvdData, RcvdMessages and RcvdRecipients. This queue contains messages that have been received into OfficeTalk by the gateway but have yet to be delivered to a user.

The Sent queue is made up of the following tables: SentData, SentMessages and SentRecipients. This queue contains messages that have been sent from OfficeTalk clients but have yet to be delivered to the recipient by the OfficeTalk gateway.

Summary

This problem is probably due to one or more messages being stuck in the send or receive queue; that is to say the message cannot be processed by the OfficeTalk gateway and is causing the gateway to slow down.

Detail

To determine which message queue is causing the problem, either:

  • Use dbisqlc.exe located in the %programfiles%OfficeTalk SQL Anywhere folder on the computer having the database server. Please see this FAQ for details on how to connect to a database using ISQL.
  • Install Sybase Central (This is a graphical utility that will make renaming/deleting tables easier). Please see this FAQ for details on how to download and use Sybase Central.

Perform the following:

Close OfficeTalk on all computers

Connect to the database. Specify to connect to the OTDB (assuming default) data-source using TCP and the username: dba and password: sql.

Rename the following tables by putting a 2 at the end (or similar):

  • RcvdData (i.e. rename to RcvdData2)
  • RcvdMessages
  • RcvdRecipients


  • SentData
  • SentMessages
  • SentRecipients

For example to rename the RcvdData table use the query:

Alter Table RcvdData rename RcvdData2;

Start the gateway machine. If it is found that the gateway machine is no longer hanging then the problem is with the processing of one (or more) of the messages.

Close the gateway machine. Delete the newly created RcvdData, RcvdMessages and RcvdRecipients tables. Rename the RcvdData2, RcvdMessages2 and RcvdRecipient2 tables back to RcvdData, RcvdMessages and RcvdRecipient respectively.

Start the OfficeTalk gateway machine again. If OfficeTalk no longer hangs, then the problem is most likely with the sending of messages. If OfficeTalk still hangs then the problem is with the receiving of messages.

Prove this by closing OfficeTalk; renaming RcvdData, RcvdMessages and RcvdRecipient tables back to RcvdData2, RcvdMessages2 and RcvdRecipient2 again respectively. Delete the SentData, SentMessages and SentRecipients tables (these are blank). Rename the SentData2, SentMessages2 and SentRecipients2 tables to SentData, SentMessages and SentRecipients respectively.

Start the OfficeTalk gateway machine again. If OfficeTalk no longer hangs, then the problem is most likely with the receiving of Messages if OfficeTalk still hangs then the problem is with the sending of messages.

Close OfficeTalk; delete the blank RcvdData, RcvdMessages and RcvdRecipient tables; and rename the RcvdData2, RcvdMessages2 and RcvdRecipient2 tables back to RcvdData, RcvdMessages and RcvdRecipient respectively.

It should now be known if the problem was is in the send queue or receive queue. If the problem was determined to be in the sending of messages then open the SentMessages table. If the messages are dispensable you may simply truncate the SentData, SentMessages and SentRecipients tables. All 3 tables must be treated together.

For example to truncate the SentData table type the following:

Truncate Table SentData;

If the problem was determined to be in the receiving of messages then open the RcvdMessages table. If the messages are dispensable you may simply truncate the RcvdData, RcvdMessages and RcvdRecipient tables. All 3 tables must be treated together.

OfficeTalk can then be started and functionality can continue as normal. If however, messages in these raw queues are n

Was this article helpful?

Related Articles