MST File Transform will not apply over network

[CFConner]

I hope someone can help me with this - I'm in a real pickle if I cannot get this to work.

Here's the situation:

I have a installation that checks for the existence of an MST file in the same folder that the installation is executed from. If it finds it, then when it runs one of the MSI packages (not installaware) it passes the TRANSFORM=<MST PACKAGE> to the command line for RUN PROGRAM.

I can run the program on the local hard drive from any folder and the transform is applied correctly.

When I run the setup from a network share that is a UNC path i.e. \\server\client\install.msi where the MST file is also in \\server\client folder as well - the installation will pass the command line to RUN PROGRAM - which is correct. I have verified this by writing the output of the command line that I put into a variable into a text file before calling RUN PROGRAM with the same variable. However, the installation fails and the MST file is not applied.

I have tried BOTH MSI (Un)Install and the RUN PROGRAM (using MSIEXEC) and the command line for that to be in my variable - everything looks good but does not work when run from a network UNC path only the local hard drive.

=-Chris

[CFConner]

Here's an interesting tidbit.

I just rebuilt the project using a web install. (I did it so I could build the projects faster ) As usual, the behavior still showed the same - however in the event log I did get this: (running the installation from a UNC path)

Windows Installer installed the product. Product Name: Clients 4.0. Product Version: 4.0.295. Product Language: 1033. Installation success or error status: 1624.

1624 means it had an error applying the transform.

Now, if I open a command window and run the EXACT SAME COMMAND for the Run Program - it works - ARRGH!

=-Chris

[CFConner]

Is it possible that the Run Program (and in essence the MSI (Un)Installer) is escaping the \\ characters in the UNC Path? It would explain the error and why running it from the command line works?!

Since I am not a C developer - do I need to put in an extra whack? like \\\\servername\clients\transform.mst for it to properly esacpe to \\servername\clients\transform.mst ???

Just an idea.

=-Chris

[CFConner]

I found "the problem". ARRRRRGGGH!

Anyway, I just needed to check if the string contains the \\ character - if it does, I need to add \\ to it so that the Run Program and MSI (Un)Installer can find my transform file since it will escape the \ character - i.e. \\\\servername\share\transform.mst = \\servername\share\transform.mst

I hope this helps anyone else out there.

=-Chris