dayley

Comments

  • Answer to my previous question: "Also, I meant to answer your question about the job engine needing the smaller scripts - for now, this is still the case, but it may change in the next implementation of it. We'll know more once the beta & QA testing progress a little further. Regards,KateSolarWinds Support Team"
  • I thought the new Windows event log monitor was RPC-based, not WMI-based: We have had some serious CPU usage problems on some of our older servers when we use WMI-based Orion monitors.
  • Please confirm that as of NPM 9.5.1 / APM 3.1 Orion is no longer storing multiple copies of the scripts in the scheduling database. What is the new maximum size of the JobEngine35.sdf file? We were no longer pulling event logs with a script anyway. We have some other scripts that are affected by this though. We need to run…
  • Has this problem been fixed in the NPM 9.5.1/APM 3.1 releases?
  • The "short" reference script that SolarWinds provided is: Set shl = CreateObject("WScript.Shell") c = "cscript /nologo c:\wineventlog.vbs" Set a = WScript.Arguments For n = 0 to a.Length - 1 c = c + " " + a(n) Next wscript.echo "Exec " & c Set e = shl.Exec(c) Set o = e.StdOut While Not o.AtEndOfStream wscript.echo…
  • As an alternative to clustering the main NPM / APM server (list item #20), all the pollers could be raised to the same level so that they are identical but run independently. i.e. They all run their own complete set of the same services (e.g. alerting engine, job scheduler, etc.), but all connect to and update the same…
  • Update: The SolarWinds developers kindly provided a method for increasing the maximum size of the SQL CE file: * Stop all Orion services on the main poller. * Go to C:Program Files\Common Files\SolarWinds\JobEngine\SWJobSchedulerSvc.exe.config . Make a backup copy of this file - just in case. After that's done, right-click…
  • I'll add three more to the list: 18) In the Advanced Alert Manager, it would be extremely helpful to be able to trigger, reset, or suppress alerts based on the Component Message - in the same way that Statistic Data can be used. 19) One of our major concerns with agentless monitoring is how to deal with those times when…
  • I'll list the top 8 in priority order: 1, 11, 2, 8, 9, 14, 10, 16 There is a case open for item #1: Case #147787
  • We have 6 APM additional pollers and 2 additional web servers. Our case number for this issue is #111026. Polling Engine Mode is set to 'Poller-Bound'.
  • I'd like that, but, unfortunately, our conversation will need to wait until things settle down a little... They're somewhat hectic right now. In the meantime, here is another point (that I'm glad to hear you're working on): 17) No "node group" APM template inheritance. i.e. A node collection abstraction layer is needed to…
  • We were shooting for an easy way to use a domain service account that wasn't a local administrator to monitor servers. We decided to use a domain account that was a local admin anyway, rather than modify the WMI settings on all the monitored servers. Our domain admin's didn't like the idea of a service account having local…
  • Here is another: 16) The inability to connect to a different name space with a WMI monitor. Currently, this monitor is limited to only allow connections to the "root\cimv2" namespace.
  • I see. Can the job scheduling be extended to the pollers (i.e. poller-bound)? That would at least spread out the load a little. Thanks for the assurance that your team is looking into our problem. I'm glad to hear there's a fall-back option (increasing the maximum db size) if nothing else works. We're currently…
  • Workaround example (not optimized): Option Explicit const INVALID_PARAMS = 1, SUCCESS = 0, FAIL = 1 Dim oColEvents, oSvc, lst_args Dim strComputer, strEventArea , strEventID,strEventType, intEventID, strEventSource, strLoggedByUser, strTimeSpanMins, strFindExclusionText, strFindMatchText, strSQL, strSuffix Dim arg_count,…
  • Correction to my previous post item #1: "Truncation of returned component messages to 150 characters" should be "Truncation of returned component messages to 250 characters" While I'm here, I'll add a three more: 13) The ability to control what is in the mouse-over pop-up box. For applications, this could save a LOT of…
  • I contacted pguenther directly on this and received the reply: "Unfortunately I did not ever get this to work. We have shelved the APM module for now and are focusing on redesigning the rest of the system with EOC." It seems to me that unless this issue has already been addressed in recent versions of APM, our ability to…
  • Because of its installation prereq.'s (e.g. .NET upgrades). Apparently, there is an older version that doesn't use .NET that we might be able to use.
  • I think the problem is with 'CreateObject("WbemScripting.SWbemDateTime")'. Windows 2000 doesn't support this, so the out-of-the-box Orion monitor fails. I'm surprised that SolarWinds hasn't fixed this yet... Resources for a potential work-around: http://www.freevbcode.com/ShowCode.asp?ID=6774…
  • We fixed this by adapting the procedure found at: http://seer.entsupport.symantec.com/docs/280500.htm for the SNMP Trap service. On one server, it was necessary to copy the snmptrap.exe file from another server to get it to work. If there are permission problems, putting the executable in another location than System32 and…
  • This is the reply from SolarWinds: Thank you for contacting SolarWinds, Inc. Customer Support. Unfortunately ErrorMessage field in tables serving APM is set to nvarchar(250) which means you can store 250 unicode characters (249 plus termination character) 16 ErrorMessage nvarchar 250 I have to say I'm disappointed. A…
  • Here is a partial list of our APM/NPM frustrations / feature requests: 1) Truncation of returned component messages to 150 characters. Orion has the ability in Windows script monitors to return message text to Orion. We pass it along to our trouble ticketing system, but it arrives incomplete because Orion truncates the…
  • So what was the final result of this query? We're experiencing a similar situation.