Export to Text causes a runtime 450 Error

I am using SolarWinds Engineers Toolset version 9.2 on a server loaded with Windows Server 2003 SP2.  The server also has SQL 2005 installed.

 When I try Export to Text File I get the following Error:

Runtime Error 450: Wrong number of arguments or invalid property assignment

 This error occurs on Network Perf Monitor, Real Time Interface Monitor, Syslog Server, Ping Sweep, Trace Route, IP Address Management, SNMP Sweep, Subnet List, MIB Walk, and MIB Viewer. 

 Any idea how to fix this error?

I'm one of the Systems Engineers from General Dynamics who works with this platform.  We have two platforms in which the Toolset is loaded.  The one that is experiencing this error is also running Cirrus.  I mention this because I've occasionally seen this error in Cirrus.

Our other platform running toolset 9.2 does not experience this error, but does not have Cirrus or SQL installed on it.

Any ideas would be appreciated.

Greg,

Thanks for the quick reply.

We're running version 9.2 of the Toolset and 3.5 of Cirrus.  Unfortunately, these platforms are baselined, and are fielded throughout the Army.  We don't have the ability to upgrade.

Is there any fix that can be performed to get the two apps to play nicer together?

Thanks,

Sean

Greg,

I'm not in the software development area, so I don't have a copy of 9.2, but I'll try and get those folks to do a re-install.

I must admit, however, that I'm not very optimistic that this will work, as we have two versions of this platform that were developed separately, and both are experiencing the same error.

Thanks,

Sean

 Hi Sean,

 We have worked together in the past.  I last saw you in Germany back in 2006.  I work for CECOM.  I have no idea how to fix this error.  I suspect it may be related to SQL in some fashion.  I forwarded this error to Butch and Raul at SEC.  Butch told me he sent it forward to Taunton for research.

 Jeff

Greg/Jeff  -

Per Greg's suggestion, we re-installed the Toolset on a freshly cloned WAN Mgr.  The export problem went away.  We also ran a quick test on Cirrus and encountered no problems.

I created a low-level PTR (the user may not export but may still 'Save') and suggested that the Toolset be installed after Cirrus during the next build iteration.

Thanks...