The database snapshot was saved by a newer version of SQL Compare

GurpreetGill · March 14, 2019 5:43AM

Hi
We are using RG Azure DevOps extension ( build and Release) to do the deployments to SQL Server.
Everything was working well, but suddenly today start getting deployment error as

"The database snapshot was saved by a newer version of SQL Compare"

We are not using SQL Compare any where, but just use SQL Change Automation only.

Any pointer to look into?

Thanks
Gill

Diogo · March 14, 2019 11:44AM

Hi @GurpreetGill,

SQL Change Automation uses SQL Compare internally so that's why you saw this message.

I think I reproduced your issue and there was a problem trying to update SQL Change Automation from the Powershell Gallery. We've release a new version of the Azure DevOps extensions (3.0.5 for Build and 3.0.3 for Release). Could you please try it and see if it resolves your problem?

Thanks

GurpreetGill · March 14, 2019 2:02PM

Hi Diogo

No more ""The database snapshot was saved by a newer version of SQL Compare" error

but now getting this.

System.Management.Automation.CmdletInvocationException: The project C:\Windows\TEMP\DLM Automation\y4oa5k4a.0yr\XXXXXX.sqlproj can not be read: The type initializer for 'Microsoft.Build.Shared.NativeMethodsShared' threw an exception. ---> RedGate.Versioning.Automation.Shared.Errors.TerminatingException: The project C:\Windows\TEMP\DLM Automation\y4oa5k4a.0yr\XXXXXX.sqlproj can not be read: The type initializer for 'Microsoft.Build.Shared.NativeMethodsShared' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Microsoft.Build.Shared.NativeMethodsShared' threw an exception. ---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime.InteropServices.RuntimeInformation, Version=4.0.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

LegacyVSTSPowerShellHost.exe completed with return code: -1.

GurpreetGill · March 14, 2019 2:05PM

Hi @Diogo

no more getting this error

"The database snapshot was saved by a newer version of SQL Compare"

but start getting new one.

System.Management.Automation.CmdletInvocationException: The project C:\Windows\TEMP\DLM Automation\y4oa5k4a.0yr\SCA.NW04.sqlproj can not be read: The type initializer for 'Microsoft.Build.Shared.NativeMethodsShared' threw an exception. ---> RedGate.Versioning.Automation.Shared.Errors.TerminatingException: The project C:\Windows\TEMP\DLM Automation\y4oa5k4a.0yr\SCA.NW04.sqlproj can not be read: The type initializer for 'Microsoft.Build.Shared.NativeMethodsShared' threw an exception. ---> System.TypeInitializationException: The type initializer for 'Microsoft.Build.Shared.NativeMethodsShared' threw an exception. ---> System.IO.FileNotFoundException: Could not load file or assembly 'System.Runtime.InteropServices.RuntimeInformation, Version=4.0.1.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.

LegacyVSTSPowerShellHost.exe completed with return code: -1.

Please help.

Thanks
Gill

Diogo · March 14, 2019 3:01PM

Hi @GurpreetGill

There might be a problem with our latest Powershell module then.
Could you please try to change your tasks to use version 3.1.10.3430? You can do that on your task definitions if you go to "SQL Change Automation version", pick "Specific" and enter 3.1.10.3430 on the specific version to be used and Save.

Does it help?

GurpreetGill · March 14, 2019 3:40PM

Hi @Diogo

Version "3.1.10.3430", worked.

BUT, this is not good example, where you release latest version without proper simple testing.

Hope for quick fix.

Thanks
Gill

samssb82 · March 14, 2019 7:41PM

We are also using the Azure DevOps plug in and I am receiving this same error. It doesn't appear it is downloading / installing the latest version of the Powershell module. Even if I specify a specific version it doesn't appear to be downloading / installing it. Also, how do you see what version this error is referencing?

Diogo · March 14, 2019 8:53PM

@samssb82 each cmdlet outputs the version of the module. For example

If you have SQL Change Automation locally installed on your agents I think it will still use the installed version.

samssb82 · March 14, 2019 8:56PM

@Diogo - Thanks for the response. I do see that portion, but when it says "The database snapshot was saved by a newer version of SQL Compare" it doesn't reference what version the database snapshot was saved with.

Diogo · March 14, 2019 9:02PM

samssb82 I'm afraid that version is not exposed by the error message.

Are you still getting this problem with version 3.1.10.3430 of SQL Change Automation?

samssb82 · March 14, 2019 9:52PM

@Diogo - I believe my problem is that the Azure Devops plugin is not installing the latest version. It appears it always had prior to this afternoon as our release servers all have various numbers of older versions installed (up through 3.1.9 something), but do not have the 3.1.10 version installed.

Diogo · March 14, 2019 10:11PM

@samssb82 you might need to update the Build and Release extensions to the versions I mentioned earlier today.

If that does not work please contact support so that we can have a closer look.

ChrisKaczor · March 19, 2019 4:21PM

In our case we're seeing this error using TFS which installs/uses the ReadyRoll.MSBuild NuGet package.

According to our build logs a few days ago we were getting ReadyRoll.MSBuild.3.0.19073.6043 and everything worked fine. Today we're getting ReadyRoll.MSBuild.3.0.19077.6044 which has this error.

Shouldn't a newer version be okay? We haven't done anything manually - this is just a new package that is automatically being provided by NuGet via the TFS add-on.

I don't see the 3.0.19073.6043 version on NuGet anymore - did it get removed? I'm guessing it had a newer version of SQL Compare than what is in the current version and since we had builds/deploys using that version we're getting this error now that the older version is being used.

On a dev system I deleted everything in __SchemaSnapshot and that got around it but I'd rather not do that for all our databases/environments.

ChrisKaczor · March 19, 2019 4:33PM

I did some digging and the SQL Compare version definitely changed. Here are the versions of RedGate.SQLCompare.Engine.dll in the various versions:

- 3.0.19059.5510 had 13.7.3.9474
- 3.0.19073.6043 had 13.7.5.9770
- 3.0.19077.6044 has 13.7.3.9474

I'm guessing 3.0.19073.6043 had the new version of SQL Compare accidentally (or it had a bug) and it was yanked once someone realized and it was replaced with 3.0.19077.6044 that had the old version.

You can't do that! Now any databases done with the 3.0.19073.6043 version will have that error.

Diogo · March 21, 2019 3:34PM

@ChrisKaczor I can only apologize for any problems we may have caused you.
We've released version 3.0.19080.6206 which should solve your problem.

WillC · June 24, 2019 8:36AM

I'm getting this issue with version 3.2.19157.8337, even though our last successful release was also deployed with the same version.

Diogo · June 24, 2019 4:02PM

Hi @WillC does that still happen on version 3.2.19162?

WillC · June 25, 2019 6:01AM

We have the version set to latest on our release and that version is not being picked up. It is using the 3.2.19157 version, I added that in as a specific version and it can't be found

Diogo · June 25, 2019 8:53AM

Hi @WillC, that version should be available now.
Hope it helps.

The database snapshot was saved by a newer version of SQL Compare

Answers

Product Learning

Community Forums

Events & Friends

Simple Talk