Windows Installer error 2203
bohuslav
problem. Whenever I try to install any software that uses the Windows
Installer, the installation fails with error 2203. This is a huge problem,
because I cannot install any new software the uses the Windows Installer!
Has anyone else run into this problem, and how can I fix it?
Thanks
Bob
Rich [Microsoft Windows Installer MVP]
"bohuslav" <bohu...@earthlink.net> spake the secret code
<e9gqmzY0...@TK2MSFTNGP09.phx.gbl> thusly:
>Has anyone else run into this problem, and how can I fix it?
Try running one of the installs with verbose logging:
msiexec /l*v c:\foo.log /i <path to .msi>
Then look in the log for details on error 2203, the error template
from the WI docs is:
Database: [2]. Cannot open database file. System error [3].
--
"The Direct3D Graphics Pipeline"-- code samples, sample chapter, FAQ:
<http://www.xmission.com/~legalize/book/>
Pilgrimage: Utah's annual demoparty
<http://pilgrimage.scene.org>
bohuslav
.msi>), and here is an example excerpt from the installation log when the
error occurs (I included the whole action start -> action end subsection,
and this is when trying to install Microsoft Support Tools):
---------------
MSI (s) (48:98): Doing action: InstallInitialize
Action start 19:29:13: InstallInitialize.
MSI (s) (48:98): Machine policy value 'AlwaysInstallElevated' is 0
MSI (s) (48:98): User policy value 'AlwaysInstallElevated' is 0
MSI (s) (48:98): BeginTransaction: Locking Server
MSI (s) (48:98): Machine policy value 'LimitSystemRestoreCheckpointing' is 0
MSI (s) (48:98): Note: 1: 1715 2: Windows Support Tools
MSI (s) (48:98): Calling SRSetRestorePoint API. dwRestorePtType: 0,
dwEventType: 102, llSequenceNumber: 0, szDescription: "Installed Windows
Support Tools".
MSI (s) (48:98): The call to SRSetRestorePoint API succeeded. Returned
status: 0, llSequenceNumber: 117.
MSI (s) (48:98): Server not locked: locking for product
{8398B542-3CC4-44D9-83DF-696CCE70124B}
MSI (s) (48:98): Note: 1: 2203 2: C:\WINDOWS\Installer\100294e.ipi
3: -2147287035
DEBUG: Error 2203: Database: C:\WINDOWS\Installer\100294e.ipi. Cannot open
database file. System error -2147287035
DEBUG: Error 2835: The control ErrorIcon was not found on dialog
ErrorDialog
Internal Error 2835. ErrorIcon, ErrorDialog
Internal Error 2203. C:\WINDOWS\Installer\100294e.ipi, -2147287035
MSI (s) (48:98): Product: Windows Support Tools -- Internal Error 2203.
C:\WINDOWS\Installer\100294e.ipi, -2147287035
Action ended 19:29:16: InstallInitialize. Return value 3.
Action ended 19:29:16: INSTALL. Return value 3.
------------------
One other thing I noticed is that throughout the log, there are a lot of
notes with negative number results, such as -2147287035 right when the error
occurs. The other common code is -2147287038 as in:
MSI (s) (48:98): Note: 1: 2262 2: BindImage 3: -2147287038
MSI (s) (48:98): Note: 1: 2262 2: ProgId 3: -2147287038
MSI (s) (48:98): Note: 1: 2262 2: PublishComponent 3: -2147287038
MSI (s) (48:98): Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (48:98): Note: 1: 2262 2: Font 3: -2147287038
MSI (s) (48:98): Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (48:98): Note: 1: 2262 2: RemoveFile 3: -2147287038
Are these codes related to the 2203 error? Do they have to do with
permissions or something? And how do I fix it? One thing that comes to
mind is that I redefined my TMP directories to be "C:\tmp" instead of
"C:\WINDOWS\Temp\" and the specific user subdirectory. Could that be
related?
Thanks a million for your help!
Bob
"Rich [Microsoft Windows Installer MVP]" <legaliz...@mail.xmission.com>
wrote in message news:ejwt85Y0...@tk2msftngp13.phx.gbl...
bohuslav
http://support.microsoft.com/default.aspx?scid=http://support.microsoft.com:80/support/kb/articles/q186/0/63.asp&NoWebContent=1)
and found that they mean the following:
-2147287038 (80030002) %1 could not be found.
-2147287035 (80030005) Access Denied.
Also, there is an article about the 2203 error when installing Office
(http://support.microsoft.com/?kbid=324852), excerpt:
-------------------------
Error 2203. An internal error has occurred. Contact Microsoft Product
Support Services (PSS) for assistance.
The Windows Installer log file contains entries similar to the following:
MSI (s) (A5:D5): Note: 1: 2203 2: drive:\path\PRO.MSI 3: -2147287035 Error
2203. An internal error has occurred. (drive:\path\PRO.MSI -2147287035)
Contact Microsoft Product Support Services (PSS) for assistance. For
information about how to contact PSS, see
drive:\FILES\PFILES\MSOFFICE\OFFICE10\1033\PSS10R.CHM.
CAUSE
The error code -2147287035 in the Windows Installer log file indicates that
an "Access denied" error occurred. This problem may occur if incorrect
permissions are set for the folder that contains the Office XP
administrative installation point.
RESOLUTION
To resolve this behavior, grant the System account Full Control permissions
to the folder that contains the administrative installation point.
--------------------
...so this leads me to believe that I have some sort of path/permissions
problem when using the Windows Installer. Any ideas?
Thanks,
Bob
"bohuslav" <bohu...@earthlink.net> wrote in message
news:emrguJZ0...@TK2MSFTNGP10.phx.gbl...
bohuslav
It was a permissions problem with my TMP directory assignment. Since I
manually created those directories, SYSTEM never had permission to it. I
never noticed this because I still had "Simple" file/folder permissions
turned on...
Once I gave SYSTEM full permissions to my TMP folder, I am able to use
Windows Installer again. (I'm surprised I didn't see this problem with
other software, but I suppose other software ran as myself rather than
SYSTEM?)
Thanks,
Bob
"bohuslav" <bohu...@earthlink.net> wrote in message
news:uEn3NYZ...@tk2msftngp13.phx.gbl...
Rich [Microsoft Windows Installer MVP]
"bohuslav" <bohu...@earthlink.net> spake the secret code
<eLzr02Z0...@TK2MSFTNGP11.phx.gbl> thusly:
>Once I gave SYSTEM full permissions to my TMP folder, I am able to use
>Windows Installer again. (I'm surprised I didn't see this problem with
>other software, but I suppose other software ran as myself rather than
>SYSTEM?)
If you installed the other software from a different directory, then
that would also explain it.