Unable to execute the SDT request Java_EE operation pre-execute on hostname

[former_member239444]

Hello,

I'm in the process of upgrading our solution manager to 7.1. I'm in the

"Preprocessing" phase of the upgrade. The ABAP is in a waiting state for the Java phase. The Java phase failed due to the following error:

"Unable to execute the SDT request Java_EE operation pre-execute on

hostname vsodci instance 24"

This happens in the Preprocessing phase CHECK_UPGRADE_UNIT.

This is also shown in the TroubleTicket File:

class java.lang.NullPointerException: while trying to invoke the method com.sap.sdt.j2ee.model.J2EEDataModelIF.getRootJ2EEElement() of an object loaded from local variable 'model'

I see there is a new SOLAMUP patch released on friday. Can I just apply this new patch over the current one and contuinue or will it break my upgrade?

Regards,

Jacques

[jordan_vassilev · Accepted solution]

Hi All,

SAP note 1691814 has been released until a fix becomes available to all on SMP.

Best Regards,

Jordan

[Former Member]

Hi,

Patch version 30 should solve this issue.

Thanks,

KJ

[Former Member]

Replacing sdt_j2ee.jar file from SOLMANUP #30 fixed the problem.

Hi,
Patch version 30 should solve this issue.
Thanks,
KJ

Hello all,

I cannot confirm that.

I'm using Version 30 of SOLMANUP and got the same error.

Time stamp of my "sdt_j2ee.jar" is 22.02.2012 02:06"....

Is this file platform independent? Maybe I can use the "sdt_j2ee.jar" from e.g. Windows x64... I'm using OS/400.

Any solutions, does anyone have the same problem also with Version 30?

Did someone get an answer from SAP...?

Best regards

Tobias

[former_member239444]

Hi Tobias,

As I mentioned earlier, I went back to patch 24 for Linux and successfully upgrade SOL Man to 7.1. Unfortunately, I don't think you will get patch 24 anymore. No solution/response from SAP.

Regards,

Jacques

[former_member261629]

Dear Jacques,

Sap answered back to me and corrected the JAR file. I sent to you as well so next time you can also use it.

Best regards,

Róbert

[hendrik_franz]

Hi,

I have the same problem with SOLMANUP Patchlevel 30.

@Robert:

Can you perhaps supply your OSS call number to get quick support in case of calling SAP support?

Kind regards,

Hendrik

[former_member189797]

Hello All,

In case the issue occurs, kindly zip and attach to the message complete

java/log; /java/trc; sdt/log and sdt/trc directories .

Also kindly attach the <SOLMANUP dir>/java/lib/std_j2ee.jar file .

you will receive a fast response.

Thanks.

Best Regards,

Gaurav

SAP Basis Consultant.

[Former Member]

Hi Garauv,

for which component should we open the OSS message?

Best regards

Tobias

[former_member189797]

Hello Tobias,

Kindly open the message in BC-UPG-TLS-TLJ .

Hope the information helps.

Thanks.

[former_member189797]

Hello All,

One more information to add. Also kindly provide the information whether the system is a HA system or not.

Thanks.

[former_member261629]

Dear Hendrik,

I can not tell you OSS call number sorry. I got a quick answer when I provide the following to SAP:

log files

std files

trc files

and jar file.

They send me the modified JAR within an hour.

Regards,

Róbert

[Jörg_Brockmann]

Hello,

we have the same EHPI error by implementing Java-Support Packages in an Java Netweaver 2004s Instance (Java Portal).

Error-Message:

"class java.lang.NullPointerException: while trying to invoke the method com.sap.sdt.j2ee.model.J2EEDataModelIF.getRootJ2EEElement() of an object loaded from local variable 'model'"

We find an (dirty) workaround for our system (if you try this way, it´s your own risk ;-):

-> close the EHPI console when the error occurs

-> start JSPM

-> in our case: when the JSPM was started, the desired Java-Stack was ready for implementation without any modifications from us

-> then we only click "start" for deploying the Java packages an the stack was deployed succesfully

best reagards

Jörg Brockmann

[Former Member]

Hi!

I started an upgrade with SOLMANUP ver 29 and got this problem. To troubleshoot I've made the following corrections:

1. deploy latest JSPM package SP10 PL2 via SDM (did not worked)

2. download SOLMANUP #30 -> decompressed to other place and copied sdt_j2ee.jar to SOLMANUP\lib directory (worked)

Replacing sdt_j2ee.jar file from SOLMANUP #30 fixed the problem.

Cheers,

Fernando

[former_member239444]

HI,

Just to let you know my upgrade of Solution Manager completed successfully using SOLMANUP patch 24.

Regards,

Jacques

[former_member239444]

Hi All,

I eventually reset my upgrade and used an older patch(24) of SOLMANUP. This solved my problem. I notice that SAP has release a couple of new patches in just a few days for SOLMANUP. The patch I had the issue on was 28. In the mean time I see there is already a patch 30.

Regards,

Jacques

[Former Member]

Hi,

I encountered this issue using patch version 29. My environment is Win x64. I just checked in SAP SMP, some of the environment already released the patch version 30 but not windows.

Thanks,

KJ

[former_member261629]

Dear All,

We had a same problem during the upgrade and SAP could solve it. They modified the JAR file in /java/lib .

File name is : sdt_j2ee.jar

Best regards

Róbert Polgá

[Former Member]

what modification did they perform in jar file? do you have any insight on this? .

Thanks,

Prabhat

[former_member261629]

Dear Prabhat,

I can not tell you exactly what kind of modification they did, but if send me a mail to robert.polgar_at_hu.ibm.com (remove_at_ and put @) and I can send you the JAR file.

Best regards

Róbert

Edited by: Róbert Polgár on Feb 28, 2012 10:10 AM

[Former Member]

Thanks Robert,

I used the sdt_j2ee.jar file which you sent to me on my email and it worked for me too.

Thanks a lot for your help.

[Former Member]

Hi Robert,

Thanks for your help. Replaced the file "sdt_j2ee.jar " and SOLMANUP continued with the upgrade.

Regards,

Faure.

[hendrik_franz]

Dear all,

please open a call. SAP Support will check your issue and you will get a quick response as Gaurav

already stated.

Hendrik

Edited by: Hendrik Franz on Mar 2, 2012 8:32 AM

[Former Member]

Hi,

We're facing the same error during installation of EHP5...is anyone able to send us the jar file to pau.soldevilacorominas_at_realtech.de?

We need that file as soon as posible in order to fix this issue.

Thanks and Regards,

Pau

[Former Member]

Hi Gurus,

I have use Patch 30 for Solman,and i am in pre-processing phase, but for Java it is giving the same error. that you guys are facing.

Unable to execute the SDT request Java_EE operation pre-execute on hostname abcapp01instance 60 Modules execution failed. Execution of the unit UPGRADE failed. Connection to the Upgrade Tool was closed.

Please let me know what should i do.

I can see patch 31 has already been released. should i replace the jar file, Replacing the jar file requires the restart of the upgrade??

[Former Member]

Hallo,

had the same issues with patch 29 and 30 (Unix). I opened a message with SAP with a reference to this thread who gave me a new sdt_j2ee.jar which fixed the issue.

Hence I suggest you open a message with SAP as well.

Regards, Thomas.

[Former Member]

Hi John,

I don't believe that the error is fixed in SOLMANUP 31. The only release note you can find for this version is the following:

IBM i: Improve error handling during deletion of shadow schema

You don't need to open a customer message to get the modified jar file. You can download it from sap note #1691814.

Best regards

Tobias

[Former Member]

Just one question.

After replacing the jar file, do we need to kill all the current process of SOLMANUP from OS level and then start again.

Or is it just replace the file.

go to the URL

start the upgrade by entering username and password.

and then continue.

Or is it something else?

Waiting for your replies.

[Former Member]

Or is it just replace the file.
go to the URL
start the upgrade by entering username and password.
and then continue.

this worked for me...

[Former Member]

Hi Gurus,

Now the java error is not coming... I have replaced the jar file in java/lib directory.

I am in pre-processing phase for the ABAP.

But I have also started recieving the error for the ABAP stack now.

-

---

Unable to execute the SDT Request ABAP operation pre-execute on hostname <abcdxyz> Instance 60

Pre-Uptime execution of ABAP upgrade request ABAP has failed Error from Unit observer

Tool died unexpectedly with sapparam: sapargv(argc, argv) has not been called.

sapparam(1c) No profile used.

sapparam: SAPSYSTEMNAME neither in profile nor in Commandline.

-

---

Any ideas on this.??? please help

[Former Member]

I think you should give this hint a try:

sapparam: SAPSYSTEMNAME neither in profile nor in Commandline.

Please check if the parameter SAPSYSTEMNAME is entered in your DEFAULT.PFL

I know it is time-consuming, but you should read all the notes, which are mentioned in the Upgrade/Installationguide.

There a lot of solutions for such problems...

Tobias

[Former Member]

Thanks all.

Issue resolved, It was file permission issue on usr/sap/trans.

I had changed the permission of trans/tmp and trans/log.

Also, i have replaced the jar file as suggested by the sap note. and it worked. The java error is now gone as well.

Pre-processing is in progres....

[former_member208255]

This message was moderated.

[former_member239444]

Still waiting for SAP to respond to my "high" call that I've logged 3 days ago.

Regards,

[Former Member]

Hello,

we are also facing same issue - please let me know once you have the solution.

Thanks

Shaik

[Former Member]

I also logged a ticket to SAP with this issue and SAP says that they recieved many tickets for this issue and they forwarded my ticket to upgrade developement centre, Hence it looks like SAP also doesn't solution for this issue and they are working to find one now.

lets keep this thread going until somebody recieve any solution from either SAP or somewhere else. it will help others following this path of upgrade in future.

-Prabhat

[former_member414558]

Prabhat and Robert,

Is it possible to send the .jat file at my mail id kush.sharma_at_lausd.net

Thanks

Kush

Basis Lead

[Former Member]

Hi,

We encountered this error as well. If there any solution to this?

Thanks,

KJ

[Former Member]

I am also facing the same issue, please share the solution if you already resolved this issue.

Thanks,

Prabhat