Client problems -> use the connection tester first

[Hemoco]

Download from here : http://www.lansweeper.com/kb/2/The-RPC-server-is-unavailable.html

Use this tool from the same machine where the service is installed.
Make sure it runs using the same account as the service.

Test the machines that are giving problems in three different ways:
- On hostname (netbios name)
- On FQDN (long name : computer.domain.local)
- On IPaddress

[neosys]

Great, I am going to let it run for a while and keep on configuring the server.
But I am already considering getting the premium version !

[neosys]

Computer rebooted this morning and is all fine now.

I will use the beta service 3.5.1 now.
But what is the lsupgrade.exe used for ?
I have not seen it mentioned in the Important-readme.pdf

Thansks !

[Hemoco]

neosys wrote:

But what is the lsupgrade.exe used for ?

It's used to run the sql scripts.

[Hemoco]

The version 3.5.1 beta, this version tries on both fqdn,ip and hostname : http://www.lansweeper.com/forum/yaf_postst1514_Lansweeper-Service-351-update-1-beta.aspx

I would also suggest to repair WMI on this machine : http://www.lansweeper.com/repairwmi.zip

[neosys]

Hello I have only one PC still in red on my inventory.

LS Connect with FQDN is OK:

Remote WMI test
-----------------------------------------------
Found: Microsoft Windows XP Professional Service Pack 3
\root\cimv2 Remote WMI access test OK

Remote Registry test using WMI
-----------------------------------------------
Found: Microsoft Windows XP Service Pack 3
\root\default Remote WMI access test OK

But using IP is not... I checked the Windows Firewall locally and the DNS entries...
Remote WMI test
-----------------------------------------------
\root\cimv2 Remote WMI access test FAILED
Provider load failure

Remote Registry test using WMI
-----------------------------------------------
Found: Microsoft Windows XP Service Pack 3
\root\default Remote WMI access test OK

But still When I launch the agent locally on the machine I get errors in the console.

Any Idea on how I could solve this problem ?

They all are like this:
Memory Provider load failure 2009-04-28 13:22:47
Videocontroller Provider load failure 2009-04-28 13:18:47
Usbcontroller Provider load failure 2009-04-28 13:16:47
Tape Provider load failure 2009-04-28 13:14:47
Sound Provider load failure 2009-04-28 13:12:47
Serialport Provider load failure 2009-04-28 13:10:47
Scsi 2009-04-28 13:08:47
Quickfix Provider load failure 2009-04-28 13:06:47
Processor Provider load failure 2009-04-28 13:04:47
Potsmodem 2009-04-28 13:02:47
Portconnector Provider load failure 2009-04-28 13:02:47
Portablebattery 2009-04-28 13:00:47
Pointing Provider load failure 2009-04-28 13:00:47
Pcmcia 2009-04-28 12:58:47
Parallelport Provider load failure 2009-04-28 12:58:47
Pagefile Provider load failure 2009-04-28 12:56:47
Osrecovery 2009-04-28 12:54:47
Onboarddevice Provider load failure 2009-04-28 12:54:47
Networkclient 2009-04-28 12:52:47
Keyboard Provider load failure 2009-04-28 12:52:47
Infrared Provider load failure 2009-04-28 12:50:47
Idecontroller 2009-04-28 12:48:47
Environment Provider load failure 2009-04-28 12:46:47
Displaycontrconf Provider load failure 2009-04-28 12:44:47
Displayconf 2009-04-28 12:42:47
Diskpartition Provider load failure 2009-04-28 12:42:47
Codec 2009-04-28 12:40:47
Desktopmon Provider load failure 2009-04-28 12:40:47
Desktop Provider load failure 2009-04-28 12:38:47
Dcomapp 2009-04-28 12:36:47
Compsysprod Provider load failure 2009-04-28 12:36:47
Componentcat 2009-04-28 12:34:47
Comapplication Provider load failure 2009-04-28 12:34:47
Cdrom Provider load failure 2009-04-28 12:32:47
Bus Provider load failure 2009-04-28 12:30:47
Bootconfig Provider load failure 2009-04-28 12:28:47
Bios 2009-04-28 12:26:47
Battery 2009-04-28 12:24:47
Baseboard 2009-04-28 12:22:47
Process 2009-04-28 12:20:47
Floppy 2009-04-28 12:18:47
Usersingroup Provider load failure 2009-04-28 12:18:47
Groups 2009-04-28 12:16:47
Users 2009-04-28 12:14:47
Proxy Provider load failure 2009-04-28 12:14:47
Compsystem 2009-04-28 12:12:47
Os Provider load failure 2009-04-28 12:12:47
Services 2009-04-28 12:10:47
Harddisk Provider load failure 2009-04-28 12:10:47
Network 2009-04-28 12:08:47
Printers Provider load failure 2009-04-28 12:08:47
Shares Provider load failure 2009-04-28 12:06:47
Autorun Provider load failure 2009-04-28 12:04:47

[neosys]

Did the knowledge base check,
WMIrepair
WMIDiag
I was missing one file C:\WINDOWS\System32\WBEM\wmiprvse.exe
=> Recopy from a working system the missing WMI system files to 'C:\WINDOWS\SYSTEM32\WBEM\'
And restarted the Windows Management Instrumentation Service.

But still the PC is RED in LS ;-(

[Hemoco]

neosys wrote:
Did the knowledge base check,
But still the PC is RED in LS ;-(

What does the connection tester show on fqdn,computername and ipaddress?

[neosys]

One of our PC can connect to the server but does not finish/complete the inventory and stays RED in the console.

Here is the log trace:

2009-04-24 08:55:41: PC107
at System.Runtime.InteropServices.Marshal.ThrowExceptionForHRInternal(Int32 errorCode, IntPtr errorInfo)
at System.Management.ManagementObjectCollection.ManagementObjectEnumerator.MoveNext()
at LansweeperService.MdlWmi.GetWMI(String Querystr, String Table, clsComputer& mycomputer, String section, SqlConnection& sqlcon)

The console error screen shows various hardware "Provider load failure"
and
Registry The system cannot find the file specified. (Exception from HRESULT: 0x80070002)

Any ideas ?

[Hemoco]

WMI doesn't use a specific port so this can be tricky