July 18, 2016 at 7:01 pm
Hi All,
Just had a complaint from an user about the errors he was getting when tried to do the right click/edit a table. The user has: windows login - only public server role, mapped db user as a member of the db_datareader,db_datawriter and public database roles.
The first error was:
An exception occured while executing a Transact-SQL statement or batch.
Additional info: VIEW SERVER STATE permission was denied on object 'server', database 'master' ... Error:300
and the next one appearing after pressing the OK button..
Exception has been thrown by the target of an invocation.(mscorlib)
Additional info: Attempted to read or write protected memory. This is often an indication that other memory is corrupt.
The errors are pretty confusing, especially the first one that suggests the lack of credentials.
The cause of the errors is the lack of compatibility between SSMS 2012 and the Sql Server 2014 database engine. Now, this may be obvious for some people
but because I found a lot of workarounds that includes granting the View Server State permissions - which is not good, I decided to share the experience 🙂
Upgrade to SSMS 2016, it's free and don't take much time.
Regards
Dean
D.Mincic
😀
MCTS Sql Server 2008, Database Development
July 19, 2016 at 6:07 am
Upwards compatibility is never guaranteed. This is because new functionality is introduced that older software can't cope with.
----------------------------------------------------The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood... Theodore RooseveltThe Scary DBAAuthor of: SQL Server 2017 Query Performance Tuning, 5th Edition and SQL Server Execution Plans, 3rd EditionProduct Evangelist for Red Gate Software
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply