Service commands and location-code utility limitations.
Scope
Service commands and location-code utility behavior for TunnelWatch 4/5. Confirm the installed service names and paths before service work.
TunnelWatch 4 service files
The start and stop files address these Windows service names, in the same order:
twwstunnelhandlerdsicloudclienttwdatacollectorsvc
TW 4 Start.bat issues net start for each name. TW 4 Stop.bat issues net stop for each name. Both end with pause, leaving the command window open for the operator to read the output.
Neither file checks each command's result or verifies the final service state. Reaching the pause prompt therefore does not prove all services started or stopped. A technician using an approved service procedure needs to confirm the installed names and examine each result. Stopping these services interrupts their functions; coordinate the wash downtime before service work.
TunnelWatch 5 location-code file
This file asks for the old and new location codes and assumes a D:\TW installation. Its intended sequence is:
| Stage | Observed behavior |
|---|---|
| Stop services | Stops tunnelhandler, twws and twdatacollectorsvc. It does not stop dsicloudclient here. |
| Back up | Creates D:\TW\Dat\backupLoc, copies the data-directory files and TW.ini, then displays a confirmation prompt. |
| Prepare renamed files | Creates a Temp directory and copies files selected by the old location-code prefix using the new prefix. |
| Replace data | Deletes files from the current data directory, then copies the prepared files back. |
| Edit configuration | Opens TW.ini in Notepad and asks the operator to update LOCID and LOCID4. |
| Restart services | Starts the four service names listed above. |
| Update registry | Writes DSILocationCode under the 32-bit or WOW6432Node DSI software key. |
Location-code utility defects
The file has no enforced checks for successful service stops, directory changes, backups or replacement copies. Its confirmation comparisons expect quoted answers, and its copy-to-temp line has an unmatched quotation mark. It also jumps to an ErrorCheck label that is absent from the file.
Do not use this location-code utility as an installation procedure. A failed backup or directory change can lead to deletion in the wrong location. Have the responsible technician validate a corrected procedure before changing location codes. The executable utility is not included here.
Information for support
Record the installed TunnelWatch version, service names and current states, installation drive, current location code and the reason for a proposed change. Preserve the output of any approved service work and verify the resulting application state before the wash returns to operation.