Here's a little background.  We just installed Exchange 2013,and want to move the mailbox database from the C:\ drive to another drive; let's call this Exchange 2013 server EXC2.  We're planning on moving the mailboxes after the database is moved to a new drive.

The Exchange 2007 is still running; let's call the Exchange 2007 server, EXC1.

When attempting the Move-databasepath command on EXC2, the Exchange 2013 server, we get an error that states that the database cannot be found on exc1, the Exchange 2007 server.  That error is correct because the database is on EXC2, Exchange 2013, and not on exc1.

Even though the EMS is running on the Exchange 2013 server and says that it is connected to the 2013 server, it attempts to perform the move on the 2007 server.

Here is a clip from the EMS

The operation couldn't be performed because object 'Mailbox Database 2065386436.edb' couldn't be found on
'Exchange 2007 FQDN.
    + CategoryInfo          : NotSpecified: (:) [Move-DatabasePath], ManagementObjectNotFoundException
    + FullyQualifiedErrorId : EBBBD516,Microsoft.Exchange.Management.SystemConfigurationTasks.MoveDatabasePath
    + PSComputerName        : Exchange 2013 FQDN

Anyone seen this before where the database move attempts to move the database on another server and says the database can't be found?  And has anyone fixed it?

Thanks,
Paul

Hello,

I agree with damird's suggestion to check the path for the database 2065386436.

If there is any update, please free let me know.

If you have any feedback on our support, please click here

Yes, the Get-MailboxDatabase command returned the correct path on the database.  To get around the problem, I created a new database on the drive that we needed it to be on and deleted the default database that was installed when installing Exchange 2013.  It was a new blank database with no mailboxes in it yet so that's how I got around it.

After coming across another issue which I will probably post in another thread is the EMS on the 2013 server is making changes on the 2007 server.  When I switched over, I had a lot of spam coming in.  I went to the shell enabled the Antispam and set the settings.  It didn't help at all.  I then looked at the settings on the 2007 server, the 2007 server settings were being changed to what I was entering on the 2013 shell.

I couldn't make any changes to the 2013 antispam settings so I routed incoming mail back to the 2007 server for spam filtering temporarily until I can figure out how to make the EMS shell on the 2013 server update the 2013 server.

After running into that issue, I was guessing it was trying to move the database on the 2007 server, but couldn't locate it.  After re-reading the error message now, that's exactly what it was trying to do.  Why would it try to perform the move on the 2007 server when I'm using the shell on 2013?

Any input would be helpful.  Should I close this thread out or leave it open as the issue that I had with the database is the same issue that I had with spam filtering?  The shell on 2013 is tied to the 2007 server and can't make updates on the 2013 server.

Thanks,
Paul

Hello,

Sorry for delayed response.

In order to avoid confusion, we troubleshooting a issue per post usually. So I recommend you create a new post for your another issue.

Before you use the move-databasepath cmdlet, you need to make sure the file exists that you saved your database data.

Besides, please spefic another DC for your exchange server if there are multiple DCs in your environment to check the result.

Here is the article on move-databasepath cmdlet for your reference.

Move-DatabasePath

http://technet.microsoft.com/en-us/library/bb124742(v=exchg.150).aspx

If you have any feedback on our support, please click here