Archive

Archive for December, 2014

[Error] mod_ossl: Failed to open the wallet [Hint: incorrect path, incorrect password, bad wallet, …]

PURPOSE:
1. Oracle HTTP Server (OHS) is configured for SSL.
2. When attempting to start OHS via “opmnctl” it fails with the following errors:

Error –> Process (index=1,uid=216625458,pid=7403) failed to start a managed process after the maximum retry limit
Log:
$ORACLE_HOME\opmn\logs\HTTP_Server~1

3. The following errors can be seen in the $ORACLE_HOME\Apache\Apache\error_log:

[error] mod_ossl: Init: SSL call to NZ function nzos_OpenWallet failed with error 28759 (Server host.domain:4443, wallet file:c:\WALLETS)
[error] mod_ossl: Failed to open the wallet [Hint: incorrect path, incorrect password, bad wallet, ...]

CAUSE:
1.”SSLWallet” is not pointing at the correct Wallet location.
2. Auto-Login is not checked in the Wallet.
3. The oracle user does not have the permission to access the wallet files (ewallet.p12 and cwallet.sso).
4. This issue may also occur if the user used to start OHS is not same as the user who installed Oracle Application Server in the first place. In this case, this user may not have not the proper permission to access the wallet files.

SOLUTION:
1. Open the $ORACLE_HOME\Apache\Apache\conf\ssl.conf. Check the SSLWallet directive points to the correct Wallet:

SSLWallet file:/<wallet_location>

2. As the oracle user, start Wallet Manager, and open the Wallet at the above location. Make sure “Auto-Login” is checked, and save.
3. Check the ownership and permissions on the wallet files (cwallet.sso and ewallet.p12) at the above location. Check that they are owned by the owner of the ORACLE_HOME\Apache\Apache\bin\httpd processes. If you don’t want to bother with ownership and permission give “Everyone” full permissions to those two files.
4. Start OHS and test you can now access via HTTPS.

How to upgrade SQL Server Exress.

Few days ago I spend almost all day trying to upgrade SQL Server Express. And I mean – not uninstall and install again – just upgrade. In may case I wanted to upgrade SQL Server Express 2005 to SP4 but it should also work with other SQL Server Express editions. Here is how you can upgrade your SQL Server Express:
1. Download the SQLEXPR file. Yes, I know it doesn’t seem to suggest just the SP. Do it anyway.
2. I would suggest storing it on the root of the SQL box you’re trying to upgrade, or maybe in C:\TMP like I usually do (makes for easier typing, here in a minute…).
3. Log onto that box, run CMD.exe as “Run As Administrator”.
4. Navigate to where you stored the Download in Step 1.
5. Copy and paste this whole line at the Command Prompt:

SQLEXPR.exe /qb UPGRADE=SQL_Engine,SQL_Data_Files,Client_Components,Connectivity INSTANCENAME=YOUR_SQL_INSTANCE_NAME

6. The Setup will launch. It’s only going to upgrade the necessary components, so just follow the prompts.
7. When it’s done, you’ll be back at the Command window. Exit.
8. To confirm the upgrade, log into the Management Studio, launch a new Query, and paste this command into the Query window, precisely as you see it here, no changes:

select serverproperty('PRODUCTLEVEL') as sql_product_level

9. Then click the “Execute” button, and in a few seconds, in a small area near the bottom of the Query window, you’ll see the version.

I hope this helps someone else who wasted time scouring the Internet for this information.