topic Re: 7MTT Access not possible after installation in ONTAP Discussions

topic Re: 7MTT Access not possible after installation in ONTAP Discussions https://community.netapp.com/t5/ONTAP-Discussions/7MTT-Access-not-possible-after-installation/m-p/124680#M26809 <P>Hi,</P><P> </P><P>Can you check the compatability of Java version installed.</P><P> </P><P>Thanks</P><P> </P><P> </P> Tue, 25 Oct 2016 10:24:02 GMT hariprak 2016-10-25T10:24:02Z 7MTT Access not possible after installation https://community.netapp.com/t5/ONTAP-Discussions/7MTT-Access-not-possible-after-installation/m-p/124528#M26748 <P>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?</P><P> </P><P>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.<BR />2016/10/21 11:09:34.769 | INFO   | jvm 1    |<BR />2016/10/21 11:09:34.769 | INFO   | jvm 1    | WrapperSimpleApp Error:     at com.netapp.common.platform.windows.FileSystemNativeImpl.setFileSecurityDescriptor(Native Method)<BR />2016/10/21 11:09:34.769 | INFO   | jvm 1    | WrapperSimpleApp Error:     at com.netapp.common.platform.windows.OperatingSystemImpl.changeFileSecurity(OperatingSystemImpl.java:276)<BR />2016/10/21 11:09:34.769 | INFO   | jvm 1    | WrapperSimpleApp Error:     ... 59 more<BR />2016/10/21 11:09:34.769 | INFO   | jvm 1    | WrapperManager Debug: WrapperManager.stop(1) called by thread: WrapperSimpleAppMain<BR />2016/10/21 11:09:34.769 | INFO   | jvm 1    | WrapperManager Debug: Send a packet STOP : 1<BR />2016/10/21 11:09:34.769 | DEBUG  | wrapperp | read a packet STOP : 1<BR />2016/10/21 11:09:34.769 | DEBUG  | wrapper  | JVM requested a shutdown. (1)<BR />2016/10/21 11:09:34.769 | DEBUG  | wrapper  | wrapperStopProcess(1, FALSE) called.<BR />2016/10/21 11:09:34.769 | DEBUG  | wrapper  | Sending stop signal to JVM<BR />2016/10/21 11:09:34.769 | DEBUG  | wrapperp | send a packet STOP : NULL<BR />2016/10/21 11:09:34.878 | INFO   | jvm 1    | WrapperManager Debug: Received a packet STOP :<BR />2016/10/21 11:09:34.878 | INFO   | jvm 1    | WrapperManager Debug: Stopped checking for control events.<BR />2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperManager Debug: Thread, WrapperSimpleAppMain, handling the shutdown process.<BR />2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperManager Debug: calling listener.stop()<BR />2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperSimpleApp Debug: stop(1)<BR />2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperManager Debug: returned from listener.stop() -> 1<BR />2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperManager Debug: shutdownJVM(1) Thread: WrapperSimpleAppMain<BR />2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperManager Debug: wait for 0 shutdown locks to be released.<BR />2016/10/21 11:09:35.862 | INFO   | jvm 1    | WrapperManager Debug: Send a packet STOPPED : 1<BR />2016/10/21 11:09:35.862 | DEBUG  | wrapperp | read a packet STOPPED : 1<BR />2016/10/21 11:09:35.862 | DEBUG  | wrapper  | JVM signaled that it was stopped.<BR />2016/10/21 11:09:36.081 | INFO   | jvm 1    | WrapperManager Debug: Closing backend connection.<BR />2016/10/21 11:09:36.081 | INFO   | jvm 1    | WrapperManager Debug: Closed backend socket (Normal): java.net.SocketException: Socket closed<BR />2016/10/21 11:09:36.081 | INFO   | jvm 1    | WrapperManager Debug: Returned from backend handler.<BR />2016/10/21 11:09:36.081 | DEBUG  | wrapperp | socket read no code (closed?).<BR />2016/10/21 11:09:36.081 | DEBUG  | wrapperp | closing backend socket.<BR />2016/10/21 11:09:36.628 | INFO   | jvm 1    | WrapperManager Debug: Server daemon shut down<BR />2016/10/21 11:09:36.628 | INFO   | jvm 1    | WrapperManager Debug: calling System.exit(1)<BR />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<BR />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<BR />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.<BR />2016/10/21 11:09:37.175 | DEBUG  | wrapper  | JVM exited normally.<BR />2016/10/21 11:09:37.503 | STATUS | wrapper  | <-- Wrapper Stopped</P><P> </P> Fri, 21 Oct 2016 09:24:03 GMT https://community.netapp.com/t5/ONTAP-Discussions/7MTT-Access-not-possible-after-installation/m-p/124528#M26748 skellner 2016-10-21T09:24:03Z Re: 7MTT Access not possible after installation https://community.netapp.com/t5/ONTAP-Discussions/7MTT-Access-not-possible-after-installation/m-p/124680#M26809 <P>Hi,</P><P> </P><P>Can you check the compatability of Java version installed.</P><P> </P><P>Thanks</P><P> </P><P> </P> Tue, 25 Oct 2016 10:24:02 GMT https://community.netapp.com/t5/ONTAP-Discussions/7MTT-Access-not-possible-after-installation/m-p/124680#M26809 hariprak 2016-10-25T10:24:02Z Re: 7MTT Access not possible after installation https://community.netapp.com/t5/ONTAP-Discussions/7MTT-Access-not-possible-after-installation/m-p/124684#M26813 <P>Meanwhile I got it working. The issue was related to a german W2K12. During startup of the service the following error message occured.</P><P> </P><P><SPAN><FONT size="2" face="Calibri,sans-serif"><SPAN><FONT color="red">Error 1332: Zuordnungen von Kontennamen und Sicherheitskennungen wurden nicht durchgeführt</FONT></SPAN></FONT></SPAN></P><P> </P><P>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.</P><P> </P><P> </P><P> </P> Tue, 25 Oct 2016 10:51:39 GMT https://community.netapp.com/t5/ONTAP-Discussions/7MTT-Access-not-possible-after-installation/m-p/124684#M26813 skellner 2016-10-25T10:51:39Z Re: 7MTT Access not possible after installation https://community.netapp.com/t5/ONTAP-Discussions/7MTT-Access-not-possible-after-installation/m-p/124686#M26814 <P>Good to know the issue got fixed.</P> Tue, 25 Oct 2016 10:55:56 GMT https://community.netapp.com/t5/ONTAP-Discussions/7MTT-Access-not-possible-after-installation/m-p/124686#M26814 hariprak 2016-10-25T10:55:56Z Re: 7MTT Access not possible after installation https://community.netapp.com/t5/ONTAP-Discussions/7MTT-Access-not-possible-after-installation/m-p/142906#M31713 <P>The problem is unfortunately still existing in the 2018 release (7MTT 3.3.1). </P> <P> </P> <P>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.</P> <P> </P> <P>This makes it hard to use the tool in germany, as most customers use german version!!</P> <P> </P> Mon, 24 Sep 2018 10:59:16 GMT https://community.netapp.com/t5/ONTAP-Discussions/7MTT-Access-not-possible-after-installation/m-p/142906#M31713 UweRoosAvnet 2018-09-24T10:59:16Z