Unable to open transactions in Mii workbench

[dan_kellackey]

When logging onto our corporate Mii server, which I haven't done in a long time, I can open the workbench, but get the following error when opening transactions:

sap mii could not initialize class com.sap.xmii.xacute.editors.transaction.dialogs.linkeditor.LinkEditorBottomPanel

I am able to open query,display, and irpt pages objects normally.  Also Help | Settings doesn't function either, no error.

I don't have this issue on our local Mii server workbenches, they are working normally.

Mii version 12.2.2

BR,

Dan K

[dan_kellackey · Accepted solution]

I recieved the following information from our corporate IT department.  Adding the line to the java.policy file resolved the issue.

I was orginally runnig jre 6u26, then went up to 6u31, then back down to 6u26 and editied the policy.

Thank you all for your help,

Dan Kellackey

According to this link: https://forums.oracle.com/forums/thread.jspa?threadID=2300815&start=15&tstart=0



Summary from Oracle on this issue:

"In JDK 6u29 a change was made to bring Java into closer alignment with
the web Same Origin Policy. In some cases this has caused existing applications
to break. The problem manifests when secure cookies are expected to be sent
over an insecure connection. If you application depends on this behavior you
will need to sign the application. In addition, if the request originates via a
LiveConnect (javascript) call then it will need to be wrapped in a
doPriviliged() block as javascript calls are treated as untrusted and do not
carry the same protection domain.

I realize that if your application uses just the Microsoft RSProxy class for
remote scripting this isnt a likely solution for you. Were still looking at
this.



The following documents contain some relevant information:

http://download.oracle.com/javase/tutorial/deployment/applet/security.html

http://download.oracle.com/javase/7/docs/technotes/guides/security/doprivileged.html

http://www.oracle.com/technetwork/java/seccodeguide-139067.html#6-0

"



Solution





There are two solutions so far:



1. Rollback to a version previous of the JRE less than 1.6.0_29.



2. In the java.policy file, add the following line:

permission com.sun.deploy.security.SecureCookiePermission
"*.some.site.com:80-", "listen,accept,connect,resolve";



Where "*.some.site.com:80" is the domain that applets are running in
and the port is the server port of the webserver.



Add this inside the section that starts with:



// default permissions granted to all domains



grant {

// other existing permissions

// Add the line above here

};





The file you can find under the folder "../Java/JRE6/lib/security".



This would have to be done on every client that will access the MII applets. If
you have both 32 and 64 bit jre installed you will need to modify the
java.policy file in both versions.

[khaleelurrehman_badeghar]

Hi Dan

Just close the workbench and refresh your MII portal and then reopen the workbench.

I was facing the same problem but doing so helped me.

Thanks and Regards

Khaleel

[dan_kellackey]

I wasn't sure what you meant by refresh the Mii portal.  I tried both reloading the Mii home page, and selecting a menu option MII | MII JCOProxy Reset.  Neither had an effect. 

I got a suggestion from our corporate IT, about adding a line to the java.policy file, which was successful.  I also noted that they were using Source Control, while my local workbench did not.

Thank you for the help,

Dan Kellackey

[HariCS23]

Hi Dan,Do you know the operating system type in your central server ? ( 32 bit or 64 bit ) ?

If it is 64 bit, its better to keep both 32 bit and 64 bit JRE in the system .

Thanks

Hari

[Former Member]

Hi Hari,

Only 32 bit JRE is supported by MII not 64 bit.

Regards,

Suman

[Former Member]

Hi Dan,

Does Java version is same on both corporate & local MII servers?. Kindly check the java version on both these servers and let us know.

Check NWE logs for any specific errors.

Thanks

S.Rajesh

[dan_kellackey]

Our corporate IT suggested to upgrade slightly to version 1.6.0.31.  I unistalled my version, installed version 31, delete temporary files, and get the same error.