Import to Consolidation "fails"

[michael_voss2]

Hello everybody!

Currently I'm facing a problem when importing a request into consolidation using the Transport Studio. I create an activity in NWDS, change some source files (deployment from NWDS to development portal and testing there work fine) an finally check in, activate and release the activity. The request shows up in Transport Studio as expected. When importing the request into consolidation ("Import" in Transport Studio), this seems to work, but when checking the details of the request, I see something like "Propagatable:### exists allready in the repository. No import necessary" in the Repository-import details. The SDM-deployment-notification says "...RequestId: #### ==> no resulting DCs for deployment". But since we definitely changed source code and checked in changed files, I'd expect an import to be necessary, as well as a deployment. Well, after the import (which returns successfully), I see a new request to be assembled; after assembly, a new request waits to be imported to Test, but when importing (which returns successfully as well), the log says: "Step Repository-import ended with result 'not needed'".

What am I doing wrong ? This has worked flawlessly hundreds of times before...

Thanks

Michael

[Former Member · Accepted solution]

Hi Michael,

in addition, this can happen if you mark a SC as 'development' and this SC doesn't meant to be developed. It can be used only for build or deployment.

Could you please tell us which SCs from SAP are you using? Older versions of SCs might contain delivery errors, check if are using the latest versions.

Regards,

Jonas Cella

[michael_voss2 · Accepted solution]

Hi !

Thank you for your hints; but I think my problem must be somewhere different. Let me elaborate a little more on this:

We have a Software Component with three Development Components. One of those implements a WebService, which has been successfully deployed to Consolidation, Test and Production environment several times before. The DC and the SC are deployable. Some days ago, I changed some lines of code to achieve a different logging behaviour; the changes were made in a new Activity that hat been checked in, activated and released. A local build works fine, deployment to my development portal works and the WebService works as expected. When importing into Consolidation via Transport Studio, I get the above message in the log file.

Edited by: Michael Voss on Dec 8, 2010 9:16 AM

[dao_ha · Accepted solution]

Hi Michael,

Please verify that your changes are successfully deployed on the QA, Prod runtime systems. Also, check whether the box 'Disable automatic deployment' in the CMS Landscape Configurator (Runtime Systems tab) is checked.

Hope it helps.

Regards,

Dao

[michael_voss2 · Accepted solution]

Hi Dao!

Thanks for your hint, but import and deployment have been working for quite some time and nothing has changed in the track configuration. The requests simply do not get imported with the message "no need to import"...

[dao_ha · Accepted solution]

Hi Michael,

Just want to clarify: did your changes get deployed successfully or not? If there's no other errors in the logs then please make sure that the SDM password wasn't changed.

Also, what type of DC are you trying to build as not all DC types are deployable. Please take a look at this thread to see if it helps

Regards,

Dao

[michael_voss2 · Accepted solution]

Ok, finally got it sorted out!

In the DC (Java), the WebService Deployment Descriptor somehow got lost in NWDS (actually, it didn't get added to DTR after deleting and recreating it). When we created a new Deployment Descriptor and added it to DTR correctly, the import into Consolidation worked fine again.

Sorry for bothering you, this was not a problem for this forum.

Thanks anyway!

[Former Member]

Hello Michael,

could you please check on the latest defaultTraces if you find any entry like "VMO"? If you are using MSSQL database I'd recommend you to take a look at the following SAP notes:

>> 985821 - DTR Import Hangs on MSSQL Database

>> 1096029 - Hanging initial DTR import of huge components on MSSQL

After that restart the engine and trigger re-import. If if fails then go to the Transport Studio on CMS WebUI and click on the Consolidation tab. There you must see the SC and the state "Import Failed", select the SC and press the button "Details".

You will see three steps: Repository-import, CBS-make and SDM-deployment-notification. Each one of these steps will have a log file, press the button "View Log File" for each one and paste the contents here.

I hope we can see more details of the issue. Thank you!

Regards,

Jonas Cella

[blanca_serrano]

Hello Michael,

This occurs if the assembly does not have deployable components.

Also please check whether in the landscape configurator of the track the SC is "Sources and archives". If not, then please change it and do a "update CMS". In case if it is entered as "Sources", assembly will consider only sources and no deployables.

Also please have a look at :

SAP Note No. 1027362, it states the list of SCA's that cannot be deployed.

I hope this helps you.

Regards,

Blanca