(new to group) Poor performance of Timeslips

Hello everyone.  New to the group and have been doing some searches - not finding much yet.  I presume that this has been covered before and there may be some great articles to read that I just haven't found yet.

My client has complained off and on about poor performance of Timeslips.  New server made things better for a little while.  New network hardware made things better for a little while.  Everything I've tried seems to make it better... you guessed it...for a little while.

Server: 2008 SBS running on ESXi server (bonded nics - 2Gb), 20Gb RAM

user count: 17 with rarely more than 5 in at the same time except toward the end of the month when the attorneys are scrambling to get their time in.

AV: have specifically excluded the datashare on the server, the install point on the workstations, disabled scanning of network drives and have explicitly excluded the list of extensions.  Have touched every workstation to ensure that the TEMP folder is within the excluded TS folder.

When it was on the old SBS server (2003) I disabled opportunistic locking myself.  Within our ticketing system I see that we worked with Sage support and they edited the registry to disable it on the new server.  Today I found that it was not (HKLM\system\currentcontrolset\services\lanmanserver\parameters\ enableoplocks was not there so I created it.  reboot of server is scheduled for tonight.

So... This client is wanting Timeslips to run like a champ and it just isn't.  Looking for more suggestions.

TIA,

Eric

  • 0

    Hi Eric,

    Please understand that I am not an IT person and I will assume your workstations are current.  There are performance settings in the setup menu that you can turn off if you are not using any of those features.  If the slip list is taking a performance hit, view it by ID and specify the last 5000 slips for example.

    You might research SMB (server message blocks??).  We have seen that be an issue on the server side.

    Good luck and I am sure others will chime in.  

  • 0 in reply to AllenH

    One other thing to check......your network cards should not be allowed to go to sleep.