SharePoint Server 2010: Designer Error “data source already exists in BDCM”

So here’s an error that, at the time I encountered it, did not have a great deal of information about it on the web:

The system definition with the same name as this data source already exists in the Business Data Connectivity Metadata Store and it refers to a different data source. Cannot complete operation generation. Add a connection to this data source with a different name and try again.

I encountered this error after deleting an External Content Type, then recreating it with the same name. The solution ended up being rather simple: close SP 2010 Designer and reopen again. Voila!

Chrissy is a PowerShell MVP who has worked in IT for nearly 20 years, and currently serves as a Sr. Database Engineer in Belgium. Always an avid scripter, she attended the Monad session at Microsoft’s Professional Developers Conference in Los Angeles back in 2005 and has worked and played with PowerShell ever since. Chrissy is currently pursuing an MS in Systems Engineering at Regis University and helps maintain in her spare time. She holds a number of certifications, including those relating to SQL Server, SuSE Linux, SharePoint and network security. She recently became co-lead of the SQL PASS PowerShell Virtual Chapter. You can follow her on Twitter at @cl.

Posted in SharePoint
8 comments on “SharePoint Server 2010: Designer Error “data source already exists in BDCM”
  1. Salvador Rodriguez says:

    I was about to rebuild the entire site.

  2. Leo says:

    Cool ! It helped !

  3. Ravi Ranjan Karn says:

    thanks ! It simple and perfect.

  4. Hector Higuera says:

    Actually it is a tab that you may have still have open with that same name. Just closing the tab will have the error corrected.

  5. Gladi On a Glider says:

    MAN… the fix at… kept me thinking how do I re-discover a datasource after deleting it.

    The fix you suggest is very simple and IT WORKS. Thank a lot.

  6. tuyennguyencanada says:

    Thank you

  7. Fuzzy says:

    This “feature” still “works” in SP Designer 2013 and this solution worked for m as well.

Leave a Reply

Your email address will not be published. Required fields are marked *