Hi dirkvergagen,We have received your email.By my understanding, the issue has been solved by the following step:1. Use admin account whose mailbox is on Exchange 20162. Move all arbitration mailbox to Exchange 2016When we have coexisted environment, we suggest you move all arbitration mailboxes to higher version Exchange.Best Regard,Jim XuPlease remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected] XuTechNet Community Support.
Re: Object reference not set to an instance of an object. If it is the first run, then it is a full. Can you store the logs on a google drive / dropbox / onedrive / your own choice of sharing platform and PM me a link? Location: Belgium, the land of the fries, the beer, the chocolate and the diamonds.
Hi dirkverhagen,Welcome to our forum.Did you add Exchange server to this DAG?Did you add database copy to another Exchange server?By this issue, we suggest you do the following steps for troubleshooting:1. Run the command: Get-DatabaseAvailabilityGroup to check if the configuration is correct2. Check the connect between DAG members and Witness server(include Ping and DNS resolve), check A record for FSW in DNS to have correct setting3.
Restart “Cluster Service” on DAG member4. Run AD replication manually and clear browser cache, then login ECP to check if the issue persistIn addition, please check if there are related errors in application log and post them for our troubleshooting.Best Regard,Jim XuPlease remember to mark the replies as answers if they help, and unmark the answers if they provide no help.
If you have feedback for TechNet Support, contact [email protected] XuTechNet Community Support. Hi Jim,See reference image below to point out where the error wasIn my situation when I only had a DAG without members it showed:DAGNAMEWITNESS SERVERserver1.contoso.comWhen I add 1 or multiple mailbox server to the DAG it showed:Object reference not set to an instance of an object (this text was in a golden/yellow bar, if I clicked on it, it disappeared)WITNESS SERVERAnd further it showed nothing more.Strangest part of it all, I removed the DAG for 10th time configured it again and added 1 mailbox server to it. Still same error.
So because it was weekend I let it be and wanted to troubleshoot further today. To my surprise the error was gone and it showslike in reference image. What fixed it I unfortunately don't know. I know i'm not the only one with the problem. See comment in this blog post. Hi Jim-Xu,OK so the error was gone yesterday when viewing in ECP on server1.Today i logged in RDP to server1 and see no error.Then i logged in RDP to server2 and going to ECP the error is there.I attached a screenshot of the error.So issue still persists unfortunately.So the problem still exists when going ecp on server2 and not in ecp when on server1.Since we have 6 servers in DAG i logged in RDP on all 6 servers and opened ECP and viewed DAG.On server2 and server6 i have the error, all other servers dont show the error.All servers are in same vlan/subnet etc, no firewall etc.
Hi dirkverhagen,Welcome to your back.Because this issue just occur on server2, we know there are no problems with Exchange DAG. We suggest you do the following steps for troubleshooting:1. Login server 2 directly without RDP to have a try2. Reset browser or use different browser3.
Run the following command to reset IIS: IISReset /NoForce4. Rebuild Windows profile on server2 to check if the issue persist5. Run the following command to check DC and GC on server2, then compare with server 1:Get-ADServerSettings FLBest Regard,Jim XuPlease remember to mark the replies as answers if they help, and unmark the answers if they provide no help.
If you have feedback for TechNet Support, contact [email protected] XuTechNet Community Support. Hi Jim Xu,A new day, new problems:-)So we had the error on server2 and server6.This morning the customer changed the vdir urls and rebooted all servers.all Vdir for all servers point to exchange.ednet.com/autodiscover scp point to exchange.ednet.com/autodiscover/autodisover.xmlexchange.ednet.com DNS points to a single Exchange 2013 serverLogin in all servers and going in ECP now we have the error on all servers:-(1) Same error2) Reset and rebooted server, error persists3) after iisreset and reboot server, error persists4) error persists5) we have error now on all servers. Hi dirkverhagen,Please update Exchange to the last. By your post, if you are using Exchange 2016, please update it to Exchange 2016 CU1.In addition, please re-run Prepared schema and AD by the following link, then run AD replication manually to check if the issue persist:Regard,Jim XuPlease remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected] XuTechNet Community Support. Hi dirkverhagen,Please tell us the OS version of Exchange 2016 in your organization.If OS is Windows server 2012, we must pre-stage the cluster name object (CNO) before adding members to the DAG. Please refer to the following link:Regard,Jim XuPlease remember to mark the replies as answers if they help, and unmark the answers if they provide no help.
If you have feedback for TechNet Support, contact [email protected] XuTechNet Community Support.
This question already has an answer here:.31 answers.8 answersI keep getting this error when I run the program.Object reference not set to an instance of an object.Description: An unhandled exception occurred during the execution of the current web request.Please review the stack trace for more information about the error and where it originated in the code.Exception Details: System.NullReferenceException: Object reference not set to an instance of an object. Source Error:Line with error:Line 156: if (strSearch ' strSearch.Trim.Length 0)What is the correct way it should be written?