Issue with SetNamedSecurityInfo Returning Error Code 59 on Shared File

Rishi C 0

Hello,

I am encountering an issue with the **SetNamedSecurityInfo **API while attempting to modify the security settings of shared files. I have five shared files, and the API works as expected on four of them. However, for one specific shared file, the API returns error code 59 (ERROR_UNEXP_NET_ERR: An unexpected network error occurred), even though the file is fully accessible via the Microsoft Management Console (MMC).

Could you please advise on why this specific file would trigger error 59 in **SetNamedSecurityInfo **while being accessible through MMC, and how I can resolve this issue?

Tong Xu - MSFT 2,461 Reputation points Microsoft Vendor

2024-10-01T02:54:37.2066667+00:00

What kind of the specific shared file? What's the difference between the specific shared file and the four of them?
Tong Xu - MSFT 2,461 Reputation points Microsoft Vendor

2024-10-01T03:10:37.86+00:00

And could you show how do you use it in your code?
Rishi C 0 Reputation points

2024-10-01T13:06:55.75+00:00

Am so sorry, Am a developer from product company. I guess, Am not allow to sharing the product code.

Also am mentioned specific share file is not a uncommon one. It's looks like common shared files.

For example :

Share1 ( SACL enabled Successfully )

Share2 ( SACL enabled Successfully )

Share3 ( SACL enabled Successfully )

Share4 ( SACL enabled Successfully )

Share5 ( Failed due to error code 59 )

But able to view the shared file via MMC
Rishi C 0 Reputation points

2024-10-01T13:09:49+00:00

Sorry Tong, Am developer from product based company and Am not allow to share the code
Tong Xu - MSFT 2,461 Reputation points Microsoft Vendor

2024-10-02T03:57:31.6633333+00:00

So... what's the difference of the specific shared file of data type identifies? Error code 59 means an unexpected network error occurred. Is that the shared in a group or domain which need privilege to access?
Rishi C 0 Reputation points

2024-10-03T14:30:12.6833333+00:00

The above image contains information about how SACL to be apply for our shares. Also the user who used for impersonation haves enough privilege to access the shared folder.
Tong Xu - MSFT 2,461 Reputation points Microsoft Vendor

2024-10-04T07:29:11.4433333+00:00

Honestly, I don't have any clues. This is more about to the privilege of Ntfs system. But right now you have no problem with access deny. Error code 59 means you have network issue. Are they working on some kind of server or Active Directory?

At least a mininal reproducible sample that we can found some crumbs.
Rishi C 0 Reputation points

2024-10-07T12:07:21.9766667+00:00

Am using Windows server os and it's joined in Active directory. If error code 59 is network issue means then how the share is accessible via MMC.
Tong Xu - MSFT 2,461 Reputation points Microsoft Vendor

2024-10-08T07:07:20.1666667+00:00

Ok, I got this. Considered your work around and business confidentiality. I'll provide a plan to help you solve it. It may need to be paid. If you need it, I'll consult the high level developer.

1 answer

Tong Xu - MSFT 2,461 Reputation points Microsoft Vendor

2024-10-08T09:14:28.38+00:00

I've already confirmed. High level developer cam help you build the environment to reproduce and solve, Don't worry about it, if the support engineer determines that the issue is the result of a bug the service request will be a no-charge case and you won't be charged.

As this issue is complex, to resolve this issue as soon as possible, you can open an incident via 'Contact us' tab at link below:https://developer.microsoft.com/en-us/windows/support/

Please choose the 'Technical Support - Coding/Debugging' for Windows SDK for this issue.

Thank you for accepting this answer in advance.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Issue with SetNamedSecurityInfo Returning Error Code 59 on Shared File

1 answer

Your answer