Visual Studio – FIX: The ‘SqlStudio Profile Package’ Package Did Not Load Correctly

SQL
1 Comment

I am not sure what changes I made in one of my Virtual Machine, but I was running into an issue. In this blog, we would discuss how to fix error “The ‘SqlStudio Profile Package’ package did not load correctly” while launching Visual Studio.

Visual Studio - FIX: The 'SqlStudio Profile Package' Package Did Not Load Correctly ssdt-err-01

I checked into the file mentioned but didn’t find anything interesting to tell me the solution.

WORKAROUND/SOLUTION

I search on the internet and found various solutions. In this blog, I would share the consolidated list of solutions.

  1. Based on one of the StackOverFlow link, delete below file.

%UserProfile%\AppData\Local\Microsoft\VisualStudio\11.0\ComponentModelCache

  1. Rename below folders

C:\Users\<UserName>\AppData\Roaming\Microsoft\VisualStudio\11.0

C:\Users\<UserName>\AppData\Local\Microsoft\VisualStudio\11.0

  1. Download and install SSDT from below this link.
  2. Go to ‘Add/Remove Programs’ in Control Panel. Select “Microsoft SQL Server 2012 Data-Tier App Framework”, right click and choose “Repair”. If you find more versions of it, do the repair for all of them.

For me, option # 1 worked. If you face the same problem, please comment and let me know which option works for you. If you find any other solution, please comment and share with others. We will be looking forward to learning from you.

If you face any error which is difficult to troubleshoot. Do reach out to us and we might have seen them earlier and can fix them pretty easily if we know the solution by heart.

Reference: Pinal Dave (https://blog.sqlauthority.com)

SQL Error Messages, SQL Profiler, SQL Server, Visual Studio, Windows
Previous Post
SQL SERVER – Availability Group Seen in SSMS but missing in Cluster Manager. What’s Wrong?
Next Post
SQL SERVER – Cannot Drop the Assembly ‘ISSERVER’, Because it Does not Exist or You do not Have Permission

Related Posts

1 Comment. Leave new

  • Thank you,

    It worked for me on VS2019 by cleaning the local cache:
    C:\Users\userAccount\AppData\Local\Microsoft\VisualStudio\16.0_…… (current date folder)

    Reply

Leave a Reply