May 16 2017 11:42 PM
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
May 17 2017 05:04 AM
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.
May 17 2017 05:41 AM
Thanks Kevin,
also i have Exchange 2013 CU 15, i also open a case with MS support but im waiting for their call.
May 17 2017 06:48 AM - edited May 17 2017 06:49 AM
Same Problem. Would you please send a solution if you got?
Exchange 2016 CU5
May 17 2017 06:48 AM
May 17 2017 07:12 AM
May 17 2017 08:21 AM
We have the same issue here. We're supposed to start migrating 700 users...
Does anyone have news from MS?
Thanks
May 17 2017 08:37 AM
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
May 17 2017 10:10 AM
May 17 2017 11:01 AM - edited May 17 2017 11:03 AM
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.
May 17 2017 11:21 AM
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.
May 17 2017 11:23 AM
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.
May 17 2017 01:11 PM
May 17 2017 02:01 PM
May 17 2017 04:18 PM
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.
May 17 2017 04:51 PM
May 17 2017 05:40 PM
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.
May 17 2017 07:19 PM
May 18 2017 02:55 AM