As ordebit Get-ADUser?

Question

As ordebit Get-ADUser?

Hello!
When you call a cmdlet with the following command: Get-ADUser -filter * -property *
I have this error popping up:

Get-ADUser : object Reference not set to an instance of an object.
line:1 char:1
+ Get-ADUser -filter * -property * | select name
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 + CategoryInfo : NotSpecified: (:) [Get-ADUser], NullReferenceException
 + FullyQualifiedErrorId : ActiveDirectoryCmdlet:System.NullReferenceException,Microsoft.ActiveDirectory.Management.Commands.GetADUser

I know that the error is causes by a specific user, probably in uchetku something wrong.
1. How to figure out what's wrong with uchetku, and correct?
2. How to handle the error that the cmdlet Get-ADUser continued to work, and was not interrupted because of an error?

Thank you!

z.s. Get-ADUser -filter * - fulfills without errors, but with -property * an error occurs

minnie.Shields87 asked July 8th 19 at 16:20

Related questions

More answers about "As ordebit Get-ADUser?"

1 answer

marques_Rutherford answered on · Answer 1 · 2019-07-08T16:22:10.575Z

marques_Rutherford answered on July 8th 19 at 16:22

add -erroraction silentlycontinue
In General, it is not necessary to search for users from all over AD
limit the scope of the searchbase-om
Or you have a mess in AD and the user to be created anywhere?

-erroraction silentlycontinue does not help, still

Get-ADUser : object Reference not set to an instance of an object.
line:1 char:1
+ Get-ADUser -filter * -property * -erroraction silentlycontinue
+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
 + CategoryInfo : NotSpecified: (:) [Get-ADUser], NullReferenceException
 + FullyQualifiedErrorId : ActiveDirectoryCmdlet:System.NullReferenceException,Microsoft.ActiveDirectory.Management.Commands.GetADUser

the search area doesn't matter, it's just, when Get-ADUser comes to a specific user, I get this error. I found out empirically. - minnie.Shields87 commented on July 8th 19 at 16:25