- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Hi,
I have a problem with the standalone install for EG8.3.
Right now, we used the standard SDW installation for our EG-Installation.
We deploy software using DSM.
Now we wanted to move to the standalone installation, cause it is much faster and less error-prone.
Before we install, there is always a sasdm.exe -uninstallall to ensure a clean environment.
But now - we have a problem. The installation runs fine at the first run. But when I run the installation again - the uninstall seems to be frozen - till the timeout after about 2 hours.
Does -uninstallall not work for standalone-installations?
Accepted Solutions
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Got it solved. We hat the sasdm.exe and the setup.exe whitelisted to the virusscan but missed the Zulu java.exe.
After adding the java.exe to the whitelist, everything works fine
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
As per the guide that comes with the independent installer it says that the process of removing the software is different. You can read more about it under section "Appendix A — Independent Installation of SAS Products" -> sub section "Uninstallation"
http://support.sas.com/documentation/installcenter/en/ikdeploywizug/66034/PDF/default/user.pdf
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
We have successfully used the Windows Control Panel to remove the Software.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
@Kurt_Bremser yeah, I am sure that works, but I have to automate the (de)installation for ~800 ClientPCs. We have to use DSM for this.
How ever I did some further investigations:
The Uninstall is done, when SAS freezes. That means, the log says, EG is uninstalled and starts to cleanup the directory - but the java.exe (Zulu) stays running.
Seems like this is the problem.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Sounds like a problem for SAS Tech Support.
- Mark as New
- Bookmark
- Subscribe
- Mute
- RSS Feed
- Permalink
- Report Inappropriate Content
Got it solved. We hat the sasdm.exe and the setup.exe whitelisted to the virusscan but missed the Zulu java.exe.
After adding the java.exe to the whitelist, everything works fine