CreateControlInterface Failed in SAP Management console

[Former Member]

Hello,

I am trying to perform a Netweaver 7.4 install on Suse Linux and getting an error. The install finishes without issue and everything looks fine and dandy. But when I try to start the SAP Management Console I get an error saying CreateControlInterface failed. I googled around but couldn't find a resolution to the problem. This is the error:

java.lang.NullPointerException

          at com.sap.managementconsole.common.DataLoader.createControlInterface(DataLoader.java:440)

          at com.sap.managementconsole.common.DataLoader.startup(DataLoader.java:342)

          at com.sap.managementconsole.common.DataLoader.access$400(DataLoader.java:74)

          at com.sap.managementconsole.common.DataLoader$2.execute(DataLoader.java:604)

          at com.sap.managementconsole.operations.AuthorizedOperation.execute(AuthorizedOperation.java:59)

          at com.sap.managementconsole.common.DataLoader.reinitialize(DataLoader.java:616)

          at com.sap.managementconsole.common.ThreadPoolDataLoader$2.execute(ThreadPoolDataLoader.java:102)

          at com.sap.managementconsole.common.DataLoader.executeAllQueuedOperations(DataLoader.java:707)

          at com.sap.managementconsole.common.ThreadPoolDataLoader$DataLoaderTask.execute(ThreadPoolDataLoader.java:127)

          at com.sap.managementconsole.common.ThreadPoolManager$ThreadPoolElement.run(ThreadPoolManager.java:282)

          at java.lang.Thread.run(Unknown Source)

Any ideas?

[Former Member · Accepted solution]

I am not quite sure but as per Note 1153713 - Problems with SAP Management Console (Java)

This comes only in SAP MC with Java 1.7 Update 45 and I am facing the same..This is JRE issue and downgrading won't help?

I tried myself by lowering the JRE to 17 and MMC J worked.

[Former Member · Accepted solution]

JRE 7u40 fixed the issue for me as well. Apparently this is a common issue. Oracle has started to enforce certain security practices that were started with JRE 7's release. Now that they are enforced, everyone is scrambling to update their code.

[christian_schwarzenberger]

Hello Ryan,

I'm from the SAPMC development team and the solution to your problem is the following:

Update your SAPMC to the latest available version for your release (721 in your case ?)

The note 1153713 is not complete and shows the latest 720 version numbers only.

I'm going to change that in the future and list the latest versions for all releases.

You may also see note 1014480 on how to update the SAPMC.

With the latest SAPMC version you should have no problems. If you still encounter the error, please open a CSN message on component BC-CCM-MC.

By the way: The thread http://scn.sap.com/thread/3351531

is completely wrong in my opinion. Please ignore it.

Regards,

Christian

[Former Member]

Hi Christian,

Sorry for the late response. The answer ended up being my jre version. Downgrading form 7u45 to 7u40 fixed the issue. Nothing else solved the problem at the time that I was having it.

Ryan

[christian_schwarzenberger]

Hello Ryan,

Downgrading your JRE is merely a workaround. As Jason already stated, Oracle enforced these security changes in the last patches not without reason.

From the security point of view it is completely viable to not execute unsigned applets which cannot be trusted.

The real fix was done in SAPMC in the last weeks and is available now on Service Marketplace.

Our recommendation is to use the latest JRE together with the lastest SAPMC!

Best Regards,

Christian

[former_member45419]

Hi Ryan,

pls check this threads..

http://scn.sap.com/thread/3351531

Regards

Nayeem

[Former Member]

Hi ,

Check if dispatcher or web dispatcher is running properly.

Further paste dev_icm logs

Regards

Ram

[Former Member]

Hello Ryan,

I've found a fix... see OSS Note http://service.sap.com/sap/support/notes/1153713 (you will need to switch to German as the English version is not up to date). 

The fix is to download the latest 720 kernel version of the SAPMC.  I have a 721_EXT Kernel installed and it seems that even updating to the latest SAPMC library from that kernel does not fix the issue... you will need to go to http://service.sap.com/swdc --> Support Packages and Patches --> Browse our Download Catalog --> Additional Components --> SAP Kernel --> SAP KERNEL 64-BIT UNICODE --> SAP KERNEL 7.20 64-BIT UNICODE.  Select your operating system and then choose Database Independent.  Download the "sapmc_516" SAR file and then update your SAP Kernel accordingly.

After restarting your system, you should be able to use the SAP MC again without any issues.

Hope this helps resolve your issue.

Cheers,

Steve

[Former Member]

Will try and get back to you.

Edit: unfortunately after install and restart I have the same issues.

[manish_singh13]

Hi,

This is very new and unique error you are getting. I looked up and found some additional details like if your IP and FQDN entries are maintained in hosts file. Also if your hostcontrol is updated or not.

So please alongwith providing std.err, out, dev_icm log files, check above mentioned details also.

Thanks,

Manish Singh

[manish_singh13]

Hi Ryan,

First of all can you confirm if you have installed ABAP or JAVA stack on your system. Secondly try to check the status of your instance if that is up and running or not.

Thanks,

Manish P Singh

[Former Member]

Java stack. Yes it is running.

[Former Member]

I am having the same error on NW 7.3 EHP1