Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SQL Server 2017 compatibility issues #5

Open
retohugi opened this issue Apr 25, 2018 · 0 comments
Open

SQL Server 2017 compatibility issues #5

retohugi opened this issue Apr 25, 2018 · 0 comments
Labels

Comments

@retohugi
Copy link
Collaborator

It seems we have issues restoring DBs with Import-ScDatabases, while manual restores work fine. Exception encountered:

The running command stopped because the preference variable "ErrorActionPreference" or common parameter is set to Stop: System.Data.SqlClient.SqlException (0x80131904): The operating system returned the error '32(The process cannot access the file because it is being used by another process.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\xxx_sc8_internet_master.mdf'. File 'Sitecore.Master.Data' cannot be restored to 'C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\xxx_sc8_internet_master.mdf'. Use WITH MOVE to identify a valid location for the file. The operating system returned the error '32(The process cannot access the file because it is being used by another process.)' while attempting 'RestoreContainer::ValidateTargetForCreation' on 'C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\xxx_sc8_internet_master.ldf'. File 'Sitecore.Master.Log' cannot be restored to 'C:\Program Files\Microsoft SQL Server\MSSQL14.MSSQLSERVER\MSSQL\DATA\xxx_sc8_internet_master.ldf'. Use WITH MOVE to identify a valid location for the file. Problems were identified while planning for the RESTORE statement. Previous messages provide details. RESTORE DATABASE is terminating abnormally. at Microsoft.SqlServer.Management.Common.ConnectionManager.ExecuteTSql(ExecuteTSqlAction action, Object execObject, DataSet fillDataSet, Boolean catchException) at Microsoft.SqlServer.Management.Common.ServerConnection.ExecuteNonQuery(String sqlCommand, ExecutionTypes executionType, Boolean retry) ClientConnectionId:0a3d41a0-6575-4bfa-8925-9b5c7e7af734 Error Number:3634,State:1,Class:16

@retohugi retohugi added the bug label Apr 25, 2018
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

1 participant