Post reply

SSMS connection attempt results in "Errors in the metadata manager. ..."

  • July 17, 2019 at 3:23 pm

    #3663801

    Hello experts,

    I have a colleague who's trying to connect to one of our dev database servers, and when they launch SQL Server Management Studio, they see this error after clicking connect:

    Errors in the metadata manager. Either the trace with the ID of 'MicrosoftProfilerTrace156...' does not exist in the server with the ID of 'DBSERVER', or the users does not have permissions to access the object.

    I tried some quick Googling and, as I suspected, most of the search result are about permissions to run Profiler. But I can't understand why any permissions for Profiler would matter when they are just trying to connect to the db server and are not trying to connect through Profiler.

    One possible clue - in the error, 'DBSERVER' is just the computer name, not the fully qualified name. Is it possible that some part of their SSMS installation is having an issue with name resolution? If so, does anyone know how I can go about troubleshooting that?

    Thanks for any help,

    webrunner

    -------------------
    A SQL query walks into a bar and sees two tables. He walks up to them and asks, "Can I join you?"
    Ref.: http://tkyte.blogspot.com/2009/02/sql-joke.html

  • July 18, 2019 at 4:10 pm

    #3664235

    Thanks for posting your issue and hopefully someone will answer soon.

    This is an automated bump to increase visibility of your question.

  • July 18, 2019 at 5:17 pm

    #3664254

    I've seen related errors with Analysis Services before - you may want to check if they are connecting to Analysis Services or Database Engine.

    Sue

Viewing 3 posts - 1 through 2 (of 2 total)

You must be logged in to reply to this topic. Login to reply