Forum Discussion
Haniel Croitoru
Dec 09, 2020Learn Expert
Applying Sensitivity Labels to files prior to Migration
Hi all,
I'm in the process of migrating a client from a file share to Microsoft 365. Part of the migration includes applying sensitivity labels. So far, we did an inventory and know what labe...
GlennDPC
Mar 25, 2021Copper Contributor
I also have this problem!
Doesn't matter how simple the implementation is.. simply calling this function causes a hardcrash of powershell ide or command line. as you said around 50% of the time.
Doesn't matter how simple the implementation is.. simply calling this function causes a hardcrash of powershell ide or command line. as you said around 50% of the time.
- Bill_DavisApr 07, 2021Copper ContributorI also have this problem. Set-AIPFileLabel will crash a huge amount of the time either with a System.NullReferenceException: or sometimes even worse with a " System.AccessViolationException: Attempted to read or write protected memory."
Using MCAS is not really an replacement for powershell.- StephenESAug 02, 2021Copper Contributor
Has anyone found anything from MS on this?
We too are receiving these random crashes. Initially we thought it was due to some complex hash tables we used to reset labels.
We made some minor mods but still randomly get these errors.
TRY/CATCH did not help. Any fixes found on your end?
- Bill_DavisAug 06, 2021Copper Contributor
We noticed this was worse when deleting files during the labeling process. Our workaround is to leave the files around until we've labeled them all, and then delete them. My guess is that there is some issue where the powershell commands are holding onto file handles and breaking if those files disappear.