[ISS Support Case] Batch Management Batch ID Log Scripting Error

Last updated: October 17th, 2025

Description

Client reached out as the user migrated from Batch 2014 to Batch Management 2023 R2. Since this change scripts that were working previously that allowed the operators to adjust the parameters of the Batch before starting the Batch no longer function properly. This is due to the Batch ID Log being created when the Batch is set to Ready. In the previous version the Batch ID Log was not created until the Batch was set to Run.

Author: Kevin Modlin
Published: October 17th, 2025

Details:

Product: Batch Management

Version: 2023 R2

Solution: [Solution is visible below when you're logged in and have a current subscription]

Date Created:	03/17/2025
Case:	88900

Give feedback about this article

Recommended articles

[ISS Support Case] Batch 2023 R2 license acquisition failure

Batch is failing to acquire a license from client's consignment license.

[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"

[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.

[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.