
Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-15-2010 09:30 PM
Since updating to the latest beta, I've been seeing this error in my C:\Program Files\Lansweeper\Service\Errorlog.txt file. I have about 8 pc's with this error.
4/15/2010 3:03:37 PM: MAID162043 BATTERY Invalid parameter
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementPath.SetWbemPath(IWbemPath wbemPath, String path)
at System.Management.ManagementPath.CreateWbemPath(String path)
at System.Management.ManagementPath..ctor(String path)
at System.Management.ManagementObject.GetManagementObject(IWbemClassObjectFreeThreaded wbemObject, ManagementScope scope)
at System.Management.ManagementBaseObject.GetBaseObject(IWbemClassObjectFreeThreaded wbemObject, ManagementScope scope)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.get_Current()
at LansweeperService.MdlWmi.GetWMI(String Querystr, String Table, LS_Computer& mycomputer, String section, SqlConnection& sqlcon)
4/15/2010 3:03:37 PM: MAID162043 BATTERY Invalid parameter
at System.Management.ManagementException.ThrowWithExtendedInfo(ManagementStatus errorCode)
at System.Management.ManagementPath.SetWbemPath(IWbemPath wbemPath, String path)
at System.Management.ManagementPath.CreateWbemPath(String path)
at System.Management.ManagementPath..ctor(String path)
at System.Management.ManagementObject.GetManagementObject(IWbemClassObjectFreeThreaded wbemObject, ManagementScope scope)
at System.Management.ManagementBaseObject.GetBaseObject(IWbemClassObjectFreeThreaded wbemObject, ManagementScope scope)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.get_Current()
at LansweeperService.MdlWmi.GetWMI(String Querystr, String Table, LS_Computer& mycomputer, String section, SqlConnection& sqlcon)
Labels:
- Labels:
-
Archive
3 REPLIES 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-16-2010 07:37 PM
Maybe this WMI class isn't implemented on these machines, in this case you can safely ignore this error.

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-16-2010 04:47 PM
As it turns out, all the PC's showing up are Gateways. I looked on my 3.5 version that I still have running and yes, they do show up in that log file too. We just added those users to our domain a few weeks ago, so I guess they jumped out at me when I looked at the 4.0 log file.
SystemProduct
Name: M250
Vendor: Gateway
IdentifyingNumber: 0036392248
UUID: 722B7C88-79B5-5491-3845-00E0B885B8B9
Version: 1008469
Date: 3/4/2010 12:29:22 AM
All have:
OS: Microsoft Windows XP Professional
SP: Service Pack 3
SystemProduct
Name: M250
Vendor: Gateway
IdentifyingNumber: 0036392248
UUID: 722B7C88-79B5-5491-3845-00E0B885B8B9
Version: 1008469
Date: 3/4/2010 12:29:22 AM
All have:
OS: Microsoft Windows XP Professional
SP: Service Pack 3

Options
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎04-15-2010 09:36 PM
Did you have the same error in 3.5?
Do these computers have the same OS/SP?
Do these computers have the same OS/SP?
