Skip to main content

Search

Welcome to Tibero GTS!

Hang Issue Occurs When Running system.vbs

Document TypeㅣTroubleshooting 

CategoryㅣInstallation

Applicable Product Versionsㅣ6FS07, 6FS07PS, 7FS02, 7FS02PS

Document NumberㅣTINTS011

 

Issue

After running system.vbs, even though the passwords for the sys and syscat accounts are entered correctly, the script no longer proceeds and hangs.

Note
This issue occurred in Tibero version 7.2.2.
 
Below is an example.
C:\Tibero\tibero7\scripts>cscript //H:cscript
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.

The default script host is now set to "cscript.exe".


C:\Tibero\tibero7\scripts>system.vbs
Microsoft (R) Windows Script Host Version 5.812
Copyright (C) Microsoft Corporation. All rights reserved.


Enter SYS password:
tibero
Enter SYSCAT password:
syscat
Creating additional system index ...
     Running C:\Tibero\tibero7\scripts\create_additional_system_index.sql ...
 
After canceling the script execution at this point and retrying, the following error occurs and the script does not run.
C:\Tibero\tibero7\scripts>system.vbs(415, 9) Microsoft VBScript runtime error: Permission denied.

 

Cause

The system.vbs script references the %TMP% environment variable when running to save working files (tmp_log, tmp_sql), and this path includes %USERPROFILE%. During the initial run, the %USERPROFILE% value is recognized correctly, and files are created in that path, but if the user folder name is long (e.g., C:\Users\TmaxTiberoSupportTeam), internally the path is converted to a short name (e.g., Tmax~1) and referenced. During this process, the script fails to properly recognize the converted tempDir path, causing the SQL file execution step to enter an infinite wait state.
For the same reason, because it tries to access the tempDir path with the corrupted USERPROFILE name, the Microsoft VBScript runtime error: Permission denied occurs again upon retry.

 

Solutions

If the script hangs when running system.vbs, check the initially created tmp_log file in the tmpDir path. If the path is truncated, change the %TMP% environment variable to an accessible path and then rerun the script.
 
 
 

Related to