[sims] Client Not Responding Running Reports

[tmcd35]

Hi guys,

 

I thought I'd check in here and see if there is a known issue in the community before I start harassing Capita.

 

The local SIMS client appears to slow to a crawl and regularly freezes when running or designing reports. The problem only seems to appear with reports, everything else is fine.

 

The SIMS server is practically idle and so is the client machine (dual core, 768mb, XP 32bit).

 

If this is 'normal' then how are others coping? If it's not then I think I might need to place a support call with Capita.

 

Thanks

[matt40k]

What's the disc activity like? You could do with 2GB ram on the workstations. What's the server like? How many users etc using SIMS? What's the network connection on the workstation\server?

[tmcd35]

Both server and workstation looks pretty idle to me. I agree with the ram and see if I can get some in but barely over 600mb is in use. The server is new, dual core 4Gb 64bit v.fast hard drives. This is a new SIMS install and if there are 3 people actively using it at the same time it's a lot (this will change). Network connection - 100mbps on the workstation, 1Gbps on the server, again nothing else happening to get in the way.

 

The problem definitely looks like its at the client end rather than the server end. Maybe it is the ram? I'll upgrade one machine and see.

 

Thanks.

[vikpaw]

Sounds like RAM. Which version of Office are you on? I noticed 2010 being rather slow with elements of reporting.

[matt40k]

I noticed 2010 being rather slow with elements of reporting.

 

One of the joys of being not supported.

[tmcd35]

We're using Office 03 atm. Still it wasn't getting far enough through reporting to worry about any Office version! I think it might have been RAM. I found a spare 3Gb and upgraded one machine, it seems better. With my thinking hat now on (should have used it early), Windows was showing RAM free but maybe it was not enough when the reporting module was asking for allocation. ie, I was looking at the RAM commit figures at the wrong point in the process and thinking everything was fine.

 

Time will tell.

 

Thanks for your help.

[vikpaw]

One of the joys of being not supported.

 

Agreed, unfortunately my advice was not taken as the whole school 'had' to take the opportunity to move to win 7 with office 2010. I'm still on 2007 (only upgraded a few months back) and the server is staying on 2003. I'm also asking that anyone that designs reports has another machine with office 2k7 on, as i've found many things that don't work, like result tags, mailmerge and some reports!