InstallAware package trying to install with this command:
setup.exe /s /l=c:\inst.log /ALL_USERS="TRUE"
Installing from SCCM as Administrator and User can interact we are receiving this error:
MSI (s) (BC:5C) [13:44:01:986]: Executing op: ActionStart(Name=CreateFolders,Description=Creating folders,Template=Folder: [1])
MSI (s) (BC:5C) [13:44:01:986]: Executing op: FolderCreate(Folder=\\serverName\DEPTAPPS\ALTERY~1.9\ALTERY~1.EXE\Alteryx 10.0 (User),Foreign=0,,)
MSI (s) (BC:5C) [13:44:01:986]: Note: 1: 1312 2: \\serverName\DEPTAPPS\ALTERY~1.9\ALTERY~1.EXE
MSI (s) (BC:5C) [13:44:02:002]: Note: 1: 2205 2: 3: Error
MSI (s) (BC:5C) [13:44:02:002]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1312
Error 1312. Cannot create the directory '\\serverName\DEPTAPPS\ALTERY~1.9\ALTERY~1.EXE'. A file with this name already exists. Please rename or remove the file and click retry, or click Cancel to exit.
MSI (s) (BC:5C) [13:44:02:002]: Note: 1: 2205 2: 3: Error
MSI (s) (BC:5C) [13:44:02:002]: Note: 1: 2228 2: 3: Error 4: SELECT `Message` FROM `Error` WHERE `Error` = 1709
MSI (s) (BC:5C) [13:44:02:002]: Product: Alteryx -- Error 1312. Cannot create the directory '\\serverName\apps$\DEPTAPPS\ALTERY~1.9\ALTERY~1.EXE'. A file with this name already exists. Please rename or remove the file and click retry, or click Cancel to exit.
Action ended 13:44:02: InstallFinalize. Return value 3.
Error still appears if copied from sever locally via script and if by SCCM.
I could get it to install by removing the .msi's CreateFolder Table and create folder structure for the Shortcut Table. But other problems cropped up like no files being installed
I do not use InstallAware. This is for SCCM deployment to multiple users. install has to be in System Context
Error 1312 When installing in SCCM
Re: Error 1312 When installing in SCCM
Anybody? A quick Google search determines that this is a standard problem with this product without a solution.
Additionally the command line of /TARGET_DIR="<path>" does not work. The vendor is of no help.
As stated before editing the .MSI and removing CreateFolder Table entries will allow the install to happen.
The problem at this point is that no files get installed. The windows installer registry entries shows that the product is installed.
We will be forced to reject the software if it cannot be installed by SCCM.
Additionally the command line of /TARGET_DIR="<path>" does not work. The vendor is of no help.
As stated before editing the .MSI and removing CreateFolder Table entries will allow the install to happen.
The problem at this point is that no files get installed. The windows installer registry entries shows that the product is installed.
We will be forced to reject the software if it cannot be installed by SCCM.
-
- Site Admin
- Posts: 5361
- Joined: Sun Aug 22, 2010 4:28 am
Re: Error 1312 When installing in SCCM
Dear Cygnusx1,
This forum is exclusively intended to those developers who use our tool to generate their setup packages.
Honestly I don't know from which online "bible" you found that "this is a standard problem with this product without a solution".
The InstallAware tool doesn't have any limitation to generate setup packages and to run them under System account context.
This is widely demonstrated by the dozen of topics about the "argument" present with this forum.
InstallAware is a development tool and as any other development tool, it's the developer that uses the tool "full" responsible on how the package code has been developed and implemented. We cannot be responsible for that and at the same time, we cannot modify, alter or replace something that we haven't developed.
That said and to close down the matter, you must contact the software vendor that released the setup package directly.
It's clear that exist a problem on how that package has been developed and released.
Finally you may try the following, instead of the one you used where the ALLUSERS pre-defined variable is misspelled.
- setup.exe /s /l=c:\inst.log ALLUSERS=TRUE
However the above command line example may not work correctly, if who released the package decided to assign or to control such variable's value at setup Runtime.
Regards
This forum is exclusively intended to those developers who use our tool to generate their setup packages.
Honestly I don't know from which online "bible" you found that "this is a standard problem with this product without a solution".
The InstallAware tool doesn't have any limitation to generate setup packages and to run them under System account context.
This is widely demonstrated by the dozen of topics about the "argument" present with this forum.
InstallAware is a development tool and as any other development tool, it's the developer that uses the tool "full" responsible on how the package code has been developed and implemented. We cannot be responsible for that and at the same time, we cannot modify, alter or replace something that we haven't developed.
That said and to close down the matter, you must contact the software vendor that released the setup package directly.
It's clear that exist a problem on how that package has been developed and released.
Finally you may try the following, instead of the one you used where the ALLUSERS pre-defined variable is misspelled.
- setup.exe /s /l=c:\inst.log ALLUSERS=TRUE
However the above command line example may not work correctly, if who released the package decided to assign or to control such variable's value at setup Runtime.
Regards
Francesco Toscano
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
InstallAware Software
White Papers (HowTos) - http://www.installaware.com/publication ... papers.htm
Publications - http://www.installaware.com/publications-review.htm
InstallAware Help -F1 anywhere in the InstallAware IDE
Who is online
Users browsing this forum: No registered users and 108 guests