on 04-26-2008 5:42 AM
hii all,
I have a DC which have been built and deployed fine and giving the perfect output when running on portal. This has been deployed on local server.But while tranporting it to QUALITY server for testing,itz cannot be imported there and giving an error "DC Broken".....!
plz do help out....
Activate fixed version of broken DC.
If the DC itself contains the error you should check out the affected files from DTR, fix the problem in the SAP NetWeaver Developer Studio and then check in and activate the new version. As a result of the activation the DC will directly go from broken state to OK state. For example: as announced before a deprecated interface was deleted by the provider. You change your code and use a new interface that was specified as an alternative.
http://help.sap.com/saphelp_nw70/helpdata/EN/46/14fa07c15214dce10000000a155369/frameset.htm
nikhiL
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
hiii,
Thanks a lot for your reply.
But, i have another query....the project was last transported to quality on 10th march , after that i have released atleast 20activities, among which only the recently released activity was transported to quality...is the error coming bacause all the 20activities need to be transported in sequence????
plzz do reply.
Thanks,
Parama.
Hi Parama,
If there are any dependencies between DC's then you need to transfer them in a sequence like Used DCs first and then the other DCs which are using them. If you don't do them in a sequence then you will get an error. That you can find it out by seeing the Error Stack Trace.
If there is no dependency between the DCs then you can transfer them in any order.
Thanks n Regards,
Jhansi Miryala
Yeah. because dependency makes build errors at following situations.
1. A used DC or public part does not exist
2. Using and used DC are in different software component (SC) compartments but there is no usage dependency between the two SCs
3. A DC tries to use the child DC of some other DC, which is not allowed.
nikhiL
Hi Parama,
Please see the Stack trace of the error. Because there are many reasons for the Broken DC. Refer to the following link which explains the procedure to resolve the same.
Fixing Broken Development Components:
http://help.sap.com/saphelp_nw70/helpdata/EN/46/14fa07c15214dce10000000a155369/frameset.htm
Thanks n Regards,
Jhansi Miryala
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
84 | |
10 | |
10 | |
10 | |
7 | |
6 | |
6 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.