[SA 9.0.176 Pro] - Update workspace

	Mindflux wrote:
	Hadn't you used the SCS repo previously with success or am I remembering wrong?

In previous version, yes. In 9, no. I've been struggling with this since the beta. The funny (and most annoying) thing is that only the tables are able to evade me, all the rest comes down to the workspace.

Last edited by gemisigo on Wed Nov 09, 2016 11:07 am; edited 1 time in total

	SysOp wrote:
	I believe what you see in the log indicates the root cause of the issue. There is something wrong with SQL Server Shared Management Objects. To fix this issue, please follow instructions here https://msdn.microsoft.com/en-us/library/ms162189.aspx?f=255&MSPPError=-2147217396

I've already been through that page. The installer offered to repair the installation but that did not help.

	SysOp wrote:
	Another way to fix that is to install a recent version of SSMS, which is now free. You can download one here https://msdn.microsoft.com/en-us/library/mt238290.aspx?f=255&MSPPError=-2147217396

I'm already using that version with its last update (26 October) on board. I repaired that one as well, alas to no avail.

What I noticed when uninstalling stuff was that installed applications (components) were named:
Microsoft SQL Server 2014 Management Objects
Microsoft SQL Server 2014 Management Objects (x64)
Microsoft SQL Server 2016 Management Objects
Microsoft SQL Server 2016 Management Objects (x64)

There were no Microsoft SQL Server 2012 Management Objects entries whatsoever and 2012 is the instance version I'm desperately trying to press under source control.

I also tried to figure out if it worked in an 2014 instance but when creating an 2014 localdb instance with the test database in it and test tables created, both Database Explorer and Repository Browser failed to retrieve anything beside schema dbo. Popups, however, had shown the tables and were able to retrieve columns as well.

I removed and then reinstalled the last version of SQL Server Management Studio. The error message persists, also SMO for 2014 x86/x64 were not reinstalled. I downloaded and installed Shared Management Objects from the SQL Server feature pack for both 2012 and 2014. Now those are okay, but I still get that error message. It is referring to Microsoft.SqlServer.Smo, Version=9.0.242.0. Why 9.0.x? Isn't that SQL Server 2005?

I don't think Sa asks for any specific version of SMO. It shouldn't. I'm researching this one. Please hold on for a little while.

It appears that two specific versions are actually tried, and it's expected that newest SMO installer should create references for old versions for backward compatibility, but it looks like not anymore

saddl.exe utility attemps first to load assembly Microsoft.SqlServer.Smo, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91 and as a fall back if that one fails, it attempts to load Microsoft.SqlServer.Smo, Version=9.0.242.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91. If both fail you get the message recorded in the log file.

Here is a link to Microsoft SQL Server 2008 Service Pack 2 Feature Pack. This is a collection of stand-alone install packages that includes SMO v10 as well.

I can't believe it :) I tried every damned Feature Pack from 2016 through 2014 and 2012 back to 2008 R2 for both x86 and x64, have even given a try to 2008 sp3 versions which failed when it refused to install over a newer version. And now you're telling me I've given up before making the final step? Not that I'd expect this one not to fail. I guess I'll have to remove 2008 R2 versions for this to work.

Any reasons SA is not updated to work with the latest one?

Odd.

I'm not even sure how they all got loaded but this is on my Workstation but obviously my SCS works:

I don't have the 2008 SP2 management objects in this list.

Odd, indeed. I managed to make it work, finally. This is what I have now:

As you can see, I too have 2008 R2 (though a slightly newer version 10.53 vs 10.51) and even that one did not work until I installed the plain 2008 (10.3.5500.0).

The only thing I can think of is at one time I had SSMS 2008 (non R2) on my machine, and I removed it in favor of the R2 version (for some reason). Perhaps a shared library got left behind.

This all being said and discovered if the dependency is that fragile and specific perhaps SQL Assistant can include it in the installer somehow?

	Quote:
	Any reasons SA is not updated to work with the latest one

Unfortunately not. I assume developers who implemented the interface to SMO worked with version available at the time and then everything was fine while Microsoft maintained backward compatibility. At some point I guess they dropped support for old versions.

I have raised a high priority ticket for this issue.

SysOp wrote:

	Quote:
	Any reasons SA is not updated to work with the latest one

Unfortunately not. I assume developers who implemented the interface to SMO worked with version available at the time and then everything was fine while Microsoft maintained backward compatibility. At some point I guess they dropped support for old versions.

I have raised a high priority ticket for this issue.

Please ask that if they can don't break backwards compatibility. If suddenly SQL Assistant needs SMO from 2012,2014 or 2016 and I'm running the SMO libraries from 2008 I don't want to chase this down too. Can the logic check for (latest)SMO on the machine and attempt to use that?

	Quote:
	If suddenly SQL Assistant needs SMO from 2012,2014 or 2016 and I'm running the SMO libraries from 2008 I don't want to chase this down too. Can the logic check for (latest)SMO on the machine and attempt to use that

I hope so too. But probably depends on depends on SMO cross-version compatibility.

Sorry, it looks like this topic has been accidentally locked.