Unable to detect base monitor/corrupt memory error.
EngadaSQL
Posts: 6
I've come back for a second attempt at getting a trial of SQL monitor up and running in my organisation (first attempt was a year or so ago and didn't quite go to plan so was aborted)
I've installed all components of the monitor version 3.2 on my desktop machine - Windows 8 64 bit, IIS 8, SQL server 2012 SP1.
When I navigate to the website in my browser I get an unable to detect base monitor error. I've confirmed firstly in task manager that the base monitor server is running, I've confirmed secondly using sysinternals TCPView utility that it is listening on port 7399 and that that port is open on my firewall (windows firewall).
If I click on the connect to base monitor button, leaving the details as they are since they are correct, It returns an error "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." - This error appearing next to the base monitor computer input box.
Any thoughts on what might be causing this error? I had similar problems the first time around - refer to post http://www.red-gate.com/MessageBoard/viewtopic.php?t=13673&highlight=
I've installed all components of the monitor version 3.2 on my desktop machine - Windows 8 64 bit, IIS 8, SQL server 2012 SP1.
When I navigate to the website in my browser I get an unable to detect base monitor error. I've confirmed firstly in task manager that the base monitor server is running, I've confirmed secondly using sysinternals TCPView utility that it is listening on port 7399 and that that port is open on my firewall (windows firewall).
If I click on the connect to base monitor button, leaving the details as they are since they are correct, It returns an error "Attempted to read or write protected memory. This is often an indication that other memory is corrupt." - This error appearing next to the base monitor computer input box.
Any thoughts on what might be causing this error? I had similar problems the first time around - refer to post http://www.red-gate.com/MessageBoard/viewtopic.php?t=13673&highlight=
Comments
Can you confirm whether you have the Visual Studio Debugger running? and does disabling it make any difference to the behaviour?
Can you also ensure that you have the latest release installed, it is currently version 3.2.1 and can be downloaded here. It could be that one of the website files that IIS is trying to access has been corrupted.
ftp://support.red-gate.com/patches/SqlM ... .1.231.zip
Please let me know how you get on or if you have any questions.