- Revenera Community
- InstallShield Forum
- Error 1152: Error extracting Setup.INI to the temporary location - URGENT, CRITICAL
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Printer Friendly Page
Error 1152: Error extracting Setup.INI to the temporary location - URGENT, CRITICAL
Issue: While installing Windows application (which we develop), one of our user is seeing an error 1152: Error extracting Setup.INI to the temporary location – see attached screenshot for more information.
Observations: Our team has found out following so:
- When user experiences this issue, they can only install our Windows application from C:\Temp location. Our software’s default installation location is C:\Program Files (x86)\<Company's name>\.
- This was reported previously by 2 other users. That time since it was just limited, we asked user to install via C:\Temp location and it was working as good step 3 solution.
- Our team tried all resolution mentioned from various blogs on Google related with error 1152:
- Uninstall previous build and delete all application related files from machine.
- Did fresh installation of this Windows application
- Did Disk cleanup
- Tried to creating new Temp folder
None of above suggestions have worked so far. We are wanting to understand if there's a way to programmatically resolve this issue. If so, kindly share details at earliest convenience as it's impacting our ability to release our application in production.
Did you tried the suggestion in below KB article.
If you are seeing this issue for specific user or all users in that machine? If this issue happens for a specific user then verify the users has access to temp location.
Sorry for delay in responding!
We tried all the suggestions mentioned in KB article but are still seeing the issue.
Also, this machine on which we are seeing this issue is a corporate machine belonging to 1 user. Corporate admins can log in but we are unable to confirm if they are also seeing the issue as it's difficult for us to work with them to confirm this issue. We will have to have them try install this application with which we're seeing the issues.
Is there anything else which we can try at our end to resolve this issue programmatically? Is there a possibility to have a remote session with someone from Flexera?
Thank you for your assistance so far!
Also, if you check the error message, we are getting an error while extracting Setup.INI file to the temporary location.
Actually, we are speculating that there are other applications developed within our organizations which might also have Setup.INI as part of their installer and we think if that application did not get uninstalled correctly, it causing an issue with our application as even our application has Setup.INI. We believe this is default INI file which is included with every application installer.
What we were wondering: Is there a way to change name of Setup.INI (default) to <applicationname>Setup.INI (ex: ABCSetup.INI)? That way our application's Setup.INI filename will be unique and we won't see this conflict or error while extracting this INI file to temporary location. Do you think this will solve the issue? If so, can you let us know where to find this file within our *.ism file?
Are you able to see the same behavior with any project(meaning if you create a test project and install you will see the same behavior) sample will help us to understand its a issue with any project created with installshield or only with that specific installer.
Could you please navigate to Get Support > Open New Case in the top menu and open a new case, You can also raise a case with our Support Team about this issue, by email at firstname.lastname@example.org
Creating a support case will allow us to submit an issue request, if necessary, for tracking purposes. If you have a valid, active, unexpired technical support contract (maintenance plan).
Make sure on creating support case, you share all details like installation verbose log and machine OS details and issue happens for all user or any specific user and issue is reproducible with sample project or only specific to one installer.
Thanks for responding. We do not know how to create this error. So do you think creating test project will really help? What are we trying to achieve with this activity?
Do you still want us to proceed an open a support case?
Yes, case will help us to understand the issue in a better way with meetings.
Still you didnt confirm what is that machine OS? win10 0r server?
Are you able to reproduce the issue locally? Please confirm the details.
Issue is seen on Windows 10 machine. Not server. Yes, we are able to reproduce the issue locally.