Error Code 1603

[JTFARockz]

I tried to install BF2 again and when it finished downloading and I tried to install it, it just poped up a message saying "Error Code 1603"

Apparently it is a fatal error???

I am using Origin to download BF2

[Obiwan120]

Well according to this(here): This error message is displayed by the Windows Installer engine and is a general error code that indicates a problem occurred during the installation. The following is the probable list of known causes for this error to occur:

Short file name creation is disabled on the target machine.

An Install Script custom action is prototyped incorrectly.

A file is locked and cannot be overwritten.

The Microsoft Windows Installer Service is not installed correctly.

The Windows Temp folders are full.

The setup was corrupted after installation and, therefore, fails with this error during
un-installation.

An older version of Install Shield Developer is being used.

Print and File sharing is not installed if your application needs it.

Not entirely sure how to fix this, but that site may help. Someone who is more technologically educated will be here soon.

[JTFARockz]

Yeah I saw that before I posted this, but I have no idea how to fix it

[MaSSive]

Re-run the setup with verbose logging enabled using steps similar to those that are listed here.
Step 1: Generate a verbose log file named msi*.log in the %temp% directory the next time the setup package is executed. (Click here to know more ways to generate log)

Code: Select all

msiexec /i <msipath>setup.msi /l*v c:\temp\msi.log

[/indent]Step 2: Open the verbose log in a text editor such as notepad and search for the string ?return value 3″. In nearly all cases, this will take us to the section in the verbose log that lists the action that failed that initially caused setup to rollback.
Step 3: Review the contents of the log file immediately above the ?return value 3″ string to determine which custom action or standard action failed. Depending on which action is failing, We will need to proceed to more detailed debugging from here.
One can find that the biggest hurdle to debugging a failed setup is often zeroing in on which part of the setup is actually failing, and this trick of searching for ?return value 3″ ends up helping speed this process up in nearly all cases. Of course, it does not work in 100% of scenarios.You can find some ways of troubleshooting the logs here -
My Installation breaks because of Custom Actions, How do I fix it?
Understand the Windows Installer LogsKnown Solutions
The following solutions have resolved this error in the majority of cases:

1. Make sure short file name creation is enabled on the target machine. You can check to ensure that the target machine does not have short file name creation disabled by navigating to the following registry entry:

   Code: Select all

   HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\FileSystem 

   [/indent]Make sure the value ?NtfsDisable8dot3NameCreation? is equal to 0. This indicates that short file name creation is enabled. A value of 1 indicates that this functionality is disabled. You should change the value to 0. After modifying this value, the target machine should be rebooted before attempting to launch the setup again.Note: If the target machine should normally have short file name creation disabled, it can be disabled after the install completes by resetting ?NtfsDisable8dot3NameCreation? to 1 and rebooting.
2. To ensure that the Windows Installer Service is properly installed and configured, it is recommended that users install the file InstmsiA.exe on Windows 95/98/Me or InstmsiW.exe on Win NT systems. These files are shipped with your InstallShield product and are located in the following location: <Product Path>\Redist\Language Independent\i386. If the service is installed, to know the status of the service exection, you could also goto services.msc in the command prompt, check the status of the Windows Installer Service. ?Stopping and restarting it can help?
3. Empty all temporary folders. The specific temporary folders for a machine can be determined by accessing the DOS prompt and typing set. Note the values listed for TEMP and TMP, and delete all files in those locations.
4. Make sure no other applications, including utilities such as virus scanners, are running in the background. Close all running applications and utilities, and launch the installation again.
5. If this error occurs during un-installation, use the Microsoft Windows Installer CleanUp utility to uninstall the installation. Once the installation has been successfully un-installed, you can then debug the project to determine what caused the original error.

Its explained, so try that.

[JTFARockz]

...
I have no idea how to do any of that...

[JTFARockz]

If anyone can please help me with doing what Massive said please do so.

[JTFARockz]

Actually thread can be closed, apparently after 3 times of trying to re-install it actually did!! but the message that said it appeared and disappeared so fast you would need a super slow mo camera to catch it. Had tome help from a friend in TART. We were both LOL when we figured it out. But it is still weird how t says I need to re-install...

Thanks Massive and Obiwan120 for trying to help me out!!


LOVE PR!!! <3