Transport Error In NWDI

Question

Hi All,
for my application, i did check in, create new activity> clicked on Activation> then pressed on ok
if i click on activation requests> in the results>it showing as " Request not yet available the request is still in process",
though it showed the message,
i went to transport view in that >waiting>in that  i released my application,
then i went to CMS--> consolidation, i tranported there, while importing this not yet effecting in QA.
when ever i used to checin, go to checkin>create activity (display name)>clicked activation
the activation request shows as "Request not yet available the request is still in process"
when ever i used to check in  N no of times i used to get the same message,
what was wrong send me step by step frm check in
Thanks&Regards
charan
Edited by: charan12 on Jan 6, 2011 2:35 PM

Answer 1

Hi,
This is the process of Deployment
Component Build Service (CBS) builds one or more new archives in a build request. CBS notifies Change Management Service (CMS) that an automatic deployment is pending and sends it the corresponding build request ID. This ID is entered in the table TC_CMS_TCS_NOTIFY. The automatic deployment function then contacts CBS, fetches the archives, and deploys them to the runtime system. The result of the deployment is saved to the table TC_CMS_TCS_DCQUEUE.
There are 3 scenarios you might want to check.
1. In CBS WebUI see whether the requests are getting queued for the track in use. If the requests are queued then go to Visual Admin and start the CBS Service.
2. Even though you checked in and in Development you import the import is still running then you might want to check whether the Request is Queued in TCS Deployer, if the request hangs there then it is processing the request.
If it takes longer time than usual you might want to Trigger the deployment manually.
To do Manually go to http://<hostname>:<portnumber>/TCS/Deployer and login as Administrator and trigger the deployment for the specific Buildspace.
Check the below link for further details:
http://help.sap.com/saphelp_nw04/helpdata/en/4e/a5214174abef23e10000000a155106/content.htm
http://wiki.sdn.sap.com/wiki/display/JDI/Commonerrorswith+NWDI
3. Increase the memory on the NWDI server so that request gets processed.
Hope this helps.
Cheers-
Pramod