Dear VC team,
we face an issue when we are unable to get the task log listed - each time it crashes the VC client (it works only for few minutes after VC server restarted).

Configuration:
- We use VC 8.3.1
- We have VC server running on 'server A' (Windows Core server 2008 R2, 8 core Xeon CPU, 16GB RAM, same network as VC client)
- We have VC client running on 'server B' (Windows Server 2012 R2, 4core Xeon CPU, 8GB RAM, same network as VC server)
- We have over 850+ jobs

Issue:
1) Let's consider the VC server running for 2+ hours
2) If we open any task on VC client and right mouse click on 'Task log'
3) The VC client is trying to draw the 'Task history' window for 60+ seconds, however it is not successfully and then it throw 'Error handler' with the info that 'Unhandled Exception occured'.


Question:
- Have you seen this before (on model where client and server runs on separate machines, but in the same network AND having 800+ jobs)?
- Is there any internal time-out set-up on VC8 client, at which the Error handler is thrown? Can we extend this time out?

Additional informations
- It was working fine when we had there around 300 jobs, however once we migrated there another 500+ jobs from our old VC6, it started to behave like that...
- Originaly the VC8.3.1 server has just 4 cores and 8 GB memory - after this issue appeared, we increased it to 8 cores and 16GB RAM, but it didn't help...

Thanks for your advice - the VC task log feature is really critical for us.

Best Regards,

Hi

I experienced the same thing before I switched to external database.
Resolved it by restarting the client (only), hopefully same works for you.