Value cannot be null - by CQuel

Status : 

  External<br /><br />
		This item may be valid but belongs to an external system out of the direct control of this product team.<br /><br />
		A more detailed explanation for the resolution of this particular item may have been provided in the comments section.

Sign in
to vote
ID 573771 Comments
Status Closed Workarounds
Type Bug Repros 8
Opened 7/8/2010 3:56:04 AM
Access Restriction Public


First installed Express Edition (to try), but after installation I always get the same error in SSMS. After connecting to server, after expanding databases, ...

Value cannot be null
Parameter name: viewInfo (Microsoft.SqlServer.Management.SqlStudio.Explorer)
Sign in to post a comment.
Posted by Daniel Kevorkian on 9/4/2014 at 12:40 PM
FIX: Add your user as a local admin. Log off and log back in. Installation works; no error!
Posted by weir on 1/17/2014 at 11:29 AM
BillyShledon's workaround-- running SSMS as Administrator-- worked for me. Prior to trying that I had verified my %TEMP% and %TMP% paths were valid and tried the "2" dir workaround without success. SSMS is on Windows 8.1, and the error was appearing after connecting to a server, both when the client tools were R2 RTM and after applying R2 SP2.
Posted by tedka on 6/10/2011 at 12:41 PM
Chiken79 - nailed it - missing dir after cleanup tool - wierd that dir is called "2"
Posted by Microsoft on 5/20/2011 at 8:36 AM
We were able to repro the issue, this is actually a .net issue. Repairing .net 4.0 usually solves this issue.

Devesh Nagpal
Posted by TechVsLife2 on 10/17/2010 at 9:52 AM
Thread posted here:
Posted by TechVsLife2 on 10/17/2010 at 9:52 AM
Same problem--got this error only after the latest round of windows security updates and also installing windows Live Essentials. Not sure which is the cause. Repair does not solve, no workaround solves. Using sql R2 x64 on windows 7 x64.
Posted by kokoś on 7/9/2010 at 7:27 AM
I installed SQL Server 2008 R2 Enterprise Edition (64-bit) on Windows Server 2008 R2 and at first everything was OK. After installing IBM iAccess I receive the same error. Repairing SQL Server installation and even reinstalling it does not help.