Skip to main content
NetApp Knowledge Base

SMO Service won't start due to Java error after update to 3.4.2P4

  1. Last updated
  2. Save as PDF
Views:
184
Visibility:
Public
Votes:
5
Category:
snapmanager-for-oracle
Specialty:
legacy
Last Updated:

Applies to

SnapManager for Oracle (SMO) 4.3.2

Issue

Error: SMO-01501: Error occurred while attempting to start the SnapManager Windows Service: Could not initialize classjavax.crypto.JceSecurity

SMSAP-01501: Error occurred while attempting to start the SnapManager Windows Service: Could not initialize class
javax.crypto.JceSecurity

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.