While running a standard Endevor job, it reported it was unable to verify a footprint and ended the action ? why ? what can I do?

book

Article ID: 40184

calendar_today

Updated On:

Products

CA Endevor Software Change Manager (SCM) CA Endevor Software Change Manager - Natural Integration (SCM) CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) CA Endevor Software Change Manager - Enterprise Workbench (SCM)

Issue/Introduction

Question:

While running a standard Endevor job, it reported it was unable to verify a footprint and ended the action – why – what I do?

 

Answer:

The error message you are receiving is more than likely the C1G0030E UNABLE TO VERIFY FOOTPRINT for ELEMENT in the Base, Delta, and Component base/delta or processor library.

The C1G0030E message is always associate with the C1G0030I message which will give one the Endevor inventory location for where the problem resides.

With the information at hand one can go into Endevor and do a footprint display on the library will the problem is reported to confirm the problem.

To correct the problem:

If it is a problem with an element first check to see if a Source output library exists and the member is there, if it is, copy the member to a library outside of Endevor and then delete the member and re-add it.  

If there is not SOL and the problem is in the Delta library, check to if the base library is a reverse unencrypted library.  If yes, copy the member from the base to a library outside of Endevor, delete the member from Endevor and re-add.

If the steps above are not available, check your archive files and after deleting the element in Endevor transfer the element from the archive file to Endevor.

If the problem is in the component, do a delete component only and regenerate the element in Endevor.

If you have any questions please do not hesitate to call your local Endevor Support team.

 

Environment

Release:
Component: ENDBAS