RSG Exchange 2007 Restore error

I have Exchange 2007 and was able to restore my database to a RSG to restore a users mailbox. This user left a few months ago and no longer has an AD account or mailbox. It has been more then 30 days so her mailbox is deleted. When I run the powershell command
to restore.
Restore-Mailbox -Identity <Username> -RSGDatabase <databasename>
I get the error that the specified mailbox "guid" does not exist on database <RSGDatabase>
I've checked the RSG database and the user is in it. How do I restore this user
I've created a new AD and Mailbox for the user

I would suggest using one of your backups and creating a recovery database and pulling the users mailbox from that recovery database.
http://www.msexchange.org/articles-tutorials/exchange-server-2007/high-availability-recovery/Working-Recovery-Storage-Groups-Exchange-2007.html

Similar Messages

Exchange 2007 Restore

Hello Everybody,
I am trying to restore Exchange 2007 database. I tried to do the soft recovery since my database was in the dirty shutdown and it ran very well since I had all the required logs but still
it is in dirty shut down. Please check below
C:\>eseutil /r E02 /l "i:\Program Files\Microsoft\Exchange Server\Mailbox\Manage
rs Storage" /s "i:\Program Files\Microsoft\Exchange Server\Mailbox\Managers Stor
age" /d "h:\Program Files\Microsoft\Exchange Server\Mailbox\Managers Storage\Man
agers Database.edb"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 08.01
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating RECOVERY mode...
Logfile base name: E02
Log files: i:\Program Files\Microsoft\Exchange Server\Mailbox\Manage
rs Storage
System files: i:\Program Files\Microsoft\Exchange Server\Mailbox\Manage
rs Storage
Database Directory: h:\Program Files\Microsoft\Exchange Server\Mailbox\Manage
rs Storage\Managers Database.edb
Performing soft recovery...
Restore Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
Operation completed successfully in 2.343 seconds.
C:\>eseutil /mh "h:\Program Files\Microsoft\Exchange Server\Mailbox\Managers Sto
rage\Managers Database.edb"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 08.01
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
Database: h:\Program Files\Microsoft\Exchange Server\Mailbox\Managers S
torage\Managers Database.edb
File Type: Database
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,12
Engine ulVersion: 0x620,12
Created ulVersion: 0x620,12
DB Signature: Create time:02/21/2012 15:01:30 Rand:683474569 Computer:
cbDbPage: 8192
dbtime: 401104910 (0x17e8600e)
State: Dirty Shutdown
Log Required: 355061-355072 (0x56af5-0x56b00)
Log Committed: 0-355073 (0x0-0x56b01)
Streaming File: No
Shadowed: Yes
Last Objid: 39159
Scrub Dbtime: 0 (0x0)
Scrub Date: 00/00/1900 00:00:00
Repair Count: 0
Repair Date: 00/00/1900 00:00:00
Old Repair Count: 0
Last Consistent: (0x5432B,74E,DD) 01/20/2015 18:23:22
Last Attach: (0x5432D,9,86) 01/20/2015 18:27:32
Last Detach: (0x0,0,0) 00/00/1900 00:00:00
Dbid: 1
Log Signature: Create time:02/21/2012 15:01:29 Rand:683467044 Computer:
OS Version: (5.2.3790 SP 2)
Previous Full Backup:
Log Gen: 354267-354281 (0x567db-0x567e9) - OSSnapshot
Mark: (0x567EA,8,16)
http://www.arabitpro.com

Yes I have read that and tried but no luck. Check the below command its without .edb
C:\>eseutil /r E02 /l "i:\Program Files\Microsoft\Exchange Server\Mailbox\Manage
rs Storage" /s "i:\Program Files\Microsoft\Exchange Server\Mailbox\Managers Stor
age" /d "h:\Program Files\Microsoft\Exchange Server\Mailbox\Managers Storage\Man
agers"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 08.01
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating RECOVERY mode...
Logfile base name: E02
Log files: i:\Program Files\Microsoft\Exchange Server\Mailbox\Manage
rs Storage
System files: i:\Program Files\Microsoft\Exchange Server\Mailbox\Manage
rs Storage
Database Directory: h:\Program Files\Microsoft\Exchange Server\Mailbox\Manage
rs Storage\Managers
Performing soft recovery...
Restore Status (% complete)
0 10 20 30 40 50 60 70 80 90 100
|----|----|----|----|----|----|----|----|----|----|
Operation completed successfully in 3.406 seconds.
C:\>eseutil /mh "h:\Program Files\Microsoft\Exchange Server\Mailbox\Managers Sto
rage\Managers Database.edb"
Extensible Storage Engine Utilities for Microsoft(R) Exchange Server
Version 08.01
Copyright (C) Microsoft Corporation. All Rights Reserved.
Initiating FILE DUMP mode...
Database: h:\Program Files\Microsoft\Exchange Server\Mailbox\Managers S
torage\Managers Database.edb
File Type: Database
Format ulMagic: 0x89abcdef
Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,12
Engine ulVersion: 0x620,12
Created ulVersion: 0x620,12
DB Signature: Create time:02/21/2012 15:01:30 Rand:683474569 Computer:
cbDbPage: 8192
dbtime: 401104910 (0x17e8600e)
State: Dirty Shutdown
Log Required: 355061-355072 (0x56af5-0x56b00)
Log Committed: 0-355073 (0x0-0x56b01)
Streaming File: No
Shadowed: Yes
Last Objid: 39159
Scrub Dbtime: 0 (0x0)
Scrub Date: 00/00/1900 00:00:00
Repair Count: 0
Repair Date: 00/00/1900 00:00:00
Old Repair Count: 0
Last Consistent: (0x5432B,74E,DD) 01/20/2015 18:23:22
Last Attach: (0x5432D,9,86) 01/20/2015 18:27:32
Last Detach: (0x0,0,0) 00/00/1900 00:00:00
Dbid: 1
Log Signature: Create time:02/21/2012 15:01:29 Rand:683467044 Computer:
OS Version: (5.2.3790 SP 2)
Previous Full Backup:
Log Gen: 354267-354281 (0x567db-0x567e9) - OSSnapshot
Mark: (0x567EA,8,16)
Mark: 02/08/2015 00:29:06
Previous Incremental Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Previous Copy Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Previous Differential Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current Full Backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
Current Shadow copy backup:
Log Gen: 0-0 (0x0-0x0)
Mark: (0x0,0,0)
Mark: 00/00/1900 00:00:00
cpgUpgrade55Format: 0
cpgUpgradeFreePages: 0
cpgUpgradeSpaceMapPages: 0
ECC Fix Success Count: none
Old ECC Fix Success Count: none
ECC Fix Error Count: none
Old ECC Fix Error Count: none
Bad Checksum Error Count: none
Old bad Checksum Error Count: none
Operation completed successfully in 0.985 seconds.
http://www.arabitpro.com

Exchange 2007 config error SITE_3

Hello to all!
I have an Exchange 2007 server, and after some update, the attached error showing up:
It's in hungarian, it says this:
"File name: ...
Error: The next configuration route can't be recognized: ..."
This problem was in the applicationHost.config file, and in the IIS7, there was a SITE_3 site, which we couldn't open.
But we swap the applicationHost.config file with an older version from
C:\inetpub\history, regarding to this site:
http://shipoint.com/2012/03/27/fixing-corrupted-applicationhost-config-file-in-iis-7/
The IIS is back to normal, there are no SITE_3 there, but in the Exchange management console, there is still the same error. I get this error too, when I wirte Get-OwaVirtualDirectory to the Management shell. Is there anyone, who saw something like this,
and had succesfully fixed it?

Hello
everyone,
thank you
for
answering,
finally
opened
with
Microsoft
support
case
and
showed
me
that
delete
servers
from
ADSEDIT.
I deleted
the
servers
that
should
not
be
and
immediately
everything
started
to
work
properly
Many
thanks to
all
for
the
help
Microsoft Certified IT Professional Server Administrator

Exchange 2007 OWA Error after installing Service Pack 3 (MSExchange OWA event 65)

Hi everyone, I have multiple servers in Exchange 2007 SP1, Windows Server 2003 SP2 64bit.
I installed SP3 and RU15 a CAS / HUB server and now I access OWA, showing the below error:
Outlook Web Access did not initialize. There has been an event for the system administrator can resolve the problem. Contact the support of the organization.
Object reference not set to an instance of an object.
Request
URL: https: // mailserver01: 443 / owa / auth / error.aspx url = https: // mailserver01 / owa / & reason = 0
Exception
Exception type: Microsoft.Exchange.Clients.Owa.Core.OwaInvalidConfigurationException
Exception message: Object reference not set to an instance of an object.
Call stack
in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager () in Microsoft.Exchange.Clients.Owa.Core.Globals.InitializeApplication () in Microsoft.Exchange.Clients.Owa.Core.Global.ExecuteApplicationStart (Object sender,
EventArgs e)
Inner Exception
Exception type: System.NullReferenceException
Exception message: Object reference not set to an instance of an object.
Call stack
in Microsoft.Exchange.Clients.Owa.Core.Configuration.CheckPublicFolders (ADSystemConfigurationSession session, ADObjectID [] pfdbIds, Boolean & allLegacy, Boolean & allLater) in Microsoft.Exchange.Clients.Owa.Core.Configuration..ctor (ADSystemConfigurationSession
session, String virtualDirectory , String WebSiteName, ADObjectID distinguishedName, Boolean isPhoneticSupportEnabled) in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.LoadConfiguration () in Microsoft.Exchange.Clients.Owa.Core.OwaConfigurationManager.CreateAndLoadConfigurationManager
In server events next event is logged
Event Type: Error
Event Source: MSExchange OWA
Event Category: ADNotifications
Event ID:. 65
Date: 12/27/2014
Time: 7:20:54
User: Not available
Team: mailserver01
Description:
There was an error loading the configuration parameters of Outlook Web Access. Virtual directory "owa". Website: "Default Web Site".
Error message:
"Object reference not set to an instance of an object."
HOW CAN I SOLVE THIS?
thank you very much
Microsoft Certified IT Professional Server Administrator

Hello
everyone,
thank you
for
answering,
finally
opened
with
Microsoft
support
case
and
showed
me
that
delete
servers
from
ADSEDIT.
I deleted
the
servers
that
should
not
be
and
immediately
everything
started
to
work
properly
Many
thanks to
all
for
the
help
Microsoft Certified IT Professional Server Administrator

Exchange 2007 attachmentpath Error

I'm attempting to work with Microsoft Exchange 2007 in Cf
8.0.1 and I'm running into some problems. I've never worked with
Exchange in Cf before. I'm able to establish a connection without
any difficulty and I can view the Inbox for example, but every time
I attempt to download an attachment I get the following error:
Exchange error Code : 501.
I'm able to see the attachment information, but if I set
attachmentPath I get the error.
I realize there was a bug about this in the initial Cf8
release (
http://www.adobe.com/support/documentation/en/coldfusion/801/cf801releasenotes.pdf)
but the update should be installed and the administrator confirms
I'm running:
Server Product ColdFusion
Version 8,0,1,196946
Edition Enterprise
Any help would be appreciated.

I've been able to bring up a legacy Exchange 2003 server and
migrate the mailbox. The same code can now work flawlessly with
attachments. Now I just have to find the place on this site to
submit a bug.

Exchange 2007 - restored (merged) Mailboxes - Problem with items in Outlook

Hey guys,
last week we had to restore and merge our Exchange Mailbox Database. We had a running Database with data until Oct 14 and merged a recent backup into the User Mailboxes.
Some mailboxes didn´t have problems, others have from then on doublicated Mails, Calendar Items, Tasks, ... even deleted/renamed folders appear now again WITH email content.
I don´t understand what happend there and if I can do something.
Hope someone could help me!
Regards

Hi,
According your post, I understand that some mailbox contain duplicate items after restore and merge mailbox.
If I misunderstand your concern, please do not hesitate to let me know.
Are you run Restore-Mailbox with AllowDuplicates parameter? Please double check in OWA.
Besides, please run below command to check the structure of mailbox folder:
MailboxFolderStatistics “identity” | Select Name,FolderSize,FolderAndSubfolderSize
If the issue only occur on Outlook client side, please run Outlook with online mode or reconfigure a new profile for testing.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Error while installing 2nd exchange 2007 on our domain

We are installing the 2nd exchange 2007 on our domain - for obvious reasons of not able to upgrage the exisitng version to SP3 RU10 - as the server crashes everytime we do an update.
So we thought we will setup a second new exchange 2007 server with all HT MB & CAS & update it fully and move the mailboxes etc.
1st Exchange Server: EXCH01
2nd Exchange Server: EXCH02
We are doing a fresh install on a fresh vmware machine
OS: Windows Server Enterprise Service Pack 2
Exchange 2007 Service Pack 1
During the hub transport installation part we ran into an error
Exchange Server component Hub Transport Role failed.
Error: Error:
Property IsProvisionedServer cannot be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. Current version of the object is 0.0 (6.5.6500.0).
Log Name: Application
Source: MSExchangeSetup
Event ID: 1002
Now I am unable to uninstall the application as well, even while uninstalling the same error is thrown.
Also, when we open the EMC on 1st exchange server we get an error saying
"Warning:
Object PGCMAIL01 has been corrupted and it is in an inconsistent state. The following validation errors have occurred:
Warning:
Cannot calculate value of property "AdminDisplayVersion": "SerialNumber property is not present.".

Hi,
According to your description, I understand that failed install second Exchange 2007 with error “Property IsProvisionedServer cannot be set on this object because it requires the object to have version 0.1 (8.0.535.0) or later. Current version of the object
is 0.0 (6.5.6500.0).”.
If I misunderstand your concern, please do not hesitate to let me know.
Which current Exchange version are you used in your environment?
I want to double confirm whether run Setup /PrepareAD and Setup /PrepareDomain to complete the prerequisite preparation. More details about Preparing Active Directory for Exchange 2007, for your reference:
https://technet.microsoft.com/en-us/library/bb288907(v=exchg.80).aspx. If not, please run it and try again.
Besides, we can use ADSIEdit to double check the version and get more clear-cut error message in Exchange Setup log.
Thanks
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Allen Wang
TechNet Community Support

Exchange 2007 database won't mount due to MapiExceptionCallFailed errors

A server is running Exchange Server 2007 SP2 on Windows Server 2008 64-bit. After a couple years of running smoothly, the Windows Application event log started filling up with several instances every minute of the following error:
MSExchangeIS (2644) First Storage Group: A bad page link (error -327) has been detected in a B-Tree (ObjectId: 5, PgnoRoot: 10) of database H:\Microsoft\Exchange Server\Mailbox\First Storage Group\Mailbox Database.edb (165296 => 3185, 817790).
Messages sent to a specific mailbox on the server started getting returned as undeliverable with the message:
#550 5.2.0 STOREDRV.Deliver: The Microsoft Exchange Information Store service reported an error. The following information should help identify the cause of this error: "MapiExceptionCallFailed..."
I assumed that the event log messages and the delivery errors were related so I ran "eseutil /d" on the database but it exited with the message, "Operation terminated with error -1605 (JET_errKeyDuplicate, Illegal duplicate key) after 76.578 seconds. Running
eseutil /mh reports the database state as clean shutdown.
The Exchange database had been backed up nightly using Windows Server 2008 Backup. I restored the latest backup of the .edb file. Unfortunately, the corruption behind the bad page link error seemingly had propagated through the backups because the restored
.edb file had the same issues.
I then attempted to create a new clean database with the goal of then transferring mailbox data from the old to the new as described in the article "Simplifying the Dial Tone Database Recovery Process in Exchange 2007" (http://blogs.technet.com/b/dhardin/archive/2009/08/25/simplifying-the-dial-tone-database-recovery-process-in-exchange-2007.aspx).
I successfully created the new storage group and database with empty instances of all mailboxes but attempts to mount the old database yield this message:
Error: Exchange is unable to mount the database that you specified. Specified database: FASTMAIL\NewStorageGroup\Mailbox Database; Error code: MapiExceptionCallFailed: Unable to mount database. (hr=0x80004005, ec=-344)
I then tried to return to the initial state of having a corrupted database but one that would at least function temporarily for all but the one broken mailbox. The idea would be to instruct individual users to run the Outlook archive command to back their
messages up locally into .pst files. Unfortunately, all attempts to mount the original .edb file yield the same MapiExceptionCallFailed error. I also tried to mount the database after deleting the transaction log files.
I searched the web for information on this error. There are some pages describing similar errors such as "hr=0x80004005, ec=2417" but I could not find any for "ec=-344". Some articles recommend running IsInteg.exe but this utility only works for databases
that are already mounted and I am unable to mount the database.
The Exchange server is running again using the empty database so that the users can at least send and receive mail. I get the sinking feeling that all hope is lost and the historical mail data that was stored on the server is gone for good. Before I face
the pitchforks of the angry mob, I figured that I would at least post an inquiry on an Exchange-related forum.
Are there any other steps I should take to try to recover the old data?

have you checked the health of the database using eseutil /mh "edbfilename.edb" ?
is the state: Clean Shutdown ?
If it is in clean shutdown state, then move the old logs, chk, .jrs files and select the option "This database can be overwritten by a restore" and mount the database.
In case if your database is not in clean shutdown state then you would need to work towards getting the database to clean shutdown using any of the following strategies based on the criteria that the database is affected with !
1. soft recovery
2. Hard Recovery
3. Hard repair
M.P.K ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your question. ~~ This
Information is provided is "AS IS" and confers NO Rights!!

Restore Exchange 2007 database backup on Exchange 2010 server

Hi,
We have a requirement to restore mailbox from 2 years old when backup taken from Exchange 2007 server. Now we are on Exchange 2010 server where backup happens. So out of 2 years 1 year backup happen from Exchange 2007 & later happen from Exchange 2010
server using Netbackup.
We have 2 Exchange 2010 mailbox server & 1 Exchange 2007 mailbox server. Mailbox to be restore currently exists on Exchange 2010 mailbox server & functional.
can someone guide me with exact steps or best practice for restoring mailbox. confused by reading over multiple posts.

Hi ,
You cannot export data to a .pst file from a mailbox that is in a recovery storage group (RSG).
Mailboxes that are in a database that has been mounted in an RSG cannot be connected to Active Directory directory service accounts. These mailboxes have to be merged into existing mailboxes, or copied to a folder in an existing mailbox.
More information:
How to Export Mailbox Data:
http://technet.microsoft.com/en-us/library/bb266964(v=exchg.80).aspx
Recovery Storage Group and PST's:<//span>
http://social.technet.microsoft.com/Forums/sa/exchangesvravailabilityandisasterrecoverylegacy/thread/f0a062fa-1ec7-4d0c-aa58-bd7356df140d
Understanding Recovery Storage Groups:
http://technet.microsoft.com/en-us/library/bb124039(v=exchg.80).aspx
Wendy Liu
TechNet Community Support

Migration from Exchange 2007 to 2013 gives error "Failed to communicate with the mailbox database'

I have been trying to migrate several databases from Exchange 2007 to Exchange 2013. The migration started successfully, and many of the mailboxes moved successfully (about 70). The remaining mailboxes, failed. Looking deeper, we found a few issues; The
two 2013 Mailbox servers were on different versions. The Server had run out of disk space, and the NIC drivers needed to be updated.
Now when we try to migrate a mailbox that had failed in the earlier batch, we get the following error:
Data migrated:
Migration rate:
Error:
MigrationTransientException: Failed to communicate with the mailbox database. --> Failed to communicate with the mailbox database. --> MapiExceptionNetworkError: Unable to make connection to the server. ‎(hr=0x80040115, ec=-2147221227)‎ Diagnostic
context:    ......    Lid: 9624    dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam:
0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server
FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[2]: Long val: 3749909585    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 45169   StoreEc: 0x824
Lid: 50544   ClientVersion: 15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 44273      Lid: 49064   dwParam: 0x1    Lid: 37288
StoreEc: 0x6AB         Lid: 49064   dwParam: 0x2    Lid: 59431   EMSMDB.EcDoConnectEx called [length=203]    Lid: 51239   EMSMDB.EcDoConnectEx exception [rpc_status=0x6D9][latency=0]
Lid: 62184      Lid: 16280   dwParam: 0x0 Msg: EEInfo: ComputerName: n/a    Lid: 8600    dwParam: 0x0 Msg: EEInfo: ProcessID: 3460    Lid: 12696   dwParam: 0x0 Msg: EEInfo:
Generation Time: 0414-04-07T16:32:03.2100000Z    Lid: 10648   dwParam: 0x0 Msg: EEInfo: Generating component: 2    Lid: 14744   dwParam: 0x0 Msg: EEInfo: Status: 1753    Lid: 9624
dwParam: 0x0 Msg: EEInfo: Detection location: 501    Lid: 13720   dwParam: 0x0 Msg: EEInfo: Flags: 0    Lid: 11672   dwParam: 0x0 Msg: EEInfo: NumberOfParameters: 4    Lid: 8856
dwParam: 0x0 Msg: EEInfo: prm[0]: Unicode string: ncacn_ip_tcp    Lid: 8856    dwParam: 0x0 Msg: EEInfo: prm[1]: Unicode string: <Server FQDN>    Lid: 12952   dwParam: 0x0 Msg: EEInfo:
prm[2]: Long val: 2767313664    Lid: 12952   dwParam: 0x0 Msg: EEInfo: prm[3]: Long val: 382312662    Lid: 59505   StoreEc: 0x824         Lid: 50544   ClientVersion:
15.0.847.32    Lid: 52080   StoreEc: 0x824         Lid: 36081      Lid: 51152      Lid: 52465   StoreEc: 0x80040115
Lid: 60065      Lid: 33777   StoreEc: 0x80040115    Lid: 59805      Lid: 52487   StoreEc: 0x80040115    Lid: 19778      Lid: 27970
StoreEc: 0x80040115    Lid: 17730      Lid: 25922   StoreEc: 0x80040115
All of the issues listed above have been corrected, and all of the databases are mounted. Users are able to send and receive mail, but I can not migrate mail using the Migration Batch utility.
The destination server is a Hyper-V Guest running Server 2012, SP1, and Exchange 2013
The Source Server is Running Exchange 2007.
I have tried doing a test move to another destination server that is also Server 2012, and Exchange 2013, and the migration also failed.
I would appreciate any help you can give me!
Thanks,
Jon

Any update if you have resolved the issue.
Not similar, but this thread can be helpful while you migrate the mailboxes from exchange 2007 to 2013. Please check :http://social.technet.microsoft.com/Forums/exchange/en-US/721f0ae4-623a-4b02-adaf-f561d86c0426/move-mailboxes-and-public-folders-from-exchange-2007-to-exchange-2013?forum=exchangesvrdeploy&prof=required

Error: The specified mailbox database [Mailbox Database Name] does not exist, when you try to export mailbox in Exchange 2007

[Symptom]
======================
In Exchange 2007, when you want to export mailbox to a .pst file, you should run the
Export-Mailbox cmdlet from a 32-bit computer that has the following installed:
The 32-bit version of the Exchange management tools
Microsoft Office Outlook 2003 SP2 or later versions
If not, you may encounter the following error message:
You check that you have these required installed, but you get the error below when you run Export-Mailbox in EMS.
“The specified mailbox database [Mailbox Database Name] does not exist.”
[Cause Analysis]
=======================================
This is because that the account you use to run Export-Mailbox cmdlet don’t have the Exchange Server Administrator role assigned.
You can check if this account has been delegated the Exchange Server Administrator role through the following path.
EMC -> Organization Configuration-> Check permissions in the result pane.
To delegate this Exchange Server Administrator role, right click on the
Organization Configuration node and choose Add Exchange Administrator,
you will see the Add Exchange Administrator window.
[More Information]
==============================
Export-Mailbox
http://technet.microsoft.com/en-gb/library/aa998579(v=exchg.80).aspx
How to Export and Import mailboxes to PST files in Exchange 2007 SP1
http://blogs.technet.com/b/exchange/archive/2007/04/13/3401913.aspx
Exchange 2007 cannot export pst files via its powershell
http://social.technet.microsoft.com/Forums/forefront/en-US/b3bc0dce-35f3-4a69-9a33-4f2a855b9f94/exchange-2007-cannot-export-pst-files-via-its-powershell?forum=exchangesvrgenerallegacy
Please click to vote if the post helps you. This can be beneficial to other community members reading the thread.

Hi,
Based on my test, if you make the user the owner of the database (rather than a user with the db_owner role), when you create a query, it creates it under the dbo schema rather than DOMAIN\username.
Steps to do so (in Management Studio):
Right click database, select Properties
Click File
Change Owner in the textbox
OK to confirm
Downside - other users under db_owner role will still have their username appended. So schemas have to be created for these users.
Jaynet Zhang
TechNet Community Support

HTTP 500 error when opening a legacy shared mailbox in OWA 2013 (Exchange 2007/2013 coexistence environment)

Hi,
Our Exchange 2013/2007 coexistence environment is set up and all is working apart from this:
Mailbox A has full permissions to Mailbox B. Mailbox A is migrated to Exchange 2013, but Mailbox B remains on Exchange 2007. If I login to Outlook Web App 2013 as Mailbox A and then "Open another mailbox..." and select Mailbox B, a new window opens
up saying "HTTP 500 Internal Server Error". The URL it is trying is :
https://webmail.ourdomain.com/owa/[email protected]/?offline=disabled
( I can open Mailbox A in Outlook 2010 and do "Open Other users's folder.." and Mailbox B opens up just fine. )
Our legacy CAS server's External and Internal URLs are set to :
https://legacy.ourdomain.com/owa
and the Exchange 2013 CAS server's External and Internal URLs are set to :
https://webmail.ourdomain.com/owa
We have FBA enabled on both the E2K7 and E2K13 OWA
In the IIS logs:
2015-03-02 16:36:50 <E2K13_IP> POST /owa/service.svc action=SubscribeToNotification&UA=0&ID=-25&AC=1&CorrelationID=c2899211-568d-4da4-a163-351a8621c9fd_142531419466924;&cafeReqId=7ffae082-a96f-42fd-85f8-bf23775ed5de; 443 ourdomain.com\MailboxA
<LoadBalancer_IP> Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0)
https://webmail.ourdomain.com/owa/#path=/mail 200 0 0 109
2015-03-02 16:36:50 <E2K13_IP> GET /owa/ offline=disabled&CorrelationID=<empty>;&cafeReqId=7c8e137f-cdb7-4449-9cb8-f36f94539244; 443 ourdomain.com\MailboxA <LoadBalancer_IP> Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0)
- 500 0 0 265
In the OWA HTTP Proxy logs:
2015-03-02T16:36:50.096Z,7c8e137f-cdb7-4449-9cb8-f36f94539244,15,0,913,7,,Owa,webmail.ourdomain.com,/owa/,,FBA,True,ourdomain.com\MailboxA,ourdomain.com,[email protected],Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2;
.NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0),<LoadBalancer_IP>,<Exchange2013ServerName>,500,,ServerNotFound,GET,,,,,ExplicitLogon-SMTP-Header,,,,0,,,,40,9,,0,7;,7,,0,7,,0,46.8643,0,,,,,,,,,1,10,0,,10,,50,50,?offline=disabled,,BeginRequest=2015-03-02T16:36:50.049Z;CorrelationID=<empty>;ProxyState-Run=None;ServerLocatorRefresh=beebf732-0f99-47a0-9f36-d266573f1510;RefreshingCacheEntry=CacheEntry(BackEndServer
<Exchange2007ServerName>.ourdomain.com~1912832083|ResourceForest |LastRefreshTime 2015-03-02T16:01:29.3265514Z|IsSourceCachedData False);ProxyState-Complete=CalculateBackEnd;EndRequest=2015-03-02T16:36:50.096Z;I32:ADS.C[<DC_Name>]=1;F:ADS.AL[<DC_Name>]=6.6401;I32:ATE.C[<DC_Name>.ourdomain.com]=1;F:ATE.AL[<DC_Name>.ourdomain.com]=0,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
The server <Exchange2013ServerName>.ourdomain.com was not found in the topology. ---> Microsoft.Exchange.Data.Storage.ServerNotFoundException: The server <Exchange2013ServerName>.ourdomain.com was not found in the topology.
at Microsoft.Exchange.Data.Storage.ServiceTopology.GetSite(String serverFullyQualifiedDomainName)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetServiceTopologyWithSites(String serverFqdn ServiceTopology
topology)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetE12ExternalUrl[ServiceType](BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.OwaProxyRequestHandler.GetE12TargetServer(BackEndServer
mailboxServer)    at Microsoft.Exchange.HttpProxy.BEServerCookieProxyRequestHandler`1.GetDownLevelClientAccessServer(AnchorMailbox anchorMailbox BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.LatencyTracker.GetLatency[T](Func`1
operationToTrack Int64& latency)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon beacon)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass3b.<OnCalculateTargetBackEndCompleted>b__3a()
--- End of inner exception stack trace ---;
Hoping that somebody can help ?
Thanks

Hi Ansev,
Thank you for your question.
By my testing, user who was migrated to Exchange 2013 cannot access mailbox on Exchange 2007 with 500 error, although user account have “Full Access Permission” to mailbox on Exchange 2007.
I suggest we migrate account which has “Full Access Permission” for other user to Exchange 2013.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Error during Exchange 2007 mailbox provisioning with IDM 8.1.1.1

Hi
We want to create Exchange 2007 mailboxes from IDM.
When we let Exchange set the SMTP address (EmailAddressPolicyEnabled=true), it works fine
But when we set the SMTP address in IDM with the attribute PrimarySmtpAddress (and EmailAddressPolicyEnabled=false) there are an error and an information in the provisioning task
Error : PowerShell:6c13f14c-3825-4064-a585-48b4756de3a3 is not a mailbox user
Information : Added exchange mailbox to the user based on the RecipientType change from: 'User' to: 'UserMailbox'
We see that the mailbox has the SMTP address set by Exchange.
After 5mn, the task ends successfully and we see that the SMTP address is the one set by the IDM attribute PrimarySmtpAddress.
We guess that this error is caused by the active directory replication delay between controllers.
Does anybody know how to solve this problem ?
Thank you

Hi Patrick
Thank you for your answer.
The cmdlet enable-mailbox can be used with the PrimarySmtpAddress option and, in this case, the EmailAddressPolicyEnabled option is automatically set to false.
Cf. the MS technet help : "The PrimarySmtpAddress parameter specifies the primary SMTP address for the mailbox. By default, the primary SMTP address is generated based on the default e-mail address policy. If you specify a primary SMTP address by using this parameter, the command sets the EmailAddressPolicyEnabled attribute of the mailbox to $false, and the e-mail addresses of this mailbox aren't automatically updated based on e-mail address policies."
I have tested this option on our Exchange 2007 environment and it works fine.
In IDM if PrimarySmtpAddress is used but not EmailAddressPolicyEnabled, there is an error : "PowerShell:The e-mail addresses for this recipient are automatically generated based on e-mail address policies. To modify the primary SMTP address for this recipient, you must disable automatic updating of e-mail addresses based on e-mail address policy”
If PrimarySmtpAddress is used and EmailAddressPolicyEnabled is set to false, then the log shows that 2 powershell commands are run by the gateway, the second immediately after the first.
Enable-Mailbox with the parameters -Identity and -Database, run with no error
Set-Mailbox with the parameters -Identity, -EmailAddressPolicyEnabled (set to FALSE) and -PrimarySmtpAddress, run with the error “…is not a mailbox user.”
After 5 mn (the retry delay) another powershell command is run :
Set-Mailbox with the parameters -Identity, -EmailAddressPolicyEnabled (set to FALSE) and -PrimarySmtpAddress, run with no error.
The solution would be that IDM, when PrimarySmtpAddress is set, runs only the command Enable-Mailbox with the parameters PrimarySmtpAddress, which set automatically EmailAddressPolicyEnabled to FALSE
Gilles

Restore Exchange 2007 SP3 to Windows 2008 R2 from Windows 2003

Perhaps I'm being dense, but I had Exchange 2007 SP3 installed on a Windows 2003 Server, and I've used "setup /mode:recoverserver" to restore it to a Windows 2008 R2 server... how do I restore the databases which I backed up with the Windows backup tool
on 2003?
I installed KB974674, the restore tool onto the 2008 R2 server but when I try and restore the backup it comes up with "this feature is no longer supported". Something I'm missing here?

These things marked as answers are not answers.
I have now thoroughly tested using setup /mode:recoverserver and it works fine going from Windows 2003 to Windows 2008 R2 with Exchange 2007 SP3, done several installations now without a problem.
"Setup /m:RecoverServer cannot be used across operating systems. A server that was originally running Windows Server 2003 can be recovered only on Windows Server 2003, and a server that was originally running Windows Server 2008 can
be recovered only on Windows Server 2008."
This appears to be wrong, unless someone can tell me why it's right (I haven't tried moving Unified Messaging yet). I've done it to 2008 R2 several times now and also in the other direction, from 2008 R2 to 2003, I can't find anything that didn't work
afterward, although I haven't really thoroughly tested OWA yet, I admit (but it does appear to be working).
I think that documentation is out-of-date as it doesn't mention R2 plus I think it was written before SP3 came out and that paragraph is just wrong.
Basically how I do it is like this:
Dismount databases from the 2003 server and copy the storage group folders to a network location or removable media.
Install the Windows 2008 R2 server using the same machine account that was being used by the 2003 server. Install the prerequisites needed for Exchange 2007 SP3 installation on 2008 R2 (note in addition to the IIS components and RPC over HTTP this
also requires the AD tools in RSAT, which I haven't found mentioned in technical documentation). Install the relevant windows updates.
Install Exchange 2007 SP3 using setup /mode:recoverserver Install the update rollup.
Copy the storage groups into the relevant folders on the new server and mount them. Migrate any relevant certificates (e.g. for ActiveSync).
Obviously then check it all over with the diagnostic tools and check it with EXBPA. The backups are obviously totally different, but really I think you should be using DPM anyway.
To me that was pretty easy to do, to be honest. About 1.5 on a scale of one to ten. Basically install it, recover it, copy over some files and mount them.
Seriously on a halfway decent server I've done it in under an hour.

Exchange 2003 sp2 to exchange 2007 sp1 upgrade error

Hi,
We had Windows 2003 DCs and Exchange 2003 servers. We migrated AD DCs to windows 2008 R2 at parent domain.
We have one parent domain and 10 child domains in remote sites .3 remote sites have been migrated to windows 2008 R2.
Now at parent domain I am trying to install exchange 2007 SP1 on a server with windows 2008 R2 SP1. I am facing certain issues:
1. When I run setup /PrepareSchema on this new exchange server , the organization check fails with error stating that : cannot find at least one DC running windows 2003 SP1 or later in DC=xyx,DC=com. This could be the result of moving DC objects in AD. Check
that at least one DC running windows server 2003 SP1 or later is located in the "Domian Controllers" OU and rerun setup".
2. When I try to install exchange server 2007 , I get the following error
Object cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported
by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Can any one shed light on this issue.
Regards
Syed
sa

You cannot install Exchange 2007 SP1 on Windows 2008 R2 SP1 as it is unsupported.
Only version of Exchange 2007 supported when OS is Windows 2008 R2 or R2 SP1 is Exchange 2007 SP3.
Where are you installing Exchange ? child or parent domain ?
2. When I try to install exchange server 2007 , I get the following error "Object
cannot be saved because its ExchangeVersion property is 0.10 (14.0.100.0), which is not supported by the current version 0.1 (8.0.535.0). You will need a later version of Exchange.".
Above error indicates that Exchange setup is trying to modify
a version of an object which might have been created when organization is prepared for Exchange 2010. don't you have exchange 2010 Servers already in your environment ?
Please give more information about your current email infrastructure
and whether if you are installing exchange on parent or child domain?
Pavan Maganti ~ ( Exchange | 2003/2007/2010/E15(2013)) ~~ Please remember to click “Vote As Helpful" if it really helps and "Mark as Answer” if it answers your question, “Unmark as Answer” if a marked post does not actually answer your
question. ~~ This Information is provided is "AS IS" and confers NO Rights!!

RSG Exchange 2007 Restore error

Similar Messages

Maybe you are looking for