1. We found some error in SMS log
Execution is complete for program SAP 620.78 Upgrade. The exit code is 1, the execution status is FailureNonRetry execmgr 2011/3/2 上午 09:38:31 1540 (0x0604)
The user has logged off. execmgr 2011/3/2 上午 10:18:39 832 (0x0340)
Execution Manager timer has been fired. execmgr 2011/3/2 上午 10:19:39 1188 (0x04A4)
A user has logged on. execmgr 2011/3/2 上午 10:20:25 3328 (0x0D00)==============================
According to above log, it is not like nothing happens but SMS actually runs the program and program exits with exit code 1.
SMS considers exit code 1 as a failure code. Typically, 0 is considered as success.
Asked customer double confirmed using below command remotely on test client without /silent switch in command line.
2. In process monitor log, we found when setup process down, the program will write some msg to C:\WINDOWS\SapSetup.log
899 下午 02:36:58.7529949 SapSetup.exe 3196 SetRenameInformationFile C:\WINDOWS\SapSetup.log NAME COLLISION ReplaceIfExists: False, FileName: C:\WINDOWS\SapSetup1.log
3. We collect SapSetup.log for further check
14:35:31 sapfeish 1 “C:\WINDOWS\system32\vbscript.dll” successfully loaded.
14:35:31 SapFeiUt 3 Security : failed to calculate CRC32 checksum for ‘C:\WINDOWS\system32\CCM\Cache\setup\sapsetup.xsc‘
14:35:31 sapfeish 1W Failed to open script file ‘C:\WINDOWS\system32\CCM\Cache\setup\sapsetup.xsc’: The system cannot find the path specified. Error code 0x3 (3)
14:35:31 sapsetup 1E Failed to open/parse setup script C:\WINDOWS\system32\CCM\Cache\setup\sapsetup.xsc. Last error 0x0 (0)
14:36:13 sapfeish 3 Scripting Host shutdown
According to above log, we can find the setup program made a mistake with wrong path to C:\WINDOWS\system32\CCM\Cache\setup\ from C:\WINDOWS\system32\CCM\Cache\T0100000.1.System\setup\
So that’s why setup always failed with “Failed to open/parse setup script C:\WINDOWS\system32\CCM\Cache\setup\sapsetup.xsc”
It seems SAP setup program doesn’t support the directory structure like …\T0100000.1.System\setup\
Due to the install file is designed by GPO deployment. We can workaround it by using bat file and add a copy statement to avoid above App installation path redirect error.