August 17, 2018 at 9:10 am
Hi,
SQL server agent is running with the same service account on primary and secondary servers.
The account has read/write access on the backup share.
But the LS backup job is filing without any error. There are no errors in error log.
Message
Executed as user: xx1. The step failed.
is the SQL server service also need to run with the same service account on the primary?
Thank you !!
August 17, 2018 at 12:48 pm
adisql - Friday, August 17, 2018 9:10 AMHi,SQL server agent is running with the same service account on primary and secondary servers.
The account has read/write access on the backup share.
But the LS backup job is filing without any error. There are no errors in error log.Message
Executed as user: xx1. The step failed.is the SQL server service also need to run with the same service account on the primary?
Thank you !!
That's not much information to go on. Try look at the log_shipping_monitor_history_detail in msdb.
You can also pull the command out of the job and run it from the command line on the server which will usually give more information.
Did this ever work or is this a new process on the server?
Sue
August 20, 2018 at 6:41 am
Sue_H - Friday, August 17, 2018 12:48 PMadisql - Friday, August 17, 2018 9:10 AMHi,SQL server agent is running with the same service account on primary and secondary servers.
The account has read/write access on the backup share.
But the LS backup job is filing without any error. There are no errors in error log.Message
Executed as user: xx1. The step failed.is the SQL server service also need to run with the same service account on the primary?
Thank you !!
That's not much information to go on. Try look at the log_shipping_monitor_history_detail in msdb.
You can also pull the command out of the job and run it from the command line on the server which will usually give more information.
Did this ever work or is this a new process on the server?Sue
This is a new process to set up.
I tried executing the job command from the backup Job step on the SQL server:
and it displayed dialog that .NET Framework 3.5 is required on the server.
August 20, 2018 at 6:57 am
adisql - Monday, August 20, 2018 6:41 AMSue_H - Friday, August 17, 2018 12:48 PMadisql - Friday, August 17, 2018 9:10 AMHi,SQL server agent is running with the same service account on primary and secondary servers.
The account has read/write access on the backup share.
But the LS backup job is filing without any error. There are no errors in error log.Message
Executed as user: xx1. The step failed.is the SQL server service also need to run with the same service account on the primary?
Thank you !!
That's not much information to go on. Try look at the log_shipping_monitor_history_detail in msdb.
You can also pull the command out of the job and run it from the command line on the server which will usually give more information.
Did this ever work or is this a new process on the server?Sue
This is a new process to set up.
I tried executing the job command from the backup Job step on the SQL server:
and it displayed dialog that .NET Framework 3.5 is required on the server.
On SQL Server 2016, this was fixed in CU1.
You could install .NET Framework 3.5 and restart the server to get things working but you really should get current on patches.
Sue
August 20, 2018 at 8:39 am
Sue_H - Monday, August 20, 2018 6:57 AMadisql - Monday, August 20, 2018 6:41 AMSue_H - Friday, August 17, 2018 12:48 PMadisql - Friday, August 17, 2018 9:10 AMHi,SQL server agent is running with the same service account on primary and secondary servers.
The account has read/write access on the backup share.
But the LS backup job is filing without any error. There are no errors in error log.Message
Executed as user: xx1. The step failed.is the SQL server service also need to run with the same service account on the primary?
Thank you !!
That's not much information to go on. Try look at the log_shipping_monitor_history_detail in msdb.
You can also pull the command out of the job and run it from the command line on the server which will usually give more information.
Did this ever work or is this a new process on the server?Sue
This is a new process to set up.
I tried executing the job command from the backup Job step on the SQL server:
and it displayed dialog that .NET Framework 3.5 is required on the server.
On SQL Server 2016, this was fixed in CU1.
You could install .NET Framework 3.5 and restart the server to get things working but you really should get current on patches.Sue
Thank you Sue !!
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply