[ISS Support Case] Failing to Upgrade Batch Management 2017 (V12.1) To Batch Management 2023 R2 (V13.1)
Last updated: October 17th, 2025Description
Client reached out as when user was attempting to configure the History Server tab under Batch Management it would fail with the following errors: Component: History Server "ExecutionNonQuery failed for Database "B2BatchHistory" "An exception occurred while executing a Transact-SQL statement or batch." "ExecuteNonQuery failed for Database 'B2BatchHistory'. An exception occurred while executing a Transact-SQL statement or batch. Cannot drop type 'dbo.Text_Chunk_NVARCHAR128' because it is being referenced by object 'EquipStatus'. There may be other objects that reference this type."
- 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: | 05/21/2025 |
| Case: | 97862 |
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