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.

Error Win64 agent connecting server: Code #400

Hello,

connection to the OCS server fails with the actual version of OCS.

current version of Win64 agent 2.6.0.1 (same issue with agent 2.6.0.0)
current version of OCS server 2.7

The log file of the windows agent contains the following message:

Starting OCS Inventory NG Agent on Sunday, April 5, 2020 06:00:32.
AGENT => Running OCS Inventory NG Agent Version 2.6.0.1
AGENT => Using OCS Inventory NG FrameWork Version 2.6.0.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.6.0.0>
AGENT => Sending Prolog
ERROR *** AGENT => Failed to send Prolog <HTTP Status Code #400>
AGENT => Unloading communication provider
AGENT => Unloading plug-in(s)
AGENT => Execution duration: 00:00:00.

Also in the apache log on the server you could the eror code 400

Some clients have an older version of the Windows agent (2.1.1.). With the older agent the communication with the server works.
in OCS Inventory NG agent for Windows by (160 points)

3 Answers

0 votes

Hello !

I also have this issue and after many days of troubleshooting I have found the solution.

All you need to do is replace the Ocsinventory.pm file on current folder of ocsinventory-server

Like this:

- go to /usr/local/share/perl5/Apache and delete the old Osinventory.pm file

- go to the installation folder of version 2.7 -> copy new Osinventory.pm file and paste to the path above

- restart httpd or apache 

Enjoy !!!

by (140 points)
0 votes
Check your ocs server logs to see if there is a conection. And enable debug en ocsinventory.ini. Perhaps that helps.
by (2k points)
edited by
0 votes

Updating the file Osinventory.pm helped - Thank you

by (160 points)
 
Powered by Question2Answer
...