Cash Book Poor Performance - LawsonGuru.com

Name	Points
Greg Moeller	4184
David Williams	3349
Kat V	2984
Woozy	1973
Jimmy Chiu	1883
Kwane McNeal	1437
Ragu Raghavan	1377
Roger French	1315
mark.cook	1244
Chris Martin	825

SteveB

New Member

Posts: 2

7/11/2014 2:03 PM

Is anyone else experiencing very slow Cash Book performance?
When users run single line reconciliations, it takes 2 minutes for the process to complete. But when users try to do multiple lines, the process times out in Smart Office and Portal (multiple lines can be successfully processed using LID).
We have opened a case with Infor and they had us rebuild indexes on CBTRANS and CBCONSOL which did not solve the issue. To resolve the time out issue, Infor had us increase the read/write time out for IOS from 60 seconds to 900 seconds which did resolve the timeout issue.

• Our application, web, database, LBI and Smart Office servers are running Windows Server 2008 R2
• Database engine is SQL Server 2008 R2
• IBM Websphere 7
• Lawson S3 Core Technology 9.0.1.12.204
• Lawson S3 Applications 9.0.1 MSP 7
• Lawson EMSS 9.0.1.5
• Infor Smart Office 10.0.5.4.10
• Lawson Business Intelligence 9.0.4.2.136
• ViewPoint 10.1.0.2151

Tags: Cash Book Slow CB80

John Henley

Posts: 3366

New Poster

Engaged Reader

Avid Reader

7/11/2014 2:55 PM

Are you experiencing any other performance issues in Portal, or it is just in CB80?

SteveB

New Member

Posts: 2

7/11/2014 4:33 PM

John,

We are experiencing the issue with any of the CB Processes in both Portal and Smart Office. The ofher modules are not having this issue.

John Henley

Posts: 3366

New Poster

Engaged Reader

Avid Reader

7/17/2014 6:46 PM

Since you're not experiencing slowness with other modules when using Portal, this doesn't suggest a Portal or IOS issue, but rather an issue specific to CB80.

How long has this been a problem?

Do you see any .cfg files in your LAWDIR/prodline/cbsrc folder?

Did they have you try to recompile CB80 as well as any programs invoked by CB80?
If one or more of them was compiled in trace mode, that would slow it down considerably.

Have you tried to use the timestats functions to see if the issue is database/index related (within Lawson) and/or run the verifymssql command to look for any missing indexes?