January 25, 2024 at 1:47 pm
Cannot open backup device. Operating System error 5.
SQL Backup failing to network share.
SQLServer service runs under NT Service\MSSQLSERVER.
Is changing to a network service or domain account the only option ?
NT Service\MSSQLSERVER is Not searcheable in the network share folder.
Any interim solutions.
Thanks
January 25, 2024 at 5:58 pm
The service has no access to the network share. The ONLY solutions are to switch it to an account that has access OR store the backup files locally and manually move them to where they need to go.
ALL local accounts (like NT Service\MSSQLSERVER) are local to the machine and will not have access to your network storage.
The above is all just my opinion on what you should do.
As with all advice you find on a random internet forum - you shouldn't blindly follow it. Always test on a test server to see if there is negative side effects before making changes to live!
I recommend you NEVER run "random code" you found online on any system you care about UNLESS you understand and can verify the code OR you don't care if the code trashes your system.
January 25, 2024 at 9:57 pm
So, it looks like your SQLServer service is running under NT Service\MSSQLSERVER and is hitting a wall when trying to access a network share. Classic case of permission drama. Your service account is like that one person at a party who can't get past the velvet rope because they're not on the guest list. In tech speak, it's a local account, which means no backstage passes to the network storage.You asked if switching to a network service or a domain account is the only option. Well, it's the most straightforward one. Think of it as getting a VIP pass for your service account. It's like telling the bouncer, "Hey, this account's with me," and suddenly, doors open.But, if for some reason you can't or don't want to switch accounts, there's a workaround. It's like the tech equivalent of sneaking in through the back door. You could store the backup files locally and then manually strut them over to where they need to be. It's more hands-on and a bit of a hassle, but hey, sometimes you gotta do what you gotta do.Remember, though, changing things in the world of SQL Server can be like juggling flaming torches – thrilling but potentially hair-raising. So, test your changes on a non-critical server first. Don't just take my word for it – or anyone else's on the internet
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply