THE SQL Server Blog Spot on the Web

Welcome to SQLblog.com - The SQL Server blog spot on the web Sign in | |
in Search

Greg Low (The Bit Bucket: IDisposable)

Ramblings of Greg Low (SQL Server MVP, MCM and Microsoft RD) - SQL Down Under

SSMS SQL Server 2014 CU4 Issue: The type initializer for ‘PropertyMetadataProvider’ threw an exception

Published Wednesday, October 29, 2014 1:11 PM by Greg Low

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

 

Fred said:

Hi Greg,

I have the same problem than you.

Unofrtunately, I am not very familiar with ProcessExplorer.

Could you please elabaorate more on how to find the dependencies.

Thanks a lot.

November 3, 2014 2:46 PM
 

Greg Low said:

To use Process Explorer to investigate:

Download and unzip the SysInternals process explorer.

Right-click procexp.exe and make sure you Run As Administrator if you have UAC enabled.

Find and click on the SSMS process from the list of processes. Type Control-L to make the lower pane appear. This (by default) will show the DLLs involved. Find the Microsoft.SqlServer.Smo.dll and right-click it to find its properties.

Hope this helps.

November 3, 2014 5:56 PM
 

Greg Low said:

Microsoft have posted a workaround:

Temporary workaround - it's still suggested to install CU5 when it's released as that will contain the full fix.

1. Exit SSMS and SSDT

2. Open administrator command prompt

3. Run this command :

cd %WINDIR%\assembly\GAC_MSIL\Microsoft.SqlServer.Smo

4. Run this command:

rmdir /Q /S 12.0.0.0__89845dcd8080cc91

5. Run the SQL2014 setup media

6. Browse to the Maintenance tab

7. Click the Repair link to launch the repair dialog

8. Wait for pre-req steps to finish then click Repair button

9. Once the repair is finished launch SSMS – you should be able to connect without error now

November 14, 2014 5:40 PM
 

David Gardiner said:

Greg,

do you do those steps after you've installed CU4?

November 25, 2014 8:01 PM
 

Greg Low said:

I did them after. Basically if you update to CU4 and you don't see any issue when connecting to the DB engine from SSMS, then there's nothing to worry about. It's only if you then have an issue.

November 25, 2014 10:30 PM

Leave a Comment

(required) 
(required) 
Submit

This Blog

Syndication

Tags

No tags have been created or used yet.

Archives

Privacy Statement