HCW Error when configuring the mail flow

%3CLINGO-SUB%20id%3D%22lingo-sub-70585%22%20slang%3D%22en-US%22%3EHCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70585%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3Eim%20trying%20to%20run%20the%20HCW%20and%20i%20have%20the%20below%20error%20when%20it%20reach%20the%20mail%20flow%20configuration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHCW0000%20PowerShell%20failed%20to%20invoke%20'New-InboundConnector'%3A%20Parameter%20count%20mismatch.%20An%20unexpected%20error%20has%20occurred%20and%20a%20Watson%20dump%20is%20being%20generated%3A%20Parameter%20count%20mismatch%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-LABS%20id%3D%22lingo-labs-70585%22%20slang%3D%22en-US%22%3E%3CLINGO-LABEL%3EExchange%3C%2FLINGO-LABEL%3E%3CLINGO-LABEL%3EOffice%20365%3C%2FLINGO-LABEL%3E%3C%2FLINGO-LABS%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72858%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72858%22%20slang%3D%22en-US%22%3E%3CP%3EMay%20I%20inquire%20the%20thread%20here%20to%20clarify%20something.%26nbsp%3B%20Were%20existing%20hybrid%20connectors%20mailflow%26nbsp%3Baffected%20by%20this%20or%20just%20the%20creation%20of%20new%20ones%2Fhybrid%20wizard%20completion%3F%26nbsp%3B%20In%20other%20words%2C%20was%20any%20mail%20destined%20for%20on-prem%20from%20O365%20or%20vice%20versa%20down%3F%26nbsp%3B%20I%20didn't%20get%20that%20existing%20connectors%20stopped%20working.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72846%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72846%22%20slang%3D%22en-US%22%3E%3CP%3Eyay%2C%20our%20tenant%20is%20also%20fixed%20now.%20Create%20manual%20connector%20and%20HCW%20works%20again.%20But%20still%203%20days%20without%20hybrid%20mail%20delivery%2C%20bad%20thing.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72612%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72612%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20also%20finally%20able%20to%20create%20the%20connector%20and%20verified%20that%20it%20is%20usable.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72515%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72515%22%20slang%3D%22en-US%22%3E%3CP%3EWorked%20for%20me%20as%20of%208am%20CST%20this%20morning.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72514%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72514%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can%20now%20successfully%20run%20%3CSPAN%3EGet-%3CU%3EHybridMailflowDatacenterIPs%3C%2FU%3E%20.%20Not%20sure%20if%20the%20rest%20of%20the%20wizard%20will%20work%20but%20I%20will%20give%20it%20a%20shot.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72168%22%20slang%3D%22en-US%22%3ERe%3A%20Solution%20for%20some%20possibly%20(Re%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72168%22%20slang%3D%22en-US%22%3E%3CP%3EHi%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20been%20told%20the%20folllowing%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26gt%3B%26gt%3B%26gt%3B%26gt%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EI%20have%20confirmed%20with%20our%20Team%20and%20it%20appears%20that%20they%20are%20still%20working%20for%20the%20services%20to%20be%20back%20up%20with%20regards%20to%20the%20mail%20connector.%20They%20have%20already%20corrected%20the%20issue%20with%20the%20creation%20but%20the%20services%20are%20not%20fully%20working.%20We%20will%20be%20sending%20you%20another%20follow%20up%20once%20we%20have%20the%20update.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3E%26gt%3B%26gt%3B%26gt%3B%26gt%3B%26gt%3B%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ERegards%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EJohn%20Ellwood%20%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72166%22%20slang%3D%22en-US%22%3ERe%3A%20Solution%20for%20some%20possibly%20(Re%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72166%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20also%20still%20not%20able%20to%20create%20the%20connector.%3C%2FP%3E%3CP%3EMy%20tenants%20are%20in%20the%20Europe%20region.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72165%22%20slang%3D%22en-US%22%3ERe%3A%20Solution%20for%20some%20possibly%20(Re%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72165%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20still%20getting%20the%20error.....%20it%20is%20so%20frustrating!!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENothing%20from%20MS%20regarding%20my%20case%2C%20I%20am%20going%20to%20have%20to%20chase.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72161%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72161%22%20slang%3D%22en-US%22%3E%3CP%3EI%20can%20now%20configure%20connectors%20without%20the%20error%20message%20being%20displayed.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHowever%20if%20you%20configure%20more%20than%20one%20connector%20the%20rules%20are%20not%20working%20correctly.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20getting%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3E%3CFONT%20color%3D%22%23000000%22%3E()%3A%20SMTP%20server%20response%3A%20550%205.7.64%20TenantAttribution%3B%20Relay%20Access%20Denied%20%3C%2FFONT%3E%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3Efor%20a%20server%20which%20has%20been%20added%20to%20the%20list.%20Another%20server%20was%20working%20correctly.%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThe%20problem%20seems%20to%20have%20gotten%20more%20complex%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3ERegards%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%3CSPAN%3EJohn%20Ellwood%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72108%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72108%22%20slang%3D%22en-US%22%3E%3CP%3EHi%20Friends%2C%3C%2FP%3E%3CP%3EToday%20%3CSTRONG%3EMay%2022%3C%2FSTRONG%3E%2C%20at%20%3CSTRONG%3E20%20hours%3C%2FSTRONG%3E%20UTC%20Mexico%20City%2C%20I%20had%20the%20same%20error%20in%20HCW%20over%20Exchange%20Server%202013%20CU16%2C%20its%20today%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ENow%2C%20i%20checked%20two%20thisng%3A%3C%2FP%3E%3CP%3E1.%20Create%20a%20inbound%20connector%20in%20ECP%20of%20Exchange%20Online%2C%20a%20simple%20configuration%20result%20in%20the%20same%20error%20that%20view%20in%20the%20HCW%20in%20my%20Exchange%20On-premise.%3C%2FP%3E%3CP%3E2.%20Create%20is%20OK%20when%20add%20inbound%20connector%20through%20of%20power%20shell%2C%20so...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhat%20do%20you%20do%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECreate%20a%20new%20admin%20globar%20user%20and%20enter%20in%20the%20HCW%2C%20...%20%C2%A1the%20configuration%20is%20complete!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EVery%20very%20unusual%20solution%2C%20but%20worked%20for%20my%2C%20as%20indicated%20by%20other%20post.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards!%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EJM%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72042%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72042%22%20slang%3D%22en-US%22%3EI%20raised%20a%20SR%20and%20got%20told%20that%20this%20is%20part%20of%20a%20wider%20outage%20and%20no%20troubleshooting%20can%20be%20carried%20out%20because%20of%20it.%20I%20can%20see%20that%20the%20incident%20is%20now%20in%20a%20'restoring%20service'%20phase%20but%20it%20still%20doesn't%20work%20for%20us.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72039%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72039%22%20slang%3D%22en-US%22%3E%3CP%3EOpened%20an%20SR%20through%20the%20tenant%20at%2010am.%20%26nbsp%3Bat%202pm%20I%20have%20ony%20recieved%20a%20single%20email%2C%20and%20the%20tech%20won't%20answer%20subsequent%20emails......%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'm%20sure%20this%20issue%20is%20costing%20a%20lot%20of%20money%20for%20clients%20and%20implementation%20providers.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-72034%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-72034%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20still%20do%20not%20have%20a%20fix%2080%20hours%20after%20reporting%20the%20problem!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71946%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71946%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20still%20in%20the%203%25.%20Can't%20run%20the%20Get-HybridMailflowDatacenterIPs%20command.%20Still%20receive%20the%20Parameter%20count%20mismatch.error.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71925%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71925%22%20slang%3D%22en-US%22%3E%3CP%3EI%20stumbled%20upon%20this%20thread%20today%20and%20I'm%20getting%20the%20same%20error.%20Quite%20annoying!%20What%20is%20the%20ETA%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71859%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71859%22%20slang%3D%22en-US%22%3EI%20have%20the%20same%20issues%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71832%22%20slang%3D%22en-US%22%3ERe%3A%20Solution%20for%20some%20possibly%20(Re%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71832%22%20slang%3D%22en-US%22%3ESame%20here%20-%20was%20finally%20able%20to%20finish%20the%20HCW.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71821%22%20slang%3D%22en-US%22%3ERe%3A%20Solution%20for%20some%20possibly%20(Re%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71821%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20issue%20is%20fixed%20i%20don't%20know%20what%20happened%20i%20belive%20Microsoft%20is%20working%20to%20fix%20the%20issue%20but%20it's%20gradually%20%26nbsp%3Bnot%20a%20fix%20for%20all%20tenants%2C%20i%20just%20kept%20terying%20until%20the%20HCW%20work.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71818%22%20slang%3D%22en-US%22%3ERe%3A%20Solution%20for%20some%20possibly%20(Re%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71818%22%20slang%3D%22en-US%22%3E%3CP%3EMy%20Customer%20is%20suffering%20from%20the%20same%20problem.%20Looks%20like%20we%20are%20in%20the%203%25%20left.%20Need%20to%20change%20the%20connector%20after%20a%20datacenter%20migration.%20Production%20Mails%20are%20effected.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71742%22%20slang%3D%22en-US%22%3ERe%3A%20Solution%20for%20some%20possibly%20(Re%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71742%22%20slang%3D%22en-US%22%3E%3CP%3EI%20had%20a%20chat%20with%20support%20and%20completed%20some%20remote%20sessions%20and%20recieved%20this%20email...%20using%20the%20steps%20provided%20with%20a%20new%20Global%20Admin%20did%20not%20work%2C%20Same%20Error...%20I%20awate%20a%20fix...%20tomorrow...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3E'As%20discussed%2C%20it%20seems%20that%20you%20are%20also%20part%20of%20the%20affected%20tenants%20for%20Service%20Degradation%20EX102057.%20Title%3A%20Mail%20connector%20issue%20User%20Impact%3A%20Administrators%20may%20be%20unable%20to%20create%20or%20modify%20mail%20connectors.%20More%20info%3A%20This%20is%20an%20incremental%20update%20to%20provide%20the%20latest%20status%20on%20the%20issue.%20Current%20status%3A%20The%20deployment%20of%20the%20fix%20is%2097%20percent%20complete.%20We%E2%80%99ll%20provide%20an%20update%20on%20Monday%20confirming%20full%20service%20restoration.%3C%2FEM%3E%3CBR%20%2F%3E%3CBR%20%2F%3E%3CEM%3EIn%20addition%2C%20try%20to%20add%201%20more%20global%20admin%20that%20will%20perform%20adding%20the%20mail%20connector%20in%20Exchange%20Admin%20Center%20and%20try%20again.'%3C%2FEM%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71720%22%20slang%3D%22en-US%22%3ESolution%20for%20some%20possibly%20(Re%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow)%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71720%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20finishing%20the%20migration%20of%26nbsp%3Babout%20460%20users%20to%20Office%20365%20this%20weekend%2C%20and%20they%20have%20a%20Barracuda%20archiver%2C%20so%20when%20I%20went%20to%20create%20a%20connector%20to%20the%20archiver%2C%20I%20also%20got%20that%20%22parameter%20count%20mismatch%22%20error%20when%20trying%20to%20finish%20it.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20was%20using%20an%20IP%20address%20for%20the%20%22%3CSPAN%3EHow%20do%20you%20want%20to%20route%20email%20messages%3F%3C%2FSPAN%3E%26nbsp%3B(smarthost)%22%20screen.%20On%20a%20whim%2C%20I%20decided%20to%20throw%20a%20random%20FQDN%20in%20there%20instead%20to%20test%2C%20and%20it%20saved%20fine.%20This%20customer%20already%20had%20a%20DNS%20entry%20so%20I%20updated%20it%20with%20the%20correct%20one%2Cbut%20if%20you%20don't%2C%20I%20suggest%20that%20you%20just%20create%20a%20DNS%20entry%2C%20and%20use%20that%20FQDN.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EYour%20problem%20may%20be%20different%2C%20but%20this%20may%20help%20someone.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71685%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71685%22%20slang%3D%22en-US%22%3E%3CP%3EI%20worked%20with%20support%20to%20skip%20the%20MailGUID%20value..%20(I%20really%20don't%20want%20to%20do%20a%20Hybrid%20Rollout%2C%20but%20rather%20a%20cutover%20process).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThe%20problem%20with%20AD%20Connect%20is%2C%20if%20it%20sees%20exchange%20in%20the%20domain%2C%20it%20forces%20a%20hybrid%20rollout..%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71679%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71679%22%20slang%3D%22en-US%22%3E%3CP%3ELooks%20like%20we%20have%20a%20winner%2C%20I%20was%20able%20to%20create%20a%20connector...%3C%2FP%3E%3CP%3EI%20hope%20everyones%20issue%20with%20this%20is%20fixed...%3C%2FP%3E%3CP%3Eregs.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71678%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71678%22%20slang%3D%22en-US%22%3E%3CP%3Esame%20error%20in%20dthe%20hybride%20wizard%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EHCW0%20-%20%26nbsp%3BPowerShell%20failed%20to%20invoke%20'Get-HybridMailflowDatacenterIPs'%3A%20Parameter%20count%20mismatch.%20An%20unexpected%20error%20has%20occurred%20and%20a%20Watson%20dump%20is%20being%20generated%3A%20Parameter%20count%20mismatch.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71659%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71659%22%20slang%3D%22en-US%22%3EStandard%20line%20from%20Microsoft%20is%20%2224%20to%2048%20hours%22.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71658%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71658%22%20slang%3D%22en-US%22%3E%3CP%3ESupport%20told%20me%20that%20the%20ETA%20is%20Monday%2C%20so%20im%20keeping%20my%20fingers%20crossed%20and%20hope%20for%20the%20best...%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71653%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71653%22%20slang%3D%22en-US%22%3E%3CP%3EAny%20ETA%20on%20this%3F..%20I'm%20doing%20a%20migration%20this%20weekend%20and%20it%20looks%20like%20the%20same%20problem.%20%26nbsp%3B%3C%2FP%3E%3CP%3E%22HCW0000%20PowerShell%20failed%20to%20invoke%20'Get-HybridMailflowDatacenterIPs'%3A%20Parameter%20count%20mismatch.%20An%20unexpected%20error%20has%20occurred%20and%20a%20Watson%20dump%20is%20being%20generated%3A%20Parameter%20count%20mismatch.%22%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71638%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71638%22%20slang%3D%22en-US%22%3ENo%20I%20think%20they%20are%20rolling%20out%20fix%20to%20everyone.%20Not%20sure%20if%20a%20ticket%20will%20get%20a%20customer%20tenant%20priority%20or%20not.%20I%20doubt%20it%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71635%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71635%22%20slang%3D%22en-US%22%3E%3CP%3EWe're%20having%20this%20issue%20too%20(in%20Office%20365%2C%20trying%20to%20create%20an%20inbound%20connector).%20Do%20you%20know%20if%20the%20fix%20they're%20working%20on%20will%20automatically%20address%20our%20issue%20once%20it's%20fully%20rolled%20out%2C%20or%20do%20I%20need%20to%20explicitly%20call%20into%20support%20so%20they%20can%20patch%26nbsp%3Bour%20specific%20instance%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71608%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71608%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20confirmed%20with%20Microsoft%20this%20is%20an%20issue%20with%20a%20specific%20datacenter%20and%20that%20they%20are%20working%20actively%20on%20an%20internal%20case%20to%20resolve.%20Next%20update%20will%20be%209%20PM%20UTC%205-20-2017.%20%26nbsp%3BThey%20are%20specifically%20attaching%20customers%20tenants%20that%20call%20in%20to%20their%20case%20so%20they%20can%20go%20and%20rollout%20the%20patch.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71607%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71607%22%20slang%3D%22en-US%22%3E%3CP%3EConnectors%20created%20now%20by%20HCW%20and%20could%20be%20done%20manually%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71599%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71599%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20experiencing%20the%20same%20issue.%20You%20can%20connect%20through%20Azure%20AD%20shell%20and%20run%20the%26nbsp%3B%3CSPAN%3EGet-%3CU%3EHybridMailflowDatacenterIPs%3C%2FU%3E%20command%20and%20you%20receive%20the%20same%20%3CU%3E%22Parameter%20count%20mismatch%3C%2FU%3E.%22%20error.%20We%20have%20ticket%20open%20and%20are%20going%20to%20confirm%20with%20Microsoft.%20We've%20succesfully%20tried%20from%20two%20seperate%20tenants%20and%20get%20the%20error.%3C%2FSPAN%3E%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71543%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71543%22%20slang%3D%22en-US%22%3ESame%20issue%20here.%20Support%20did%20not%20seem%20aware%20of%20any%20issues.%20Received%20the%20'wait%202%20hours%20and%20try%20it%20again'%20response.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71498%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71498%22%20slang%3D%22en-US%22%3EJust%20got%20a%20call%20myself%20too%20same%20ETA%20-%20hopefully%20today%20or%20Monday.%20Cross%20fingers!%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71425%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71425%22%20slang%3D%22en-US%22%3E%3CP%3ETHere%20is%20an%20issue%20from%20office%20365.%20Incident%20EX102057%20today%208PM%20UTC%20will%20be%20next%20update.%3C%2FP%3E%3CP%3E%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FHow-to-check-Office-365-service-health-932AD3AD-533C-418A-B938-6E44E8BC33B0%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%26amp%3BfromAR%3D1%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FHow-to-check-Office-365-service-health-932AD3AD-533C-418A-B938-6E44E8BC33B0%3Fui%3Den-US%26amp%3Brs%3Den-US%26amp%3Bad%3DUS%26amp%3BfromAR%3D1%3C%2FA%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71423%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71423%22%20slang%3D%22en-US%22%3E%3CP%3EGreat%20%3A%5C%3C%2Fimg%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStrange%20thing%20is%20my%20recieve%20is%20working%20fine%20so%20mail%20is%20now%20following%20in%20(Which%20it%20wasnt)%20but%20the%20send%20is%20goosed..%20rather%20royally%20annoying!!%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71420%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71420%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20got%20a%20call%20from%20support%20stating%20they%20are%20working%20on%20the%20issue%20and%20have%20fixed%20it%20for%20about%2050%25%20of%20the%20users%2C%20he%20told%20me%20i%20could%20expect%20a%20fix%20during%20today%20or%20by%20Monday%3C%2FP%3E%3CP%3Eoh%20well%2C%20its%20not%20like%20e-mail%20is%20relevant%20for%20a%20business%20%2FSet-SarcasmMode%20off%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71417%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71417%22%20slang%3D%22en-US%22%3EI%20am%20experiencing%20the%20same%20problem%20when%20trying%20to%20create%20the%20inbound%20connector%20using%20OnPremises%20option.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71416%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71416%22%20slang%3D%22en-US%22%3ELooking%20at%20the%20incident%20Ryan%20posted%2C%20it%20sounds%20like%20it's%20a%20backend%20issue%2C%20so%20there%20should%20be%20nothing%20for%20us%20to%20update.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71415%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71415%22%20slang%3D%22en-US%22%3E%3CP%3EThis%20seems%20to%20be%20quite%20and%20issue...%20and%20isnt%20half%20dragging%20on.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20have%20lost%20the%20ability%20to%20set%20up%20a%20conector%20to%20inpremis.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20setting%20it%20up%20im%20getting%20%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EError%20-%20Parameter%20Count%20Mismatch%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDo%20we%20know%20how%20to%20update%20is%20being%20deployed%2C%20is%20it%20going%20to%20O365%20or%20through%20Updates%3F%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71414%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71414%22%20slang%3D%22en-US%22%3EGood%20to%20know%20it's%20at%20least%20showing%20up%20on%20someone's%20dashboard!%20Went%20to%20go%20look%20at%20mine%20and%20nothing%20about%20this.%20It's%20read-only%20Friday%2C%20so%20I%20won't%20be%20testing%20anything%20out%20today!%20%3AD%3C%2Fimg%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71382%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71382%22%20slang%3D%22en-US%22%3E%3CP%3EI%20opened%20a%20ticket%20last%20night%2C%20and%20received%20this%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CEM%3ETitle%3A%20Mail%20connector%20issue%3CBR%20%2F%3E%3CBR%20%2F%3EUser%20Impact%3A%20Administrators%20may%20be%20unable%20to%20create%20or%20modify%20mail%20connectors.%3CBR%20%2F%3E%3CBR%20%2F%3ECurrent%20status%3A%20We've%20initiated%20the%20deployment%20of%20the%20fix%20and%20we'll%20continue%20to%20monitor%20service%20health%20throughout%20the%20deployment%20process.%3CBR%20%2F%3E%3CBR%20%2F%3EScope%20of%20impact%3A%20Your%20organization%20is%20affected%20by%20this%20event.%3CBR%20%2F%3E%3CBR%20%2F%3EStart%20time%3A%20Monday%2C%20May%2015%2C%202017%2C%20at%208%3A02%20PM%20UTC%3CBR%20%2F%3E%3CBR%20%2F%3EPreliminary%20root%20cause%3A%20A%20recent%20update%20to%20the%20environment%2C%20intended%20to%20resolve%20a%20previously%20existing%20code%20defect%2C%20caused%20the%20mail%20connector%20service%20to%20become%20degraded.%3CBR%20%2F%3E%3CBR%20%2F%3ENext%20update%20by%3A%20Friday%2C%20May%2019%2C%202017%2C%20at%2012%3A00%20AM%20UTC%3C%2FEM%3E%3C%2FP%3E%3CP%3E%3CSTRONG%3E%3CEM%3ELast%20Updated%3A%3C%2FEM%3E%3C%2FSTRONG%3E%3CEM%3E%20May%2018%202017%204%3A53PM%20UTC%3C%2FEM%3E%26nbsp%3B%26nbsp%3B%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71371%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71371%22%20slang%3D%22en-US%22%3E%3CP%3E3rd%20day%20is%20gone.%20yes%20thats%20shocking.%20you%20are%20right!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71368%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71368%22%20slang%3D%22en-US%22%3EExactly%20the%20same%20issue%20here....%20I%20have%20spoken%20to%20MS%20support%20and%20all%20they%20said%20is%20they%20are%20aware%20and%20working%20on%20a%20fix%2C%20there%20is%20no%20time%20frame%20as%20yet!%3CBR%20%2F%3E%3CBR%20%2F%3EThis%20shocking!%3CBR%20%2F%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71363%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71363%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20had%20a%20chance%20to%20do%20this%2C%20no%20luck.%20%26nbsp%3BI%20received%20a%20different%20error%20this%20time%2C%20but%20it%20was%20on%20the%20same%20set-inboundconnctor%20command.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWinRM%20cannot%20complete%20the%20operation.%20%26nbsp%3BVerify%20that%20the%20specified%20computer%20name%20is%20valid%2C%20that%20the%20computer%20is%20accessible%20over%20the%20network%2C%20and%20that%20a%20firewall%20exception%20for%20the%20WinRM%20service%20is%20enabled%20and%20allows%20access%20from%20this%20computer.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EStill%20waiting%20for%20my%20call%20back%20from%20MS%20after%20getting%20it%20transferred%20to%20another%20group.%20%26nbsp%3B%20%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71328%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71328%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20error%20here%3C%2FP%3E%3CP%3EAccounting%20software%20sends%20out%20invoices%20and%20needs%20a%20connector%20to%20use%20office%20365%20or%20office%20365%20refuses%20inbound%20email%20from%20the%20software.%3C%2FP%3E%3CP%3ECompany%20switched%20ISP%20and%20has%20a%20new%20IP%20address%2C%20editing%20the%20existing%20connector%20resulted%20in%20Parameter%20Count%20Mismatch%20event%2C%20removing%20the%20connector%20and%20recreating%20it%20with%20the%20new%20IP%20has%20the%20same%20result.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71283%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71283%22%20slang%3D%22en-US%22%3E%3CP%3EHi.%3C%2FP%3E%3CP%3ESame%20Error%20after%26nbsp%3Bnew%20User%20and%20select%20Full%20Hybridconfiguration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71267%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71267%22%20slang%3D%22en-US%22%3EHi%20Ron%2C%20I%20created%20an%20office%20365%20only%20account%20with%20a%20UPN%20of%20tenant.onmicrosoft.com%20as%20the%20username.%20add%20user%20role%20as%20org%20admin.%20In%20the%20HCW%20wizard%20use%20the%20new%20account%20to%20signing%20to%20office365.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71166%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71166%22%20slang%3D%22en-US%22%3EI'm%20not%20sure%20what%20you%20mean%2C%20I%20didn't%20imply%20anything%20worked.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71152%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71152%22%20slang%3D%22en-US%22%3E%3CP%3EVimal%20-%20can%20clarify%20more%20please.%20When%20you%20say%20%22I%20created%20a%20new%20org%20admin%20account%2C%20did%20not%20assign%20any%20permissions%22%20do%20you%20mean%20you%20created%20a%26nbsp%3Bnew%20account%20in%20your%20local%20AD%20and%20then%20added%20it%20to%20the%20Exchange%20Org%20admin%20Security%20group%20within%20AD%20then%20run%20the%20HCW%3F%20If%20so%2C%20what%20do%20you%20mean%20that%20you%20did%20not%20assign%20any%20permissions%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EPlease%20kindly%20elaborate-%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI%20am%20willing%20to%20try%20this%20method%20at%20this%20point%20with%20a%20little%20more%20background%20on%20the%20requirements.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E-Ron%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71150%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71150%22%20slang%3D%22en-US%22%3E%3CP%3EMr.%20Schoenfld%2C%20unfortantely%20that%20does%20not%20work%20either.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71149%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71149%22%20slang%3D%22en-US%22%3E%3CP%3EJust%20got%20off%20the%20phone%20with%20Microsoft%20Support.%20%26nbsp%3BThey%20informed%20me%20that%20they%20are%20aware%20of%20the%20problem%20and%20stated%20that%20a%20%22small%20amount%22%20of%20customers%20have%20reported%20this%20problem%20and%20do%20not%20have%20an%20ETA%20for%20the%20resolution.%20%26nbsp%3B%3CBR%20%2F%3E%3CBR%20%2F%3EAdding%20to%20this%2C%20today%20I%20was%20attempting%20to%20setup%20SMTP%20relay%20with%20on-premises%20organization%20to%20Office%20365.%20and%20experienced%20the%20exact%20same%20error%20seen%20with%20the%20HCW%20when%20setting%20up%20the%20connector%20within%20Office%20365.%20%26nbsp%3BOnly%20this%20time%20I%20was%20simply%20setting%20up%20a%20SMTP%20relay%20connector.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%26nbsp%3BAs%20we%20all%20know%2C%20the%20process%20of%20setting%20up%20SMTP%20relay%20with%20Office%20365%20tenant%20is%20a%20VERY%20easy%20process%2C%20and%20to%20make%20things%20even%20easier%2C%20this%20article%20walks%20you%20through%20the%20steps%20to%20a%20tee%20(How%20to%20set%20up%20a%20multifunction%20device%20or%20application%20to%20send%20email%20using%20Office%20365%20-%20%3CA%20href%3D%22https%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FHow-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4%22%20target%3D%22_blank%22%20rel%3D%22noopener%20noreferrer%22%3Ehttps%3A%2F%2Fsupport.office.com%2Fen-us%2Farticle%2FHow-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4%3C%2FA%3E).%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ESo%20the%20problem%20is%20not%20only%20affecting%20Hybrid%20Deployments%2FEnvironments.%20%26nbsp%3BIt%20is%20affecting%20tenants%20who%20attempt%20to%20setup%2Fconfigure%20connectors%20in%20the%20EAC.%20%26nbsp%3BMy%20tenante%20today%20is%20currently%20NOT%20in%20a%20hybrid%20configuration.%20%26nbsp%3BSimply%2C%20the%20problem%20is%20within%20the%20Office%20365%20EAC%20%26gt%3B%20Mail%20Flow%20%26gt%3B%20Connectors.%20%26nbsp%3BWhether%20you%20are%20performing%20a%20new-inboundconnector%20command%20VIA%20the%20HCW%2C%20or%20simply%20trying%20to%20setup%20a%20SMTP%20relay%20connector%2C%20you%20will%20receive%20the%20following%20%22generic%22%20error%3A%3C%2FP%3E%3CP%3E%3CBR%20%2F%3Eerror%3CBR%20%2F%3EParameter%20count%20mismatch.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71120%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71120%22%20slang%3D%22en-US%22%3EDoesn't%20work.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71105%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71105%22%20slang%3D%22en-US%22%3ECreate%20office%20365%20organization%20admin%20and%20then%20use%20that%20new%20account%20for%20HWC%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71097%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71097%22%20slang%3D%22en-US%22%3E%3CP%3ECreating%20new%20Admin%20Account%20in%20Office%20365%20and%20re-run%20Hybrid%20config%20wizard%20worked.%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71058%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71058%22%20slang%3D%22en-US%22%3E%3CP%3EI%20was%20finally%20able%20to%20re-run%20the%20HCW%20sucessfuly.%26nbsp%3B%20HOWEVER%20-%20since%20we%20were%20an%20existing%20install%2C%20here's%20my%20tale%20of%20woe%3A%26nbsp%3Bthe%20wizard%26nbsp%3Brebuilds%20the%20connectors%20which%20rebuilt%20the%20queues.%26nbsp%3BNormally%20this%20probably%20is%20no%20big%20deal%20for%20a%20new%20install%20or%20when%20the%20wizard%26nbsp%3Bruns%20to%20completion%20in%26nbsp%3Ba%20few%20seconds.%26nbsp%3B%26nbsp%3BUnfortunaltly%2C%20since%20we%20had%20been%20down%20for%20almost%20a%20day%2C%20this%20had%20the%20lovely%20effect%20of%20wiping%20out%20all%20the%20email%20that%20had%20been%20pending%20for%20my%20enterprise%20for%20the%20last%2024%20hours.%26nbsp%3B%20Microsoft's%20helpful%20response%26nbsp%3B-%20%22oops%22.%26nbsp%3B%20And%20of%20course%20their%20official%20position%20is%20that%20%22you%20can't%20lose%20mail%20with%20our%20system%20so%20we%20don't%20do%20backups%22.%26nbsp%3B%20We%20are%20exploring%20what%20we%20can%20do.%26nbsp%3B%20If%20you%20are%20a%20production%20environment%20-%20be%20warned.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71056%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71056%22%20slang%3D%22en-US%22%3ERemoving%20the%20connector%20and%20readding%20it%20will%20not%20work.%20I%20have%20been%20trying%20to%20setup%20a%20connector%20net%20new%2C%20with%20no%20existing%20configuration%20in%20place.%20I%20have%20even%20tried%20manually%20rebuilding%20the%20connector%20to%20no%20avail.%20Ultimately%2C%20it%20appears%20this%20is%20server%20error.%20My%20assumption%20is%20that%20the%20scope%20is%20fairly%20small%2C%20considering%20there%20is%20not%20more%20outcry%20currently.%20As%20far%20as%20confidence%20goes%2C%20I%20have%20done%2050-60%20migrations%20now%20and%20would%20still%20recommend%20Office%20365%20again%20and%20again.%20Things%20happen%20and%20when%20you%20are%20maintaining%20such%20a%20large%20infrastructure%2C%20and%20an%20issue%20impacts%20a%20small%20subset%20of%20users%20in%20an%20unpredictable%20way%2C%20it%20can%20be%20hard%20to%20catch.%20I've%20certainly%20seen%20uptimes%20incomparable%20to%20Exchange%20OnPrem.%20We%20just%20need%20to%20bring%20attention%20to%20the%20issue%20and%20it%20will%20get%20resolved.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71048%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71048%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20plan%20on%20removing%20the%20connector%20via%20PS%20instead%20of%20the%20ECP%20late%20on%20a%20Friday%20night.%20Let%20it%20%22marinate%22%20thru%20the%20night%20to%20allow%20for%20that%20connector%20to%20%22purge%22%20from%20theTenant.%20Then%20re-run%20the%20HCW%20on%20Saturday%20morning%20with%20fingers%20crossed%20that%20it%20had%20enough%20time%20to%20delete.%20%26nbsp%3BI%20asked%20and%20was%20told%20if%20it%20still%20errors%20at%20that%20time%2C%20that%20it%20is%26nbsp%3Bok%20to%20continue%20to%20try%20to%20run%20the%20HCW%20until%20success%20every%20couple%20of%20hours.%20In%20other%20words%2C%20not%20harm%20or%20ill%20effect%20to%20continue%20to%20try%20setup%20the%20HCW.%20Not%20exaclty%20the%26nbsp%3Bbest%20way%20or%20definitely%20a%20flaw%20on%20this%20whole%20process%20IMO%20as%20obviously%20others%20are%20experiencing%20the%20same%20issues%20even%20with%20different%20type%20of%20HCW%20deployments.%20Very%20frustrating%20to%20say%20the%20least%20and%20of%20course%20does%20not%20instill%20confidence%20with%20our%20leadership%20with%20the%20problems%20we%20have%20experienced%20just%20trying%20to%20lay%20the%20tracks%20in%20preparation%20for%20a%20migration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20will%20push%20back%20our%20migration%20at%20least%20another%20week%20now.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EI'll%20update%20with%20our%20progress.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71041%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71041%22%20slang%3D%22en-US%22%3EI'm%20certain%20it%20is%20something%20on%20their%20end.%20The%20error%20is%3A%3CBR%20%2F%3E%3CBR%20%2F%3EA%20variable%20that%20cannot%20be%20referenced%20in%20restricted%20language%20mode%20or%20a%20Data%20section%20is%20being%20referenced.%20Variables%20that%20can%20be%20referenced%20include%20the%20following%3A%20%24PSCulture%2C%20%24PSUICulture%2C%20%24true%2C%20%24false%2C%20and%20%24null%3CBR%20%2F%3E%2B%20CategoryInfo%20%3A%20InvalidOperation%3A%20(%3A)%20%5B%5D%2C%20RuntimeException%3CBR%20%2F%3E%2B%20FullyQualifiedErrorId%20%3A%20VariableReferenceNotSupportedInDataSection%3CBR%20%2F%3E%2B%20PSComputerName%20%3A%20outlook.office365.com%3CBR%20%2F%3E%3CBR%20%2F%3ESince%20it%20is%20a%20remote%20session%2C%20I%20don't%20think%20we%20have%20any%20control%20over%20this.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71029%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71029%22%20slang%3D%22en-US%22%3ENo%20luck%20on%20the%20new%20account%20for%20me.%20When%20you%20say%20org%20account%2C%20you%20mean%20in%20the%20on-premises%20server%2C%20right%3F%20Or%20did%20you%20use%20a%20new%20account%20in%20Exchange%20Online%3F%3CBR%20%2F%3E%3CBR%20%2F%3ETom%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71023%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71023%22%20slang%3D%22en-US%22%3EI%20can%20create%20inbound%20connectors%2C%20just%20not%20set%20type%20to%20OnPremises.%20That's%20what%20throwing%20the%20exception.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71010%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71010%22%20slang%3D%22en-US%22%3E%3CP%3EFor%20Me%20it%20is%20not%20change%20%2C%3C%2FP%3E%3CP%3ESurprizingly%20even%20if%20you%20do%20direct%20connection%20to%20Office%20365%20portal%20via%20ps%20and%20give%20the%20command%20get-hybriddatacenterips%20%2C%20it%20gives%20the%20same%20Dump%20error%2C%3C%2FP%3E%3CP%3EI%20am%20not%20sure%20how%20changing%20admin%20account%20resolve%20this%20issue%20%2C%20unless%20there%20is%20cache%20thing%20being%20cleared%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%2C%3C%2FP%3E%3CP%3EHasan%20Reza%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71006%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71006%22%20slang%3D%22en-US%22%3EJust%20to%20confirm%20creating%20a%20new%20org%20admin%20accounts%20work%20for%202%20of%20my%20clients%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71005%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71005%22%20slang%3D%22en-US%22%3E%3CP%3EI%20am%20also%20having%20the%20same%20problem%20using%20the%20Office%20365%20Exchange%26nbsp%3Badmin%20center.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWhen%20I%20try%20an%20turn%20on%20an%20existing%20connector%20which%20is%20currently%20off%20I%20get%20the%20error%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EParameter%20count%20mismatch.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ERegards%3C%2FP%3E%3CP%3EJohn%20Ellwood%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-71002%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-71002%22%20slang%3D%22en-US%22%3E%3CP%3EHI%20Guys%2C%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ETrying%20to%20work%20this%20issue%20arround%20came%20accross%20a%20senario.%20I%20created%20a%20new%20org%20admin%20account%2C%20did%20not%20assign%20any%20permission.%20Then%20try%20to%20run%20the%20Hybrid%20Wizard%2C%20It%20worked.%20While%20i%20try%20the%20old%20admin%20account%20same%20error.%20Test%20it%20guys%20maybe%20it%20will%20work%20for%20you.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70995%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70995%22%20slang%3D%22en-US%22%3EDear%20Vimal%2C%20You%20are%20absolutely%20write%20%2C%20but%20your%20solution%20requires%20either%20a%20existing%20hybrid%20setup%20to%20look%20at%20command%20%2C%20or%20please%20be%20a%20bit%20more%20elaborative%20on%20command%20that%20need%20to%20run%20on%20cloud%20and%20command%20be%20run%20on%20tenant%2C%20Thanks%20and%20regards%2C%20Hasan%20Reza%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70908%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70908%22%20slang%3D%22en-US%22%3EHI%20Guys%2C%20Who%20ever%20need%20a%20work%20around%20follow%20the%20process%20below.%20Create%20a%20partner%20inbound%20connector%20and%20set%20the%20cert%20TLS%20authentication%20to%20your%20hybrid%20server%20certificate%20subject%20name%20or%20your%20hybrid%20transport%20server%20certificate%20subject%20name.%20Create%20a%20transport%20rule%20and%20select%20sender%20ip%20addresses%20belong%20to%20one%20of%20these%20ranges%2C%20add%20all%20your%20onprem%20hybrid%20server%20public%20IP%20address.%20Then..%20Do%20the%20following...%20Set%20the%20spam%20confidence%20level%20(SCL)%20to%20'-1'%20and%20set%20message%20header%20'X-MS-Exchange-Organization-BypassClutter'%20with%20the%20value%20'true'%20Rule%20mode%20Enforce%20Hopefully%20this%20will%20guys.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70902%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70902%22%20slang%3D%22en-US%22%3E%3CP%3EYeah%2C%26nbsp%3BI%20confirmed%20you%20can't%20create%20or%20edit%20any%20kind%20of%20inbound%26nbsp%3Bconnector%20whether%20it's%20via%20the%20GUI%20or%20via%20PowerShell.%20%26nbsp%3BYou%20always%20get%20the%20%22Parameter%20Count%20Mismatch%22%20error%20no%20matter%20what%20you%20do.%20%26nbsp%3BMicrosoft%20support%20deleted%20my%20existing%20inbound%20connector%20while%20troubleshooting%20so%20I%20can't%20modify%20my%20outbound%26nbsp%3Bconnector%20either%20since%20it%20does%20a%20check%20to%20make%20sure%20you%20have%20an%20inbound%20connector%20before%20saving.%20%26nbsp%3B%20I'm%20stuck%20with%20no%20mail%20flow%20until%20they%20fix%20this.%3C%2FP%3E%3CDIV%20class%3D%22ModalDlg%20msgbx%22%3E%26nbsp%3B%3C%2FDIV%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70897%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70897%22%20slang%3D%22en-US%22%3ESame%20error%20here.%20I%20have%20not%20re-run%20the%20HCW%20but%20have%20been%20trying%20to%20modify%20a%20connector%20since%20yesterday%20mid-day%20with%20no%20success.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70884%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70884%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20error%20here.%20Existing%202%2B%20year%20hybrid%20environment%20(2013%20CU%2016)%20that's%20been%20running%20fine.%20Re-ran%20the%20Hybrid%20Configuration%20Wizard%20today%20to%20replace%20an%20expiring%20certificate%20and%20hit%20this%20error.%20%26nbsp%3BIt%20has%20now%20fouled%20up%20our%20connectors%20and%20we%20are%20down.%20%26nbsp%3BSupport%20is%20so%20far%20clueless.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70847%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70847%22%20slang%3D%22en-US%22%3ESame%20error%20here.%20Single%20domain%2C%20brand%20new%20tenant%2C%20brand%20new%20Exchange%202016%20server.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70837%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70837%22%20slang%3D%22en-US%22%3EExisting%20tenant%20here%20-%20the%20hybrid%20has%20been%20setup%20for%20a%20few%20weeks.%20Was%20adding%20a%20new%20email%20domain%20and%20using%20the%20HCW%20to%20add%20the%20trust%20and%20update%20the%20connector.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70815%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70815%22%20slang%3D%22en-US%22%3E%3CP%3EExchange%202013%20CU15.%20Trying%20to%20validate%20connectors%20on%20a%20new%20tennant%2C%20with%20multiple%20subdomains%20and%20getting%20the%20same%20error.%3CBR%20%2F%3E%3CBR%20%2F%3EChecked%20Service%20Health%20and%20didn't%20see%20anything%20yet.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70814%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70814%22%20slang%3D%22en-US%22%3E%3CP%3EI%20opened%20a%20case.%20I'm%20told%20it%20is%20an%20ongoing%20known%20issue%20and%20to%20wait%2048%20-%2072%20hours.%3C%2FP%3E%3CP%3EI'm%20expecting%20a%20call%20back%20sometime%20today%20though.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70805%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70805%22%20slang%3D%22en-US%22%3E%3CP%3EI%20also%20work%20with%20Kevin%20Eyer%20and%20wanted%20to%20provide%20an%20update%3A%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EWe%20are%20being%20told%20that%20since%20we%20already%20manually%20added%20a%20connector%20to%20our%20Tenant%20to%20allow%20mail%20flow%20from%20Office%20365%20cloud%20only%20mailboxes%20to%20our%20mailboxes%20on-premise%20which%20is%20required%20to%20continue%20mail%20flow%20from%26nbsp%3BO365%20Tenant%20users%20to%20our%20on%20premise%20users%20when%26nbsp%3Bwe%20added%20our%20domain%2C%20that%20is%20causing%20the%20error.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EUpon%20further%20reveiw%20of%20the%20logs%20by%20MS%2C%20they%20show%26nbsp%3Bthat%20the%26nbsp%3Broot%20cause%20of%20the%20issue%20is%20that%20there%20is%20already%20an%20existing%20trust%20relationship%20with%20your%20onPrem%20environment.%20This%20can%20be%20seen%20in%20the%20log%2C%20if%20you%20look%20for%20this%20error%3A%20%22%20PowerShell%20failed%20to%20invoke%20'Set-FederatedOrganizationIdentifier'%3A%20A%20trust%20relationship%20has%20already%20been%20defined%20for%20this%20organization.%22%20in%20additon%20to%20the%20original%20error%20posted%20by%20the%20OP.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EIn%20a%20nutshell%2C%20they%20are%20claiming%20that%20the%20connector%20we%26nbsp%3Bcreated%20a%20few%20days%20ago%20(which%20was%20required%20because%20as%26nbsp%3Bsoon%20as%20we%20added%20our%20domain%20to%20an%20already%20established%20Tenant%20%7Bdue%20to%20a%20merger%7D%20it%20broke%20mail%20flow%20from%26nbsp%3BO365%20to%20our%20user%20on-premise%20and%20a%20connector%20had%20to%20be%20created%20to%20establish%20mail%20flow%20again)%20is%20causing%26nbsp%3Bthe%20error%20even%20though%20I%20didn't%20realize%20adding%20a%20connector%20creates%20a%20Federation%20Trust%3F%20.....%26nbsp%3BInsert%20sarcasm.%20However%2C%20in%20the%20end%20the%20fix%20they%20are%20claiming%20is%20to%20remove%20our%20connector%2C%20wait%26nbsp%3B24%20hours%26nbsp%3Bfor%26nbsp%3Bit%20to%26nbsp%3B%22purge%22%20the%20connector%20from%20the%20Tenant%20then%20rerun%20the%20HCW.%20Of%20course%20this%20will%26nbsp%3Bbreak%26nbsp%3Bmail%20flow%20from%20O365%20to%20our%20on-premise%20during%20this%20time.%26nbsp%3B%20We%20did%20remove%20the%20connector%20from%20our%20Tenant%20and%20reran%20the%20HCW%20but%20still%20errored.%20They%20are%20claiming%20it%20may%20take%20up%20to%2024%20hours%20to%20remove%20and%20do%20not%20support%20to%20manually%20purge%20the%20connector%20via%20PS%20commands...sigh%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3ECurious%20to%20hear%20others%20response%20on%20if%20you%20are%20setting%20up%20Hybrid%20to%20a%20brand%20new%20Tenant%20with%20no%20domains%20or%26nbsp%3Bis%20your%20Tenant%20already%26nbsp%3Bestablished%20and%20you%20have%20added%20the%20domain%26nbsp%3Bto%20the%26nbsp%3BTenant%20along%20with%20the%20connector%20required%20then%20runnign%20the%20HCW.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThis%20is%20definitely%26nbsp%3Bholding%20up%20our%20migration%20and%20discussing%20internally%20on%20the%20next%20steps%20or%20using%20a%203rd%20party%20tool.%3CBR%20%2F%3E%26nbsp%3B%3CBR%20%2F%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70790%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70790%22%20slang%3D%22en-US%22%3ESame%20issue%20here.%20E2016%20CU4%2C%20trying%20to%20run%20the%20HCW%20to%20add%20a%20new%20domain.%20I'll%20be%20opening%20up%20a%20ticket%20as%20well.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70748%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70748%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20are%20experiencing%20the%20same%20issue.%20Our%20work%20is%20at%20a%20standstill.%20In%20the%20midst%20of%20configuring%20our%20hybrid%20configuration.%3C%2FP%3E%3CBLOCKQUOTE%3E%3CHR%20%2F%3E%3CA%20href%3D%22https%3A%2F%2Ftechcommunity.microsoft.com%2Ft5%2Fuser%2Fviewprofilepage%2Fuser-id%2F50780%22%20target%3D%22_blank%22%3E%40Teka%20Teka%3C%2FA%3E%20wrote%3A%3CBR%20%2F%3E%3CP%3EHi%20All%2C%3C%2FP%3E%3CP%3Eim%20trying%20to%20run%20the%20HCW%20and%20i%20have%20the%20below%20error%20when%20it%20reach%20the%20mail%20flow%20configuration.%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EHCW0000%20PowerShell%20failed%20to%20invoke%20'New-InboundConnector'%3A%20Parameter%20count%20mismatch.%20An%20unexpected%20error%20has%20occurred%20and%20a%20Watson%20dump%20is%20being%20generated%3A%20Parameter%20count%20mismatch%3C%2FSPAN%3E%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3E%3CSPAN%3EThanks%3C%2FSPAN%3E%3C%2FP%3E%3CHR%20%2F%3E%3C%2FBLOCKQUOTE%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70743%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70743%22%20slang%3D%22en-US%22%3E%3CP%3EWe%20have%20the%20same%20issue%20here.%20We're%20supposed%20to%20start%20migrating%20700%20users...%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EDoes%20anyone%20have%20news%20from%20MS%3F%3C%2FP%3E%3CP%3E%26nbsp%3B%3C%2FP%3E%3CP%3EThanks%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70720%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70720%22%20slang%3D%22en-US%22%3E%3CP%3EWill%20Do!%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70699%22%20slang%3D%22en-US%22%3ERe%3A%20RE%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70699%22%20slang%3D%22en-US%22%3EDid%20MS%20Support%20indicate%20an%20ETA%3F%20This%20is%20holding%20up%20our%20migration%20for%20the%20entire%20organization.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70688%22%20slang%3D%22en-US%22%3ERE%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70688%22%20slang%3D%22en-US%22%3EI%20just%20had%20a%20call%20with%20MS%20support%20and%20they%20confirmed%20it's%20a%20known%20issue%20for%20them%20and%20the%20back%20end%20team%20are%20working%20to%20fix%20it.%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70687%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70687%22%20slang%3D%22en-US%22%3E%3CP%3ESame%20Problem.%20Would%20you%20please%20send%20a%20solution%20if%20you%20got%3F%3C%2FP%3E%3CP%3EExchange%202016%20CU5%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70660%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70660%22%20slang%3D%22en-US%22%3E%3CP%3EThanks%20Kevin%2C%3C%2FP%3E%3CP%3Ealso%20i%20have%20Exchange%202013%20CU%2015%2C%20i%20also%20open%20a%20case%20with%20MS%20support%20but%20im%20waiting%20for%20their%20call.%3C%2FP%3E%3C%2FLINGO-BODY%3E%3CLINGO-SUB%20id%3D%22lingo-sub-70638%22%20slang%3D%22en-US%22%3ERe%3A%20HCW%20Error%20when%20configuring%20the%20mail%20flow%3C%2FLINGO-SUB%3E%3CLINGO-BODY%20id%3D%22lingo-body-70638%22%20slang%3D%22en-US%22%3E%3CP%3EInteresting%20enough%20I%20had%20this%20same%20error%20yesterday%20too.%20%26nbsp%3BI%20am%20configuring%20the%20HCW%20in%20an%20Exchange%202013%20CU15%20environment%20with%20(2)%20CAS%20servers%20and%20(2)%20MBX%20servers.%20%26nbsp%3BI%20put%20a%20call%20into%20Office%20365%20support%20and%20after%20troubleshooting%2C%20they%20are%20having%20to%20escalate%20the%20issue.%20%26nbsp%3BOnce%20I%20learn%20more%20I%20will%20post%20here%20in%20this%20community.%20%26nbsp%3B%3C%2FP%3E%3C%2FLINGO-BODY%3E
Occasional Contributor

Hi All,

im trying to run the HCW and i have the below error when it reach the mail flow configuration.

 

HCW0000 PowerShell failed to invoke 'New-InboundConnector': Parameter count mismatch. An unexpected error has occurred and a Watson dump is being generated: Parameter count mismatch

 

Thanks

84 Replies

Interesting enough I had this same error yesterday too.  I am configuring the HCW in an Exchange 2013 CU15 environment with (2) CAS servers and (2) MBX servers.  I put a call into Office 365 support and after troubleshooting, they are having to escalate the issue.  Once I learn more I will post here in this community.  

Thanks Kevin,

also i have Exchange 2013 CU 15, i also open a case with MS support but im waiting for their call.

Same Problem. Would you please send a solution if you got?

Exchange 2016 CU5

I just had a call with MS support and they confirmed it's a known issue for them and the back end team are working to fix it.
Did MS Support indicate an ETA? This is holding up our migration for the entire organization.

Will Do!

We have the same issue here. We're supposed to start migrating 700 users...

 

Does anyone have news from MS?

 

Thanks

We are experiencing the same issue. Our work is at a standstill. In the midst of configuring our hybrid configuration.


@Teka Teka wrote:

Hi All,

im trying to run the HCW and i have the below error when it reach the mail flow configuration.

 

HCW0000 PowerShell failed to invoke 'New-InboundConnector': Parameter count mismatch. An unexpected error has occurred and a Watson dump is being generated: Parameter count mismatch

 

Thanks


 

Same issue here. E2016 CU4, trying to run the HCW to add a new domain. I'll be opening up a ticket as well.

I also work with Kevin Eyer and wanted to provide an update:

 

We are being told that since we already manually added a connector to our Tenant to allow mail flow from Office 365 cloud only mailboxes to our mailboxes on-premise which is required to continue mail flow from O365 Tenant users to our on premise users when we added our domain, that is causing the error.

 

Upon further reveiw of the logs by MS, they show that the root cause of the issue is that there is already an existing trust relationship with your onPrem environment. This can be seen in the log, if you look for this error: " PowerShell failed to invoke 'Set-FederatedOrganizationIdentifier': A trust relationship has already been defined for this organization." in additon to the original error posted by the OP.

 

In a nutshell, they are claiming that the connector we created a few days ago (which was required because as soon as we added our domain to an already established Tenant {due to a merger} it broke mail flow from O365 to our user on-premise and a connector had to be created to establish mail flow again) is causing the error even though I didn't realize adding a connector creates a Federation Trust? ..... Insert sarcasm. However, in the end the fix they are claiming is to remove our connector, wait 24 hours for it to "purge" the connector from the Tenant then rerun the HCW. Of course this will break mail flow from O365 to our on-premise during this time.  We did remove the connector from our Tenant and reran the HCW but still errored. They are claiming it may take up to 24 hours to remove and do not support to manually purge the connector via PS commands...sigh

 

Curious to hear others response on if you are setting up Hybrid to a brand new Tenant with no domains or is your Tenant already established and you have added the domain to the Tenant along with the connector required then runnign the HCW.

 

This is definitely holding up our migration and discussing internally on the next steps or using a 3rd party tool.
 
 

I opened a case. I'm told it is an ongoing known issue and to wait 48 - 72 hours.

I'm expecting a call back sometime today though.

Exchange 2013 CU15. Trying to validate connectors on a new tennant, with multiple subdomains and getting the same error.

Checked Service Health and didn't see anything yet.

Existing tenant here - the hybrid has been setup for a few weeks. Was adding a new email domain and using the HCW to add the trust and update the connector.
Same error here. Single domain, brand new tenant, brand new Exchange 2016 server.

Same error here. Existing 2+ year hybrid environment (2013 CU 16) that's been running fine. Re-ran the Hybrid Configuration Wizard today to replace an expiring certificate and hit this error.  It has now fouled up our connectors and we are down.  Support is so far clueless.

Same error here. I have not re-run the HCW but have been trying to modify a connector since yesterday mid-day with no success.

Yeah, I confirmed you can't create or edit any kind of inbound connector whether it's via the GUI or via PowerShell.  You always get the "Parameter Count Mismatch" error no matter what you do.  Microsoft support deleted my existing inbound connector while troubleshooting so I can't modify my outbound connector either since it does a check to make sure you have an inbound connector before saving.   I'm stuck with no mail flow until they fix this.

 
HI Guys, Who ever need a work around follow the process below. Create a partner inbound connector and set the cert TLS authentication to your hybrid server certificate subject name or your hybrid transport server certificate subject name. Create a transport rule and select sender ip addresses belong to one of these ranges, add all your onprem hybrid server public IP address. Then.. Do the following... Set the spam confidence level (SCL) to '-1' and set message header 'X-MS-Exchange-Organization-BypassClutter' with the value 'true' Rule mode Enforce Hopefully this will guys.
Dear Vimal, You are absolutely write , but your solution requires either a existing hybrid setup to look at command , or please be a bit more elaborative on command that need to run on cloud and command be run on tenant, Thanks and regards, Hasan Reza