Re: Srv2008, Ech2007, BESv5 - MAPI problems?? (8004011d)
Just to clear this up for anyone who was having similar issues.
I uninstalled BES Express 5.0.1 and attempted to test from scratch. I went through all the pre-install tasks hitting warnings about permissions already existing.. Fine all the way through till..
Problem
During install the BES installer wouldn't resolve it's own name.. It would by IP, but also wouldn't then continue through the setup.
Environment: Windows Server 2008 R2 Standard + Exchange 2007 (x64)
Resolution
This problem was resolved by disabling IPv6. I was told not to do this as Exchange 2007 doesn't work well without it but after testing my emails are still getting out and internal emails are still working. (I'm yet to recieve emails from the outside world but this will be fine one I finish migration and MX records are switched - Expected result)
Ref:
experts-exchange.com/Hardware/Handhelds_-_PDAs/Blackberry/Q_26604476.html
For those without EE access the resolution is documented on the MS site also.
support.microsoft.com/kb/929852
So. I continue on my journey wondering what is next in store for me..
Problem
Very minor problem and fixed within a few minutes. During the install of BES it upgraded my version of SQL Express (I think to SP3). I hit an error while trying to create the SQL database.
Resolution
Nice and easy. While logged in as the account I wanted to promote (to have SQL superpowers) I did the following;
Start > Microsoft SQL Server 2005 > Configuration Tools > SQL Server Surface Area Configuration
Then 'Add New Administrator' and move all available permissions over (Check your user is in the top right text box.
Ok
Excellent.... What next??
Problem
OpenMsgStore() for this profile failed (8004011d) after testing IEMSTest.exe with the BESAdmin account.
I was also given an error during install which is why I again tested IEMSTest.exe. On BES Express 5.0.2 install you have a tick-box to check permissions for the user. A great addition to the install process.
Resolution
It turns out in my haste at the beginning of the pre-req setup I had created a local BESAdmin account with the same name. Having done this on the Exchange server I noticed I was adding the permissions for this to exchange (ViewOnlyAdmin, etc). I disabled this account as I do not need or want it. I then proceeded again with new found hope, and run the 'script/command' again using 'Domain\User' to identify the user I want to promote. It worked and permissions were applied.
So I plod along through the install, now confident this will work as it's been happier than the last time I attempted this.
I click finish and it's done!. Excellent!
One more thing I will note though. When loading into Internet Explorer I get an error about the certificate. I plan on tidying this up but a crude fix to skip clicking 'Click here to continue (Not Recommended)' was to install the certificate to the 'Trusted Root Certificate Authorities' store.
Thankyou & Goodnight!!!
Adrian
Last edited by SinrG202; 01-06-2011 at 09:56 AM..
|