We had SQL Monitor up and running on an Amazon EC2 instance. We upgraded the instance to increase the memory and CPU on the vm and now the web app fails to connect to the Base Monitor. The Base Monitor service is up and running and appears to be listening on port 7399.
On the "Unable to connect..." web page, if I click on the "Connect to Base Monitor" button, I get the message:
"Attempted to read or write protected memory. This is often an indication that other memory is corrupt."
We tried a complete re-install, but unfortunately get the exact same error message.
We are using SQL Monitor 3.3 running on Windows Server 2012, with SQL Server 2012 and IIS 8.
Thanks for your help.