CBS server error

[Former Member]

Checkin and activate request was all working fine in NWDS for past few days but now we are getting below error

Retrieving pending activities failed: CBS Server Error: The compartment for given software component is being initialized( internal code: BS_SC_META_DATE_NOT_AVAILABLE)

When I checked cbs log at the file system level, we found this DB2 error

DB2 SQL Error: SQLCODE=-101, SQLSTATE=54001, SQLERRMC=null, DRIVER=3.53.70

In the CBS WebUI I see the below request type with queued state

INIT_COMPARTMENT

owner as TC.CBS.SERVICE

Request state as QUEUED

My last deployment is failed.

Please advice

Praveen

[former_member214355]

hi

Could you verify the following CBS configuration setting for me?

1. The idlestart parameter of the CBS config should be set to false

for the details on how to check that, please go to

http://help.sap.com/saphelp_nw04/helpdata/en/31/9959400d9d1059e10000000a

155106/frameset.htm

2.If this is set correctly to 'false' maybe the request processing mode

is set to 'OFF' for that particular buildspace (can be seen in the CBS

WebUI). could you check that as well?

Please keep me updated on the result

Kenny

[Former Member]

Kenny,

I checked and everything is correctly set as your said.

idelstart=false

and request processing mode is set to ON

Any let me know if I had to look anything else.

We even restarted CBS service and restarted portal server as well.

Thanks

Praveen

[Former Member]

HI,

During creation of an user account in "Identity management" (UME), it is

possible to set a timeout for the password. This forces the user to change his password after the defined timeout.

If this is the problem,

Solution :

The NWDI Administrator has to logon in "Identity management" (UME) to

update the password for the communication user on request. After this step,

he has to follow all steps described in the note 896427 to update CMS

track connection in CMS WebUI.

Regards,

Satya.

[Former Member]

Just checked it's not a problem with NWDI_ADM user.

The check-in and activate request was all working fine for more than a week successfully, it stopped suddenly. Found that due to some network issue the build failed. All network issues are resolved now, but this queue still there as in my first post above. Don't know what to do? Any advice?

Any advice?

Thanks

Praveen

Edited by: Praveen11 on Aug 3, 2009 10:29 AM

[Former Member]

Hi,

check if the input mode for the build space is OPEN or PRIVILEGED.

if it is PRIVILEGED, change it to OPEN.

Regards,

Satya.

[Former Member]

The input mode is OPEN.

I think it must be something simple that I need to turn it back on, just missing something. As said in my previous post, due to network issue the build failed and queued, now all network issues are resolved but just trying to fix this QUEUED.

How about I click "Initialize" button on the buildspace of CBS? Would this repair the data and sync with DTR ? Please advice

Thankss

Praveen

Edited by: Praveen11 on Aug 3, 2009 12:39 PM

[Former Member]

HI,

in the default trace are you getting any error message like

'Buildspace<name> doesnot own workspace<name> ?

Regards,

Satya.

[Former Member]

Satya, I don't have access to filesystem logs, I can see defaulttrace from nwa at error level. I can only check it tomorrow with Basis.

Lets say if I see the message that you mentioned, what should I do then?

Thanks

Praveen

[Former Member]

We ended up creating new track for ESS and retro-fitted all the development changes manually into the new track.

After deleted the error track the DTR still maintained it's source, I tried to create a new track with the same name to see if it would pick up undeleted DTR WS, but still had the same issue so had to create new track.

Thanks

Praveen

[Former Member]

Closing this thead, I had useful information for this thead but problem is not 100% resolved. We ended up creating new track and start working on it.

Thanks

Praveen

[Former Member]

HI,

check SAP note 1127973

Regards,

Satya.

[Former Member]

Unable to read the note, I get this message

The requested SAP Note is either in reworking or is released internally only

Thanks

Praveen