locked
The field with Id {GUID} defined in feature {GUID} was found in the current site collection or in a subsite. RRS feed

  • Question

  • Hi all,

    Although related issues has been posted before, I would like to ask for any help regarding the precise situation we are facing with a  SharePoint Server 2010 Enterprise Edition, SP1 application:

    We are getting this error "The field with Id {GUID} defined in feature {GUID} was found in the current site collection or in a subsite." when trying to activate a Site-Scope feature on our PRE-production environment. In the Integration-Development environments it went just fine. Anything strange happened in preproduction machine when deploying the very same WSP package.

    The GUID displayed on the error belongs to a Field definition which already existed on preproduction and exists in production environment. This is in fact our concern. From one side, we can't figure out what went wrong with SharePoint, and from the another we couldn't be able to reproduce this anomaly on the previous stages to the preproduction so we are afraid this problem could be repeated in the future.

    the problematic Field definition is the next one:

    <Field
            ID="{D2D6FA66-81EB-439c-9907-007DDD28E405}"
            UniqueId="{D2D6FA66-81EB-439c-9907-007DDD28E405}"
            Title="CallTitle"
            Type="Text"
            Name="CallTitle"
            DisplayName="Heading"
            Group="ProjectFields"
            Required="FALSE"
            StaticName="CallTitle">
      </Field>

    At packcge level it is located at  WSP_ROORT\<ProjectFolderName>\ContenTypes\Elements.xml

    Any help will be very appreciated.

    Thanks in advanced,

    Iker




    Thursday, May 10, 2012 11:10 AM

Answers

  • Hi,

    Adding the Overwrite="TRUE" attribute on each field definition made the Job. But I cannot figure out what happened with SharePoint since in previous deploys this wasn't needed.

    Thank you all.


    • Marked as answer by IKer Elgezabal Friday, May 11, 2012 10:01 AM
    • Unmarked as answer by GuYuming Friday, February 17, 2017 7:54 AM
    • Marked as answer by GuYuming Friday, February 17, 2017 8:14 AM
    Friday, May 11, 2012 10:01 AM

All replies

  • Hi IKer Elgezabal,

    Your issue seems to be documented in the following KB: http://support.microsoft.com/kb/2022443.

    You could try to apply the suggested solution.

    Regards,

    Ludovic Caffin

    Thursday, May 10, 2012 12:26 PM
  • Hi Ludovic,

    We are not using the Visual Studio in Preproduction, the deployment is being launched via PowerShell.

    Thanks

    Iker

    Thursday, May 10, 2012 12:49 PM
  • Hi,

    The field With Title "CallTitle" you have assigned ID="{D2D6FA66-81EB-439c-9907-007DDD28E405}",This ID has already being used for the another column.

    You need to change the GUID.

    Solution : Try With Different GUID(it should be unique and make sure no other element is using it)

    Mark as answer if it solves your problem :)


    "The Only Way To Get Smarter Is By Playing A Smarter Opponent"

    Thursday, May 10, 2012 12:56 PM
  • Even if you are using powershell, there could be interresting elements in this KB.

    It is written a such error can be thrown when you first deployed a field with a package, then retracted it (but the field was not retracted correctly...), and finally redeployed a package with the same field but with a different id in the elements.xml.

    Do you think you could be in this situation?

    Thursday, May 10, 2012 4:23 PM
  • Hi,

    Adding the Overwrite="TRUE" attribute on each field definition made the Job. But I cannot figure out what happened with SharePoint since in previous deploys this wasn't needed.

    Thank you all.


    • Marked as answer by IKer Elgezabal Friday, May 11, 2012 10:01 AM
    • Unmarked as answer by GuYuming Friday, February 17, 2017 7:54 AM
    • Marked as answer by GuYuming Friday, February 17, 2017 8:14 AM
    Friday, May 11, 2012 10:01 AM
  • I see no overwrite attribute in https://msdn.microsoft.com/en-us/library/office/ms437580(v=office.14).aspx ;

    but there is related code in SPFieldElement

    Friday, February 17, 2017 8:19 AM