cancel
Showing results for 
Search instead for 
Did you mean: 

PST Will Not Migrate to Mailboxes on Particular Exchange Server

karmakoma
Level 5
Hello,

I'm having some issues migrating pst's to users on a particular Exchange 2k3 Server. This is both server driven and via PST Migration wizard.

The migration job appears to just hang at the first message to migrate and that is it. No errors, nothing in the dtrace it just does nothing. This happens to any mailbox on this particular Exchange server. Migrating PST to another user residing on a different Exchange server works fine. Move users mailbox from problem Exchange server to working Exchange server and PST migration works.

It appears to be a permission issue but I cannot figure out where. EV service account has full Exchange admin control to Exchange server.

Does anyone have any ideas? I've logged a call with EV Tech Support and I think they are also struggling to figure out what the issue may be.

Thanks!
1 ACCEPTED SOLUTION

Accepted Solutions

John_Chisari
Level 6
Partner Accredited
 I know the original poster was going to post - but thought I would beat him to it! :p

Anyway, the hang was actually caused by Outlook prompting which mailbox to use - they had 2 mailboxes setup - evault and evault1 - so PST Migration was using evault as the mailbox to open - and hung at that point.

This was fixed by upgrading to EV2007 SP5 - and making sure all the archiving tasks (mailbox, journal and public folder) were using an SMTP address for the EV System mailbox.  Since EV2007 SP4 the tasks now use the SMTP address by default.

Hope that helps someone else out there, will also be putting a technote together for this issue.

View solution in original post

15 REPLIES 15

MichelZ
Level 6
Partner Accredited Certified
Interesting one. On the EV Server, logged on as service account, can you open up the Mailbox of such a User in Outlook? Are you able to send e-mail for the User there? Cheers

cloudficient - EV Migration, creators of EVComplete.

karmakoma
Level 5
Hi,

Ok tried what you suggested. Logged on EV server with EV service account. Opened mailbox of user on problem exchange server. Attempted to send a message. I don't have permissions.

I went back to Exchange system manager to check permission on problem exchange server. The EV service account is there with full permissions including "send as" however the Exchange Domain Admins group (of which the EV account is a member) has deny permissions on "send as". So this looks like where my problem is.

Interestingly the working exchange server has exactly the same permissions (Exchange Domain Admins group has deny permission on "send as".

So I removed the EV service account from the Exchange Domain Admins Group, logged off and logged back in to the EV server and attempted to send a message. Still don't have permissions!!!

Hmmm....

Wayne_Humphrey
Level 6
Partner Accredited Certified
If the Service Account is in the Admin group, then he will be granted explicit deny on send as / receive as.  You cannot also make a change and expect it to be instantaneous, it requires replication which could take some time, or you can force it.

Also you can do the following to turn on the Security Page, to make your life easier

The Exchange 2003 and 2000 System Manager

The Situation:
You have navigated to the Exchange 2003 System manager and now you want to change permissions for objects in your Exchange Organization.

The problem:
Exchange 2003 System Manager does not display the Security Tab, so you cannot modify the permissions. The default position is that when you check any of the Exchange Organization objects, there is no Security Tab.

The solution - Security TabShowSecurityPage Registry setting DWORD

To display the permissions tab, make this change to the registry.

1. Here is the correct path to navigate: HKEY_Current_User\Software\ Microsoft\Exchange\ExAdmin
2. Once you reach the above section of the registry you need to create a DWORD called ShowSecurityPage
3. A value of 1 (Numeric one) means on, whilst 0 (Zero) means off
4. Close the Exchange System Manager, then reopen ESM

So you should now get this:
imagebrowser image        imagebrowser image
Without ShowSecurityPage                  With ShowSecurityPage

I hope this helps.

--wayne

karmakoma
Level 5

I did force replication and still unable to send on behalf of user whose mailbox resides on problem exchange server.

Thanks for the nice tip though.

karmakoma
Level 5
I tried sending an email from a mailbox on the working exchange server using the EV service account.

I was not able to.

philt
Level 5
what is the group membership of your evservice account?

karmakoma
Level 5
Hi, the EV service account is only a member of domain users and a messageone distribution list.

It is a member of local admins on the Exchange servers and the EV server. The EV service account also has full permissions on all exchange servers via Exchange System manager.imagebrowser image
imagebrowser image

Wayne_Humphrey
Level 6
Partner Accredited Certified
Scroll down on the security page and show us a screen-shot of send as / receive as permissions please.

karmakoma
Level 5
Here you go!
imagebrowser image

Wayne_Humphrey
Level 6
Partner Accredited Certified
Is INVSYDMEXC01 the server? you wanna drill down and check out the Storage Group and the Mail Store, permissions then :)  I would also suggest setting the ShowSecurityPage regkey.

As I mentioned before:

Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Exchange\EXAdmin]
"ShowSecurityPage"=dword:00000001

karmakoma
Level 5
is the server. I checked storage group, mail stores and the permissions propagate from the top level. These all have EV service account with full permissions and no deny. Perhaps I should try removing and readding the EV service account from the exchange server.

In order for PST archiving to work I definitely need the EV service account to have send as/receive as permissions to the mailboxes? The way to test this as stated above is to try to send an email from a mailbox using the EV service account? This does not work however this is the case from mailboxes on both my exchange servers yet pst migration works on one of the exchange servers fine.

It's got to be a permission issue but I'm stumped as to where it might be.

Wayne_Humphrey
Level 6
Partner Accredited Certified
How, about trying to add a new user from scratch.

karmakoma
Level 5
Symantec engineer has picked up this forum post and recommended I not make anymore changes for the time being. They are sending me a .dll from their lab which they hope will identify the issue.

It has been seen before but there is no official fix for it as yet.

I'll keep you posted.

Wayne_Humphrey
Level 6
Partner Accredited Certified
If you cannot open the mailbox using the service account or send a mail, that is an Exchange issue. So why is there a case logged with Symantec? Sould it not be logged with Microsoft?


John_Chisari
Level 6
Partner Accredited
 I know the original poster was going to post - but thought I would beat him to it! :p

Anyway, the hang was actually caused by Outlook prompting which mailbox to use - they had 2 mailboxes setup - evault and evault1 - so PST Migration was using evault as the mailbox to open - and hung at that point.

This was fixed by upgrading to EV2007 SP5 - and making sure all the archiving tasks (mailbox, journal and public folder) were using an SMTP address for the EV System mailbox.  Since EV2007 SP4 the tasks now use the SMTP address by default.

Hope that helps someone else out there, will also be putting a technote together for this issue.