ESS Modification. Check-in/Activate --> Request INIT_COMPARTMENT hangs

[Former Member]

Hi all,

We have made some modifications on the ESS code to solve some problems regarding the Dutch Postal Code. The code changes are described by SAP and are actually quite easy to implement. We created a new project for ess/nl/addr and started editing.

After build and deploy we saw no problems. When we check in and want to activate the mods, the troubles begin. I got an error that there was a compartment being initialized:

Retrieving pending activities failed: CBS server error: The compartment for given software component is being initialized (internal code: BS_SC_META_DATA_NOT_AVAILABLE)

What can be done about this? I can not find my changes in my CMS to transport them through the landscape.

Any help is highly appreciated and points will be awarded.

Best regards,

Jan Laros

Edited by: Jan Laros on Jan 29, 2008 8:53 AM

[Former Member]

This message was moderated.

[Former Member]

Was this solved ? Please reply!

[Former Member]

Hi Veena,

Sorry for my late reply. Sorry that I doesn't answer to your private email you sendt me. But, would you you answer to something that you doesn't know? Especially if the mail was marked with high priority? (every spam mail about viagra or whatever else is send with high priority).

To your question, I don't know if this is solved. As long as the thread is open I think it's not.

Now I now you you, and I so I will also answer to your private mails. But at first, please post your problem at SDN and not to members, who are so friendly to give their email address in there profile. Everyone wants to here about you're problem (the one you posted ) and everyone should be able to get the solution.

So understand me that I don't answer to your mail!

Regards,

Daniel

(P.s if you want private communication, use Xing, there you'll find me)

[Former Member]

Could you guys check my CBS properties in Visual Admin? Have I made any significant mistakes?

Screen: http://tweakers.net/ext/f/zlnBComez99I5JC9hhpG1urA/full.jpg

Best regards,

Jan

[Former Member]

Hi all,

Can it be a problem that all my systems are NW 7.0 SP13, except for the NWDI server? NWDI system is on SP12.

BR,

Jan Laros

[Former Member]

Hi,

I think you're are right. Your NWDI SP is to low (or in detail SAP Buildt Tool of NWDI (SAP_BUILDT) is to low. NWDI server should always have the highest SP level. Please refer to SAP Note 1118779. This describes the problem.

Hope this helps.

Regards,

Daniel

[Former Member]

Hi Jan,

with "hangs" you mean that the INIT_COMPARTMENT request is "processing" forever?

If the request is only queued but not processed, check the idleStart flag in the CBS properties.

Otherwise I'd simply try to restart the CBS. What version do you use? Is it a single node or a cluster?

Regards,

Marc

[Former Member]

Hi Marc,

Thanks for your reply!

The "INIT_COMPARTMENT" in staying queued.

The "Idle start" property is et to "false" and I have already tred to restart the CBS service in VA.

This has not helped.

We use Netweaver 7.0 SP13 and it is a single node. If you need anything more, please let me know.

Best regards,

Jan Laros

[Former Member]

Hi,

Does anyone else have a clue or suggestions for me to try?

Best regards,

Jan Laros

[Former Member]

Hi Jan,

I had a similar problem with queued requests in CBS, the solution was to execute "restore system state" in CMS, as CMS had lost the connection to CBS. Details see SDN track

Maybe you could try that.

Best regards

Cornelia

[Former Member]

Hi Cornelia,

Thank you for your reply. We have already deployed quite some custom development on the ESS component on the Portal we are talking about here. When I click restore system state, a popup asks me to confirm: "All the software component versions shown here will be added to the import queue". Will this have any influence on my custom development that has already been deployed and transported to test? Or can I just remove the newly added component versions from the import queue?

Best regards,

Jan

[Former Member]

Hi Jan,

I'm not sure about the ESS components - we had this with a self developed application which we re-deployed (by adding it to the import queue and importing it), and the application was not affected.

So I think CMS takes the latest version of the software component and imports that again.

Maybe you should save the names of the activities you deployed into your ESS, so in case something's missing later, you can redeploy the application by adding these activities to the import queue.

Old versions of these activities should be set to outdated by CMS when you try to import them, so you wouldn't have any problems with them.

Best regards,

Cornelia