SQL Server 2017: Attaching DB from unc path error 5123

Question

Post reply

SQL Server 2017: Attaching DB from unc path error 5123

deubel_m

SSC-Addicted

Points: 465
More actions
May 28, 2019 at 9:24 am

#3647746

Hi there,
as the title implies we face an issue with attaching dbs on network shares. We always get the error 5123.
Even if the db on the current server, has been detached and reattached to the same server.
Havn't found any hints so far.

Regards
June 3, 2019 at 2:11 pm

This was removed by the editor as SPAM
June 3, 2019 at 2:13 pm

This was removed by the editor as SPAM
July 16, 2019 at 10:02 am

This was removed by the editor as SPAM
July 16, 2019 at 10:03 am

This was removed by the editor as SPAM

Viewing 8 posts - 1 through 7 (of 7 total)

You must be logged in to reply to this topic. Login to reply

Jo Pattyn SSC-Dedicated Points: 32350 More actions · Answer 1

Service account of instance has access to the share?

deubel_m SSC-Addicted Points: 465 More actions · Answer 2

Jo Pattyn wrote:

Service account of instance has access to the share?

Yes, definitly. The service accounts have full control on the share and has full control NTFS permissions.

Creating dbs on the share is not a problem. Only detaching and reattaching.

Sue_H SSC Guru Points: 90860 More actions · Answer 3

Did you check the permissions on the files themselves (not the share)? When detatching files in SSMS, if you aren't running SSMS as administrator, the file permissions change to whoever detached and the service account no longer has access.

Sue