We are in the process of migrating our domain to Windows Server 2008 from Windows Server 2003. At this stage, I have two 2008 DC's and one remaining 2003 DC.
My BES 4.0 is installed to a Windows 2000 member server. I am ready to retire my 2003 Domain controller. Yesterday, I did a 'test' shutdown on the 2003 DC to determine if any unexpected issues arose. I then restarted all the member servers, including BES. When the BES server came back up, all the services appeared to start, but none of the Blackberry devices would receive mail and there was an event id 10000 repeated in the event log which basically said:
'BES' Agent 1 failed to initialize within 30 seconds.
That repeats about 10 times, then the log gets flooded with various 20049 and 16058 events relating to Exchange Connector and Blackberry Synchronization Service.
I restarted it a few times, and went through my BES configuration to see if anything appeared to be looking for the 2003 DC, but I found nothing referencing it. The Exchange server is working normally. So then I brought the 2003 DC back online, rebooted the BES server once more. With the 2003 DC online, all is normal with BES again. It's not a DNS issue because the BES Server's DNS points to the 2008 DC's, and has for some time.
So, bottom line is with the 2003 DC out of the mix BES won't run. It seems there is something about having the 2003 DC online that BES needs, but I don't know what. I am wondering if v4.0 of BES may be incompatible with a 2008 domain even though it's running on a Windows 2000 server. Any help is appreciated!
-Gard Brown
This Question has been solved and asker verified All Experts Exchange premium technology solutions are available to subscription members.
Experts Exchange has been collecting answers to technology questions since 1996…3 million and counting! If you have a question, chances are we already have your answer.
If you can't find the exact answer you're looking for, ask our exclusive community of 50,000 experts. You’ll get a personalized answer from a trusted professional.
Thousands of free tech tips, tricks, how-to’s and tutorials are available in our peer reviewed articles section. See for yourself how smart our experts are, no login required.
Save solutions to your questions, answers you’ve discovered through searching plus helpful articles in your personal knowledgebase for easy future access.
Access the answers to your technology questions today.
30-day free trial. Register in 60 seconds.
Members of the expert community talk about why the experience at Experts Exchange is different than what you will find anywhere else.
Try it out and discover for yourself.
30-day free trial. Register in 60 seconds.
Join the community of experts here and help other tech pros by answering question in your area of expertise. You can earn FREE access to all Experts Exchange's premium features and resources.
Thanks SysExpert,
I have verified that the 2008 DC's are global catalog servers. I'll try the dcdiag and netdiag idea and see what I get.
I believe all roles are transferred off the 2003 DC, as it never held any of the main roles. The 2003 server that did has already been dcpromo'd out of the picture with no issues. However, I can't be certain, so I will do my due diligence and be sure.
I'll post back the results.
Ok,
I ran the DCDIAG and NETDIAG as SysExpert suggested. It verified that all the primary roles are assigned and functioning on one of the 2008 DC's. No errors were found on either the 2008 DC or the 2003 DC. With the 2003 DC offline, the only error on the 2008 DC was that it could not replicate with the 2003 DC, which is to be expected.
I have a network with 3 DC's and 17 member servers, and everything works fine EXCEPT BES when the 2003 DC is offline... So I am thinking it has to be something with BES specifically. There are other Windows 2000 member servers, and they are all fine. In fact, everything but BES is fine on the BES server. There are no errors in the event log or issues with any other service on the machine except BES with the 2003 DC offline. I just don't want to demote the 2003 DC until I know for sure that BES will function properly.
So, I am still looking for answers I guess.
I tried something new. I shut down the 2003 DC. Before I rebooted the BES server, this time I logged in and reset the MAPI profile. Then I restarted the BES Services. They came online ok, so then I tried a full BES server restart. This time, it came up with no issues. The 2003 DC is powered off, but not yet disjoined from the domain. However, this is the farthest I have gotten on this, so I am thinking my issue may be resolved. If anything adverse happens after I demote and disjoin the 2003 DC, I will post back, but for now, it's looking good.
Business Accounts
Answer for Membership
by: SysExpertPosted on 2009-06-05 at 09:31:25ID: 24558007
have you checked the roles of the 2003, including global catalog
I would run dcdiag and netdiag in verbose mode to a file and look for fail errors
I would do this twice. once with 2003 DC up, and once again with it down.
compare results - I think that the 2003 has some role not transferred to the 2008 servers.
I hope this helps !