Link to home
Start Free TrialLog in
Avatar of Luca
Luca

asked on

SQL Anywhere installtion preventing further msi installations

Hello Team

we are currently trying to install SQL Anywhere 17 unattended in system context. Regarding the documentation http://dcx.sap.com/sqla170/en/html/8168a3fa6ce21014a346e584d7ae12a7.html we use the following installation string (unfortunately the two msi can not be executed directly - they have to be executed via setup.exe)

User generated image
Setup.exe /l:1031 /s "/v: /qn REGKEY=ABCDE-FGHIJ-KLMNO-12345-67890 samples=0 sa32=1 sa64=1 sm32=0 sm64=0 sr32=0 sr64=0 ml32=0 ml64=0 at32=0 at64=0 reboot=reallysuppress"

During installation 3 MSIEXEC processes are starting but only two of them are terminating. Because of this further unattended MSI Installation will fail because an access to C:\Windows\Installer\inprogressinstallinfo.ipi is still active

User generated image
User generated image
User generated image
First i thought killing the remaining msiexec process will solve the problem (it is working with logged on system account (psexec -i) Unfortunately killing the remaining process in unattended mode is not possible (access denied) I also tried to restart "windows installer" service but no success

Maybe anyone has the same issue with a working solution

Regarding https://www.itninja.com/question/sqlanywhere-12-not-installing-in-system-context-specifically-in-win-8-1-machine this issue occurs with older installations aswell...
Avatar of Darren Collins
Darren Collins
Flag of United Kingdom of Great Britain and Northern Ireland image

Error 2203 in Windows Installer is when the msiexec process(es) "cannot access the default temporary folder in Windows (%temp%). "[1]

This led me to look for other installations where people had issues accessing 'C:\Windows\Installer\inprogressinstallinfo.ipi'
 during the Windows Installer process.  See links [2] and [3] below.  In each case it was caused by issues related to accessing %temp%.

In a default system, the SYSTEM account uses C:\Windows\Temp as its temp folder.  If your setup has altered this for some reason then this could be the issue, e.g changed the location of %TEMP% or %TMP%.  

Maybe try this: in the script that executes the Setup.exe command as the SYSTEM account, try putting above it setting  the %temp% and %tmp% to c:\windows\temp.

So in batch this would be:
... previous code ...
Set TEMP=C:\Windows\Temp
Set TMP=C:\Windows\Temp
Setup.exe /l:1031 /s "/v: /qn REGKEY=ABCDE-FGHIJ-KLMNO-12345-67890 samples=0 sa32=1 sa64=1 sm32=0 sm64=0 sr32=0 sr64=0 ml32=0 ml64=0 at32=0 at64=0 reboot=reallysuppress"
... any other code ...

Open in new window

... this will then temporarily set those two variables for that session only.


[1] https://support.microsoft.com/en-us/help/2000547/error-2203-an-internal-error-occurred-when-you-install-a-microsoft-off
[2] https://www.advancedinstaller.com/forums/viewtopic.php?t=33464
[3] https://www.kiwipiet.com/2018/09/error-2203-database-cwindowsinstallerin.html

Hope this helps,
Regards, Daz
Avatar of Luca
Luca

ASKER

Hello Daz

unfortunately no luck. Still the same behavior

$env:temp = "C:\Windows\TEMP"
$env:tmp = "C:\Windows\TEMP"
& Setup.exe /l:1031 /s "/v: /qn REGKEY=ABCDE-FGHIJ-KLMNO-12345-67890 samples=0 sa32=1 sa64=1 sm32=0 sm64=0 sr32=0 sr64=0 ml32=0 ml64=0 at32=0 at64=0 reboot=reallysuppress"

Open in new window


Regards
ASKER CERTIFIED SOLUTION
Avatar of Luca
Luca

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial