Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Error 1624: Error applying transforms. Verify that the specified transform paths are valid.

2,463 views
Skip to first unread message

Eike Saß

unread,
Sep 18, 2001, 5:56:21 AM9/18/01
to
I got this error message, even if I start my MSI Package without any
transforms ("msiexec /i package.msi") I just created the project with
Installshield IPWI 2.03.

What's wrong??

Thanx Eike


Christian Baumgärtel

unread,
Sep 18, 2001, 7:42:03 AM9/18/01
to
I had a similar problem with WfWI.
The problem was: In the Property ProductLanguage of the Property Table were
specified more than one
language id, for example: 1031,2055,3079
and also in the Languages field of the summary information stream.
If you have a system with regional settings that correpond to a language id
other than the first
(in this example:1031, which means German(Germany)),
for example, German(Austria), which means (2055 or 3079), then your
installation fails with
the error you described.
MSI seems to have a built-in mechanism for supporting multiple languages,
which seems not to be well-documented (I don't even know if it is supported
any more),
but for each additional language you have to provide a transform,
describing the correct localization of your installation.
To avoid this problem, simple specify ONLY ONE language id in MSI, if you
localized msi for only one language. You can use ORCA
to edit your installation msi file.

Hope this helps,
Christian


"Eike Saß" <eik...@gmx.de> wrote in message
news:uzTQIgCQBHA.1628@tkmsftngp05...

Eike Saß

unread,
Sep 20, 2001, 5:56:51 AM9/20/01
to
Thanx Christian, but I think my problem is different.
 
If I install my product on a new OS, it works without problems.
 
If I install it on a machine with an old version of our product (identical product code and upgrade code), I get this error. The log file says some more details:
 
=== Verbose logging started: 20.09.01  11:41:35  Build type: SHIP UNICODE 1.20.1827.00  Calling process: C:\WINNT\System32\MSIEXEC.EXE ===
MSI (c) (A9:AF): Resetting cached policy values
MSI (c) (A9:AF): ******* RunEngine:
           ******* Product: <some path>\product.msi
           ******* Action:
           ******* CommandLine:  TRANSFORMS="1031.MST"
...
MSI (c) (A9:AF): Original package ==> <some path>\product.msi
MSI (c) (A9:AF): Package we're running from ==> C:\TEMP\9bfba8c.msi
....
MSI (c) (A9:AF): Searching for item Products\345D0C14FD994D11295900102002D45C in per-user managed key
MSI (c) (A9:AF): Searching for item Products\345D0C14FD994D11295900102002D45C in per-user non-managed key
MSI (c) (A9:AF): Found item Products\345D0C14FD994D11295900102002D45C
MSI (c) (A9:AF): Looking for storage transform: 1033
MSI (c) (A9:AF): Note: 1: 2203 2: 1033 3: -2147287038
MSI (c) (A9:AF): Note: 1: 2729
1: 2203 2: 1033 3: -2147287038
Fehler bei der Anwendung von Transformen. Stellen Sie sicher, dass die angegebenen Transformpfade gültig sind.
1033
 
I started the installation with the german transform (1031.mst). So, why does it look for the english one? The old version of our product was installed with a german tranform too.
 
Another remark: If I build my installation set for one language only, i.e. without any transforms, I get the same error.
 
New ideas are very welcome.
 
Thanks, Eike
 

Christian Baumgärtel

unread,
Sep 20, 2001, 2:35:21 PM9/20/01
to
Well, I think there are at least two problems mixing here.
First, as far as I know, normally you cannot install a newer version of your product over an older one,
if you don't change the product code, or don't specify special command line options
(You can upgrade an installation by reinstalling the product, which means specifying the
REINSTALL and REINSTALLMODE property, read "Patching and Upgrades" in the SDK Help)
May be the installer only wants to display an error message in the correct language?
What is the system locale of your operating system? (I.e. the regional settings)?
Is it German(Germany)?
Note that the installer seems to look for a transform embedded in .msi, not a transform
specified by a .mst file, and this could be caused by the problem I had reported .
 
 
Christian
 
"Eike Saß" <eik...@gmx.de> wrote in message news:O4zxypbQBHA.1220@tkmsftngp05...
0 new messages