Welcome to OCS Inventory NG community support, where you can ask questions and receive answers from other members of the community.

Please ask questions only in English or French.

Release 2.6 available

The official documentation can be found on http://wiki.ocsinventory-ng.org. Read it before asking your question.

[RESOLU] AGENT 2.1.1.1 : Pas d'affichage de l'inventaire local

Bonjour à tous,

Je rencontre un bug sur la nouvelle version de l'agent OCS. Lorsque je lance OcsSystray.exe et que je vais dans "Afficher les informations d'inventaire", rien n'apparait.

Sur mon serveur, les informations sont bien remontés. J'ai l'impression qu'il n'arrive pas à lire le fichier OCSInventory.xml généré par OCS-transform.xsl.

Merci pour votre aide.
in OCS Inventory NG agent for Windows by (300 points)
edited by

7 Answers

0 votes
Bonjour

Des erreurs dans le fichier ocsinventory.log?
by (70.3k points)
Quel version de windows ? Quelque chose dans le journal des évènements ou autre ?
0 votes
Bonjour, voici mon fichier de log. Mais pas d'erreurs apparentes.

==============================================================================
Starting OCS Inventory NG Agent on Monday, January 12, 2015 15:58:46.
AGENT => Running OCS Inventory NG Agent Version 2.1.1.1
AGENT => Using OCS Inventory NG FrameWork Version 2.1.1.1
AGENT => Loading plug-in(s)
AGENT => Using network connection with Communication Server
AGENT => Using Communication Provider <OCS Inventory NG cURL Communication Provider> Version <2.1.1.1>
AGENT => Sending Prolog
AGENT => Prolog successfully sent
SUPPORT => No support detected, Registration key : N/A
AGENT => Inventory required
AGENT => Launching hardware and software checks
AGENT => Communication Server ask for IpDiscover
AGENT => Sending Inventory
INVENTORY => Inventory changed since last run
AGENT => Inventory successfully sent
AGENT =>  Communication Server ask for Package Download
AGENT => Unloading communication provider
AGENT => Unloading plug-in(s)
AGENT => Execution duration: 00:00:45.
by (300 points)
0 votes
Bonjour,

Comme le suggère Kapouik, des erreurs dans le gestionnaire d'événements Windows?

Sinon, change le niveau de debug dans le fichier ocsinventory.ini pour le passer à 2.

Reposte le contenu du fichier ocsinventory.log après avoir fait la modif et relancer un inventaire.
by (70.3k points)
0 votes
Merci déjà pour vos réponse.

Dans l'observateur d'évènement, je n'ai pas d'erreur que des informations dont voici quelques bribes :

- Service start parameters FREQ: 24, OLD_FREQ: 24, TTO_WAIT: 2040.

- Unable to remove Download lock file <C:\ProgramData\OCS Inventory NG\Agent\download\lock>.

- "OCS Inventory Service" successfully started.

- OCS Inventory NG Agent executed successfully. New service parameters: FREQ: 24, OLD_FREQ: 24, TTO_WAIT: 86400.

- User manually ask displaying local inventory informations.

Je possède pour ma part un Windows 7 64bit mais j'ai des postes en XP, 7 32 bits.

Je vais modifier la valeur du débug et je reviens vers vous.
by (300 points)
0 votes
Voici le résultat du log : (j'ai modifié certaines infos par des X)

==============================================================================
Starting OCS Inventory NG Agent on Tuesday, January 13, 2015 10:03:47.
AGENT => Running OCS Inventory NG Agent Version 2.1.1.1
AGENT => Using OCS Inventory NG FrameWork Version 2.1.1.1
AGENT => Loading plug-in(s)
    DLL PLUGIN => Searching for Plug-in DLL(s) in folder <C:\Program Files (x86)\OCS Inventory Agent\plugins>
    DLL PLUGIN => 0 DLL Plug-in(s) succesfully loaded on 0 DLL(s) found
AGENT => Using network connection with Communication Server
    COM PROVIDER => Loading Communication Provider <C:\Program Files (x86)\OCS Inventory Agent\ComHTTP.dll>
AGENT => Using Communication Provider <OCS Inventory NG cURL Communication Provider> Version <2.1.1.1>
AGENT => Sending Prolog
    DID_CHECK => Read DeviceID <XX> and MACs <XX> in file <ocsinventory.dat>
    COM SERVER => Initializing cURL library for sendRequest
    COM SERVER => Using cURL without server authentication
    COM SERVER => Disabling cURL proxy support
    COM SERVER => Enabling cURL SSL server validation support using CA Bundle <C:\ProgramData\OCS Inventory NG\Agent\cacert.pem>
    COM SERVER => Sending HTTP Post request to URL <http://192.168.X.XX/ocsinventory>
    COM SERVER => HTTP Post response received <HTTP Status Code #200>
    COM SERVER => Cleaning cURL library
================= TRACE START ===============
<?xml version='1.0' encoding='UTF-8'?>
<REPLY>
  <OPTION>
    <NAME>IPDISCOVER</NAME>
    <PARAM IPDISC_LAT="100">192.168.56.0</PARAM>
  </OPTION>
  <OPTION>
    <NAME>DOWNLOAD</NAME>
    <PARAM FRAG_LATENCY="10" PERIOD_LATENCY="1" ON="0" TYPE="CONF" CYCLE_LATENCY="60" TIMEOUT="30" PERIOD_LENGTH="10" EXECUTION_TIMEOUT="120" />
  </OPTION>
  <RESPONSE>SEND</RESPONSE>
  <PROLOG_FREQ>24</PROLOG_FREQ>
</REPLY>

================= TRACE STOP ===============
AGENT => Prolog successfully sent
SUPPORT => No support detected, Registration key : N/A
    AGENT => Prolog Frequency set to 24 hour(s)
AGENT => Inventory required
AGENT => Launching hardware and software checks
    INVENTORY => Loading Download history
    INVENTORY => Logged on user ID is <X>
    INVENTORY => Operating System is <Microsoft Windows 7 Professionnel 6.1.7601 Service Pack 1>, description <XX>
    INVENTORY => Operating System uses 64 bits memory address width
    INVENTORY => Computer domain or workgroup is <XX>
    INVENTORY => User domain is <XX>
    INVENTORY => System Manufacturer <Dell Inc.>, System Model <Latitude XX non-vPro>, System S/N <XX>, Bios Manufacturer <Dell Inc.>, Bios Date <09/24/2014>, Bios Version <A15>
    INVENTORY => 1 processor(s) Intel(R) Core(TM) i5-3210M CPU @ 2.50GHz [2 core(s) x86_64] at 2501 MHz
    INVENTORY => OS Memory 4001 MB, OS Swap size 8000 MB
    INVENTORY => 2 memory slot(s) found
    INVENTORY => 4 input device(s) found
    INVENTORY => 26 system port(s) found
    INVENTORY => 5 system slot(s) found
    INVENTORY => 4 system controler(s) found
    INVENTORY => 2 storage peripheral(s) found
    INVENTORY => 2 sound device(s) found
    WARNING *** INVENTORY => Failed to retrieve modems
    INVENTORY => 3 network adapter(s) found
    INVENTORY => 7 system printer(s) found
    INVENTORY => 1 video adapter(s) found
    INVENTORY => 2 system monitor(s) found
    INVENTORY => Default IPv4 address is <192.168.XX.XXX>
    INVENTORY => Registered company <>, registered owner <XX>, Product ID <00371-OE...>
    INVENTORY => Product key <32KD2-K9...>
    INVENTORY => 424 software found
    INVENTORY => Computer/VM UUID is <XXXXXXX>
    INVENTORY => Computer seems to be physical host
    INVENTORY => System Memory set to 4096 (instead of 4001)
    INVENTORY => Reading last inventory state
AGENT => Communication Server ask for IpDiscover
    IPDISCOVER => Scanning to detect IPv4 enabled hosts for network <192.168.56.0> with <100> ms between each request
    IPDISCOVER => Computer found @IPv4:192.168.xx.xx @MAC: -  NAME:XX-XX-DH.XX.XX
    IPDISCOVER => Waited 3060 ms for the threads to die
    IPDISCOVER => NETWORK scan finished, 1 hosts found, 255 scanned
    EXECUTABLE PLUGIN => Searching for VBS script(s) in folder <C:\Program Files (x86)\OCS Inventory Agent\plugins>
    EXECUTABLE PLUGIN => Searching for executable(s) in folder <C:\Program Files (x86)\OCS Inventory Agent\plugins>
AGENT => Sending Inventory
    INVENTORY => Checking last inventory state
    INVENTORY => Logical drives inventory state changed
INVENTORY => Inventory changed since last run
    INVENTORY => Generating XML document with Device properties
    INVENTORY => XML Update BIOS
    INVENTORY => XML Update 1 CPU(s)
    INVENTORY => XML Update 2 Memory Slot(s)
    INVENTORY => XML Update 4 Input Device(s)
    INVENTORY => XML Update 26 System Port(s)
    INVENTORY => XML Update 4 System Controler(s)
    INVENTORY => XML Update 5 System Slot(s)
    INVENTORY => XML Update 2 Sound Device(s)
    INVENTORY => XML Update 2 Storage Peripheral(s)
    INVENTORY => XML Update 3 Logical Drive(s)
    INVENTORY => XML Update 0 Modem(s)
    INVENTORY => XML Update 3 Network Adapter(s)
    INVENTORY => XML Update 1 Video Adapter(s)
    INVENTORY => XML Update 2 Monitor(s)
    INVENTORY => XML Update 7 Printer(s)
    INVENTORY => XML Update 425 Software
    INVENTORY => XML Update 0 Registry Value(s)
    INVENTORY => XML Update Administrative Information(s)
    INVENTORY => XML Update common Device properties
    COM SERVER => Initializing cURL library for sendRequest
    COM SERVER => Using cURL without server authentication
    COM SERVER => Disabling cURL proxy support
    COM SERVER => Enabling cURL SSL server validation support using CA Bundle <C:\ProgramData\OCS Inventory NG\Agent\cacert.pem>
    COM SERVER => Sending HTTP Post request to URL <http://192.168.X.X/ocsinventory>
    COM SERVER => HTTP Post response received <HTTP Status Code #200>
    COM SERVER => Cleaning cURL library
================= TRACE START ===============
<?xml version='1.0' encoding='UTF-8'?>
<REPLY>
  <RESPONSE>NO_ACCOUNT_UPDATE</RESPONSE>
</REPLY>

================= TRACE STOP ===============
AGENT => Inventory successfully sent
    INVENTORY => Writing new inventory state
AGENT =>  Communication Server ask for Package Download
    DOWNLOAD => Package history file successfully cleaned for duplicate IDs
    DOWNLOAD => Download disabled by server
AGENT => Unloading communication provider
AGENT => Unloading plug-in(s)
AGENT => Execution duration: 00:00:45.
by (300 points)
0 votes

Pour moi, le problème vient du package d'installation OCS Inventory Client. J'ai tenté ceci :

  1. Désinstallation de l'agent 2.1.1.1.
  2. Installation de l'agent 2.0.5

Et là, j'ai bien mon inventaire local.
Comment faire pour en informer les développeur? Est-ce possible?

by (300 points)
J'ai trouvé ce lien :

https://bugs.launchpad.net/ocsinventory-windows-agent/+bug/1329003

Le bug a été constaté. J'ai installé la version 2.1.1.2 de l'agent sur mon poste. Et là, cela fonctionne, j'ai bien l'inventaire qui s'affiche.

La version n'est pas fonctionnelle apparemment avec Win XP, mais ce n'est pas un problème pour moi car on migre nos poste sur du 7 voire du 8.

Bonne soirée à vous.
0 votes
Je rencontre moi aussi ce soucis, j'ai laissé l'agent 2.1.1.1 de côté pour le moment.
by (320 points)
 
Powered by Question2Answer
...