Re: Can’t reset VNXe3100 admin password

Capture.PNG.pngHi All,

I have a problem that is starting to drive me crazy.

We have a VNXe3100, that is working fine, has had more disks added, and I need to login to the admin interface to configure them.

Unfortunately, no one has logged into it in some time, and the admin credentials we have documented seem to be wrong.

I’ve gone ahead and pressed the password reset button on the back of one of the controllers, and logged into the gui ok with admin/Password123#

The first thing it does is bring up a window asking me to change the password, that is put in and once ok is clicked, displays “Configuring new passwords”

and there it stays. Forever…

Now, even though it doesn’t change the admin password, it DOES change the service password, as I can then SSH into it using the new credentials for the service account.

I noticed that the red asterisks next to the service account old and new password fields disappear a few seconds after hitting OK, but don’t do so for the admin account.

I tried to change the admin password using the UEMCLI, but it just says “You have to change the administrator password in order to perform this action”

Short of completely initializing the system back to factory defaults and losing 5TB of data, is there a way to get around it ?

(maybe the config file on a USB stick used to manually reset the ip address ? )



  • No Related Posts

7022347: “No Reflection content has been assigned to you” Message When Using the Administrative WebStation

“No Reflection Content Has Been Assigned To You”

Typically, the message “No Reflection content has been assigned to you” indicates that no sessions have been mapped to a user who is attempting to access Reflection for the Web or Reflection Security Gateway. However, if this message occurs when you are accessing components within the Administrative WebStation, the problem is that cookies are being blocked. This may occur because:

  • The browser is configured to block cookies.
  • The URL contains non-DNS-supported characters in the name of the machine serving the Administrative WebStation (Microsoft Internet Explorer only).

Follow the instructions in the sections below to troubleshoot this problem.

Browser Configured to Block Cookies

A per-session cookie is accepted onto the client computer. (Per-session cookies are deleted when the browser is closed.) If you encounter the problem described above, check your browser’s settings for cookies. Follow the instructions in your browser’s Help file to enable cookies (or, at a minimum, enable per-session cookies).

Note: If you use a language version of Reflection for the Web that differs from the locale of your operating system, enable cookies to be stored on your computer so that your language choice persists.

Non-DNS-Supported Characters in Server Name

After applying Microsoft’s cumulative patch Q319182 or higher for Internet Explorer, cookies are blocked if a server name used in a URL contains non-DNS-supported characters. For more information about cumulative patch Q319182, see the following Microsoft Knowledge Base article:;en-us;Q319182

DNS-supported characters include the following:

  • The letters A through Z (upper and lower case)
  • The numerals 0 through 9
  • The minus sign [ – ]
  • The period [ . ]

Note: The minus sign and period cannot be used at the end of a domain name.

No characters other than those listed above are DNS-supported. (For example, the underscore, [ _ ] the exclamation mark, [ ! ] and the blank space in the server name are not DNS-supported.)

Using tools in the Administrative WebStation requires a per-session cookie. Therefore, accessing these components will fail if you are using Internet Explorer patched with Q319182 or higher and the web server name contains non-DNS-supported characters. The message “No Reflection content has been assigned to you” will be displayed.

Note: Cookies are also used to store information about the language version of Reflection for the Web or Reflection Security Gateway that you use. If you use a language version that differs from the locale of your operating system, this problem may interfere with your language choice persisting.


There are several ways to work around this problem:

  • In the URL you use to access the WebStation, enter the IP address of the web server instead of the name. Note: you will see an alert that the server name on the SSL security certificate does not match the name used to access the site. You can safely bypass this alert.
  • If you are launching the Administrative WebStation from the same machine where it is installed, replace the web server name in the URL with “localhost” to avoid using non-DNS-supported characters.
  • Rename the web server to eliminate the non-DNS-supported characters.


  • No Related Posts

smc.exe -p

I need a solution


I am trying to stop SEP with the following command line: smc.exe -p <password> -stop

But that command is not doing anything. When I try without the -p parameter the password prompt pops up and SEP is stopped after entering the right password.

When I enable smc debug log i get following entries in the logfile:

2018/03/08 15:02:29.005 [10644:10640] Entering the command line handler
2018/03/08 15:02:29.005 [10644:10640] Service request event handle: 000002AC
2018/03/08 15:02:29.005 [10644:10640] Sending CLCMD_STOPSERVICE_PASSWORD command
2018/03/08 15:02:29.021 [10644:10684] In CStatusSessionIpcHandler::OnSessionUpdateStatus.
2018/03/08 15:01:57.981 [10664:10684] eGMEStopPasswordEvent: Command line stop requested but no password supplied
2018/03/08 15:02:29.021 [10644:10684] CStatusSessionIpcHandler::OnSessionUpdateStatus: user input wrong passwd on command line.
2018/03/08 15:02:29.036 [10644:10640] Command line request completed
2018/03/08 15:02:29.036 [10644:10640] Smc password verification failed.
2018/03/08 15:02:29.036 [10644:10640] Command line has been handled

I have triple checked that the password is correct, and i also DID provide a password

This problem seems to be in SEP 14 RU1 and SEP 14 RU1 MP1.

Tested on Windows 10 and Windows 7.

Has anyone a resolution for this problem?



  • No Related Posts

ATP3.0-Splunk Event Forwarding

I need a solution


I set up ATP Endpooint3.0 and Splunk6.6, but it does not work.

There is no data at dashboard except for “Open Incidents”.

What should I do to display data in other areas?


I did..

-Splunk Settings

  -install Symantec ATP App for Splunk
  -install Symantec ATP Add-on for Splunk 
  -setting HTTP Event Collector

-ATP Settings

  -Splunk Event Forwarding settings
  -OAuth Clients settings



  • No Related Posts

3004130: “LDAP: error code 17” or blank page viewing SecureLogin applications

This document (3004130) is provided subject to the disclaimer at the end of this document.


NetIQ SecureLogin 8.x
NetIQ SecureLogin 7.x
Novell SecureLogin 6.0 (NSL 6)
eDirectory data store
iManager plugin


– Unable to administer SecureLogin through iManager

– SecureLogin iManager plugin shows no applications

– When trying to administer SecureLogin through iManager the following error is returned:

“There was an error writing data to LDAP. ([LDAP: error code 17 – Undefined Attribute Type])”


Extend the ldap schema for SecureLogin for every LDAP group in the tree

Schema mappings are LDAP group specific; perform the steps below for each LDAP group. Note that by default every LDAP server will be in its own LDAP group, so by default the following steps will need to be performed for each LDAP server.

1. From the installation files for SecureLogin run SecureLoginToolsldapschema.exe

2. Provide the IP address for the desired LDAP Server.
3. Login with the fully distinguished username that has rights to extend the schema (cn=admin,o=novell)
4. Click “Update Schema” look for any possible error messages in the status window.

Additional Information


In the eDirectory tree by defualt LDAP servers will be a part of their own LDAP Group object. The LDAP Group object is what will recieve the LDAP schema attribute mapping.

This means that if you extend the schema pointing to a LDAP server that is a member of LDAP Group A and then you run iManager against a server that is a member of LDAP Group B, it is possible that you will still receive the error “LDAP: error code 17” .

To avoid this either extend the LDAP schema against all servers that could be used for NSL administration or make the respective servers part of the same LDAP Group.

To be able to administer settings on a global level for a NSL 6 or 7 environment, the LDAP schema must be extended even if the NSL clients are not connecting over LDAP. It is required for communication with iManager.

To verify that this is the problem, look at the ldap schema for the LDAP group. In iManager, open the LDAP plugin and select LDAP Options, and pick the LDAP group the problem server is in. Then go to the Attribute Map tab, and look for the Prot: attributes. An eDirectory Attribute and a Primary LDAP attribute should be visible for each of the six SecureLogin attrbues. These all begin with Prot: SSO, as shown in the screen shot below. If these attributes are not present, run LDAPSchema.exe as described in the resolution section of this document.


This Support Knowledgebase provides a valuable tool for NetIQ/Novell/SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented “AS IS” WITHOUT WARRANTY OF ANY KIND.


  • No Related Posts