Tweet
Syncade MES cannot typically reach the internet or directly access business level systems. This is great from a Cyber Security perspective but ends up introducing some unexpected issues that can cause significant performance problems.
Install fiddler on your application servers and let the session run idle for about 5 minutes. If you see a bunch of attempts to call out to the internet your Syncade performance is being negatively impacted and in some circumstances significantly.. This is because the moment the browser opens the system thinks it connecting to the internet and needs to run security related updates prior to allowing MES related web calls to pass by.
Additionally, CRL (certificate revocation lists) hidden within certificates may attempt to reach out to the CA (certificate authorities) to check if the certificate has been revoked which more often cannot take place. Code signed packages from WSUS and certain .exe's can also cause such problems. Even if you have self-signed certificates for your MES deployment other certs from your organization or delivered with the OS likely have CRL's.
I have seen systems take 20+ seconds to respond and WFX and QRM are often significantly impacted and can say virtually every Syncade MES system on the planet without internet access is impacted by this issue unless there has been previous intervention.
If you run fiddler and see these external calls, please let me know and I will try to provide you with some guidance to solve these issues but the support will only be through this forum to help the global MES community.
Install fiddler on your application servers and let the session run idle for about 5 minutes. If you see a bunch of attempts to call out to the internet your Syncade performance is being negatively impacted and in some circumstances significantly.. This is because the moment the browser opens the system thinks it connecting to the internet and needs to run security related updates prior to allowing MES related web calls to pass by.
Additionally, CRL (certificate revocation lists) hidden within certificates may attempt to reach out to the CA (certificate authorities) to check if the certificate has been revoked which more often cannot take place. Code signed packages from WSUS and certain .exe's can also cause such problems. Even if you have self-signed certificates for your MES deployment other certs from your organization or delivered with the OS likely have CRL's.
I have seen systems take 20+ seconds to respond and WFX and QRM are often significantly impacted and can say virtually every Syncade MES system on the planet without internet access is impacted by this issue unless there has been previous intervention.
If you run fiddler and see these external calls, please let me know and I will try to provide you with some guidance to solve these issues but the support will only be through this forum to help the global MES community.