Mid Server with a closing parenthesis ')' in the windows service name, doesn't start itself after upgrading, leaving the MID Server Down - Known Error

Mid Server with a closing parenthesis ')' in the windows service name, doesn't start itself after upgrading, leaving the MID Server Down Description A Mid Server with a closing parenthesis ")" in the windows service name, doesn't start itself after upgrading, leaving the MID Server Down. Given the service name is usually snc_mid_ followed by the MID Server's Name as seen in the instance and config.xml, naming the MID Server using curved brackets causes this.

"Output=xxx was unexpected at this time." in the wrapper.log/dist_upgrade.log.0 is seen, where xxx is the first word after the ) in the name.

Steps to Reproduce

Using the ZIP file, Install a Windows MID Server in Yokohama or Zurich. (since the fix of PRB1662654 in Yokohama) But name the MID Server with a closing parenthesis in the middle of it - ")". e.g. "202509 (ACC Test) MID" Ensure the install folder has no special characters, spaces, brackets, etc. e.g. (to show this is not the cause, and so not PRB1898139) Run start.bat to start the MID Server (where the service will be SYETEM), then validate it, and see everything is working as expected.

Set the service to use a non-admin user, and add it to the folder permissions. Restart the service. upgrade the instance. e.g. Zurich patch 0 to patch 1. Actual behaviour:

The upgrade will fail at the point it tries to start the MID Sevrer using start.bat, after replacing all the files. Then fail again to start after the rollback, leaving the MID Server down.

INFO | jvm 1 | 2025/09/29 11:24:27.777 | Sep 29, 2025 11:24:27 AM com.snc.dist.mid_upgrade. UpgradeMain executeCommand INFO | jvm 1 | 2025/09/29 11:24:27.777 | INFO: Executing command `"C:\ServiceNow\2\ agent\start.bat "`. Working dir: `C:\ServiceNow\2\agent`. Current user: `midservice`. INFO | jvm 1 | 2025/09/29 11:24:28.234 | Sep 29, 2025 11:24:28 AM com.snc.dist.mid_upgrade.UpgradeMain executeCommand INFO | jvm 1 | 2025/09/29 11:24:28.234 | INFO: Execution result: ExitCode=255 INFO | jvm 1 | 2025/09/29 11:24:28.234 | Output= MID was unexpected at this time. INFO | jvm 1 | 2025/09/29 11:24:28.234 | INFO | jvm 1 | 2025/09/29 11:24:28.234 | ErrorMsg=Process exited with an error: 255 (Exit value: 255) INFO | jvm 1 | 2025/09/29 11:24:30.237 | Sep 29, 2025 11:24:30 AM com.snc.dist.mid_upgrade.UpgradeMain executeCommand INFO | jvm 1 | 2025/09/29 11:24:30.237 | INFO: Executing command `sc query "snc_mid_202509 (ACC Test) MID"`. Working dir: `C:\ServiceNow\2\agent`. Current user: `midservice`. INFO | jvm 1 | 2025/09/29 11:24:30.269 | Sep 29, 2025 11:24:30 AM com.snc.dist.mid_upgrade.UpgradeMain executeCommand INFO | jvm 1 | 2025/09/29 11:24:30.269 | INFO: Execution result: ExitCode=0 INFO | jvm 1 | 2025/09/29 11:24:30.269 | Output= INFO | jvm 1 | 2025/09/29 11:24:30.269 | SERVICE_NAME: snc_mid_202509 (ACC Test) MID INFO | jvm 1 | 2025/09/29 11:24:30.269 | TYPE : 10 WIN32_OWN_PROCESS INFO | jvm 1 | 2025/09/29 11:24:30.269 | STATE : 1 STOPPED INFO | jvm 1 | 2025/09/29 11:24:30.269 | WIN32_EXIT_CODE : 0 (0x0) INFO | jvm 1 | 2025/09/29 11:24:30.269 | SERVICE_EXIT_CODE : 0 (0x0) INFO | jvm 1 | 2025/09/29 11:24:30.269 | CHECKPOINT : 0x0 INFO | jvm 1 | 2025/09/29 11:24:30.269 | WAIT_HINT : 0x0 INFO | jvm 1 | 2025/09/29 11:24:30.269 | INFO | jvm 1 | 2025/09/29 11:24:30.269 | ErrorMsg=null

Eventually giving up after 5 minutes: INFO | jvm 1 | 2025/09/29 11:29:28.617 | SEVERE: Unable to start MID server.

After which it does a rollback, and then fails to start it again after that too, before giving up completely another 5 minutes later.

Note the: "Output=MID was unexpected at this time " and service name "snc_mid_202509 (ACC Test) MID" where "MID" happened to be the first word, symbol, or letter, after the first of the closing parenthesis ")" in the service name

That's from this line in start.bat for /F "tokens=3 delims=: " %%s in ( 'sc query "%_CURRENT_SERVICE%" ^| findstr STATE' ) do set _SERVICE_STATUS=%%s

Which at runtime is like this: for /F "tokens=3 delims=: " %s in ('sc query "snc_mid_202509 (ACC Test) MID" | findstr STATE') do set _SERVICE_STATUS=%s

The parentheses around the "in (...)" term is messed up by the ) in the name.

Expected behaviour:

Given there is nothing wrong with having a bracket/parenthesis in a windows service name, it should work.

Workaround This problem is currently under review and targeted to be fixed in a future release. Subscribe to this Known Error article to receive notifications when more information will be available.