The most queried topics in this blog have been around troubleshooting or which solve specific error messages. I always feel when I see something new as messages, I try to check if this is available here using the search page. If these are not there, then I go about documenting what were the steps I took to actually solve the given problem. Once I successfully solve the problem about Unable to Open Maintenance Plan in Management Studio. I go about documenting the same back into as a blog post so that I will be able to find the same in future reference. It is this structure that has led me to posting so many error messages with resolutions. Thanks to you folks for supporting.
Sometimes taking care of the basics solves the problem in a very easy way. Recently my friend upgraded SQL Server 2008 R2 to SQL Server 2012 via in-place upgrade method. As per him, everything went well and there were no errors encountered in upgrade also.
But, when he was trying to open Maintenance Plan in SQL Server Management Studio, below was the error seen.
Here is the text of the message
Microsoft SQL Server Management Studio is unable to load this document:
Error loading from XML. No further detailed error information can be specified for this problem because no Events objects was passed where detailed error information can be stored.
When I did a desktop sharing with me, I realized that something is not looking right with Management Studio. I quickly realized that he was still using SQL Server 2008 R2 Management Studio to connect to the upgraded version. I asked him to use SQL Server 2014 Management Studio and as soon as we used that, there was no more error and we were able to open/edit maintenance plan without any problem.
So the root cause of the issue was version Mismatch of client and tool
How to check version of SQL Server? Refer my earlier blog SQL SERVER – Get Server Version and Additional Info
How to check version of Client Tools? We can use Help > About in SSMS as shown below.
Have you faced any error due to incorrect version? please share via comments. I am sure the learning experiences will help one and all.
Reference: Pinal Dave (https://blog.sqlauthority.com)
You have to pay attention to the backwards compatibility issues as well. There have been a few times where I have connected to a 2005 DB with SSMS for 2012 or 2014 and tried to use a feature that isn’t available in 2005.
Very True. Same version is always best. But with SSMS 17.x things are changing.
when I try to open Management Studio I get the error “The operation could not be completed”
I did not realize that I am opening incorrect SSMS version. Thanks!!
Happened with me as well.