AppSync: SQL recovery fails due to missing ldf (sql log) file(s).
Summary: In AppSync, prior to v4.0, SQL recovery fails due to missing ldf (sql log) files
This article applies to
This article does not apply to
This article is not tied to any specific product.
Not all product versions are identified in this article.
Symptoms
AppSync is failing to recover a SQL database on a mount host.
The Service Plan events will show:
Unable to recover database MyDB on the instance MySQL-QA. See the host plug-in log, application event log, and the SQL Server error log for details.
The Operating Systems Application Event log will show:
Error Mountx 17207 MSSQLSERVER FileMgr::StartLogFiles:
Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file
'L:\SourceFolder\MSSQL\logs\MyDB_2.ldf'. Diagnose and correct the operating system error, and retry the operation.
Error Mountx 17207 MSSQLSERVER FileMgr::StartLogFiles:
Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file
'L:\SourceFolder\MSSQL\logs\MyDB_3.ldf'. Diagnose and correct the operating system error, and retry the operation.
Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file
'L:\SourceFolder\MSSQL\logs\MyDB_2.ldf'. Diagnose and correct the operating system error, and retry the operation.
Error Mountx 17207 MSSQLSERVER FileMgr::StartLogFiles:
Operating system error 2(The system cannot find the file specified.) occurred while creating or opening file
'L:\SourceFolder\MSSQL\logs\MyDB_3.ldf'. Diagnose and correct the operating system error, and retry the operation.
The AppSync Plugin log on the Mount host will show:
[MountHost] SQL: Last native error: error number 5111, SQLState 01000, sql native info message [Microsoft][ODBC SQL Server Driver][SQL Server]File activation failure.
The physical file name "L:\SourceFolder\MSSQL\logs\MyDB_2.ldf" may be incorrect.
[MountHost] SQL: processSQLMessages: Message = Msg 1813, SevLevel 0, State 5, SQLState 42000, sql native info [Microsoft][ODBC SQL Server Driver][SQL Server]Could not open new database 'MyDB'. CREATE DATABASE is aborted.
[MountHost] SQL: Last native error: error number 5111, SQLState 01000, sql native info message [Microsoft][ODBC SQL Server Driver][SQL Server]File activation failure.
The physical file name "L:\SourceFolder\MSSQL\logs\MyDB_3.ldf" may be incorrect.
[MountHost] SQL: processSQLMessages: Message = Msg 1813, SevLevel 0, State 5, SQLState 42000, sql native info [Microsoft][ODBC SQL Server Driver][SQL Server]Could not open new database 'MyDB'. CREATE DATABASE is aborted.
The physical file name "L:\SourceFolder\MSSQL\logs\MyDB_2.ldf" may be incorrect.
[MountHost] SQL: processSQLMessages: Message = Msg 1813, SevLevel 0, State 5, SQLState 42000, sql native info [Microsoft][ODBC SQL Server Driver][SQL Server]Could not open new database 'MyDB'. CREATE DATABASE is aborted.
[MountHost] SQL: Last native error: error number 5111, SQLState 01000, sql native info message [Microsoft][ODBC SQL Server Driver][SQL Server]File activation failure.
The physical file name "L:\SourceFolder\MSSQL\logs\MyDB_3.ldf" may be incorrect.
[MountHost] SQL: processSQLMessages: Message = Msg 1813, SevLevel 0, State 5, SQLState 42000, sql native info [Microsoft][ODBC SQL Server Driver][SQL Server]Could not open new database 'MyDB'. CREATE DATABASE is aborted.
Cause
Software bug
Resolution
AppSync 4.0 resolves this issue.
Additional Information
The AppSync 4.0 release notes do not mention this as being fixed in the fixed in section, however it has been confirmed that the fix for this issue is in AppSync 4.0
Upgrade to AppSync 4.0 to resolve this issue.
Upgrade to AppSync 4.0 to resolve this issue.
Affected Products
AppSyncProducts
AppSyncArticle Properties
Article Number: 000170225
Article Type: Solution
Last Modified: 20 Oct 2025
Version: 6
Find answers to your questions from other Dell users
Support Services
Check if your device is covered by Support Services.