Can't move Exchange Public Folders to new server

I'm in the middle of a SBS 2003 to SBS 2008 migration and I'm at the point of moving the Public Folders. When I click 'Move All Replicas' and select the destination server, I get the following error:

The information store could not be opened
The logon to the Micosoft Exchange Server failed
MAPI 1.0
ID no. 80040111-0286-00000000
ID no. C1050000
Exchange System Manager

Also, I noticed that the destination Exchange Management Console shows that I need to "Enter the Exchange Server Product Key". Could this be the problem? Is this true or should the SBS2008 product key cover Exchange?

LVL 14
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

You need to enter the Exchange product key or the Exchange Information Store will dismount after the trail period expires.  The lack of the product key will not be preventing you from re-homing public folders.  Are there any messages in the Event logs (either system or application?)

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Shreedhar EtteCommented:
Does all the databases on the Exchange 2003 are mounted?
Determine the Perfect Price for Your IT Services

Do you wonder if your IT business is truly profitable or if you should raise your prices? Learn how to calculate your overhead burden with our free interactive tool and use it to determine the right price for your IT services. Download your free eBook now!

Philip ElderTechnical Architect - HA/Compute/StorageCommented:
What methodology are you using to migrate with?

It sounds like your Exchange did not set up properly during the Migration OS install. Check the settings in your Answer File to make sure that they are correct ... there could be a typo there.

Our Migration Guide:

Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
The problem might be the fact that, in the exchange 2003 server where you have the public folder database, the database that has the system attendant mailbox and the other systems mailboxes must be pointing to the her public folder database and not to other public folder database. So if you have SBS2003 server, with PF1 (public folder database where you are moving the replicas) and with MBX1 (mailbox database on SBS2003 server that has the system mailboxes), go to MBX1 properties and see to what public folder is it pointing and if it's not to PF1 change it and try moving the replicas again.
was i clear? please check and post.
notacomputergeekAuthor Commented:
Valutus: Thanks. Here's the error in the Application Viewer:
The description for Event ID ( 9175 ) in Source ( EXAdmin ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: OpenMsgStore, The information store could not be opened.
The logon to the Microsoft Exchange Server computer failed.
MAPI 1.0
ID no: 80040111-0286-00000000.

shreedhar: Yes, they are mounted (1 mailbox and 1 Public Folder).

MPECSInc: I used the Microsoft Migration Guide. There were no errors after the SBS 2008 installation completeted and the mailbox and PF stores are both mounted on the dest. server. All seems OK.

GreatVargas: Not sure I followed you. If I click properties on the PF store, the Associated PF tree says: "first administrative group/Public Folders". Is that what you were interested in?

Does anyone know if the error message says it can't logon to the source information server or destination?

Also, I changed the administrator password before I started the migration and the answer file had the new password in it. I checked all the services and rebooted the source server to see if there were any services dependent on the administrator password and there weren't.
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
you need to go to the properties on the MAILBOX store on sbs2003 and see what public folder that maibox store is using. It must be using the public folder store on the same server. Assuming that you only have one server with exchange 2003.
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
So if you have 1 mailbox and 1 public folder on 2003 check the properties of that mailbox store. it must be associated with the public folder on the same server.
Cliff GaliherCommented:
Common misconfigurations that will cause this error:
1) Transferring of public folders is done via SMTP. If you've changed the default SMTP connectors on SBS 2003 *or* 2008, that can cause problems. The migration guide expects defaults. One specific example that I see often is when the 2003 connectors were configured to use a smarthost. They must be reconfigured to not use a smarthost (default) during this part of the migration, or they will, of course, fail since they will attempt to deliver the PF's via the smarthost instead of directly.
2) For machines that have multiple network adapters, the LAN adapters *must* be first in the adapter binding order on both machines *EVEN IF OTHER ADAPTERS ARE ALREADY DISABLED!* Binding order still matters and can really throw off Exchange if it doesn't find what it expects.
Hope that helps,
notacomputergeekAuthor Commented:
GreatVargas: The source 'Default Public Store' is pointing to the source server.

cgaliher: The source SMTP connector was set to use DNS. Part of the steps during migration had me delete the SMTP connector on the source server. The source server has 1 NIC and the destination server has 4 NICS. The cable is plugged into NIC 1.

Don't know if this makes a difference, but part of configuring SBS 2008 is to move the data folder locations. I moved all of them to the E: drive from C.
Philip ElderTechnical Architect - HA/Compute/StorageCommented:
Did you delete the SBS SMTP Connector only?

notacomputergeekAuthor Commented:
Yes and it looks like it created  a new connector SOURCE-DESTINATION. Source and Destination are actually the two server names. Under Connectors, I also have the 'POP3 Connector Manager'. The POP3 for mailboxes service has been stopped and disabled.

I haven't reconfigured the router to point to the destination server yet. From the guide: "Ensure that the following ports are open and are directed to the IP address of the Destination Server:
•      Port 25 – SMTP e-mail". I doubt this would be causing it, but I'm unable to change the router right now.
Cliff GaliherCommented:
It absolutely could be causing it. As I said, public folder migration *RELIES* on proper SMTP flow between both servers. By proper SMTP flow, I mean properly configured SMTP connectors, proper DNS lookup, proper routing. There is a reason the migration guide was written to have tasks done in the order they were.
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
It's easy to test whats cqaliher is saying. create a mailbox on the new server and test mailfow between servers sending a message from one old mailbox of the old server  to the new one. Test mail like this in both directions. Anyway i think that if the problem was mail flow, because public folder go by smtp, the queue should be filling and the error you are getting shouldnt be appearing. anyway test and post the result.
notacomputergeekAuthor Commented:
I'll try it later. Also, the source server was set up to not receive outside e-mail directly. All outside mail was delivered to the ISP and then the Exchange server used POP3 to retrieve it. There are about 15 mailboxes.
notacomputergeekAuthor Commented:
I had created a new admin account earlier on the dest server, so I logged into owa on the dest server and sent an e-mail to an existing account. I logged into owa on the source server and the e-mail was there. I replied to the e-mail and the recipient on the new server received it.

In summary, I can send e-mail back and forth between the dest and source servers.

Also, this is probably normal, but all the users mailboxes show up in the 'Recipient Configuration' section on the dest server and the mailbox type says Legacy Mailbox.

Is it possible to continue migrating everything else and come back and do Exchange later. I have to start thinking about Plan B. Is it possible to try to migrate Exchange data except the Public Folders (there isn't much in there, so it could be re-created). BTW, this is not a test environment.

Thanks for all your input so far.
Cliff GaliherCommented:
Yes, you can skip public folders, but be aware that Exchange 2003 uses public folders for shared calendar scheduling, you may have reduced functionality until you recreate/clean up some of the aftermath.
Antonio VargasMicrosoft Senior Cloud ConsultantCommented:
My advice is, create a public folder database on the destination server, and user exchange system manager on the source server to add a replica of all public folders to the destination server. for that go to the public folder hierarquie, select each of the root public folders, right click and choose to manage content. That should not give you any errors. After the replication is complete (compare the size of the EDB files on both servers, for example, to see if tis replicated) move the mailboxes to the new server and follow the migration path. after moving everything you can even remove the replicas from the old server, with the same process, and as last resort erase the PF database in source server trough adsiedit and uninstall exchange 2003,
notacomputergeekAuthor Commented:
Nothing I did got me past this error. I wasn't able to install the Exchange Product Key, since the Microsoft Licensing site was down this weekend (DOH!)

I continued with the migration and everything else seemed to run OK, except for a few things I still need to clean up. I ended up with several issues that the Migration Guide didn't even mention.

MPECSInc: Thanks for your guide. I used it periodically to double-check things.

GreatVargas: I will try your last suggestion if I feel I need to.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.