8 Replies Latest reply on Oct 15, 2009 10:59 AM by garciam_sa

    SQL and Exchange monitors fail after upgrading to v10

      Just upgraded to v10, no issues during the upgrade.

      ipMonitor service runs as local account.

      Using specific credentials for the SQL and Exchange monitors (same ones we used previously)

      Now they are giving this: The remote device rejected the request due to an internal error and Unable to connect to the remote device.

      Interestingly, when I do a 'verify' on a SQL monitor, it shows me results.. but the monitor itself still isn't working.

        • Re: SQL and Exchange monitors fail after upgrading to v10

          Same exact situation here.  SQL and Exchange monitors worked fine in 9.0.6 but in version 10, they all started giving that error.

          Tried with the ipMonitor service running under the local system account as well as under a domain admin account in case there was a bug with the SQL monitors not using specified credentials.

          I also tried adding new SQL monitors and deleting old ones but same result...

            • Re: SQL and Exchange monitors fail after upgrading to v10
              bshopp

              Have ya'll been able  to open a support ticket?

                • Re: SQL and Exchange monitors fail after upgrading to v10

                  Hadn't yet, upgraded this evening.  Was hoping for a quick fix!

                    • Re: SQL and Exchange monitors fail after upgrading to v10
                      Fodome

                      Hi bman1978,

                      Assuming your ipMonitorSrv service is still running as a local account and the SQL/Exchange Server Monitors are still using a domain admin credential, can you try the following:

                      1. Log in to the ipMonitor web interface, open the settings page for one of the failing SQL/Exchange Server Monitors.

                      2.  Click on the "Pop-Up XML" button and note the value of the "<id>" tag.

                      3.  Log in to the ipMonitor server with the local account used to run the ipMonitor service.

                      4.  Open a new "cmd.exe" prompt and enter the following command:

                      runas /user:CREDENTIAL cmd.exe

                      where CREDENTIAL is the account impersonated by the "Credential for Monitoring" parameter in the SQL/Exchange server Monitors.  Hit enter, then specify the corresponding password.

                      5.  A new prompt should open.  In this prompt, change to the \ipMonitor\ directory.

                      6.  Enter the following command

                      ipmext_sql.exe [MONITOR_ID]

                      where MONITOR_ID is the number noted in step 2.

                      7.  Once you hit enter, the executable should run and return counters in the prompt window.

                      Are counters displayed correctly or does an error occur during this process?

                      Thanks in advance for this,

                      Chris Foley - SolarWinds - Support Specialist
                      Support:  866.530.8040  |  Fax: 512.857.0125
                      network management simplified  |  solarwinds.com

                      • Re: SQL and Exchange monitors fail after upgrading to v10
                        Fodome

                        Hi bman1978,

                        Can you also run the following command within the same CMD window:

                        ipmext_wmi.exe [MonitorName]

                        Thanks again,

                        Chris Foley - SolarWinds - Support Specialist
                        Support:  866.530.8040  |  Fax: 512.857.0125
                        network management simplified  |  solarwinds.com

                          • Re: SQL and Exchange monitors fail after upgrading to v10

                            I don't use WMI much.. and don't have a monitor that's showing this symptom.  When running the wmi check against the same ID, no output.

                            Here's the output for the SQL check:

                             

                            C:\Program Files\SolarWinds\ipMonitor>ipmext_sql 361984930684
                            0,1.00
                            2,5924.00
                            54,0.00

                              • Re: SQL and Exchange monitors fail after upgrading to v10
                                Fodome

                                Bman1978,

                                At this point we are investigating the test results here and attempting to replicate.

                                In the meantime, can you open a case using the following form:

                                http://www.solarwinds.com/support/ticket

                                I will then grab it and continue this offline.

                                Thank you,

                                Chris Foley - SolarWinds - Support Specialist
                                Support:  866.530.8040  |  Fax: 512.857.0125
                                network management simplified  |  solarwinds.com

                                • Re: SQL and Exchange monitors fail after upgrading to v10

                                  One thing I notice is that in a SQL Monitor, if I disable all of the SQL Server Counters but leave the SQL Server Performance Counters enabled, the values for those come up when I hit Verify.

                                  However, if I try it with the first two of the SQL Server Counters enabled (Minimum SQL Memory and Cache Hit Ratio Percentage), those come up as Unavailable and it says "Threshold failed or could not locate any Data Counters from "server.domain.com". Reason: System errorcode=0xffffffff"

                                  Selecting anything beyond those two make them all (including the previously working ones) switch to No Value and it says "Threshold failed or could not locate any Data Counters from "server.domain.com". Reason: Unable to connect to the remote device "

                                  (server.domain.com substituted for actual server name)