ONTAP Discussions

7MTT Access not possible after installation

skellner
5,166 Views

I'm trying to run 7MTT on  a windows 2012 R2 Standard Server of my customer. The service is started but I can't access the tool in any browser. It says connection refused. In the server-console.log the following error message is logged. Can anybody help on this?

 

2016/10/21 11:09:34.769 | INFO   | jvm 1    | WrapperSimpleApp Error: Caused by: com.netapp.common.platform.JNIException: Zuordnungen von Kontennamen und Sicherheitskennungen wurden nicht durchgeführt.
2016/10/21 11:09:34.769 | INFO   | jvm 1    |
2016/10/21 11:09:34.769 | INFO   | jvm 1    | WrapperSimpleApp Error:     at com.netapp.common.platform.windows.FileSystemNativeImpl.setFileSecurityDescriptor(Native Method)
2016/10/21 11:09:34.769 | INFO   | jvm 1    | WrapperSimpleApp Error:     at com.netapp.common.platform.windows.OperatingSystemImpl.changeFileSecurity(OperatingSystemImpl.java:276)
2016/10/21 11:09:34.769 | INFO   | jvm 1    | WrapperSimpleApp Error:     ... 59 more
2016/10/21 11:09:34.769 | INFO   | jvm 1    | WrapperManager Debug: WrapperManager.stop(1) called by thread: WrapperSimpleAppMain
2016/10/21 11:09:34.769 | INFO   | jvm 1    | WrapperManager Debug: Send a packet STOP : 1
2016/10/21 11:09:34.769 | DEBUG  | wrapperp | read a packet STOP : 1
2016/10/21 11:09:34.769 | DEBUG  | wrapper  | JVM requested a shutdown. (1)
2016/10/21 11:09:34.769 | DEBUG  | wrapper  | wrapperStopProcess(1, FALSE) called.
2016/10/21 11:09:34.769 | DEBUG  | wrapper  | Sending stop signal to JVM
2016/10/21 11:09:34.769 | DEBUG  | wrapperp | send a packet STOP : NULL
2016/10/21 11:09:34.878 | INFO   | jvm 1    | WrapperManager Debug: Received a packet STOP :
2016/10/21 11:09:34.878 | INFO   | jvm 1    | WrapperManager Debug: Stopped checking for control events.
2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperManager Debug: Thread, WrapperSimpleAppMain, handling the shutdown process.
2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperManager Debug: calling listener.stop()
2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperSimpleApp Debug: stop(1)
2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperManager Debug: returned from listener.stop() -> 1
2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperManager Debug: shutdownJVM(1) Thread: WrapperSimpleAppMain
2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperManager Debug: wait for 0 shutdown locks to be released.
2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperManager Debug: Send a packet STOPPED : 1
2016/10/21 11:09:35.862 | DEBUG  | wrapperp | read a packet STOPPED : 1
2016/10/21 11:09:35.862 | DEBUG  | wrapper  | JVM signaled that it was stopped.
2016/10/21 11:09:36.081 | INFO   | jvm 1    | WrapperManager Debug: Closing backend connection.
2016/10/21 11:09:36.081 | INFO   | jvm 1    | WrapperManager Debug: Closed backend socket (Normal): java.net.SocketException: Socket closed
2016/10/21 11:09:36.081 | INFO   | jvm 1    | WrapperManager Debug: Returned from backend handler.
2016/10/21 11:09:36.081 | DEBUG  | wrapperp | socket read no code (closed?).
2016/10/21 11:09:36.081 | DEBUG  | wrapperp | closing backend socket.
2016/10/21 11:09:36.628 | INFO   | jvm 1    | WrapperManager Debug: Server daemon shut down
2016/10/21 11:09:36.628 | INFO   | jvm 1    | WrapperManager Debug: calling System.exit(1)
2016/10/21 11:09:37.066 | INFO   | jvm 1    | Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0
2016/10/21 11:09:37.066 | INFO   | jvm 1    | Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=196m; support was removed in 8.0
2016/10/21 11:09:37.175 | DEBUG  | wrapper  | JVM process exited with a code of 1, however the wrapper exit code was already 1.
2016/10/21 11:09:37.175 | DEBUG  | wrapper  | JVM exited normally.
2016/10/21 11:09:37.503 | STATUS | wrapper  | <-- Wrapper Stopped

 

4 REPLIES 4

hariprak
5,107 Views

Hi,

 

Can you check the compatability of Java version installed.

 

Thanks

 

 

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

skellner
5,104 Views

Meanwhile I got it working. The issue was related to a german W2K12. During startup of the service the following error message occured.

 

Error 1332: Zuordnungen von Kontennamen und Sicherheitskennungen wurden nicht durchgeführt

 

The workaround is to download the languagepack and install en-us as display language. However this is not sufficient. If you only enable the display language for your user it doesn't work either. You have to copy the language settings also to the welcome screen and other users. Then windows asks for a restart. When the server is booted the service for the transition tool is able to start without errors and you can access the tool with a browser.

 

 

 

hariprak
5,101 Views

Good to know the issue got fixed.

If this post resolved your issue, help others by selecting ACCEPT AS SOLUTION or adding a KUDO.

UweRoosAvnet
4,071 Views

The problem is unfortunately still existing in the 2018 release (7MTT 3.3.1). 

 

With the german language package I tried Windows Server 2012 and 2008 without success (the 7MTT service stopped immedeately after starting it). Only to switch completely to english language pack (as described from skellner) worked for us.

 

This makes it hard to use the tool in germany, as most customers use german version!!

 

Public