Aborted TCI Upload Results in TK753 "Object directory entry LIMU COMM... does not exist"

[Matt_Fraser]

I am attempting to apply SAP Note 3266697 (Correction for Unified Rendering TCI 2212 for SAP_UI 754) to my Solution Manager system, and I've run into a situation, admittedly of my own causing, but which I can't seem now to resolve. I'm hoping someone can point me to a place (a file? a table entry?) I can delete to "reset" the TCI upload for this Note so I can start over.

Note: This system has been fully TCI-enabled for SNOTE for a long time, and I've implemented TCI-based Notes many times. I also implemented this same TCI-based Note in other systems without a problem. I just did something dumb during the upload of the TCI for this system and now I need to figure out a way to undo it.

I work remotely, so normally to upload a big TCI I would RDP to a VMware workstation that is colocated with the data center and do the upload there. This time, without thinking about it, I tried to upload the TCI directly from my remote laptop, over a slower upload connection, and it's a 100MB package. When I realized my mistake, I stopped the SNOTE transaction within SAPGUI, and then repeated the TCI upload from the VMware workstation. So far, so good.

However, when I then attempted to implement the Note, it failed with error TK753, "Object directory entry LIMU COMM SAPK754017CPSAPUI does not exist." As far as I can tell, it does exist, I can even manually merge its contents into a transport request in SE10, but not matter what I do, I cannot get SNOTE to recognize it. At this point, the Note implementation cancels, the regular Correction Instructions never get implemented, and the Note remains in a "Can be implemented" status.

I tried re-downloading the Note, re-downloading and re-uploading the TCI, all to no avail. I can't "reset" the Note because SNOTE doesn't think it's implemented in the first place. I tried releasing the workbench transport request and starting over, so that no object locks were held, and that made no difference. I can't do a TCI rollback, because the Note isn't actually implemented.

Anyone have thoughts on what I should try next?

Cheers,
Matt

[Matt_Fraser · Accepted solution]

This is solved with a new version (v11) of Note 3257359 (SNOTE: To allow object overwriting if there is no customer modification). Older versions of the Note don't solve it (or maybe even cause it, at least in Basis 740?), but this new version seems to be the trick. Download and implement (or update to) this version, then try your TCI Note again, and you should be good to go.

https://launchpad.support.sap.com/#/notes/3257359

[former_member362783]

Hi Matt.

Exactly the same problem with our SoultionManger. Opened an Incident at sap (14.12.22) but still didn't receive any answer.

Additionally: Not only the UI TCI doesn't work anymore - all TCI note implementations stops with the thekind of error message "Object directory entry LIMU COMM SAP**** does not exists".

Do you find a solution ?

Regards

Chris

[Matt_Fraser]

Hi Chris,

I took the liberty of converting your comment to an "answer" just because that makes it easier for there to be additional comments and replies to it.

I did open up a Customer Incident with SAP on 12/21/2022, so not long after first asking here. It looks like yours happened earlier, so I'm surprised you still haven't heard anything. I have had some back-and-forth discussion with engineers at SAP on mine, and they have remotely accessed my system to look at it, though no solution is available as of yet. Initially I opened it as low priority, because it didn't seem to be impeding anything too much -- there weren't any other Notes I needed to apply at the time. However, when Security Patch Day came about, which included some urgent TCI Notes to apply, I upgraded the priority to high. As of yesterday, the engineer has escalated the ticket to a higher-level support team, so it seems it must be a pretty sticky problem. I'm hopeful, with that escalation, that there will be an answer soon.

If you haven't heard anything since 12/14/2022, I would go consider increasing the priority. If it's in "Sent to SAP" or "In Processing by SAP" status, you might not be able to do that directly, so in that case you'll need to send a message to the Customer Interaction Center (there's a web form on the support.sap.com site somewhere or other; it should be relatively easy to find) and ask them to do it. If it's already in High priority status, then same thing, contact CIC and ask them to "speed up processing." It would also be worthwhile to add a comment in your incident -- and to CIC -- that you're aware of other customers (e.g., me) having the same issue, with open tickets. You can reference my ticket number: 964734 / 2022.

Cheers,
Matt

[former_member362783]

Hi Matt.

SAP was already working on the ticket - on 18.12.22 the support has escalated the ticket to a higher level. But still no solution. I added your ticket number as reference to my ticket ( 4591070 / 2022 TCI NOTE - could not be implemented

).

Chris

[Matt_Fraser]

solman_sp5,

SAP has solved the issue in our SolMan system, in that during the process of troubleshooting to find a root cause they were able to implement the Note directly. Unfortunately, I don't actually know what they did to solve it. I've asked for more information, in case this sort of thing happens again.

Cheers,
Matt

[former_member362783]

Hi. SOlved at our side as well. SOlution: Please deimplement the Note 3257359 and proceed with TCI Implementation.

Regards Chris

[ren_kokrhoun]

Thanks for that information, this solved by us although the problem...

BR René

[Matt_Fraser]

solman_sp5,

SAP "solved" the issue for us by directly manipulating our system, but they seem oddly reticent to tell us how they solved it. Nowhere did they mention to de-implement an earlier Note (3257359, which we applied last November). And, the solution is only half a solution at best, as all they did was get the current Note I was stuck on implemented for me, but I'm still unable to implement any other TCI Notes. They all end up with the same error message, despite successful uploads of the TCI itself.

I'm really frustrated by this. I've never before encountered a situation where SAP engineers wanted to directly manipulate our system without telling us what they were doing. They are usually incredibly reluctant to make changes directly in customer systems, instead typically providing either a Note or, if it's urgent, detailed instructions for the customer to do the change themself.

I'm already at the point of planning to restore our system from backup (which I took immediately prior to uploading the TCI), so I have nothing to lose with trying your idea of de-implementing 3257359 first.

FYI, if you don't tag people, they are not notified on replies to comments, since they are in "parallel" with each other. I didn't know you had responded until I came here just now to add this new comment.

Cheers,
Matt

[Matt_Fraser]

solman_sp5,

Well, that made no difference. I de-implemented 3257359 and tried again, but I still get the same error.

[former_member362783]

Deimplementing Note 3257359 was the official answer / solution from SAP. In our case - and for BR René - the problem was solved. Seems you have a different situation.

Chris

[Matt_Fraser]

solman_sp5,

It turns out that de-implemening 3257359 was not the answer, but updating it with a new version just released (v11). SAP got back to me over the weekend and indicated they had just released a new version of this Note and to update to it then try again. That did indeed solve the problem.

Cheers,
Matt

[chriswolf]

Thanks, 3257359 v5 (1st march 2023) fixed the issue when i tried to implement any TCI note.
I received that for sap ui and SAPK74001GCPSAPBASIS

Cheers

[bglobee]

Hi matt.fraser

Can you try uploading again the TCI via SPAM/SAINT (I am assuming that you uploaded it via SNOTE TCI option)?

Few prelim checks before:

1. is SNOTE in latest version? 1668882

2. is TCI framework in latest version? all relevant notes for TCI framework implemented with latest version?

3. SPAM/SAINT updated and compatible to handle changes of your note?

Then,

Option 1 - Check in SE16 --> TADIR --> LIMU / COMM / SAPK754017CPSAPUI --> to see if the TADIR entry for this really exists. If yes, then check for the package to which it belongs to.Go to SE80 --> Package --> provide the package name and search if a valid entry for this exists --> If yes, then select the object and look for menu --> 'Goto' -> 'Object Directory Entry'

--> IF it does not exist, then check if you can rescue and transport if from other system where you implemented it successfully (from other systems)

Option 2: If possible, rescue the objects from another system where the same note(with TCI was implemented).

[Matt_Fraser]

Hi Balaji,

Thanks for your quick response.

I did also try re-uploading from SPAM instead of SNOTE, and while the upload certainly seems successful (both ways), it did not change the behavior of the Note implementation within SNOTE afterwards.

SNOTE is indeed up-to-date with the latest version of 1668882. All of the TCI framework is up-to-date. SPAM is up-to-date with version 83.

Table TADIR does not show any entries for LIMU COMM SAPK754* at all (which one would think it would, since this is not the first time I've applied UR updates this way). However, in other systems where I was successful with this Note, it doesn't show an entry for this there either, so it's not clear to me how I would pull the object from there.

What is weird is that in SNOTE I can drill into the Note objects and it shows all the contents I'd expect from the upload. The contents are there! But the Note status remains "can be implemented" and that can't be changed.

So, I think it's a corrupt object directory entry, even though the object itself is present.

Cheers,
Matt

[bglobee]

Hi Matt,

then only way is to reach to SAP support. they might have a workaround. in this case, modifying TADIR or any other way seems too risky.

[mamartins]

Just to mention that is very recommended to do backup prior to any TCI implementation, and implement the TCI on low system utilization just in case of something went wrong and a DB restore will be necessary to correct the issue.