Share via


Windows Cluster 2012 R2 - Impersonation Level Error

Question

Thursday, January 16, 2020 5:11 PM

Hello,

 

We are receiving an error saying "An unexpected error is keeping you from renaming the folder. If you continue to receive this error, you can use the error code to search for help with this problem. Error 0X80070542: Either a required impersonation level was not provided, or the provided impersonation level is invalid. The error occurs when attempting to rename the folder or file in the Volume folder. However, this only occurs on one of the nodes, depending on which node is the owner.

 

We experienced this with 2 of our customers. However, one of the customers upgraded the OS from 2012 R2 to 2016, therefore, the error did not occur again.

All replies (6)

Friday, January 17, 2020 8:13 AM

Hi,

This is a CSV know issue in Windows Server 2012R2.

Microsoft will release an update in the future to solve this problem. At present, please wait patiently. We apologize for the inconvenience and thank you for your understanding!

https://support.microsoft.com/en-us/help/4534309

Hope this can help you.

BR,

Daniel

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact


Friday, January 17, 2020 1:38 PM

Ok, thanks for the info. I will let the customer know.


Monday, January 20, 2020 8:10 AM

OK.

Good luck.

Daniel

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact


Monday, January 27, 2020 1:29 AM

Hi,
Just checking in to see if the information provided was helpful. Please let us know if you would like further assistance.
Best Regards,
Daniel

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact


Monday, February 24, 2020 9:11 AM

Hi,

this update not resolved my problem

Martin Hubka nework admin


Monday, February 24, 2020 9:42 AM

Microsoft will release a update to solve this know issue in the further, in other word, for now we have no way to fix this issue. No update can resolved this issue.

Please remember to mark the replies as answers if they help.
If you have feedback for TechNet Subscriber Support, contact