Any MSI package that I try to send out with SMS 2003 fails with an error code that has almost no information. I turned on Windows Installer logging and the spot it fails is:

DEBUG: Error 2103: Could not resolve path for shell folder 26.
Internal Error 2103. 26


This only happens when the package is run as the local system. SMS 2003 runs all administrative installs as NT AUTHORITY\SYSTEM. If you run the package as a user it works fine.

Anyone have any information on why this would be? I have made several packages and also tried sending other packages I did not make and they all fail with that same error.
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
I think that shell folder 26 is the Application Data folder. On my computer, then default value in "HKEY_USERS\.DEFAULT\Software\Microsoft\Windows\CurrentVersion\Explorer\User Shell Folders\AppData" is "%USERPROFILE%\Application Data". Are you redirecting this folder to somewhere on the network are you?

If your package does not really use this folder, then you can delete it from the drectory table of your package and then MSI will not try to resolve it.
Answered 03/18/2004 by: mrtap
Senior Yellow Belt

Please log in to comment
0
I am having the same problem with my Installshield packages in SMS 2003. I have been talking to Installshield about it. I have gotten some MSIs to work but my Installshield packages are giving me the most problems. I am seeing the same problem when I deploy using ADS (Automated Deployment Services) to Windows 2000 server.
Answered 03/25/2004 by: Stone386
Yellow Belt

Please log in to comment
0
I've run into the same problem with some MSI packages as well. I've found that the ALLUSERS=1 isn't in the Property table of the MSI, so some of them think they need to put something in the current user profile during the installation (even if they really don't). I used InstallShield's DevStudio to insert that entry in the Property table and they started installing fine for me. Makes me glad I talked my boss into the InstallShield stuff.

Chris
Answered 05/17/2004 by: Kamilian
Yellow Belt

Please log in to comment
0
We are having the same issues after upgrading from 2.0 to 2003. We found the same "workaround" about setting the ALLUSERS property. These are packages that were being deployed in 2.0 for months with no issues and after the 2003 upgrade we get 2103 errors.

We are also having issues with packages that call another msi. Unless SOURCELIST is set in the call to the spawned process they fail...

Anyone have any resolution? MSFT just says re-deploy with the properties defined...
Answered 09/10/2004 by: SSPerfomance
Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity