6 Replies Latest reply on Mar 7, 2012 12:25 PM by chaldz

    .NET Runtime 2.0 Error

    chaldz

      Has any one else had trouble with ipMonitor after the upgrade to the latest version, 10.5.1, where the website will become unavailable until the ipmservice.exe is restarted?  Each time I get a .NET error and the message below in Event Logs.


      Faulting application ipmservice.exe, version 10.5.1546.1, stamp 4ef149e7, faulting module ntdll.dll, version 5.2.3790.4789, stamp 4cc1815c, debug? 0, fault address 0x0001bb72.

        • Re: .NET Runtime 2.0 Error
          Fodome

          Hello chaldz,

          To my knowledge the only ipMonitor component that relies on .NET is licensing.

          Having that said, perhaps start by installing the SolarWinds License Manager and retrieve the log from it to see if it reports any problems with the License.  Here's how:

          1. Download and install the latest License Manager from here:

          http://solarwinds.s3.amazonaws.com/solarwinds/Release/LicenseManager/LicenseManager.zip

          2. Run it and click "View Log".

          See if there are any errors.

          Let us know.

          Sincerely,

          Chris Foley | Support Representative
          SolarWinds | IT Management, Inspired By You
          Support:866.530.8040 || Fax:512.857.0125

            • Re: .NET Runtime 2.0 Error
              chaldz

              I already had License Manager installed and the log shows no errors and all entries are for when I just opened it.  I can upload the log to you if you would like to check it.

              That would be strange if the license manager is the only component that relies on .NET when the .NET error shows that the faulting application is ipmservice.exe.  This issue did not start for me until after the 10.5.1 upgrade and has occurred 3 times in the 40 days.

                • Re: .NET Runtime 2.0 Error
                  chaldz

                  I found a ipmfatal.log in \solarwinds\ipmonitor\logs.  The Date Modified date is the exact same as the date/time of the .NET error in Event Logs.  Here are the contents:

                   

                  2011-12-13 09:02:44 [build1371] cgi | uri(/cfg/cgi?sid=1478792537722&area=ajax&action=dashboard&tid=100007577504&nolayout=true&doparents=true&dofull=true&)

                  2011-12-13 09:02:44 [build1371] webthread | ssl(true)

                  2012-01-05 09:38:30 [build1531] cgi | uri(/cfg/cgi?sid=2092974850871&area=ajax&action=export&id=1483036393946)

                  5536218&preset=details&sort_field=.mon.severity&sort_order=ASC&data_type=num&sort_caption=Status&)

                  2012-01-05 09:38:30 [build1531] webthread | ssl(true)

                  2012-01-05 09:38:30 [build1531] webthread | ssl(true)

                  2012-01-05 09:38:31 [build1531] probe | id(24602867005387) type(16) ExCode(c0000005)

                  2012-01-05 09:38:31 [build1531] probe | id(26252100919471) type(206) ExCode(c0000005)

                  2012-01-05 09:38:31 [build1531] scheduler

                  2012-01-05 09:38:34 [build1531] webthread | ssl(true)

                  2012-01-05 09:38:42 [build1531] webthread | ssl(true)

                  2012-01-05 09:38:42 [build1531] webthread | ssl(true)

                  2012-02-07 17:10:24 [build1546] cgi | uri(/cfg/cgi?sid=1646301128870&area=devices&action=manage&)

                  2012-02-07 17:10:24 [build1546] cgi | uri(/cfg/cgi?sid=1646301128870&area=devices&action=manage&)

                  2012-02-07 17:10:24 [build1546] webthread | ssl(true)

                  2012-02-07 17:10:25 [build1546] probe | id(24267859556299) type(36) ExCode(c0000005)

                  2012-02-07 17:10:25 [build1546] probe | id(1281214718896) type(16) ExCode(c0000005)

                  2012-02-07 17:10:25 [build1546] scheduler

                  2012-02-07 17:10:25 [build1546] probe | id(24263564589003) type(35) ExCode(c0000005)

                  2012-02-07 17:10:38 [build1546] probe | id(10837519367811) type(41) ExCode(c0000005)

                  2012-02-07 17:10:38 [build1546] probe | id(10841814335107) type(41) ExCode(c0000005)

                  2012-02-23 15:26:37 [build1546] cgi | uri(/cfg/cgi?sid=705704668850&area=devices&action=manage&)

                  2012-02-23 15:26:37 [build1546] webthread | ssl(true)

                  2012-02-23 15:26:37 [build1546] webthread | ssl(true)

                  2012-02-23 15:26:37 [build1546] webthread | ssl(true)

                  2012-02-23 15:26:38 [build1546] scheduler

                  2012-02-23 15:26:41 [build1546] probe | id(23636521909891) type(24) ExCode(c0000005)

                    • Re: .NET Runtime 2.0 Error
                      Fodome

                      Chaldz,

                      Based on the contents of your log file, it appears you were experiencing the same issue in ipMonitor 10, 10.5 and 10.5.1.  So it does not appear to be a version-specific issue.  Having that said, I have some questions:

                      1. If you click "About" on the top-right, how many monitors does it say you have?

                      2. What operating system is your ipMonitor installation running on?

                      3. Is ipMonitor installed on a dedicated system?  What is RAM, CPU and Drive usage like?

                      4. Do you have many Groups, SmartGroups, Subnet Groups and/or Devices? 

                      Thanks in advance for your answers.

                      Sincerely,

                      Chris Foley | Support Representative
                      SolarWinds | IT Management, Inspired By You
                      Support:866.530.8040 || Fax:512.857.0125

                        • Re: .NET Runtime 2.0 Error
                          chaldz

                          I can assure you, having the webpage be unavailable and needing to restart the service did not start until I upgraded to 10.5.1 on 01/16/12.  I have ran a repair on .NET 2.0, but I have not been able to reboot the server since the 10.5.1 upgrade.

                          I have 2358 monitors, 403 devices.

                          Running on Windows 2003 Server Standard.  4GB ram, Quad core zeon 3Ghz, 500GB.  IOPS=310 at 95%; 652 at 99%,  Peak/Min CPU = 44% / 13%, Peak/Min Memory = 1.6Gb / 1.1Gb.

                          ipMonitor is installed along with a internal website which only gets 100-200 hits per day and an Antivirus Management server hosting 600 clients.

                          12 smart groups and several groups.  My groups are broken up by city, facility, area, floor, room.  I start with 20 groups and branch out from there.

                            • Re: .NET Runtime 2.0 Error
                              chaldz

                              today I noticed none of my graphs had any data and the graphs had stopped on 02/23/12 the same time the webpage went unavailable and the .NET error was recorded.  I had to reboot the server and the graphs are now working.  Restarting the services would not fix this issue.