@Hans Andersen Thanks for the update. Glad that you got the issue resolved.
It shows that it unable to find a resource file. If this works on other computers (or even the same computer but with a different Windows user login), then I still suspect that the ClickOnce location that IEE is downloaded to is corrupt. Can you try to clear it as explained previously?
Hi @Hans Andersen, Can you please click “View Detail” on the error dialog and share the complete error message? Thank you.
IEE is downloaded into a per-user profile via Microsoft functionality called ClickOnce. Most likely it has become corrupt. Please try to clear the cache and re-download IEE. There are two ways to do this:rundll32 dfshim CleanOnlineAppCache rd /s /q %localappdata%\Apps\2.0Option 1 is the preferred method. Only try the second if not successful. Be sure to close IEE before running either option.
Hi samirgergis, The DBCA template should be there as described. Here is a screen shot: Does your build home have a template folder such as below? Best regards,Ben
After a few more installations and little more investigation, I think I have identified two problems:The installer failure seems to be due to insufficient processing resources. More specifically, startup of the various WebLogic servers were taking more than 10 minutes at which point it simply timed out. Manually checking the WebLogic servers afterwards generally showed them as running. Even though the MWS server was configured for static IP, ipconfig shows “DNS Suffix Search List” and “Connection-specific DNS Suffix Search List” coming from the initial DHCP prior to setting a static IP. I could not find a way to clear these. (Note that the server is not in a LDAP domain.) As a result, when configuring the self-signed certificate the installer insists FQDN (and even warns when removed) for “Common Name”. Nevertheless, the Apache configuration files do not show FQDN.For (1), the resolution was to give the VM more CPU and memory.For (2), I was able to confirm two fixes. Ensure that FQDN
Hi @Ragaventhan Sathananda, Thank for the response.Indeed, checking the status with mws-svr.cmd shows that all components are RUNNING. As for the certificate, it used the self-signed option in the installer. (The VM is not joined to a domain.) Following installation I manually added it to Trusted Root Certification Authority on both the VM and a client PC. The browser no longer complains about the certificate (and shows the connection as secure). However, accessing the URL shows “Forbidden: You don't have permission to access / on this server.”Are there any special steps when installing using a self-signed certificate? Or do I need to join it to a AD domain? Would manually pre-generating a certificate via OpenSSL and using it during installation improve the situation?
IFS encryption uses the Blowfish/CBC/PKCS5Padding cipher.
Already have an account? Login
No account yet? Create an account
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.