The software/hardware inventory works fine on devices which have Win XP SP2 (English language) installed.
But we have other group of machines with Win XP SP2 (local language) installed. In these devices all CCM functionalities works fine but HW/SW inventory fails and give an error related to rimwbem and don't collect any hardware information.
Looking at this machines connect.log file I found this lines:
... NVD000010I [Initialize ] 00:00:00 [RIMDIFF / 00000bec] SYSTEM --- Objects are to be compared: [WBEMPREV] [WBEMCURR] NVD009409W [Pooltab_replace] 00:00:00 [RIMDIFF / 00000bec] SYSTEM --? Can't open file [C:\PROGRA~1\Novadigm\Lib\SYSTEM\RADIA\AUDIT\ZSERVICE\DISCOV~1\WBEMCURR.EDM] because (No such file or directory) (v109) NVD000010E [Edm_sortObject ] 00:00:00 [RIMDIFF / 00000bec] SYSTEM --! Error: could not read object [WBEMCURR] into memory NVD000010E [SortObjects ] 00:00:00 [RIMDIFF / 00000bec] SYSTEM --! Error sorting [WBEMCURR] NVD000010A [Edm_Exit ] 00:00:00 [RIMDIFF / 00000bec] SYSTEM --- RIMDIFF Exit code  NVD006813I [EDMFREE ] 00:00:00 [RADPNLWR / 000008e4] SYSTEM --- Object name will be [FILE ] ...
how do i make sure that i'm testing WBEMTEST with SYSTEM?
I mean, if i log to a machine with admin account, does that mean this wbemtest will run as SYSTEM? Or there is something else other than testing with certain user (admin) to make sure this test will run as SYSTEM (the same way RIM scan will try to do)?
If wbemtest gets the data then I would assume that the system id should. Is your issue that wbemcur fails to sort? If that's it try removing the Service and running from scratch. You may have a corrupt object.
Here is the fresh RIM_REPORTING log file, i don't see such info of WBEMCURR created or not, just it can't be opened.
I have manualy deleted the entire RIM_REPORTING lib sub-dir several times (under normal circumstances this is equivalent to FULL scan), but no change. Setting RIM_REPORTING from DIFF to FULL now would trigger unwanted behaviour on other clients, i'm not sure i want to do that.
Unless setting it to FULL is NOT the same as DELETING the LIB tree manualy?! Is there a reason why i shoud go and test it with full instead od deleting the LIB tree?
WBEM test works fine, there is enough disk space...scratch scratch.
WBEMCURR simply isn't created and nothing points to why or the fact that it isn't creted in the first place (when looking at the connect log). The next task is then to compare WBEMCURR and WBEMPREV and then it fails to load WBEMCURR into memory because...it isn't there...