InstallAware

Ah okay, so please can you tell me what this test setup is installing (the customer will need to know that)? And can you tell me what is the difference in your test setup or what may cause the fail in my setup?
I also want to mention that I have no problems in general with installing IA setups using a scheduled task running as SYSTEM. But through Matrix42 there seems to be a general problem. Would be great if this could be solved.

JeffryPaul wrote:OMG! IT WORKS!

The following tests were performed on Windows 7:
1. Ran SysTest.exe installer provided by Installaware (which installs WinDiff) using a scheduled task running as SYSTEM. Success!
2. Ran one of my own Installaware setups (using the native engine) created in July 2011(not sure if that was IA11 or IA12) using a scheduled task running as SYSTEM. Success!
3. Ran an updated Installaware setup (definitely IA12) using a scheduled task running as SYSTEM. Success!
4. Used my home-grown Installaware update service (which runs as SYSTEM) to install my latest Installaware setup. Success!

Due to the MSI Installer headaches, I switched to the Installaware native engine. I wonder if that change made the difference.

Thanks, Installaware, for revisiting this issue.

I don't know what your pakage does but for sure I can assure you, that my SysTest sample has been gnerated from a basic InstallAware template.
For experience, I found that often this problem can be caused by the ALLUSERS variable when it is not to set as TRUE.

You also said that you haven't found problem installing your package using a scheduled task running as SYSTEM.
Could you try if it works fine using the PSEXEC tool?

Regards

Dear Francesco,

I tried to run my setup with psexec but the setup itself is always running as a User an never as SYSTEM. Maybe I am doing something wrong. But for me it would be more interesting if your test-setup is running within Matrix42 Empirum, so I will ask the customer to try it within that deployment tool.

UPDATE: the customer was able to install the test-setup through Matrix42 Empirum (silent and with SYSTEM Account) so now my question is what can cause this error that he get's with my setup:
Sorry the message is in german but in general it is telling that the folder C:\Windows\TEMP\mia2AE6.tmp\<my-setup>.exe cannot be created because it is already existing.

Can this be prevented by setting ALLUSERS to TRUE as you have suggested?

Dear Alibaba,

to test your package using PSEXEC use the following syntax:

psexec -i -s <packagefile> /s

The above cmd runs the PACKAGEFILE under SYSTEM ACCOUNT (-s) in silent mode (/s).
For a complete list of PSEXEC comand line parameters, just enter PSEXEC.EXE in a cmd window.

If the problem is caused by the ALLUSERS variable setting, it should be fine to verify if in your code you are setting it as FALSE somewhere.

Let me know.

OK now it works.

the error 1312 did not occur using psexec for installing with SYSTEM account. I also played a bit with ALLUSERS property and set it to TRUE, FALSE or did not set it at all. Also no error 1312. But I discovered another error, see this thread:

http://www.installaware.com/forum/viewt ... f=2&t=8922

I think the error 1312 can only be reproduced and confirmed in the special Matrix42 Empirum installation scenario.

I'm happy that you solved ... but I'm really confused with other post link.

Regards

alibaba wrote:Dear Francesco,

I tried to run my setup with psexec but the setup itself is always running as a User an never as SYSTEM. Maybe I am doing something wrong. But for me it would be more interesting if your test-setup is running within Matrix42 Empirum, so I will ask the customer to try it within that deployment tool.

UPDATE: the customer was able to install the test-setup through Matrix42 Empirum (silent and with SYSTEM Account) so now my question is what can cause this error that he get's with my setup:

Code: Select all

MSI (s) (80:6C) [16:09:35:798]: Executing op: FolderCreate(Folder=C:\Program Files (x86)\EasternGraphics\pCon.planner 6\updater\data\,Foreign=0,,)
MSI (s) (80:6C) [16:09:35:798]: Executing op: FolderCreate(Folder=C:\Program Files (x86)\EasternGraphics\pCon.planner 6\updater\data\OFFLINE\mDown.dll\,Foreign=0,,)
MSI (s) (80:6C) [16:09:35:798]: Executing op: FolderCreate(Folder=C:\ProgramData\Microsoft\Windows\Start Menu\Programs\EasternGraphics\pCon.planner 6,Foreign=0,,)
MSI (s) (80:6C) [16:09:35:798]: Executing op: FolderCreate(Folder=C:\ProgramData\Microsoft\Windows\Start Menu\Programs\EasternGraphics\pCon.planner 6,Foreign=0,,)
MSI (s) (80:6C) [16:09:35:813]: Executing op: FolderCreate(Folder=C:\Windows\TEMP\mia2AE6.tmp\pCon.planner_setup.exe\,Foreign=0,,)
MSI (s) (80:6C) [16:09:35:813]: Note: 1: 1312 2: C:\Windows\TEMP\mia2AE6.tmp\pCon.planner_setup.exe 
MSI (s) (80:6C) [16:09:35:813]: Note: 1: 2205 2:  3: Error 
MSI (s) (80:6C) [16:09:35:813]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1312 
Fehler 1312. Das Verzeichnis C:\Windows\TEMP\mia2AE6.tmp\pCon.planner_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.
MSI (s) (80:6C) [16:09:35:813]: Note: 1: 2205 2:  3: Error 
MSI (s) (80:6C) [16:09:35:813]: Note: 1: 2228 2:  3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709 
MSI (s) (80:6C) [16:09:35:813]: Produkt: pCon.planner 6.4 -- Fehler 1312. Das Verzeichnis C:\Windows\TEMP\mia2AE6.tmp\pCon.planner_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.

Aktion beendet um 16:09:35: InstallFinalize. Rückgabewert 3.
MSI (s) (80:6C) [16:09:35:829]: User policy value 'DisableRollback' is 0
MSI (s) (80:6C) [16:09:35:829]: Machine policy value 'DisableRollback' is 0
MSI (s) (80:6C) [16:09:35:829]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1095860530,LangId=1033,Platform=0,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1)
MSI (s) (80:6C) [16:09:35:829]: Executing op: DialogInfo(Type=0,Argument=1033)
MSI (s) (80:6C) [16:09:35:829]: Executing op: DialogInfo(Type=1,Argument=pCon.planner 6.4)
MSI (s) (80:6C) [16:09:35:829]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Aktion wird rückgängig gemacht:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Sicherungsdateien werden entfernt,CleanupTemplate=Datei: [1])
MSI (s) (80:6C) [16:09:35:829]: Executing op: ActionStart(Name=CreateFolders,Description=Ordner werden erstellt,Template=Ordner: [1])
MSI (s) (80:6C) [16:09:35:829]: Executing op: ProductInfo(ProductKey={61FFF5E3-1D08-4F66-AC29-EF61963F2619},ProductName=pCon.planner 6.4,PackageName=pCon.planner_setup.msi,Language=1033,Version=100925441,Assignment=1,ObsoleteArg=0,,PackageMediaPath=\Windows\TEMP\mia2AE6.tmp\,PackageCode={F6B20F57-7502-4A83-84B4-99A321FAC175},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=2)
MSI (s) (80:6C) [16:09:35:829]: Executing op: FolderRemove(Folder=C:\Windows\TEMP\mia2AE6.tmp\pCon.planner_setup.exe\,Foreign=0)
MSI (s) (80:6C) [16:09:35:829]: Executing op: FolderCreate(Folder=C:\ProgramData\Microsoft\Windows\Start Menu\Programs\EasternGraphics\pCon.planner 6,Foreign=0,SecurityDescriptor=BinaryData,)
MSI (s) (80:6C) [16:09:35:829]: Executing op: FolderRemove(Folder=C:\ProgramData\Microsoft\Windows\Start Menu\Programs\EasternGraphics\pCon.planner 6,Foreign=0)
MSI (s) (80:6C) [16:09:35:845]: Note: 1: 2318 2: 

Sorry the message is in german but in general it is telling that the folder C:\Windows\TEMP\mia2AE6.tmp\<my-setup>.exe cannot be created because it is already existing.

Can this be prevented by setting ALLUSERS to TRUE as you have suggested?

Hi Alibaba,

We try here to build a setup and a automatic update for our software. I tryed it doing it from the template with a task, and i tryed with a windows service. Both i had no success. I am very frustrated. Maybe you can help us?

Hi psycodad,

what issues do you have exactly and furthermore what are you willing to pay?

I'm having this same issue with this product: http://www.epa.gov/nrmrl/wswrd/wq/model ... #Downloads

It is very frustrating to have a product not install silently using the SYSTEM account since that is how it is nearly always done in the enterprise and lab setting.

Dear User,

honestly, it is very frustrating to see that after all the time I spent with trying to describe how handle correctly an installation under SYSTEM account, there are still doubts about it.

Please have also a look at;
http://www.installaware.com/forum/viewt ... f=2&t=8783

Previously with this topic there is also a test package available;
http://www.installaware.com/forum/viewt ... 8&start=15

Regards

Sorry to dig up this old post but I am being affected by this issue and this thread does not really explain what the solution is (clearly).

From my understanding, installing from the SYSTEM account should work - you just have to make sure ALLUSERS is set to TRUE - is this correct?

My situation is that I wish to run the installer before anyone logs in to the PC. I have an app which runs on startup and therefore runs under the SYSTEM account. This app needs to execute the installer silently. So far when I execute the installer it fails with Error 1312 as in the original post. I cannot use PsExec to run as a user as that doesn't allow execution as a user from the system account. I have tried setting ALLUSERS to TRUE in the "Compiler Variables" section of Project Options. I am using InstallAware NX (we have InstallAware 18 but not converted this project to it yet).

Should my installer work, and what am I doing wrong?

Thanks in advance,
Graham

Dear Graham,

ALLUSERS is a SCRIPT variable and not a Compiler variable and you should try to force it to TRUE, at the very beginning of your main script.

Regards

FrancescoT wrote:Dear Graham,

ALLUSERS is a SCRIPT variable and not a Compiler variable and you should try to force it to TRUE, at the very beginning of your main script.

Regards

Could I also pass it in to the command line like?

setup.exe /s ALLUSERS=TRUE

Yes, you can do it!

Regards

Hi Francesco,

Unfortunately I still get the same error, so I guess it's something else in my script. Do you know if there's anything else I should be looking for?

Thanks,
Graham