Greetings.
Environment: V6.2.6, SQL2K, Win2Kpro LAN client which also has the admin and architect.
Apparently, I have a problem that should have been fixed in an earlier SP. I see that zero-byte QTS files were fixed and maybe other QTS processing issues.
Problem: Certain operations on the client, particularly doing a ReSend of an Account to a Remote user using the Administrator-user-subscription function.
This operation produces a 401K byte .qts file in the client \QueueFiles folder and it gets stuck there.
The Windows Event log:Application has a source=SLXSystem.exe, event ID: 3 warning with "W-CBProcessQueueFile timed out (part 0, file: 081018-2324008590000.que)".
Then 5 minutes later, "W-CBProcessQueueFile timed out (part 1, file: 081018-2324008590000.que)".
5 minutes later, "W-CBProcessQueueFile timed out (part 2, file: 081018-2324008590000.que)".
Then the three messages repeat, followed immediately by anther SLSSystem event "W-Cannot send Queue File 081018-2324008590000.qts_DELL2900SERVER_1706. No connection to server 'DELL2900SERVER'."
At this point, a message box pops up with "Saleslogix Logging Error: No connection to 'DEL2900SERVER'. Please contact system administrator".
If any more work is done in any SLX client that would normally be logged, additional QTS files pile up in the QueueFiles folder.
I followed the directions to clear out a bad QTS file, and sure enough, the log-jam of files sweeps through after the offending one is removed.
But, the operation I did never makes it to the WGlogs, and the remote doesn't get the resend.
I have seen mention in SLX knowlegebase articles that QTS files normally should not exceed 100K bytes. So, having a 400K QTS is a red flag.
Most LAN users do not have any problems with this issue. In fact, the very same workstation will work flawlessly doing routine edits in the client or cutting remote databases in administrator.
One other operation that has been known to trigger the log-jam QTS file is "Check for Duplicates" when we do merging of accounts. This will work most of the time, but sometimes fail with the log-jam
I have reproduced the issue on multiple client machines.
Working on the administrative workstation, I have tried: clearing the cache and temp files per SLXKB #458877, applying hotfixes 1, 2, 7, 9, 10 & 11 as these seemed to fit my environment.
Thank you for your time and consideration,
Wayne Fetters
|