Troubleshooting connectivity issues between the OCS Inventory NG Agent and the Communication Server involves diagnosing configuration errors, network restrictions, SSL/TLS certificate mismatches, or server-side database faults.
The step-by-step framework below isolates and resolves these communication failures. 1. Enable Verbose Agent Logging
Before guessing the root cause, elevate the log verbosity to pinpoint exactly where the handshake or “Prolog” fails. Windows Agent:
Open the Services console (services.msc) and stop the OCS Inventory Service.
Navigate to the hidden directory C:\ProgramData\OCS Inventory NG\Agent</code>. Open ocsinventory.ini and modify or add the line: Debug=2.
Restart the service and open ocsinventory.log to review errors.
Linux Agent: Run the agent manually from the terminal using the command:ocsinventory-agent –debug –logfile=/var/log/ocs-debug.log 2. Verify Server URL Configuration
Agents frequently fail because they target the web administration console instead of the dedicated communication endpoint.
Check the Directive: Ensure the Server= value in your agent configuration file points to the communications route, typically ending in /ocsinventory, not /ocsreports (which is the web console UI). Correct Example: Server=https://your-server-ip/ocsinventory
Manual Trigger: Force an immediate contact check on Windows by right-clicking the system tray icon and selecting “RUN OCS Inventory NG Agent Now” or executing OCSInventory.exe /NP /DEBUG via CMD. 3. Diagnose Common HTTP Status Codes
When parsing the agent logs, search for Failed to send Prolog or HTTP Status Code errors to map the failure: Windows Agent cannot connect to OCS Server
Leave a Reply