question

JoshGardner-5927 avatar image
0 Votes"
JoshGardner-5927 asked HaileSelassie commented

Is anybody familiar with the error "A server-side administrative operation has failed. Operation failed with message: Error 0xe0434352 (Unknown error (0xe0434352)) from cli_SetDagNetworkConfig"

I am attempting to configure my testbed environment's DAG's network, but any DAG network command I run gives me errors. Please note, my testbed (and production) is Exchange 2016 on-prem (CU22 with Jan SU installed).

I can find NOTHING online pertaining to these errors at all. Nothing shows in my event viewer (application or system). My testbed has NO HBSS or A/V on it, and it only has 1 network. I wonder if there was some sort of Exchange CU/SU or .NET or even an underlying AD issue (DNS?) that is causing any DAG network command to fail. I've tried these commands from all my Exchange servers (both my test bed and my production), specifically from the Primary Active Manager - to no avail. I am simply just unable to configure the DAG networks.

Figure 1 Test Bed:
170663-image.png

Figure 2 Production (because we have "ReplicationNetworks" due iSCSI storage arrays):
170607-image.png

Figure 3 Event Log
170664-image.png

Errors in Text format:
A server-side administrative operation has failed. Operation failed with message: Error 0xe0434352 (Unknown error (0xe0434352)) from cli_SetDagNetworkConfig
A server-side administrative operation has failed. Operation failed with message: Error 0xe0434352 (Unknown error (0xe0434352)) from cli_SetDagNetwork

Does anybody have any familiarity with these 2 errors? If so... please tell me how to get passed them.


office-exchange-server-administrationoffice-exchange-server-deploymentoffice-exchange-server-ha
image.png (37.3 KiB)
image.png (20.4 KiB)
image.png (20.3 KiB)
· 14
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @JoshGardner-5927

I see some related posts shared the issue caused by networking, you could temporarily disable firewall to see if any help. In addition, please also try adding Full Permissions to the Exchange Trusted Subsystem onto the CNO of the DAG, just like below:
170686-image.png

And what's the current configuration for your Exchange dag? Note to clear your personal information in the result.

 Get-DatabaseAvailabilityGroupNetwork <DAGNetworkName> | Format-List
 Get-DatabaseAvailabilityGroup | Format-List

And here is the official document introduces about
Create a database availability group network in Exchange Server


0 Votes 0 ·
image.png (32.0 KiB)

I appreciate your suggestions @joyceshen-MSFT , but I have an IP-less DAG in both my testbed and my production environment, so there is no CNO. I have also confirmed that Windows Firewall is turned off in both environments.

170946-image.png


The DAG FL is rather long so here is a two part picture
171004-image.png
170938-image.png

DAG network FL in my testbed
170929-image.png

DAG network FL in production - hope my explanations are not too convoluted
171014-image.png

Honestly I don't know how long this may have been going on, I am aware that DAG Network commands are rather uncommon after initial configuration. Its a set it and forget it. For reference, I have looked all over the Internet to see if there is something I'm missing, its not that something is horribly misconfigured, its the fact that I cannot configure the DAG networks at all.

Also it looks like the images I uploaded here with command results can no longer be loaded on the page.


0 Votes 0 ·
image.png (137.6 KiB)

To be super clear, I cannot even configure the networks that I DO want. The goal here is to:
1) remove the accidentally created ipv6 DAG network (unable)
2) disable replication on the second and third iSCSI networks to match same network configuration of the first iSCSI network settings with Set-DatabaseAvailabilityGroupNetwork -ReplicationEnabled $False (unable)
3) ignore network on the second and third iSCSI networks to match same network configuration of the first iSCSI network settings with Set-DatabaseAvailabilityGroupNetwork -IgnoreNetwork $True (unable)
4) "rescan" the DAG network with Set-DatabaseAvailabilityGroup -DiscoverNetworks (unable)
5) "reset" the manual DAG network configuration with Set-DatabaseAvailabilityGroup -ManualDagNetworkConfiguration $True (unable)

Something is preventing me from doing any sort of DAG network related commands. All of the above commands results in either of the below errors.
A server-side administrative operation has failed. Operation failed with message: Error 0xe0434352 (Unknown error (0xe0434352)) from cli_SetDagNetworkConfig
A server-side administrative operation has failed. Operation failed with message: Error 0xe0434352 (Unknown error (0xe0434352)) from cli_SetDagNetwork

0 Votes 0 ·
Show more comments
shahvikask avatar image
1 Vote"
shahvikask answered JoshGardner-5927 commented

@JoshGardner-5927

Did you find solutions? I am also facing a same issue while running Set-DatabaseAvailabilityGroupNetwork. i am trying to disable replication on MAPI nework configuration and getting same error message.

I do have same CU22 Jan SU installed in all Exchange Servers, so could it be the version issue? Did you tried running command in lower version CU?

Note: I can get the result while running Get-DatabaseAvailabilityGroupNetwork, but not working for Set command.

· 2
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@shahvikask Unfortunately not, though [sadly] I'm glad its not just me. I also have no issues with Get- commands, only the Set- commands. I was tempted to uninstall the Jan 2022 SU in my test bed to see if that would fix it, but... that seems drastic, and I dont know the impact. Hopefully it would just roll back to the Nov SU (but I really doubt it, because MS likes to do cumulative installs now).

0 Votes 0 ·

@shahvikask Just to let you know, I tried running the Set- commands after removing both the Jan 2022 SU and the Nov 2021 SU for Exchange 2016 CU 22. There was no change.

0 Votes 0 ·
HaileSelassie avatar image
0 Votes"
HaileSelassie answered JoshGardner-5927 rolled back

Same issue here, also with latest version Exchange 2019 CU11 March 2022 Security Updates. We have created an incident at Microsoft now. Will post any relevant updates

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@HaileSelassie Thanks for posting, I'm hoping more and more people will comment. Maybe this will gain visibility and traction with the Microsoft engineers and they can dive into it. More people reporting an issue makes me think there is a bug somewhere. Thank you very much for creating an incident with Microsoft, sadly we are still trying to convert things in order to get Microsoft support credit, so we are kind of stuck.

0 Votes 0 ·
HaileSelassie avatar image
0 Votes"
HaileSelassie answered

No news from MS case so far. I just realized that in the Exchange Team Blog "Released: January 2022 Exchange Server Security Updates" the issue has been added in the meantime. In the Blog Post "Released: March 2022 Exchange Server Security Updates" the issue has been mentioned as fixed:

"Modifying DAG network settings failing with error 0xe0434352 after January SUs are installed - fixed in the March SU"
Source: https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2022-exchange-server-security-updates/ba-p/3247586

What I can confirm is, that after March SU, configuring "ManualDagNetworkConfiguration" attribute on the DAG is working for me. But, configuring DAGNetworks still throws the error. I also mentioned it here:

https://techcommunity.microsoft.com/t5/exchange-team-blog/released-march-2022-exchange-server-security-updates/bc-p/3254641/highlight/true#M32440

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

HaileSelassie avatar image
0 Votes"
HaileSelassie answered JoshGardner-5927 commented

image.png (47.8 KiB)
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

@HaileSelassie Thanks for the update! I can only hope it is haha.

0 Votes 0 ·
HaileSelassie avatar image
0 Votes"
HaileSelassie answered HaileSelassie commented

I can confirm that with Exchange 2019 CU12, configuring DAG Networks (Set-DatabaseAvailabilityGroupNetwork) is now possible again

· 4
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Thank you so much for the update. I'm going to install Exchange 2016 CU23 ASAP to confirm for us as well. Pity that MS did not post that they addressed the DAG cmdlets in the blog or release notes of the KB.

0 Votes 0 ·

I just installed Exchange 2016 CU23 in my test bed and I still cannot run Set-DatabaseAvailabilityGroupNetwork commands.....

@HaileSelassie Did you have to do anything besides install the CU?

0 Votes 0 ·

Nevermind, apparently MS didnt add it in. Of course.... I followed up with a comment in the blog.

https://techcommunity.microsoft.com/t5/exchange-team-blog/released-2022-h1-cumulative-updates-for-exchange-server/bc-p/3295680

196688-image.png



0 Votes 0 ·
image.png (42.2 KiB)

@JoshGardner-5927 I verified again and I have to revise my statement, indeed I still receive the error...as also confirmed by MS not to be fixed in 2022 H1 CUs...don't know what I have verified the first time, sorry. So I was able to configure DAG and DAG Networks with Exchange 2019 CU11, after removing all Exchange Security Updates that have been applied after CU11.

0 Votes 0 ·