August 22, 2018 at 6:05 pmttinkerSubscriber
I am attempting to create a silent installation of AnsysEM 19.1, to install on Windows 10. I have gone through the process of creating the response file, and copied it to the AnsysEM folder in the install media. However, when I push the software out via a script, or just run a command and point to the setup.exe and the .iss file, the installation fails. It goes through the entire process of installing, but at the end, it deletes all of the subfolders from the C:Program FilesAnsysEM directory, except for the admin folder.
Any guidance is much appreciated.
August 22, 2018 at 6:55 pmtsiriaksAnsys Employee
Do you have any space after -f1 or -f2 flags ?
They must not have space , for example
setup.exe -s -f1response_file.iss -f2log_file.log
However, the fact that it goes through the install might indicate that you have the silent command correctly. Please check if you have any kind of software that 'restore' the state of the machine (check with IT if you are not sure). Also, check if you have enough disk space on that directory.
Does it provide any error message ?
August 22, 2018 at 8:24 pmttinkerSubscriber
Thank you for the quick reply. I do not have any spaces in the command, after -f1 or -f2. We do not have any restore software on these machines either. There is also plenty of disk space available (400GB free).
When I run the install from our script, I get the following exit code:
- Exit code: -2147213312
When I run the command straight from the AnsysEM directory, setup.exe -s -f1response_file.iss -f2log_file.log
Running the install either way, results in the same thing...after it finishes installing, it deletes all of the folders under C:Program FilesAnsysEM, except for .admin. During the installation, I can see that the other folders are populating in Program Files.
August 22, 2018 at 10:41 pmtsiriaksAnsys Employee
Just for a kick, can you try this on one of the machines and see if it helps ?
Inside the Electronics package, go into 'Prerequisites' folder and manually install all prerequisites one-by-one (except for those related to MPI), then reboot the machine and try silent install.
If this helps, you are experiencing a similar issue with installing prerequisites as stated here
August 23, 2018 at 3:12 pmttinkerSubscriber
All of the prerequisites, besides the MPIs, are installed. Just for the heck of it, I ran through them all and had the executable repair the installations...just in case. Then I restarted the machine and ran the setup. Same issue happened again, after that. Would you like me to attach the response file? I can just redact the name of the server used for the network license.
August 23, 2018 at 3:53 pmMangesh BhideAnsys Employee
Can you please post a screenshot of your .iss file
August 23, 2018 at 3:57 pmtsiriaksAnsys Employee
Yes, please copy and paste the content of the response file in the post.
August 23, 2018 at 4:23 pmttinkerSubscriber
August 23, 2018 at 4:55 pmtsiriaksAnsys Employee
During the silent installation, do you see anything being written to C:UsersPublicAppDataLocalTemp ?
August 23, 2018 at 5:18 pmttinkerSubscriber
No, nothing gets copied to that directory while it is trying to install.
August 23, 2018 at 6:24 pmtsiriaksAnsys Employee
Check if that path is accessible and writable
Also, on this line
Not sure why your response file doesn't specify the name of the license server. Please replace
withthe correct license server name
August 23, 2018 at 6:29 pmttinkerSubscriber
I just redacted the license server name, but it's correct in our .iss file. I have admin access to that temp path on all machine that it will be installed on. I can try a different path, however...just in case.
August 23, 2018 at 6:47 pmttinkerSubscriber
I ended up changing it to a folder that all users have write access in, but it still failed to install.
August 23, 2018 at 7:18 pmtsiriaksAnsys Employee
That would be a good test.
Also try temporarily disable all anti-virus software or any security stuff on the machine and make sure that you issue the silent install command in an elevated CMD Prompt
August 23, 2018 at 7:28 pmtsiriaksAnsys Employee
I forgot to emphasize that before each attempt to rerun the silent install, please remove this folder C:Program FilesAnsysEM that got created
August 23, 2018 at 7:36 pmttinkerSubscriber
Oh yea, I've been removing that folder and running from elevated cmd. Unfortunately, we do not have the rights to disable the anti-virus on the domain machines, but I can try on a machine that's not on the domain, as a test.
August 23, 2018 at 7:40 pmtsiriaksAnsys Employee
Thank you for the information.
Please let us know how it goes on the machine without the AV.
I have verified that you response file content is exactly correct.
August 24, 2018 at 4:13 pmtsiriaksAnsys Employee
If that doesn't help, I have heard another suggestion from my colleague
before attempting another silent install , wipe %temp% and C:UsersPublicAppDataLocalTemp
also, see if there is any log file created from f2 flag. Please specify the absolute path like setup.exe -s -f1response_file.iss -f2"C:Templog_file.log"
August 27, 2018 at 6:26 pmttinkerSubscriber
Thank you for the suggestions. I was able to get it silently installed on a couple non-domain-joined machines. One was freshly imaged, and was unable to install while joined, but as soon as I took it off the domain, I was able to install using the script. I forgot to disable the AV, but it still ended up working. Not sure exactly what is causing this issue. I understand it is now our problem since something with the domain seems to be preventing the install, but have y'all come across something like this before?
August 27, 2018 at 9:12 pmtsiriaksAnsys Employee
Thank you for the info. I'm also not sure what happened. Let's see if others have any thoughts on this.
One thing that can help us narrowing down the issue is, can you try (on one machine that's not working with silent install while on domain) installing it using the GUI ?
If it works, it means there is some 'response' difference during the installation between on and off domain.
If it doesn't work, something is really preventing it while it's connecting to domain.
August 27, 2018 at 9:17 pmdsurendrAnsys Employee
Adding the system to a Domain would introduce Group/User policies that are set to that Domain users.
This could have affected the install due to some user permissions that are restricted/missing.
You can check your User/Group permissions of your Domain through the Active Directory setup.
August 27, 2018 at 9:58 pmttinkerSubscriber
Installing through the GUI works just fine on domain computers. The domain user account is also a local admin on these machines. We did not run into any issues like this when installing ANSYS 19.1, just with the Electromagnetic software.
August 28, 2018 at 12:12 amtsiriaksAnsys Employee
In that case, can you compare every step that you click on the installation wizard between on domain and off domain machines, because the response file has to match exactly.
I'm still wondering about this C:UsersPublicAppDataLocalTemp , is there any difference in term of permission when on/off domain ? Is your default %temp% the same when you are on and off domain ?
August 28, 2018 at 3:42 pmttinkerSubscriber
I set that temp folder during the manual install, when I was first creating the response file. The default %temp% was the same for on/off domain machines, which would have been my user's AppDataLocalTemp directory. I have tried both paths, along with just pointing the temp location to the public documents directory. Still no luck.
August 28, 2018 at 9:11 pmtsiriaksAnsys Employee
Not sure if you have tried this, but there is a similar issue in this thread
Can you try specify the full path for everything ?
setup.exe -s -f1"C:tempresponse_file.iss" -f2"C:templog_file.log"
ELECTRONICS_191_WINX64Electronics_191_winx64AnsysEMsetup.exe" -s -f1"C:tempresponse_file.iss" -f2"C:templog_file.log"
August 30, 2018 at 12:35 pmSteve DelAnsys Employee
The -3 error means that something is missing from your .iss file. Since you are able to install interactively, I would suggest recording an iss file on the machine if you haven't tried this yet:
setup.exe -r -f1c:tempansysem_interactive.iss
Once it's done installing, you can look at the newly-created iss file and see what differences there are. You may also be able to use the recorded iss file to install on other machines.
August 30, 2018 at 12:49 pmttinkerSubscriber
When running the install from the command prompt, I do use the entire path for -f1 and -f2.
The .iss file, that I pasted above, has been reviewed, and they said there didn't look to be anything wrong with it. I have also tried to create the .iss on multiple computers, with the same results after pushing out via command/script. The silent install will only work on the machine, on which I created the .iss file. If I try to push to a new computer, it immediately deletes all of the directories from the C:Program Files, except for the .admin directory. I will try to create the .iss file on a machine in our lab OU, since most of the computers that we push out to are in that same OU.
August 30, 2018 at 1:19 pmttinkerSubscriber
Also, the machines I have tested on before did not have ANSYS installed on them. I am now trying to create the response file on a machine that has ANSYS installed, and selecting yes to the integration step...just in case that makes any difference.
August 30, 2018 at 3:32 pmttinkerSubscriber
May have FINALLY gotten the silent install working, though I'm not sure if it has to do with pushing it to our lab computers in the same OU or enabling the ANSYS 19.1 integration step. Those are the only things that are different between this .iss file and the old one. I created the .iss file on a lab machine that had ANSYS 19.1 installed, so that allowed me to enable the integration. I have pushed it to multiple lab computers, without any issues as of yet. Thank you for all of your suggestions.
August 30, 2018 at 4:04 pmtsiriaksAnsys Employee
Thank you for the update. So, you meant the issue is with the difference in a prompt that asks if we want to integrate AEDT with ANSYS ?
There should be something else too. This doesn't explain why the response file works when you take the same machine out of domain.
August 30, 2018 at 4:18 pmttinkerSubscriber
Yea, I'm not sure if that was the difference, or the fact that our lab machines are in the same OU and creating the response file on a lab machine did the trick...if the reason for the previous install failures was a group policy issue.
August 30, 2018 at 5:13 pmtsiriaksAnsys Employee
Yes, right. Should be something related to group policy that creates some differences and ultimately makes recorded response file to be invalid.
- You must be logged in to reply to this topic.
Earth Rescue – An Ansys Online Series
The climate crisis is here. But so is the human ingenuity to fight it. Earth Rescue reveals what visionary companies are doing today to engineer radical new ideas in the fight against climate change. Click here to watch the first episode.
Subscribe to the Ansys Blog to get great new content about the power of simulation delivered right to your email on a weekly basis. With content from Ansys experts, partners and customers you will learn about product development advances, thought leadership and trends and tips to better use Ansys tools. Sign up here.
- Error with workbench SceneGraphChart
- Workbench error
- Workbench not opening
- How can I renew ANSYS student version license?
- License Error
- Sizing on Ansys Workbench 19.2
- Error: Exception of type ‘Ansys.Fluent.Cortex.Cortex not availableException’ was thrown
- Licensing error while opening ANSYS Mechanical
- An error occurred when the post processor attempted to load a specific result.
- Problem with FlexNet Licensing
© 2023 Copyright ANSYS, Inc. All rights reserved.