InstallAware

Hi,

one of our customers send the log of his attempt to install a software via InstallAware.
The cause of the failure seems to be the following:

MSI (s) (D8:EC) [14:58:16:602]: Executing op: FolderCreate(Folder=c:\test\pgl_setup.exe\,Foreign=0,,)
MSI (s) (D8:EC) [14:58:16:602]: Note: 1: 1312 2: C:\test\pgl_setup.exe
MSI (s) (D8:EC) [14:58:16:602]: Note: 1: 2205 2: 3: Error
MSI (s) (D8:EC) [14:58:16:602]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1312
Fehler 1312. Das Verzeichnis C:\test\pgl_setup.exe kann nicht erstellt werden. Es ist bereits eine Datei mit diesem Namen vorhanden. Benennen Sie die Datei um, oder entfernen Sie sie, und klicken Sie auf "Wiederholen", oder klicken Sie auf "Abbrechen", um das Programm zu beenden.

Translation:
The folder [...] can not be created. A file with the name [...] already exists.

The setup was executed via SYSTEM account. Searching the InstallAware forums I can find reports of similar issues dating back to 2010.
Setup was build using IA15 Studio, which according to several forum answers should work.
Today I downloaded 3 3GB of IA18 to check with a current version, just to notice after several hours of downloading that the IA18 in contrast to the IA15 has a problem with german umlauts.

So my questions:
- what is the cause of the problem described in the log?
- how can I fix it?
- how can I get IA18 to work? (we are a german company, we need a way of creating setups in german language); this part is a bit irritating since IA15 had no problem at all regarding this


This is a critical problem and I would really appreciate a quick and substantiated solution.

Dear User,

First of all, if you try to install your package under a standard account context ... does it work fine?

If true, please have a look at the following topic;
http://www.installaware.com/forum/viewtopic.php?f=2&t=6658&hilit=user+account&start=15

Then, if not true;

- what is the cause of the problem described in the log?
- how can I fix it?

The aswer is already in your translation, the file can't be created because a file with an identical name is already present.
Unfortunately, it is not easy to give you a sure answer about the cause by the only information you shared.
For example, does it happen with a single machine only?

how can I get IA18 to work? (we are a german company, we need a way of creating setups in german language); this part is a bit irritating since IA15 had no problem at all regarding this

In reality if you should have a problem with Handling Non-latin characters, for sure this can't happen with IA 18.
InstallAware full support UNICODE and due of this, I can assure you that there isn't any problem with Handling any kind of characters ... instead this is not the same with any past ANSI versions of IA as IA 15.

Probably you didn't use the Unicode Upgrade tool before to open your project in IA 18 or probably, you used not-latin strings or characters directly in your script code (when reference to translated resource strings should be used instead).

Regards

FrancescoT wrote:First of all, if you try to install your package under a standard account context ... does it work fine?

Yes.

If true, please have a look at the following topic;
http://www.installaware.com/forum/viewtopic.php?f=2&t=6658&hilit=user+account&start=15

I did and arranged two tests:
1. Scheduled task run as local user - worked.
2. Scheduled task run as SYSTEM - Failed

The setup was started from C:\Windows\TEMP\mia7EEF.tmp\PGL_Setup.exe - which seems to be the location where the system account decompressed the setup to
and a folder with the same name could not be created... sounds similar.

Then, if not true;

- what is the cause of the problem described in the log?
- how can I fix it?

The aswer is already in your translation, the file can't be created because a file with an identical name is already present.

Why does the setup try to create a folder with the name of the setup it is started from?

I start d:\mysetup.exe
and the cause of the problem is that it can not create the folder d:\mysetup.exe

Am I the only one to regard this odd?

Unfortunately, it is not easy to give you a sure answer about the cause by the only information you shared.

What else do you need?

For example, does it happen with a single machine only?

No.


EDIT:
I used the unicode upgrade tool (thanks for the info), build a setup with IA18 and redid the test from above: starting the setup from a scheduled task run as SYSTEM.
The error reported in the log was another, the result the same: setup failed.

MSI (s) (68:54) [11:03:10:197]: Executing op: FolderCreate(,Foreign=0,,)
MSI (s) (68:54) [11:03:10:197]: Note: 1: 2343
MSI (s) (68:54) [11:03:10:197]: Note: 1: 2205 2: 3: Error
MSI (s) (68:54) [11:03:10:197]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2343
DEBUG: Error 2343: Specified path is empty.
Bei der Installation dieses Pakets ist ein unerwarteter Fehler aufgetreten. Es liegt eventuell ein das Paket betreffendes Problem vor. Der Fehlercode ist 2343. Argumente: , ,
MSI (s) (68:54) [11:03:10:380]: Note: 1: 2205 2: 3: Error
MSI (s) (68:54) [11:03:10:380]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (68:54) [11:03:10:380]: Produkt: Praxisgerechte Lösungen -- Bei der Installation dieses Pakets ist ein unerwarteter Fehler aufgetreten. Es liegt eventuell ein das Paket betreffendes Problem vor. Der Fehlercode ist 2343. Argumente: , ,
Aktion beendet um 11:03:10: InstallFinalize. Rückgabewert 3.

Dear Anja_laenge,

I suppose that very probably, this is caused by the value of the ALLUSERS pre-defined variable.
If the setup is executed under system account, this variable value must be set as TRUE, otherwise the setup fails.

Are you using an MSI file installer or as compressed EXE?
Are you running it in silent mode?

Regards

I suppose that very probably, this is caused by the value of the ALLUSERS pre-defined variable.
If the setup is executed under system account, this variable value must be set as TRUE, otherwise the setup fails.

According to the dialog in the IA IDE and the log it's value is "1".
I forced this by calling the setup with this value specified. for curiosity I did another test by calling it with "0" - made no difference in the resulting error message.

Are you using an MSI file installer or as compressed EXE?
Are you running it in silent mode?

compressed EXE in silent mode.

What I don't understand is the error message in the log created with the IA18 setup: DEBUG: Error 2343: Specified path is empty.

this is the section of the log previuos to the error:
MSI (s) (0C:3C) [13:05:25:377]: Executing op: ActionStart(Name=CreateFolders,Description=Ordner werden erstellt,Template=Ordner: [1])
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\7zS6941.tmp\data\,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:377]: Executing op: FolderCreate(Folder=C:\ProgramData\Microsoft\Windows\Start Menu\Programs\BG\[ourproduct],Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:395]: Executing op: FolderCreate(Folder=C:\ProgramData\Microsoft\Windows\Start Menu\Programs\BG\[ourproduct],Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:411]: Executing op: FolderCreate(,Foreign=0,,)
MSI (s) (0C:3C) [13:05:25:411]: Note: 1: 2343
MSI (s) (0C:3C) [13:05:25:411]: Note: 1: 2205 2: 3: Error
MSI (s) (0C:3C) [13:05:25:411]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 2343
DEBUG: Error 2343: Specified path is empty.


another installation issued as normal user (and succeeding)continued at this point with the following line:
MSI (s) (C0:E4) [09:53:00:817]: Executing op: FolderCreate(Folder=C:\Users\alaenge\Desktop\,Foreign=0,,)

Current status:

As written above a setup issued as normal user continued with the desktop folder creation.
In the log of the failed setup as SYSTEM I looked up the lines where setup determines the value for $DESKTOPDIR$

MSI (s) (0C:3C) [13:05:12:332]: SHELL32::SHGetFolderPath returned: C:\Windows\system32\config\systemprofile\Desktop

Well, ..\systemprofile\ has no subdirectory "Desktop"
Commenting out all lines in the setup concerning the desktop icon the setup succeeds as scheduled task run as SYSTEM.

Shouldn't the setup use "C:\Users\Public\Desktop" when run with ALLUSERS = 1?

Dear Anja_laenge,

I suppose your issue with the desktop folder under system account, it is simply caused by the way you used to acquire that directory.

In your main script code you should have something like the code below when setting the target desktop folder.

if Variable ALLUSERS Equals TRUE
Get Common Folder Location System->Desktop Directory into DESKTOPDIR
else
Get Folder Location System->Desktop Directory into DESKTOPDIR
end

When the ALLUSERS variable is TRUE, the "Get Common Folder Location" command should have the flag "Get for all users" selected.
Otherwise, the command will return the folder location for the current user ... and under SYSTEM account this folder doesn't exist.

The same in IA clipboard format;


Hope this helps you.

Regards

FrancescoT wrote:In your main script code you should have something like the code below when setting the target desktop folder.

if Variable ALLUSERS Equals TRUE
Get Common Folder Location System->Desktop Directory into DESKTOPDIR
else
Get Folder Location System->Desktop Directory into DESKTOPDIR
end

Hope this helps you.

It did.
I reinstalled our IA15 and checked the template produced when creating a new project and it contained similar lines to determine the folder for the start menu links but none for the desktop links?

Dear Anja_laenge,

... you can even add that code manually or with pasting the code snippet I posted (IA Clipboard format) directly in your main script (... at the very beginning of the [Process (Un)Installation] code region).

Regards