Windows 7 agent 2.0.0.8 is not sending inventory towards server

Bug #695843 reported by Marcin K.
26
This bug affects 5 people
Affects Status Importance Assigned to Milestone
OCS Inventory: Windows Agent
Fix Released
High
Didier Liroulet

Bug Description

I've noticed problem on W7 64bit agent.
It cannot send inventory towards server.

Debug log it ends like that:

INVENTORY => Inventory changed since last run
 INVENTORY => Generating XML document with Device properties
 INVENTORY => XML Update 5 Logical Drive(s)
 INVENTORY => XML Update common Device properties
 INVENTORY => XML Update BIOS
 INVENTORY => XML Update 2 Input Device(s)
 INVENTORY => XML Update 31 System Port(s)
 INVENTORY => XML Update 17 System Controler(s)
 INVENTORY => XML Update 4 System Slot(s)
 INVENTORY => XML Update 1 Sound Device(s)
 INVENTORY => XML Update 2 Storage Peripheral(s)
 INVENTORY => XML Update 2 Logical Drive(s)
 INVENTORY => XML Update 1 Modem(s)
 INVENTORY => XML Update 5 Network Adapter(s)
 INVENTORY => XML Update 1 Video Adapter(s)
 INVENTORY => XML Update 1 Monitor(s)
 INVENTORY => XML Update 5 Printer(s)
 INVENTORY => XML Update 289 Software
 INVENTORY => XML Update 0 Registry Value(s)
 INVENTORY => XML Update Administrative Information(s)

doesn't matter how many times I will run agent it always says INVENTORY => Inventory changed since last run
This is not cUrl problem as it can successfully connect

 COM SERVER => Initializing cURL library for sendRequest
 COM SERVER => Using cURL with server authentication
 COM SERVER => Disabling cURL proxy support
 COM SERVER => Enabling cURL SSL server validation support
 COM SERVER => Sending HTTP Post request to URL <http://mgt.ocs/ocsinventory>
 COM SERVER => HTTP Post response received <HTTP Status Code #200>
 COM SERVER => Cleaning cURL library

I've compared it with working Win XP log:

INVENTORY => No change since last inventory
 INVENTORY => Generating XML document with Device properties
 INVENTORY => XML Update 15 Logical Drive(s)
 INVENTORY => XML Update common Device properties
 INVENTORY => XML Update BIOS
 INVENTORY => XML Update 4 Input Device(s)
 INVENTORY => XML Update 4 System Port(s)
 INVENTORY => XML Update 8 System Controler(s)
 INVENTORY => XML Update 7 System Slot(s)
 INVENTORY => XML Update 0 Sound Device(s)
 INVENTORY => XML Update 5 Storage Peripheral(s)
 INVENTORY => XML Update 5 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 1 Monitor(s)
 INVENTORY => XML Update 0 Printer(s)
 INVENTORY => XML Update 121 Software
 INVENTORY => XML Update 0 Registry Value(s)
 INVENTORY => XML Update Administrative Information(s)
 COM SERVER => Initializing cURL library for sendRequest
 COM SERVER => Using cURL with server authentication
 COM SERVER => Disabling cURL proxy support
 COM SERVER => Enabling cURL SSL server validation support
 COM SERVER => Sending HTTP Post request to URL <http://mgt.ocs/ocsinventory>
 COM SERVER => HTTP Post response received <HTTP Status Code #200>
 COM SERVER => Cleaning cURL library
AGENT => Inventory successfully sent
 INVENTORY => Writing new inventory state
AGENT => Unloading communication provider
AGENT => Unloading plug-in(s)
AGENT => Execution duration: 00:00:04.

and in W7 64bit agent no data is send towards OCS server. I'm able to reproduce this on two different Windows 7 Ultimate 64bit compters.

Cheers,
Marcin

Marcin K. (kowalma)
description: updated
description: updated
Revision history for this message
Wojciech Wejhan (wojtek-wsnhid) wrote :

Check Application Event Log (Computer -> Manage) - i have the same problem and in my case msvcr90.dll was crashing app.

Revision history for this message
Marcin K. (kowalma) wrote :

Yeap - you're right MSVCR90.dll is crashing app...

Revision history for this message
Icem@n (ry-news) wrote :

I've the same error, and on XP too ..

but I use without install and it's possible the error come from the version of DLL, because in my logEvent the version of DLL MSVCR90.dll is not the same of directory ..

I'll checking this solution monday ;)
http://blog.kalmbach-software.de/2008/05/03/howto-deploy-vc2008-apps-without-installing-vcredist_x86exe/

Changed in ocsinventory-windows-agent:
importance: Undecided → High
assignee: nobody → Didier Liroulet (dliroulet)
Revision history for this message
GW Service (gw-service) wrote :

Same Error here, Windows 7 Enterprise 64bit german

Errorlog Application Error

Name der fehlerhaften Anwendung: OcsService.exe, Version: 2.0.0.8, Zeitstempel: 0x4d123e00
Name des fehlerhaften Moduls: MSVCR90.dll, Version: 9.0.30729.4926, Zeitstempel: 0x4a1743c1
Ausnahmecode: 0xc0000417
Fehleroffset: 0x00057f2c
ID des fehlerhaften Prozesses: 0x790
Startzeit der fehlerhaften Anwendung: 0x01cbb165a5f0de63
Pfad der fehlerhaften Anwendung: C:\Program Files (x86)\OCS Inventory Agent\OcsService.exe
Pfad des fehlerhaften Moduls: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4926_none_508ed732bcbc0e5a\MSVCR90.dll
Berichtskennung: fea5baa0-1d58-11e0-a05b-005056c00008

But on an other Windows 7 Machine the Agent work well

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Hi,

I think this bug came from strong encoded binary data in XML UTF-8, encoded like "&#x...;".

I wrote an XML cleaner, which these used data.

Could you please check if 2.0.0.10 release really solves the problem ?

You can download it from http://www.liroulet.net/download/OCS-NG-Windows-Agent-2.0.0.10.zip

Thanks a lot

Cheers

Changed in ocsinventory-windows-agent:
status: New → Fix Committed
Revision history for this message
Norman Coker (ncoker) wrote :
Download full text (13.1 KiB)

I have tested the new Version 2.0.0.10. Now it looks like that the manifest files are wrong!

here my exported eventviewer entries:

Protokollname: Application
Quelle: SideBySide
Datum: 19.01.2011 09:17:52
Ereignis-ID: 35
Aufgabenkategorie:Keine
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: NB-HSCHRAM.bbs-gmbh.com
Beschreibung:
Fehler beim Generieren des Aktivierungskontextes für "C:\Program Files\OCS Inventory Agent\download.exe". Fehler in Manifest- oder Richtliniendatei "C:\Program Files\OCS Inventory Agent\Microsoft.VC90.MFC.MANIFEST" in Zeile 4. Die im Manifest gefundene Komponenten-ID stimmt nicht mit der ID der angeforderten Komponente überein. Verweis: Microsoft.VC90.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8". Definition: Microsoft.VC90.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.1". Verwenden Sie das Programm "sxstrace.exe" für eine detaillierte Diagnose.
Ereignis-XML:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="SideBySide" />
    <EventID Qualifiers="49409">35</EventID>
    <Level>2</Level>
    <Task>0</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2011-01-19T08:17:52.000000000Z" />
    <EventRecordID>1006</EventRecordID>
    <Channel>Application</Channel>
    <Computer>NB-HSCHRAM.bbs-gmbh.com</Computer>
    <Security />
  </System>
  <EventData>
    <Data>Microsoft.VC90.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8"</Data>
    <Data>Microsoft.VC90.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.30729.1"</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>C:\Program Files\OCS Inventory Agent\download.exe</Data>
    <Data>C:\Program Files\OCS Inventory Agent\Microsoft.VC90.MFC.MANIFEST</Data>
    <Data>4</Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

Protokollname: Application
Quelle: SideBySide
Datum: 19.01.2011 09:17:52
Ereignis-ID: 35
Aufgabenkategorie:Keine
Ebene: Fehler
Schlüsselwörter:Klassisch
Benutzer: Nicht zutreffend
Computer: NB-HSCHRAM.bbs-gmbh.com
Beschreibung:
Fehler beim Generieren des Aktivierungskontextes für "C:\Program Files\OCS Inventory Agent\OcsSystray.exe". Fehler in Manifest- oder Richtliniendatei "C:\Program Files\OCS Inventory Agent\Microsoft.VC90.MFC.MANIFEST" in Zeile 4. Die im Manifest gefundene Komponenten-ID stimmt nicht mit der ID der angeforderten Komponente überein. Verweis: Microsoft.VC90.MFC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",type="win32",version="9.0.21022.8". Definition: Microsoft.VC90.MFC,processorArchitecture...

Revision history for this message
Icem@n (ry-news) wrote :

J'ai testé la version 2.0.0.10 et plantage :

Nom de l’application défaillante OCSInventory.exe, version : 2.0.0.10, horodatage : 0x4d35d6e5
Nom du module défaillant : MSVCR90.dll, version : 9.0.30729.4974, horodatage : 0x4b7a226f
Code d’exception : 0xc0000417
Décalage d’erreur : 0x00058293
ID du processus défaillant : 0x17c0
Heure de début de l’application défaillante : 0x01cbb7c9c7a3d796
Chemin d’accès de l’application défaillante : \\s319adsp1\script$\Pgm\OCSInventoryAgent2010\OCSInventory.exe
Chemin d’accès du module défaillant: C:\Windows\WinSxS\x86_microsoft.vc90.crt_1fc8b3b9a1e18e3b_9.0.30729.4974_none_50940634bcb759cb\MSVCR90.dll
ID de rapport : 0ede9d2e-23bd-11e0-a413-00219b6b1374

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Hi

I was thinking that fixing bug with strong encoded character in UTF-8 will also fix crash happeing when trying to write XML sent to server on log file. It is not the case :-(

I've unactivated this feature, only used in trace mode (/debug=2).

Could you please check if 2.0.0.11 release solves the problem ?

You can download it from http://www.liroulet.net/download/OCS-NG-Windows-Agent-2.0.0.11.zip

Thanks a lot

Cheers

Revision history for this message
Andreas Brandl (a-brandl) wrote :

Hi Didier,
I downloaded the new version and installed it on a Win7 64bit computer (same which was not working with the old version).
And .... it seems it works fine. Right now I do not see a problem :)

Thank you and thank you to the team :)

Andreas

Revision history for this message
Icem@n (ry-news) wrote :

I've tested the 2.0.0.11 and it's work for me (windows 7) I check on my full park now (no install just run commandline)

Revision history for this message
Icem@n (ry-news) wrote :

Pour la Version 2.0.0.11 installée sur un XP cela ne fonctionne pas :
Les trois erreurs suivante ce suivent à chaque exécution (enfin à chaque non exécution ;))
----
Type de l’événement : Erreur
Source de l’événement : SideBySide
Catégorie de l’événement : Aucun
ID de l’événement : 34
Date : 24/01/2011
Heure : 14:01:36
Description :
L'identité du composant trouvé dans le manifeste ne correspond pas à l'identité du composant demandé
----
Type de l’événement : Erreur
Source de l’événement : SideBySide
Catégorie de l’événement : Aucun
ID de l’événement : 58
Date : 24/01/2011
Heure : 14:01:36
Description :
Erreur de syntaxe dans le fichier manifeste ou le fichier de stratégie "C:\Program Files\OCS Inventory Agent\Microsoft.VC90.MFC.MANIFEST" à la ligne 4.
----
Type de l’événement : Erreur
Source de l’événement : SideBySide
Catégorie de l’événement : Aucun
ID de l’événement : 59
Date : 24/01/2011
Heure : 14:01:36
Description :
Generate Activation Context a échoué pour C:\Program Files\OCS Inventory Agent\OcsSystray.exe. Message d'erreur de référence : Opération réussie.

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Hi Icem@n,

The error you encounter comes from VS 2008 SP1, which already produce manifest referencing VS 2008 RTM CRT and MFC, but update all these components (for more explanation, see Jochen Kalmbach's Blog
http://blog.kalmbach-software.de/2009/05/27/deployment-of-vc2008-apps-without-installing-anything/)

Could you please check if 2.0.0.12 release really solves the problem ?

You can download it from http://www.liroulet.net/download/OCS-NG-Windows-Agent-2.0.0.12.zip

Thanks a lot

Cheers

Revision history for this message
Icem@n (ry-news) wrote :

Hi Didier,

    Now It's work fini, on XP and 7even ;)

Thank you..

Icem@n

Changed in ocsinventory-windows-agent:
status: Fix Committed → Fix Released
Revision history for this message
Jigar (pateljigar-83) wrote :

Hello,

 I am having same issue on Window Vista computers and I am trying to download version 2.0.0.12 but I guess link is broken. Can you please send me the link again.

Thanks.

Revision history for this message
Jigar (pateljigar-83) wrote :

Anyone their to help me please.

 Thanks.

Revision history for this message
siucdude (siucdude) wrote :
Revision history for this message
Jigar (pateljigar-83) wrote :

Thanks for reply but I used latest one but still I am facing the problem.

Revision history for this message
Didier Liroulet (dliroulet) wrote :

Hi Jigar

Are you having a side by side error with 2.0.0.20 ?

Could you please paste here Windows event log error ?

Cheers

Revision history for this message
Jigar (pateljigar-83) wrote :

Hey Didier,

  We have internal network issue so not able to post the event log error because without connecting the Ocs server I will get the only server connection error and that is not the error that you are looking for. So I will post it as soon as we are up. thanks for your help.

 Jigar.

Revision history for this message
Jigar (pateljigar-83) wrote :
Download full text (5.0 KiB)

Hi Didier,

 Sorry for late reply, here I am posting all the error that I can find on my computer. let me know if you need any more information.

 Thanks,
 Jigar

==============================================================================
Starting OCS Inventory NG Agent on Monday, May 23, 2011 21:42:51.
AGENT => Running OCS Inventory NG Agent Version 2.0.0.20
AGENT => Using OCS Inventory NG FrameWork Version 2.0.0.20
AGENT => Loading plug-in(s)
 PLUGIN => Searching for Plug-in DLL(s) in folder <C:\Program Files\OCS Inventory Agent\plugins>
 PLUGIN => 0 Plug-in(s) succesfully loaded
AGENT => Using network connection with Communication Server
 COM PROVIDER => Loading Communication Provider <C:\Program Files\OCS Inventory Agent\ComHTTP.dll>
==============================================================================
Starting OCS Inventory NG Agent on Monday, May 23, 2011 21:44:02.
AGENT => Running OCS Inventory NG Agent Version 2.0.0.20
AGENT => Using OCS Inventory NG FrameWork Version 2.0.0.20
AGENT => Loading plug-in(s)
 PLUGIN => Searching for Plug-in DLL(s) in folder <C:\Program Files\OCS Inventory Agent\plugins>
 PLUGIN => 0 Plug-in(s) succesfully loaded
AGENT => Using network connection with Communication Server
 COM PROVIDER => Loading Communication Provider <C:\Program Files\OCS Inventory Agent\ComHTTP.dll>
==============================================================================
Starting OCS Inventory NG Agent on Monday, May 23, 2011 21:46:25.
AGENT => Running OCS Inventory NG Agent Version 2.0.0.20
AGENT => Using OCS Inventory NG FrameWork Version 2.0.0.20
AGENT => Loading plug-in(s)
 PLUGIN => Searching for Plug-in DLL(s) in folder <C:\Program Files\OCS Inventory Agent\plugins>
 PLUGIN => 0 Plug-in(s) succesfully loaded
AGENT => Using network connection with Communication Server
 COM PROVIDER => Loading Communication Provider <C:\Program Files\OCS Inventory Agent\ComHTTP.dll>
==============================================================================
Starting OCS Inventory NG Agent on Monday, May 23, 2011 21:48:36.
AGENT => Running OCS Inventory NG Agent Version 2.0.0.20
AGENT => Using OCS Inventory NG FrameWork Version 2.0.0.20
AGENT => Loading plug-in(s)
 PLUGIN => Searching for Plug-in DLL(s) in folder <C:\Program Files\OCS Inventory Agent\plugins>
 PLUGIN => 0 Plug-in(s) succesfully loaded
AGENT => Using network connection with Communication Server
 COM PROVIDER => Loading Communication Provider <C:\Program Files\OCS Inventory Agent\ComHTTP.dll>

Faulting application ocsinventory.exe, version 2.0.0.20, time stamp 0x4dc6b3e7,
faulting module ntdll.dll, version 6.0.6002.18327, time stamp 0x4cb73436,
exception code 0xc0000005, fault offset 0x000665d6, process id 0x10d0,
application start time 0x01cc19cd04ff2a0f.

Log Name: Application
Source: Application Error
Date: 5/23/2011 9:42:51 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: Jigar-PC
Log Name: Application
Source: Application Error
Date: 5/23/2011 9:42:51 PM
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic...

Read more...

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.