Check out VSS writers state, most likely you will find some writers in a failed state. Aslo, please include your case ID (as it is advised by our forum rules), otherwise this topic will be removed by a moderator.
PTide wrote:Is your Windows 10 machine somehow taking part in AlwaysOn availablility group?
what do you mean with Always on Availability group ? its a member of a AD.
I managed to find the error I believe , VSS shadow copy services was manual and not started.
have to start it manually.
I've changed the start up type to automatically and started the server.
I've run the job once again but the same error .
what do you mean with Always on Availability group? its a member of a AD.
Just had an assumption that your problem could be MSSQL AlwaysOn related. Nevermind.
I managed to find the error I believe , VSS shadow copy services was manual and not started.
have to start it manually.
I've changed the start up type to automatically and started the server.
I've run the job once again but the same error .
Anyway thank you for your answer.
none of your solutions seems to work.
the only solution I found is reboot the VM.
created a schedule to reboot before the backup until I find a real solution.
That's exactly the reason why we always insist on opening a case with support team - troubleshooting on the forum is not an easy thing to do, especially without seeing your logs. Please open a case with support team and post your case ID in this topic.