cancel
Showing results for 
Search instead for 
Did you mean: 

CRM 7.0 EHP1

former_member186066
Participant
0 Kudos

Hello Gurus,

We are to upgrade CRM 7.0 to EHP1 CRM 7.0. During the course of it, we came across a few issues. Some of them we could resolve but one such issus has become a show stopper.

Issue description:

There are dependcies between the released level and the target level support package. (not the exact line of the error but somewhat similar)

tp.exe ended with error 249

Steps carried out:

It asked to refer to OSS note 211077. We did as per the note and it got through tp.exe error. Again, the same error popped up for r3trarns.exe, we did the same and it worked for us.

Show Stopper:

However, when the same error popped up for disp+work.exe, the same procedure did not seem to work and we are stuck with it.

During course of troubleshooting,we have made the below observation:

1. We tried to upgrade the kernel from 701 to 710. Even after replacing, the u201Cucu201D directory with the latest 710 kernel, the system still showed kernel level as 701.

2. Then, we modified the name of the folder u201Cnucu201D with u201Cnuc1u201D and tried restarting the SAP system. The system refused to come up.

It seems system is using both the UC and NUC kernel directory structure

Please help.

Thanks and Regards,

Ankit Mishra

Edited by: ankit_mishra08 on May 20, 2011 2:09 PM

Accepted Solutions (1)

Accepted Solutions (1)

markus_doehr2
Active Contributor
0 Kudos

> 1. We tried to upgrade the kernel from 701 to 710. Even after replacing, the u201Cucu201D directory with the latest 710 kernel, the system still showed kernel level as 701.

This is the wrong kernel. 7.10 is a different base released and can't be used for CRM 7.0 EHP1.

Markus

former_member186066
Participant
0 Kudos

Thanks Markus for your prompt reply. After it did not work, we reverted the settings yesterday itself.

We just had updated the 720 kernel with latest tp and r3trans in EHPI/abap/exenew. This was the same steps carried out the other but to noluck. Quite strange, the error got resolved today.

Regards,

Ankit

Answers (0)