I searched around a bit trying to find if someone else is having this issue, I was unable to find a thread. We just recently upgraded to 4.9.40 from 4.5.28, love the new interface and how fast it loads our jobs (over 900 of them).

After getting the server upgraded and then everyone's local clients, people started reporting that their job list are not populating. At first it was a couple people and then everyone who tried connecting remotely experienced the issue. The problem is intermittent, it doesn't always happen and never for everyone at the same time. For example I just loaded up the client without a problem but a co-worker right next to me could not; yesterday I could not get the job list to load. One constant throughout this has been that if you load up the client on the server, so that it is a localhost connection...that always seems to work.

I have enabled extended logging as well as client logging, so far I have seen a few failures but doesn't seem related. Is this a known problem?

Thanks,

Alex

Hi Alex,

we have not heard this before. We will setup some tests and get back to you.

---

Thanks for the quick reply, let me know if you need some log files to help out. I imagine that this is going to be a hard one to reproduce given how intermittent it is.

While we do some testing - could you please check if the remote clients are using Compression on the connection. If not, turn that on to see if it makes a difference.

---

We have been using the compression option given then # of jobs we have (10MB job file), I will have people try it both with and without to see if that makes a difference.

Thanks,

Alex

Hi Alex,

we just got a report from a customer with the same problem. After testing he found out that it was a .NET bug in an early version. He installed KB951847 and the problem was resolved. Also, it only happens when using compression on.

The .NET update can be found here:

http://www.tacktech.com/...btype=Tech&nid=23523 

---