CMS Check and import failed

Question

Hi All,
We have created a track in CMS. When do the Import-check of SCAs, we are getting "Check-failed".
Foll. are the SCAs
sap.com_SAP-JEE      
sap.com_SAP_BUILDT
sap.com_SAP_JTECHS
When we are trying to import, then we are getting the message "Import-failed".
Log file shows the foll. message
Fatal  :check failed, because the sources are not contained in the archive
Info   :Step Repository-check ended with result 'fatal error' ,stopping execution 
Can someone tell, what could be the problem and the possible solution.

Answer 1

Hi,
let me summarize the possible reasons for the error
Fatal  :check failed, because the sources are not contained in the archive
Info   :Step Repository-check ended with result 'fatal error' ,stopping execution 
First of all an SCA file can be either used for modification by customers, or not, becaues it has only build archives (meaning necessary for build -- like libraries, you can pretty much treat it that way).
An SCA can have 3 types of archives inside:
- buildarchives  -- i.e. necessary for build
- deployarchives -- i.e. deployable
- sourcearchives -- i.e. can be modified by customers
What kind of archives we are dealing with you can decide easily:
rename the given SCA file to zip, and extract it (or simulate extraction using jar -tvf *.SCA).
It can contain 3 folder respectively: BUILDARCHIVES , DEPLOYARCHIVES, SOURCEARCHIVES
Meaning, if it has a SOURCEARCHIVES folder, it has sources to be modified.
Notice, none of the initially mentioned archives (SAPBUILDT, SAPJEE, SAPJTECHS) are having sourcearchives.
So then why this error is reported?
On the top of that ESS should have sourcearchives folder, then again, why is this error coming?
I come to this point immediatelly.
Now the error message we are talking about can have 2 reasons:
1. the archive should not have sources, but due to a wrong configuration it gets confused and reports this error.
2. the archive should have sources, but it was wrongly uploaded to the marketplace (i.e. wrong delivery)
Explanation on the above 2 points:
1. In CMS webui -- Landscape Configurator -- Track Data tab you checked in the checkboxes "Developed" for such software which is not allowed to be modified. In this example you have set the Developed flag for SAPBUILDT, SAPJEE, SAPJTECHS.
Now at import CMS expects that these SCAs have sources, but since they don't you run into this error. Solution is easy: get rid of those flags and import again. The imports will work this time.
2. You downloaded ESS, correctly added the "Develped" flag in the mentioned configuration, but the ESS SCA is wrongly uploaded by sap to the marketplace. This case report it to us so we can correct the SCA which you can download again. Report the exact location from where you downloaded it, so we are aware of the exact version and filename.
See this note that explains the same:
1537477 - Failed to import SCAs into CMS track because the sources are not contained in the archive
(there is a 3rd reason in the note for this error, but I believe you face only 2 of them in this SCN discussion)
I hope this helps.
Best Regards,
Ervin