October 3, 2018 at 9:36 pm
I needed to install a new instance of SQL2014 on a server where I had already applied SQL2014SP2. Now when I attempt to apply SP1 or SP2 I am receiving this error message (expected version number changes for SP1 or 2):
The version of SQL Server instance VARONIS does not match the version expected by the SQL Server update. The installed SQL Server product version is 12.0.2000.8, and the expected SQL Server version is 12.2.5000.0.
Running @@version on the instance shows: 12.0.2000.8
Any way around this?
Thanks
October 4, 2018 at 9:44 am
Does this appear as soon as you start setup? There isn't a place/time to choose the instance to apply this against?
October 4, 2018 at 10:10 am
The SP runs through the pre-reqs without an issue, but once it gets to the available instances screen it does not allow the new instance to be selected.
October 4, 2018 at 10:36 am
Haven't seen that, though I'm not sure I've done this with 2014. I have with 2012 and 2016, and both seem to work.
Can you verify this on another instance? Perhaps there's a separate issue? I'd try, but I don't have a spare 2014 VM setup now. Everything is old (2012) or new (2016/17/19)
August 3, 2019 at 2:56 am
Posting a possible solution even though this is an old topic in case somebody else encounters this issue
I ran into this issue why when trying to applying SQL 2016 security update and I got the similar message "The version of SQL Server instance MSSQLSERVER does not match the version expected by the SQL Server update.". I forgot what version it started, but when you patch SQL Server; all the components are on the same build version now. So SQL Server engine would be 13.x.x.x. MSAS, RS, etc would be on the same version also. In my particular case, my MSAS version was still on RTM, even though the DB engine was on SP2. The version # displayed in the error told you the problem, but not necessary the details that you needed. That lit a light bulb and I went and connected to all the various services and found that the MSAS version was still on RTM.
I found the closed SP version. In this case, I re-applied SP2 which then corrected the MSAS version. Of course this means I downgraded some components that were at a higher patch level. To ensure that I got caught up on the various security updates, I went ahead and applied the latest CU.
I used this site to determine the various build levels and versions
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply