Working as freelancer gives an opportunity to see various kinds of error and having fun to fix them. Recently, one of my blog readers sent an email and asked assistance on the log shipping issue. He said that log shipping copy job is failing.
As usual, I asked him error message and he shared below piece from copy job history.
Message
2016-09-27 17:22:23.33Â *** Error: The password for this account has expired.
(mscorlib) ***
2016-09-27 17:22:24.01Â *** Error: Could not log history/error message.(Microsoft.SqlServer.Management.LogShipping) ***
The error message was descriptive enough. I asked him to follow below blog and share the output. SQL SERVER – How to Find Out When Your SQL Login Will Expire?
As expected, the password was expired. I asked him to put the right password for the service account for Agent because SQL Agent is used to perform the copy operation.
Once he put the right password the issue was resolved, but as a follow-up he asked me ways to avoid this in future.
SOLUTION/WORKAROUND
- Put the right password for the service account for SQL Agent on secondary.
- Make sure below property is checked so that it is not expired next time.
Have you encountered the same issue in production?
Reference: Pinal Dave (https://blog.sqlauthority.com)
3 Comments. Leave new
I had a similar experience with the standard virtual accunts, that were provided by the installer by default. Directly after installation everything was fine. After a server reoboot the services wouldn’t start.A required privelege is not…. the GPO revoked the privelege login as a service from the virtual account. Well…
I have a similar issue but Agent account is already set with password never expires. Log shipping copy job exactly runs successfully for 4 hours and fails automatically with this error. Once I restart SQL Server agent, copy job runs fine again for next 4 hours. Can some one guide if possible.