Home
%3CLINGO-SUB%20id%3D%22lingo-sub-333327%22%20slang%3D%22en-US%22%3ESharePoint%202016%20Hybrid%20Picker%20Failure%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-333327%22%20slang%3D%22en-US%22%3E%0A%20%26lt%3Bmeta%20http-equiv%3D%22Content-Type%22%20content%3D%22text%2Fhtml%3B%20charset%3DUTF-8%22%20%2F%26gt%3B%3CSTRONG%3EFirst%20published%20on%20MSDN%20on%20Jan%2003%2C%202018%20%3C%2FSTRONG%3E%20%3CBR%20%2F%3E%20I%20was%20helping%20a%20customer%20set%20up%20hybrid%20search%2C%20when%20we%20ran%20into%20a%20frustrating%20issue.%20We'd%20run%20the%20hybrid%20picker%2C%20choose%20hybrid%20search%20only%2C%20enter%20the%20parameters%2C%20and%20say%20create.%20The%20picker%20would%20kick%20off%2C%20and%20then%20fail%20quickly%2C%20with%20the%20message%20%22Parameters%20too%20long%20or%20contain%20forbidden%20character.%22%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%202018.01.03%2015%3A15%3A31.977%20*ERROR*%20%5BWorkflow%3DHybrid%2C%20Task%3DHybridSearchConfiguration%2C%20Phase%3DConfigure%5D%20System.Exception%3A%20Parameters%20too%20long%20or%20contain%20forbidden%20character.%20%3CBR%20%2F%3E%20at%20Microsoft.Online.CSE.HybridSP.StandardWorkflow.HybridSearchTask.ConfigureHybridSearch()%20%3CBR%20%2F%3E%20at%20Microsoft.Online.CSE.HybridSP.StandardWorkflow.HybridSearchTask.Configure()%20%3CBR%20%2F%3E%20%3CBR%20%2F%3E%20It%20turns%20out%20that%20our%20issue%20was%20that%20the%20%3CA%20href%3D%22http%3A%2F%2Fwww.microsoft.com%2Fen-us%2Fdownload%2Fdetails.aspx%3Fid%3D39267%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Online%20Services%20Sign-In%20Assistant%20%3C%2FA%3E%20and%20%3CA%20href%3D%22http%3A%2F%2Fgo.microsoft.com%2Ffwlink%2Fp%2F%3Flinkid%3D236297%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%20noopener%20noreferrer%22%3E%20Azure%20Active%20Directory%20PowerShell%20%3C%2FA%3E%20modules%20were%20not%20installed%20on%20the%20TARGET%20servers%2C%20where%20hybrid%20search%20was%20to%20be%20deployed.%20There's%20a%20checkbox%20in%20the%20wizard%20that%20says%20they're%20installed%2C%20but%20it's%20not%20specific%20as%20to%20which%20boxes.%20Be%20careful!%3C%2FLINGO-BODY%3E%3CLINGO-TEASER%20id%3D%22lingo-teaser-333327%22%20slang%3D%22en-US%22%3EFirst%20published%20on%20MSDN%20on%20Jan%2003%2C%202018%20I%20was%20helping%20a%20customer%20set%20up%20hybrid%20search%2C%20when%20we%20ran%20into%20a%20frustrating%20issue.%3C%2FLINGO-TEASER%3E%3CLINGO-LABS%20id%3D%22lingo-labs-333327%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3Esharepoint%202013%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3ESharePoint%202016%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3Esharepoint%20hybrid%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E
Microsoft
First published on MSDN on Jan 03, 2018
I was helping a customer set up hybrid search, when we ran into a frustrating issue. We'd run the hybrid picker, choose hybrid search only, enter the parameters, and say create. The picker would kick off, and then fail quickly, with the message "Parameters too long or contain forbidden character."

2018.01.03 15:15:31.977 *ERROR* [Workflow=Hybrid, Task=HybridSearchConfiguration, Phase=Configure] System.Exception: Parameters too long or contain forbidden character.
at Microsoft.Online.CSE.HybridSP.StandardWorkflow.HybridSearchTask.ConfigureHybridSearch()
at Microsoft.Online.CSE.HybridSP.StandardWorkflow.HybridSearchTask.Configure()

It turns out that our issue was that the Online Services Sign-In Assistant and Azure Active Directory PowerShell modules were not installed on the TARGET servers, where hybrid search was to be deployed. There's a checkbox in the wizard that says they're installed, but it's not specific as to which boxes. Be careful!