Re: Cannot Move Mailboxes

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance



E2k3
"Jeff Guillet, MCSE" <JeffGuilletMCSE@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:3C1B6CD1-FFF6-4247-91F7-B3B385920FA2@xxxxxxxxxxxxxxxx
So, you're able to create an E2K3 mailbox on the E2K3 server using the
same
account? Where are you creating the account from, E2K3 server or E55?

"JS" wrote:

All things mentioned in both articles checked and as should be. This is a
mixed mode environment and our Exchange 5.5 box is riding on the last
BDC. I
am not sure whether this may be causing some issues. Stumped on this. If
I
create a new user, it allows me to create a mailbox....but moving one is
a
no go...can't log onto the destination store which is the 2003 box.

"Jeff Guillet, MCSE" <JeffGuilletMCSE@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:34CC25B7-FCF7-4A22-8F96-3BD57441A11B@xxxxxxxxxxxxxxxx
Please take a look at http://support.microsoft.com/kb/264413/en-us and
http://support.microsoft.com/default.aspx?scid=kb;en-us;329685.

Jeff Guillet, MCSE

"JS" wrote:

Hello:

I posted yesterday about MAPI errors in my event logs and this appears
to
be
related to a permissions issue but I cannot figure out where and at
what
level.

I have a fresh install of Exchagne 2003 into our 5.5 site. Besides the
MAPI
error in the event logs every couple minutes, I received this error
when
trying to move a mailbox. Obviously permissions related but what and
where?
I am running under an admin account with Domain Admin, Enterprise
Admin
and
Schema Admins permissions but yet I could not log into the destination
server (I am assuming this is failing when this process attempts
access
to
the store)

The Error:

The attempt to log on to the Microsoft Exchange Server computer has
failed.
The MAPI provider failed. Microsoft Exchange Server Information Store
ID
no:
8004011d-0512-00000000.

Any ideas? I'm concerned because of the fact that this is a fresh
install
and that these permissions errors may have a rippling affect. I don't
want
to begin mailbox migration until I fully understand the root cause of
this.
I would appreciate any input.

Thanks again








.



Relevant Pages

  • Re: Restored Server but SharePoint refusing admin access
    ... > SID/BID or remove the user from the database and add it again. ... >, In SQL Configuration Manager go to SQL> Server ... > you had) you cannot access the database from that account. ... > newly added administrator account (for me, since I added a new admin ...
    (microsoft.public.windows.server.sbs)
  • Web Server - User Access and Priviledges.
    ... restriction policy that came out with the server 2003 ... Have a logon for your everyday use and one admin ... account that your or only a few people have access to. ... >Create a second Administrator account on each Web Server. ...
    (microsoft.public.win2000.security)
  • Re: Restored Server but SharePoint refusing admin access
    ... SID/BID or remove the user from the database and add it again. ... In SQL Configuration Manager go to SQL Server ... you had) you cannot access the database from that account. ... newly added administrator account (for me, since I added a new admin account ...
    (microsoft.public.windows.server.sbs)
  • Re: Protecting database from administrators
    ... If you remove the Builtin\Administrators account all you ... This resolves any of the below issues. ... server resides. ... removing "System Admin" role ...
    (microsoft.public.sqlserver.security)
  • At wits end with Portal Search errors
    ... Content for this URL is excluded by the server because a no-index ... account to access this URL. ... Added in a correct Proxy server and a fake one in Central admin ...
    (microsoft.public.sharepoint.portalserver)