The Transaction Broker Log

Navigation:  Appendices > Debugging > Scanning >

The Transaction Broker Log

Previous pageReturn to chapter overviewNext page

When a GridTemplate is scanned, QuarkXPress generates a table that lists the contents of all the textboxes of the scanned GridTemplate. This table is saved in the c:\qpp\temp\ local temporary folder, and then if the results of the scan are accepted, this temporary table is copied from your workstation to a temporary folder on the server, where the Q++Broker merges it with the shared Templates database.



When scanning occurs with no errors, but a message is generated warning that there are no textboxes in the scanned Template, then the Transaction Broker Log debug tool is used to compare the contents of the 3 tables shown above to see at which stage a problem occurred.



The screenshot above shows how the Transaction Broker Log displays the contents of each of the 3 tables described in the flow chart above. The Q++ Broker Log zone at the top-right of the dialog, is the first obvious place to search for a clue as to the cause of the failed scan. If it contains any messages (or if the checksum field above the Templates Database zone displays the message Buffer table is empty), then you should replace the Q++ Broker buffer tables as explained in the topic dealing with locked transcations.


Below each of the 3 tables headers are two numbers : the number of records and the Checksum. The absolute value of these two numbers is not important, but they should all be equal if a scan was properly imported into the shared Templates database. If there were no errors at the top of the dialog and there are discrepancies between some of the 3 tables' number of records and checksums, then the problem is most likely a network synchronization issue.

Topic 144900 updated on 17-Jul-2003.
Topic URL: