Trouble running mailbox search Exchange 2016

When trying to run a mailbox search from ECP or command shell we get the same errors, copied below.  Any idea on what direction to troubleshoot this?

[PS] C:\Windows\system32>New-MailboxSearch

cmdlet New-MailboxSearch at command pipeline position 1
Supply values for the following parameters:
Name: Domain User
The request failed. The underlying connection was closed: An unexpected error occurred on a receive.
    + CategoryInfo          : NotSpecified: (:) [], DataSourceOperationException
    + FullyQualifiedErrorId : [Server=SERVERNAME,RequestId=fda72f95-c890-40d6-8840-de18d3d4e826,TimeStamp=12/19/2017
   5:27:53 PM] [FailureCategory=Cmdlet-DataSourceOperationException] 6C09AFD7
    + PSComputerName        :

[PS] C:\Windows\system32>get-mailboxsearch
The request failed. The underlying connection was closed: An unexpected error occurred on a receive.
    + CategoryInfo          : NotSpecified: (:) [Get-MailboxSearch], DataSourceOperationException
    + FullyQualifiedErrorId : [Server=SERVERNAME,,RequestId=fda72f95-c890-40d6-8840-de18d3d4e826,TimeStamp=12/19/2017
   6:01:18 PM] [FailureCategory=Cmdlet-DataSourceOperationException] 25D67BC1,Microsoft.Exchange.Management.Tasks.Get
    + PSComputerName        :

[PS] C:\Windows\system32>$error[0] | fl -force

writeErrorStream      : True
OriginInfo            :
Exception             : System.Management.Automation.RemoteException: The request failed. The underlying connection
                        was closed: An unexpected error occurred on a receive.
TargetObject          :
CategoryInfo          : NotSpecified: (:) [Get-MailboxSearch], DataSourceOperationException
FullyQualifiedErrorId : [Server=SERVERNAME,,RequestId=5d522559-98e6-4836-9e6e-755633fdb089,TimeStamp=12/19/2017
                        6:04:26 PM] [FailureCategory=Cmdlet-DataSourceOperationException]
ErrorDetails          :
InvocationInfo        :
ScriptStackTrace      : at <ScriptBlock><Process>, <No file>: line 41
PipelineIterationInfo : {}
PSMessageDetails      :
Who is Participating?

[Product update] Infrastructure Analysis Tool is now available with Business Accounts.Learn More

I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Sunil ChauhanLead AdministratorCommented:
Is this error specific to this CMD only ?? are you able to run any other CMD on the shell?

have you tried to connect to any other shell host (CAS sever)??
JacksonTechnicalAuthor Commented:
This is only on this specific command.  All other commands work fine.  Its an on premises Exchange 2016 server with 300 mailboxes running CU6.
Todd NelsonSystems EngineerCommented:
Do you know if the account you are running "New-MailboxSearch" with has been assigned to the "Discovery Management" role group?

Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

JacksonTechnicalAuthor Commented:
Yes, the user is a member of the following Exchange Management Groups.  Compliance Management, Discovery Management, Organization Management, Records Management.  The user is also a domain admin account, shema admin, and enterprise admin.
Sunil ChauhanLead AdministratorCommented:
can try if its works when you run it for the specific mailbox, its seems you are just running it without providing any parameter.

New-MailboxSearch -Name "Hold-tailspintoys" -SourceMailboxes DG-Research -SearchQuery "'Patent' AND 'Project tailspintoys'"
JacksonTechnicalAuthor Commented:
Same result trying to specify a user.  I get the same issue when trying to use the ECP with a pop up having the same error.  When evoking New-Mailboxsearch, what exactly does it go and talk to.  That seems like what is not working.  Is it using TLS to connect to something possibly.  Just trying to determine what is going on with this command.
Sunil ChauhanLead AdministratorCommented:
try recycling ecp application pool.

did you check if you found anything on the event logs regarding this ??
JacksonTechnicalAuthor Commented:
Found the issue.  TLS 1.0 had been disabled via the registry.  We re-enabled TLS 1.0 and restarted the Exchange server.  Once done, the PowerShell commands will now run.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Seth SimmonsSr. Systems AdministratorCommented:
No comment has been added to this question in more than 21 days, so it is now classified as abandoned.

I have recommended this question be closed as follows:

-- JacksonTechnical (https:#a42414683)
-- JacksonTechnical (https:#a42410943)

If you feel this question should be closed differently, post an objection and the moderators will review all objections and close it as they feel fit. If no one objects, this question will be closed automatically the way described above.

Experts-Exchange Cleanup Volunteer
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.