[ISS Support Case] Batch Server cannot connect to PLCs Unbale to Run Batch
Last updated: March 7th, 2025Description
We have a wonderware installation with redundant servers, one batch will not run on one of the two servers. Week after labor day (15th) the engineers noticed the "issue' Engineers describe the issue as: 'one of the Batch servers are not able to connect to the PLC's'. Client was called in to collect intel and get this resolved. Possible to access system remotely. Can ping PLC Inbatch 2014 R2 Sp1 (11.0.0.0) intouch 11.0.131 Client suspects the issue is tied to a repeating IBCLI error noticed in the logs. Inbatch 2014 R2 Sp1 (11.0.0.0) intouch 11.0.131 ibcli.exe exception code 0xC0000005 goes as far back as August 29th. Event Logs and SMC logs are being collected client will be uploading them to the ticket. See Box Content.
- Author: Kevin Modlin
- Published: March 7th, 2025
Details:
| Product: Batch |
| Version: 11.1 |
| Solution: [Solution is visible below when you're logged in and have a current subscription] |
| Date Created: | 10/12/2023 |
| Case: | 85518 |
Give feedback about this article
Recommended articles
[ISS Support Case] InBatch .NET Object Parameter Not Updating Properly
When passing an empty string into BatchGui unit parameter the display fails to initialize with Batch information.
Read More[ISS Support Case] Batch Server Reporting Configuration Failure
Client reached out as they were receiving the following error when attempting to configure Batch Server Reporting on remote node: "An error occurred during configuration of the reporting d\feature" This error was shown at the same time in the logger: "The request failed with HTTP status 503: Server too Busy"
Read More[ISS Support Case] Inbatch 2014 r3 issue with reports
Inbatch reports - he clicks on it and the coniguration doesnt open. windows server 2012 r2, inbatch v2014 r3
Read More[ISS Support Case] InBatch Migration
3/4/2024: -Installed Inbatch system 2014 R2. -Wanting to upgrade to 2023 R2 Batch management. 3/5/2024: -Awaiting word back from L2 about best practices when upgrading InBatch.
Read More