Forum Discussion
HCW Error when configuring the mail flow
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
Hi Friends,
Today May 22, at 20 hours UTC Mexico City, I had the same error in HCW over Exchange Server 2013 CU16, its today
Now, i checked two thisng:
1. Create a inbound connector in ECP of Exchange Online, a simple configuration result in the same error that view in the HCW in my Exchange On-premise.
2. Create is OK when add inbound connector through of power shell, so...
What do you do?
Create a new admin globar user and enter in the HCW, ... ¡the configuration is complete!
Very very unusual solution, but worked for my, as indicated by other post.
Regards!
JM
I can now configure connectors without the error message being displayed.
However if you configure more than one connector the rules are not working correctly.
I am getting
(): SMTP server response: 550 5.7.64 TenantAttribution; Relay Access Denied
for a server which has been added to the list. Another server was working correctly.
The problem seems to have gotten more complex
Regards
John Ellwood
I was finishing the migration of about 460 users to Office 365 this weekend, and they have a Barracuda archiver, so when I went to create a connector to the archiver, I also got that "parameter count mismatch" error when trying to finish it.
I was using an IP address for the "How do you want to route email messages? (smarthost)" screen. On a whim, I decided to throw a random FQDN in there instead to test, and it saved fine. This customer already had a DNS entry so I updated it with the correct one,but if you don't, I suggest that you just create a DNS entry, and use that FQDN.
Your problem may be different, but this may help someone.
I had a chat with support and completed some remote sessions and recieved this email... using the steps provided with a new Global Admin did not work, Same Error... I awate a fix... tomorrow...
'As discussed, it seems that you are also part of the affected tenants for Service Degradation EX102057. Title: Mail connector issue User Impact: Administrators may be unable to create or modify mail connectors. More info: This is an incremental update to provide the latest status on the issue. Current status: The deployment of the fix is 97 percent complete. We’ll provide an update on Monday confirming full service restoration.
In addition, try to add 1 more global admin that will perform adding the mail connector in Exchange Admin Center and try again.'My Customer is suffering from the same problem. Looks like we are in the 3% left. Need to change the connector after a datacenter migration. Production Mails are effected.
Looks like we have a winner, I was able to create a connector...
I hope everyones issue with this is fixed...
regs.
I worked with support to skip the MailGUID value.. (I really don't want to do a Hybrid Rollout, but rather a cutover process).
The problem with AD Connect is, if it sees exchange in the domain, it forces a hybrid rollout..
We are experiencing the same issue. You can connect through Azure AD shell and run the Get-HybridMailflowDatacenterIPs command and you receive the same "Parameter count mismatch." error. We have ticket open and are going to confirm with Microsoft. We've succesfully tried from two seperate tenants and get the error.
I can now successfully run Get-HybridMailflowDatacenterIPs . Not sure if the rest of the wizard will work but I will give it a shot.
Worked for me as of 8am CST this morning.
same error in dthe hybride wizard
HCW0 - PowerShell failed to invoke 'Get-HybridMailflowDatacenterIPs': Parameter count mismatch. An unexpected error has occurred and a Watson dump is being generated: Parameter count mismatch.
Just confirmed with Microsoft this is an issue with a specific datacenter and that they are working actively on an internal case to resolve. Next update will be 9 PM UTC 5-20-2017. They are specifically attaching customers tenants that call in to their case so they can go and rollout the patch.
We're having this issue too (in Office 365, trying to create an inbound connector). Do you know if the fix they're working on will automatically address our issue once it's fully rolled out, or do I need to explicitly call into support so they can patch our specific instance?
- Same issue here. Support did not seem aware of any issues. Received the 'wait 2 hours and try it again' response.
THere is an issue from office 365. Incident EX102057 today 8PM UTC will be next update.
Just got a call from support stating they are working on the issue and have fixed it for about 50% of the users, he told me i could expect a fix during today or by Monday
oh well, its not like e-mail is relevant for a business /Set-SarcasmMode off
- Just got a call myself too same ETA - hopefully today or Monday. Cross fingers!
Great :/
Strange thing is my recieve is working fine so mail is now following in (Which it wasnt) but the send is goosed.. rather royally annoying!!
I stumbled upon this thread today and I'm getting the same error. Quite annoying! What is the ETA?
I opened a ticket last night, and received this:
Title: Mail connector issue
User Impact: Administrators may be unable to create or modify mail connectors.
Current status: We've initiated the deployment of the fix and we'll continue to monitor service health throughout the deployment process.
Scope of impact: Your organization is affected by this event.
Start time: Monday, May 15, 2017, at 8:02 PM UTC
Preliminary root cause: A recent update to the environment, intended to resolve a previously existing code defect, caused the mail connector service to become degraded.
Next update by: Friday, May 19, 2017, at 12:00 AM UTCLast Updated: May 18 2017 4:53PM UTC
This seems to be quite and issue... and isnt half dragging on.
I have lost the ability to set up a conector to inpremis.
When setting it up im getting :
Error - Parameter Count Mismatch
Do we know how to update is being deployed, is it going to O365 or through Updates?
- Looking at the incident Ryan posted, it sounds like it's a backend issue, so there should be nothing for us to update.
- Good to know it's at least showing up on someone's dashboard! Went to go look at mine and nothing about this. It's read-only Friday, so I won't be testing anything out today! :D
Same error here
Accounting software sends out invoices and needs a connector to use office 365 or office 365 refuses inbound email from the software.
Company switched ISP and has a new IP address, editing the existing connector resulted in Parameter Count Mismatch event, removing the connector and recreating it with the new IP has the same result.
- Exactly the same issue here.... I have spoken to MS support and all they said is they are aware and working on a fix, there is no time frame as yet!
This shocking!3rd day is gone. yes thats shocking. you are right!
Just got off the phone with Microsoft Support. They informed me that they are aware of the problem and stated that a "small amount" of customers have reported this problem and do not have an ETA for the resolution.
Adding to this, today I was attempting to setup SMTP relay with on-premises organization to Office 365. and experienced the exact same error seen with the HCW when setting up the connector within Office 365. Only this time I was simply setting up a SMTP relay connector.As we all know, the process of setting up SMTP relay with Office 365 tenant is a VERY easy process, and to make things even easier, this article walks you through the steps to a tee (How to set up a multifunction device or application to send email using Office 365 - https://support.office.com/en-us/article/How-to-set-up-a-multifunction-device-or-application-to-send-email-using-Office-365-69f58e99-c550-4274-ad18-c805d654b4c4).
So the problem is not only affecting Hybrid Deployments/Environments. It is affecting tenants who attempt to setup/configure connectors in the EAC. My tenante today is currently NOT in a hybrid configuration. Simply, the problem is within the Office 365 EAC > Mail Flow > Connectors. Whether you are performing a new-inboundconnector command VIA the HCW, or simply trying to setup a SMTP relay connector, you will receive the following "generic" error:
error
Parameter count mismatch.
