+11Had to give both production servers and our database server a reboot last night after an update. Just did a quick check, and all looked fine.
But today my users complain about Dispatch Console not working. So I restart DSE service on the main server. After doing this I can get one instance of Dispatch Console to work, but if I launch 2, the first will stopp. And sthe seciond be unstable.
As a note: I run Astea Cache Server on a separate server from Astea Alliance
Best answer by Phil Seifert
Hi Bjørn,
The Dispatch Console is reliant also on the REDIS cache service (Astea Cache Service). Whenever I run into spotty or strange performances or events on the DC, I restart the Astea Cache Service, the DSE service and IISRESET on all servers.
+24Hi Bjørn,
The Dispatch Console is reliant also on the REDIS cache service (Astea Cache Service). Whenever I run into spotty or strange performances or events on the DC, I restart the Astea Cache Service, the DSE service and IISRESET on all servers.
+1I want to remind that from Alliance V15 Dispatch Console updates do not go through DSE but through the framework.
Thus restarting DSE service won’t effect Dispatch Console updates.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
