Hi,

We are facing a post migration issue in our environment. We have migrated our system to server 2012 and sql 2014 ( running always and log shipping to Azure VM)
Recently we faced a log shipping failure alert as

Executed as user: username. The process could not be created for step 1 of job 0xE0FA8F9017A9064381AD5D86BAA3AA08 (reason: The system cannot find the file specified).  The step failed.

When troubleshoot found that sqllogship application file missing in BINN folder so can not run the first step, later copied the sqllogship application file from  secondary replica and fixed it but still the issue seem to occurring every day.
on checking SQL logs even viewer no concrete messages related to this issue.

Also another issue is suddenly we could not RDP the server before trouble shooting it application also looses connection to DB server, on checking in secondary replica the cluster for the primary is in down state but the server is alive. hence we need to fail-over to secondary and then re-start the primary server, after re-start the always on picks up and all are back to normal
In eventvwr we do not see any message but in sql logs we see a message as

The operating system returned error 2(The system cannot find the file specified.) to SQL Server during a read at offset 0x000000001c8000 in file 'C:\Program Files\Microsoft SQL Server\MSSQL12.MSSQLSERVER\MSSQL\Binn\mssqlsystemresource.mdf'. Additional messages in the SQL Server error log and system event log may provide more detail. This is a severe system-level error condition that threatens database integrity and must be corrected immediately. Complete a full database consistency check (DBCC CHECKDB). This error can be caused by many factors; for more information, see SQL Server Books Online.

Can someone direct me how to troubleshoot it, because from eventvwr or storage logs no error is helpful

Thanks

Sounds like an hardware/OS issue. Check the integrity of you hardware (disks, ram, network) and OS (AV).

Hi Stefan,

Thanks, we suspect as hardware issue. but we can not trace it back. one thing we noticed is AD server is not upgraded so we are planning to upgrade AD server and check for a re-occurrence if any