Today I was setting up a Linked Server from one SQL Server 2008R2 Instance to another SQL Server 2005 Instance with one of the Databases as a Catalog and I was able to create the Linked Server and Tested it successfully, but the Developer was getting an annoying Error as shown below…

The EXECUTE permission was denied on the object ‘xp_prop_oledb_provider’, database ‘mssqlsystemresource’, schema ‘sys’. (.Net SqlClient Data Provider)

What does it mean? It is complaining about a missing permission from Resource Database, which really can’t be touched by any means in terms of Permissions from our SSMS. ( Remember, Resource DB can be accessed just from File System as mdf and ldf files from your Binaries Folder)

So, how to fix this annoying Error?

My Scenario:

1. I’ve a created  a Linked Server using “Microsoft OLEDB Provider for SQL Server” as  Provider by choosing Server type as Other Provider  instead of going with SQL Server. Don’t ask me why 😀

2. I’ve logged in as a user which is not a SysAdmin and when i try to expand the Catalogs from Linked Server I got  this below error message, as you can see in below Screenshot.

Please note I’ve logged in using login “Linked” – I’ve created a test login called “Linked” for this Demo Purpose…

How to Fix this?

1.Map the User to MASTER Database( By Def. It will be added to Public Role)

2.USE MASTER

GO

GRANT EXECUTE ON SYS.XP_PROP_OLEDB_PROVIDER TO LOGIN;

Once, I did this, I’m able to access the Linked Server without any Issues as you can see below…

Howdyyyyyyy! Hope this helps

18 responses to “The EXECUTE permission was denied on the object ‘xp_prop_oledb_provider’, database ‘mssqlsystemresource’”

  1. mangesh Avatar
    mangesh

    it’s work

  2. gannicus Avatar
    gannicus

    Great work! It’s working! Very good article!
    Greetings from Poland (Europe) 🙂

  3. Sreekrishna Palaparthi Avatar
    Sreekrishna Palaparthi

    Thanks for the tip… it’s working like a charm 🙂

  4. Jejoo Avatar
    Jejoo

    Thanks for the tip

  5. rahimah Avatar
    rahimah

    awesome article..solve my issue big time..

  6. Tiago Avatar
    Tiago

    Hi there,

    And what the implications of giving access to this SP on a system database?
    What does the SP behind the scenes ?

    Cheers,
    Tiago

  7. sreekanth bandarla Avatar
    sreekanth bandarla

    AFAIK, no negative implications at the Instance level and it has only to deal with SSMS. If you are using T-SQL for querying your Linked Server, you shouldn’t even get this error message(You will get this annoying message when you try to access the linked server catalogs via SSMS)

  8. manoj Avatar
    manoj

    thanks, did work perfectly well

  9. Joe Avatar
    Joe

    worked for me also!

  10. Steph Avatar
    Steph

    thanks, did work perfectly

  11. Gobinda Sharma Avatar
    Gobinda Sharma

    Thanks, worked for me as well..!!

  12. Sanjiv Avatar
  13. prashantd Avatar

    Thank you so much for sharing information

  14. KASHANNA P Avatar

    THANKS A LOT FOR POSTING

  15. Linked servers SQL to Oracle – SQLDREAMS Avatar

    […] The EXECUTE permission was denied on the object ‘xp_prop_oledb_provider’, database &#821… […]

  16. Jessica S. (@Coffee4Jess) Avatar

    Thank you! Just what I needed 🙂

  17. Madan Avatar
    Madan

    Its worked for Me..Thanks

  18. m Avatar
    m

    It worked perfectly

Leave a comment

I’m Sreekanth

Welcome to MSSQLTREK, my little corner of the internet where I geek out about SQL Server, databases, and all things cloud. This blog is my space to share lessons learned, cool tips, real-world troubleshooting stories, and the occasional deep dive into data and performance. Whether you’re a fellow Cloud Architect, DBA, Developer, or just cloud-curious, come along for the ride — let’s explore, optimize, and build awesome data solutions together!

Let’s connect