05-09-2019, 09:38 AM
A bit of background. I have, at a client's site, approx. 6 - 8 Intraweb SA servers running on a virtual Windows 2018 server (using http.sys and running on port 80). I have limited control over what the hosting crowd decide in terms of virus / malware / windows patch update timetables etc. The reason that multiple servers run on one VM is essentially related to costs to the client. Some of the Intraweb servers have 1,000 clients, others have 50! The reason they are SA (instead of a service) is simply to do with ease of monitoring them! Eventually I will develop a "monitoring app" that will tell if a server has stopped etc.
To the issues (and this is more a query if anyone else has struck these):
1) If one of the SA servers is down and a client tries to login they don't get an error. The simply get the login screen for one of the other SAs that is running. Which confuses the client! Is there a way of having a "default" SA server ... like a 404 page!
2) Shutting down one of these SA servers causes Windows Explorer to "lock up"! This is a bit difficult to explain ... but if you close the server and there is then no desktop response. I'm on a remote connection so I know that Windows hasn't locked ... I can still do file transfers etc. If you wait long enough (15 - 30 minutes) Windows does come back (sometimes with the "Explorer has stopped responding message") and you can recover, without a reboot etc. Of course I never have such an issue on my development computer. This may be related to running them as "application" as opposed to services.
Anyway just seeing if anyone else has had such issues.
To the issues (and this is more a query if anyone else has struck these):
1) If one of the SA servers is down and a client tries to login they don't get an error. The simply get the login screen for one of the other SAs that is running. Which confuses the client! Is there a way of having a "default" SA server ... like a 404 page!
2) Shutting down one of these SA servers causes Windows Explorer to "lock up"! This is a bit difficult to explain ... but if you close the server and there is then no desktop response. I'm on a remote connection so I know that Windows hasn't locked ... I can still do file transfers etc. If you wait long enough (15 - 30 minutes) Windows does come back (sometimes with the "Explorer has stopped responding message") and you can recover, without a reboot etc. Of course I never have such an issue on my development computer. This may be related to running them as "application" as opposed to services.
Anyway just seeing if anyone else has had such issues.