Error 0xc1037986 during Exchange 2003 std remove

This morning I tried to remove Exchange 2003 on a server due to be decommissioned. During the removal I received a prompt for the installation media, and after I pointed it to my Exchange disk I received this error: "Setup failed while installing sub-component of Windows Active Directory schema update with error code 0xc1037986". It then asked to reboot, so I said yes. After a reboot, none of the Exchange services will start. I've noticed these in the event log:
Exchange Server component Microsoft Exchange Messaging and Collaboration Services failed.
Error: 0x8000ffff - An unexpected error occurred.
Exchange Server component Microsoft Exchange Forest Preparation failed.
Error: 0xc1037986 - Cannot find the file.
EventType exchangesetuperror, P1 6_5_6944_0, P2 remove, P3 microsoft exchange forest preparation, P4 install, P5 c1037986, P6 _null_, P7 1, P8 NIL, P9 NIL, P10 NIL.
Exchange Server component Microsoft Exchange System Management Tools failed.
Error: 0xe0070101 - An unknown error has occurred.
EventType exchangesetuperror, P1 6_5_6944_0, P2 remove, P3 microsoft exchange system management tools, P4 install, P5 e0070101, P6 _null_, P7 1, P8 NIL, P9 NIL, P10 NIL.
I thought I would reapply SP2 and try the removal again, but SP2 will not install because I can't start the Exchange services.
The error I am receiving matches up with "Microsoft Exchange Forest Preparation failed". Why would it be trying to run forestprep? Is there a course of action for this server now - it's in a very bad way!

I know this is an old thread, But I ran into this issue and discovered that the sbs 2003 r2 disks that were used for install wouldn't work for exchange2003 removal. since sbs2003 is nolonger available on technet, I downloaded and extracted the exchange 2003
iso ( no service packs). when asked for the sbs disk i pointed the wizard to D:\exchange2003disk\SETUP\I386\EXCHANGE and the wizard completed without error.
I hope this helps save someone the time it took me to dig through old boxes of disks looking for sbs2003 disks that would work
This did the trick for me also. I was using Exch2003SP2 media when I received the "Setup failed while installing sub-component of Windows Active Directory schema update with error code 0xc1037986" error, but when I re-attempted the uninstall using
Exch2003 (w/o any Service Packs) the uninstall completed successfully and prompted for a reboot. The Microsoft Error Reporting service popped up with 3 error reports that were generated during the uninstall and requested permission to send the reports
(which I did not) and I just rebooted instead as instructed. After reboot, system displayed message that some services could not be started. Checked the services and found that "Microsoft Exchange Management" and Simple Mail Transfer Protocol (SMTP)"
services were still listed and set to Automatic. Changed startup to Manual on each, rebooted again w/o incident. So the removal of Exch2003 with original media works, but is not 100% clean (no surprise there) during the uninstall cleanup. This is the
1st of 2 old Exch 2003 servers I am retiring. I suspect the 2nd one will behave similarly when we're ready to shut-down that unit also. Thanks for the pointers.

Similar Messages

Error in uninstall Exchange 2003 after Exchange 2010 migration.

Setup encountered an error while checking prerequisites for component "Microsoft Exchange": 0X80072030 (8240): There is no such object on the server. I searched about the error and most of the hit is referring to postmaster account point
to the old server and that doesn't apply to our environment.
http://support.microsoft.com/kb/283089
below is the errors from the setup log. Other users had reported this problem but didn't find any solution other than manually uninstall the last Exchange 2003 server.  The problem is I couldn't find any official KB for manually
remove legacy Exchange server from Exchange 2010 org, bb288905 or kb833396 do not provide enough information. So is my only choice is to call Microsoft Support?
thanks
[22:38:41] Entering ScConstructAddressListServiceDNAndCN
[22:38:41] Leaving ScConstructAddressListServiceDNAndCN
[22:38:41] === IGNORING PREVIOUS ERRORS === ScPRQ_ServerGroupsHaveNotBeenMovedOrRenamed (f:\titanium\admin\src\udog\excommon\prereq.cxx:8080)
           The operation has completed successfully.
[22:38:41] Entering CCompDomainPrep::ScGetEffectiveMode
[22:38:41] Leaving CCompDomainPrep::ScGetEffectiveMode
[22:38:41] Entering ScDetermineIfLocalDomainServerGroupHasAlreadyBeenACLedOnExchangeCT
[22:38:41] Using cached result for domain "/dc=org/dc=cityofwpg/dc=ad"
[22:38:41] The required permissions have already been set
[22:38:41] Leaving ScDetermineIfLocalDomainServerGroupHasAlreadyBeenACLedOnExchangeCT
[22:38:41] Attempting to create the SRS DOB [checking whether SRS is installed].
[22:38:41] Entering ScFindRoutingGroupThatContainsServer
[22:38:41] Leaving ScFindRoutingGroupThatContainsServer
[22:38:41] Entering ScPRQ_DoesNotContainLastMAPIMDBInMixedModeAG
[22:38:41] This prerequisite has PASSED -- ID:62235 --
[22:38:41] Leaving ScPRQ_DoesNotContainLastMAPIMDBInMixedModeAG
[22:38:41] ScPRQ_ServerIsNotRUSResponsibleServerInTheNonEmptyOrg (f:\titanium\admin\src\udog\excommon\prereq.cxx:3133)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41] CCompServer::ScCheckEVSPrerequisites (f:\titanium\admin\src\udog\exsetdata\components\server\compserver.cxx:1358)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41] CCompServer::ScCheckPrerequisites (f:\titanium\admin\src\udog\exsetdata\components\server\compserver.cxx:955)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41] CComExchSetupComponent::ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1598)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41] CComExchSetupComponent::ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1598)
           Error code 0X80072030 (8240): There is no such object on the server.
[22:38:41] === IGNORING PREVIOUS ERRORS === HrSetProblemOnInstallAction, while calling ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1399)
           The operation has completed successfully.
[22:38:41] Setup encountered an error while checking prerequisites for the component "Microsoft Exchange":
0X80072030 (8240): There is no such object on the server.
[22:43:09] CComBOIFacesFactory::QueryInterface (f:\titanium\admin\src\udog\bo\bofactory.cxx:54)
           Error code 0X80004002 (16386): No interface.

Did you also check for other accounts, i.e. non-postmaster?
Setup will check to make sure that there are no mailboxes homed onto this server.    This attribute homeMDB could still be set for a mailbox that has the Exchange attributes remove. Seen that before when people set attributes directly
via scripts.....
Cheers,
Rhoderick
Microsoft Senior Exchange PFE
Blog:
http://blogs.technet.com/rmilne
Twitter:   LinkedIn:
  Facebook:
  XING:
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.
Yes, I did. Nothing has MDB = the legacy server.    The error from setup log seems to suggest a different problem.

Is Exchange 2003 Uninstalled?

I recently did a migration from Exchange 2003 to 2010. Everything seems to be working. After having the 2003 server shut down for a week or two with no issues, I decided to uninstall it.
After a few issues with remaining mailboxes etc, the uninstall process via Add/Removed ran. I had one error during the uninstall but unfortunately I didn't write it down. I believe it said something the effect of an error with messaging or something.
After click past that, the uninstall proceeded. If I now go into Add/Remove, the option for MS Exchange is no longer there however some of the services are still on the server, specifically the System Attendant and Exchange Management and they were running.
I have stopped and disable all Exchange services.
So my question is - how can I be sure it has uninstalled correctly and what are the ramifications if it didn't? Everything seems to be working but I just have this feeling that something is still left out there and things weren't completely cleaned
up.
Thank you for your help.

Agree with ExchangeITPro to see if ExBPA gives any error.
If Exchange 2003 Server object is removed from AD (Under configuration partition) then I wouldn't worry about it.
Open ADSI Edit, expand Configuration, expand CN=Configuration,CN=<domain>, expand CN=Services, expand CN=Microsoft Exchange, expand CN=<Exchange organization name>, CN=Administrative Groups, cn = CN=Exchange Administrative Group (FYDIBOHF23SPDLT),
CN=Servers, If Exchange 2003 server is not listed here then Uninstaller should have uninstalled it properly...
Blog |
Get Your Exchange Powershell Tip of the Day from here

Exchange 2003 to 2010 Public folder Migration issue

I have successfully replicated our Exchange 2003 public folders to our exchange 2010 public folders using the addreplica script in exchange 2010 PS. I have moved all mailboxes to use the public folders on Exchange 2010. A couple of days ago I ran the
"moveallreplicas.ps1", and the command successfully ran and has removed all replica pointers in the exchange 2010 PF database pointing to the exchange 2003 database. In Exchange 2003 ESM, I still have the replication to all the PF databases, and
the 2k3 has not been removed, nor has the public folder instances folder count changed at all. In searching through the logs I am getting this error on the exchange 2003 event viewer for applications about every minute or less.
This is an SMTP protocol log for virtual server ID 1, connection #58254. The client at "xxx.xxx.xxx.xxx" sent a "xexch50" command, and the SMTP server responded with "504 Need to authenticate first ". The full command
sent was "xexch50 1076 2". This will probably cause the connection to fail.
The client IP indicated in the error is a Exchange 2010 server with the HUB/CAS roles loaded onto it. I am not sure if this is related or not.
I see some people have ran the move all replicas from the Exchange 2003 ESM, should I do that now? Is this even something to worry about since all my mailboxes are using the PF on 2010?
Thanks for any assistance!

I have looked at KB http://support.microsoft.com/?id=843106 and
it did not resolve the issue on the Exchange 2003 server or 2010.
Last night I put in the fix for the Event ID 36885, method three of this article http://support.microsoft.com/kb/933430/en-us,
and the errors on both servers seemed to go away, but then have started back up this morning after about seven hours of no errors. I thought the registry entry would fix the issue, and it appears it did, but not sure why it would come back like this. I may
try restarting the servers tonight, but kind of confused how this could still be an issue with the registry entry in place.

Exchange 2013 finds an old Exchange 2003 server

We have a new MS Server 2012. We are trying to install Exchange 2013
We migrated from an MS SBS Server 2003. We migrate AD over. The SBS 2003 is no longer on the network.
When I try to install Exchange 2013. I receive an error.
Error:
One or more servers in the existing organization are running Exchange 2000 Server or Exchange Server 2003. Installation can't proceed until all Exchange 2000 or Exchange 2003 are removed.
Any and all help is appreciated.

The correct supported method I believe is to ensure that you uninstall the old Exchange server from SBS as part of the migration, before you demote the SBS server and remove it from the domain, otherwise you end up with old records remaining in Active Directory.
If you still have the old SBS server available and it hasn't been demoted then have a look at the steps listed here
http://technet.microsoft.com/en-us/library/gg563804.aspx
If that's not possible the other option is to remove the old records via ADSIEdit as detailed here
https://social.technet.microsoft.com/forums/exchange/en-US/46ca107c-7ece-4da7-8aea-46b705793f37/removing-old-exchange-and-installing-a-new-one however you should be aware that while it reportedly does work this is not a supported method.

NOKIA N8 bug: CRITICAL ERROR OCCURED DURING INSTAL...

i purchased my nokia N8 2 weeks ago, I found some annoyin bug on it. The Error message is this: "CRITICAL ERROR OCCURED DURING INSTALLATION. WIDGET REMOVED" Then all my customized homescreen has gone & it changes to the default home screen. It seems like if you have a lot of widgets & some of them are are connected online, the noka n8 is feeling exhausted It crushes when it cannot cope the memory exhaustion or somehow, i don't know. Any one knows about his? It happens to me many times, specially when i scroll sideways to different homescreen. It really makes me sick. I don't know if i have to leave the way the default screen is to get rid of that crush, coz i have done many times of changing. I have been a Nokia fan but this kind of bug is really fraustating.
Solved!
Go to Solution.

It may be you have a faulty handset ? You can take it to a Nokia Care Point to have it checked out under the warranty. You could also try doing a reset and re-installing the software using Ovi suite before taking to a Care point.
Try backing up your contacts, calendar and note ONLY, dial *#7370# followed by 12345 and the phone will reset to 'out of the box'. Then use Ovi suite to re-install the latest firmware and then set up your phone and re-install any apps you want. If this doesn't work, you WILL need to visit a Care Point, and although it's a bit of a pain, it won't take as long as waiting for the phone to be repaired/replaced, worth giving it a try ?
Good Luck
If I have helped at all, a click on the White Star is always appreciated :
you can also help others by marking 'accept as solution'

Exchange 2003 Removal fails w/ Error code 0X80072030 (8240): There is no such object on the server- pls read

Dear all,
I know there are quite some threads regarding this issue. But I've been looking at all of them w/o any solution for my problem. Here we go...
I've followed all instructions for a Exchange 2003 to 2010 transition. All went fine to the point I'm trying to uninstall Exchange 2003 via Control Panel/Software/Remove. So far I did the following:
1. Move mailboxes to Exchange Server 2010 using Move Mailbox Wizard or Powershell => successfully
2. Rehome the Offline Address Book (OAB) generation server to Exchange Server 2010 => successfully
3. Rehome Public Folder Hierarchy on new Exchange Server 2010 Admin Group => successfully
4. Transfer all Public Folder Replicas to Exchange Server 2010 Public folder store => successfully
5. Delete Public and Private Information Stores from Exchange 2003 server => successfully
6. Delete Routing Group Connectors to Exchange Server 2003 => successfully
7. Delete Recipient Update Service agreements using ADSIEdit according to
http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx => successfully
8. Uninstall all Exchange 2003 servers => fails with "Error code 0X80072030 (8240): There is no such object on the server"
I used the following articles while migrating to Exchange 2010:
http://technet.microsoft.com/en-us/library/bb288905(EXCHG.80).aspx
http://support.microsoft.com/kb/833396/en-us
http://www.simple-talk.com/content/article.aspx?article=882
and several more.
I looked into these forums regarding my problem and came up with:
http://support.microsoft.com/kb/283089/en-us
http://support.microsoft.com/kb/822931
I investigated the following possible reasons:
- homeMDB attribute (no references to my Exchange 2003 anymore)
- HomeMDBBL attribute (as described here
http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/f0e3edd7-34e5-46b8-8061-1991aaffc30f) (no Information Stores available anymore as they have been successfully removed)
- msExchHomeServerName attribute (all pointing to my new Exchange 2010 server)
- the "famous" postmaster issue as described here:
http://support.microsoft.com/kb/283089/en-us (pointing to the new Exchange 2010 server)
In order to investigate all attribute related issues a utilized a VBS script resulting in an Excel sheet I was easily able to filter:
SET objRootDSE = GETOBJECT("LDAP://RootDSE")
strExportFile = "C:\temp\MyExport.xls"
strRoot = objRootDSE.GET("DefaultNamingContext")
strfilter = "(&(objectCategory=Person)(objectClass=User))"
strAttributes = "sAMAccountName,msExchHomeServerName,homeMDB,legacyExchangeDN,givenName,sn," & _
                                "initials,displayName,physicalDeliveryOfficeName," & _
                                "telephoneNumber,mail,wWWHomePage,profilePath," & _
                                "scriptPath,homeDirectory,homeDrive,title,department," & _
                                "company,manager,homePhone,pager,mobile," & _
                                "facsimileTelephoneNumber,ipphone,info," & _
                                "streetAddress,postOfficeBox,l,st,postalCode,c"
strScope = "subtree"
SET cn = CREATEOBJECT("ADODB.Connection")
SET cmd = CREATEOBJECT("ADODB.Command")
cn.Provider = "ADsDSOObject"
cn.Open "Active Directory Provider"
cmd.ActiveConnection = cn
cmd.Properties("Page Size") = 1000
cmd.commandtext = "<LDAP://" & strRoot & ">;" & strFilter & ";" & _
                                   strAttributes & ";" & strScope
SET rs = cmd.EXECUTE
SET objExcel = CREATEOBJECT("Excel.Application")
SET objWB = objExcel.Workbooks.Add
SET objSheet = objWB.Worksheets(1)
FOR i = 0 To rs.Fields.Count - 1
                objSheet.Cells(1, i + 1).Value = rs.Fields(i).Name
                objSheet.Cells(1, i + 1).Font.Bold = TRUE
NEXT
objSheet.Range("A2").CopyFromRecordset(rs)
objWB.SaveAs(strExportFile)
rs.close
cn.close
SET objSheet = NOTHING
SET objWB = NOTHING
objExcel.Quit()
SET objExcel = NOTHING
Wscript.echo "Script Finished..Please See " & strExportFile
What I did find is that all my Exchange enabled users have an legacyExchangeDN attribute that is still pointing to my Exchange 2003 organization:
e.g. "/o=First Organisation/ou=First Administrative Group/cn=Recipients/cn=Administrator"
Could this cause any problems?
Now the in depth look into my "Exchange Server Setup Progress.log":
[09:33:06] Leaving ScPRQ_DoesNotContainLastMAPIMDBInMixedModeAG
[09:33:06] ScPRQ_ServerIsNotRUSResponsibleServerInTheNonEmptyOrg (f:\titanium\admin\src\udog\excommon\prereq.cxx:3133)
           Error code 0X80072030 (8240): Ein solches Objekt ist auf dem Server nicht vorhanden.
[09:33:06] CCompServer::ScCheckEVSPrerequisites (f:\titanium\admin\src\udog\exsetdata\components\server\compserver.cxx:1358)
           Error code 0X80072030 (8240): Ein solches Objekt ist auf dem Server nicht vorhanden.
[09:33:06] CCompServer::ScCheckPrerequisites (f:\titanium\admin\src\udog\exsetdata\components\server\compserver.cxx:955)
           Error code 0X80072030 (8240): Ein solches Objekt ist auf dem Server nicht vorhanden.
[09:33:06] CComExchSetupComponent::ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1598)
           Error code 0X80072030 (8240): Ein solches Objekt ist auf dem Server nicht vorhanden.
[09:33:06] CComExchSetupComponent::ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1598)
           Error code 0X80072030 (8240): Ein solches Objekt ist auf dem Server nicht vorhanden.
[09:33:06] === IGNORING PREVIOUS ERRORS === HrSetProblemOnInstallAction, while calling ScCheckPrerequisites (f:\titanium\admin\src\udog\bo\comboifaces.cxx:1399)
           Der Vorgang wurde erfolgreich beendet.
[09:33:06] Ein Fehler ist beim Überprüfen der Voraussetzungen für die Komponente "Microsoft Exchange" durch Setup aufgetreten:
0X80072030 (8240): Ein solches Objekt ist auf dem Server nicht vorhanden.
[09:33:14] CComBOIFacesFactory::QueryInterface (f:\titanium\admin\src\udog\bo\bofactory.cxx:54)
I did search for:
- Error code 0X80072030 (8240)
- ScPRQ_ServerIsNotRUSResponsibleServerInTheNonEmptyOrg
Nothing so far. In case some more information is needed just let me know.
Any help would be greatly appreciated as I absolutely don't know how to remove my Exchange 2003. Manual removal is not an option.
Alex

I kept on searching and found something else:
http://www.outlookforums.com/threads/33038-cannot-uninstall-Exchange-2000
It says that the following groups need to be resided in the AD's default "Users" organizational unit:
- Exchange Domain Servers
- Exchange Enterprise Servers
- Exchange Services Group
Unfortunately I cannot find the "Exchange Services Group". Does that have something to do with my problem?
Furthermore I found out that the Exchange 2003 has been originally installed with SBS 2003 back in time. The SBS 2003 has then be migrated to a regular Windows Server 2003 infrastructure with 2 DCs. But there still is a load of stuff reminiscent of SBS
2003 within the AD.
Then I dug deeper into my AD using ADSIEdit. I found another attribute homeMTA that is pointing to a corresponding Exchange server. After adjusting my aforementioned VBS script a was able to look into that attribute as well. I found 2 users pointing to my old
Exchange server within their homeMTA attribute.
Furthermore I saw that when trying to uninstall Exchange 2003 there is no path to my installation anymore. It's empty:
Another issue?
Regards
Alex

Remove exchange 2003 error

good day ,
I start to remove Exchange2003 after success migration to Exchange2010 SP3 I delete the connector
w2k3-w2k10
w2k10-w2k3
I followed this link step by step:
http://technet.microsoft.com/en-us/library/gg576862%28v=exchg.141%29.aspx
I have two exchange2003 one w2k3frontend and w2k3exch
for w2k3frontend from add/Remove program is not working I did it with ADSIEdit
but for w2k3exch I get this message:
This server is the master routing routing group first routing group that contains other serveurs.Impossible uninstalling this server without first select a new master routing for this routing group or delete all servers in that group routing .
This server is the server update recipients for the domain. you can uninstall only after selecting another server update of recipients for this area.
so if this still master routing and the server update recipients for the domain so no problem if I delete from ADSIEdit .
can you please help me
Regards
e

Zikorai,
From what you are telling us, you won't be able to remove Exchange from that system using the setup program - go ahead and remove it manually, both from the server (if necessary) and from the directory (which will definitely be necessary) using the links
we have provided. Here are some good ones:
Removing Exchange 2003 from the Server:
This one is only necessary if you need to remove Exchange but still have the server operational for other purposes - for instance, if it is also a domain controller - http://blogs.msmvps.com/bradley/2011/01/28/manually-removing-exchange-2003-from-the-migration-process/
If the server isn't required for any other purposes, rebuild the operating system on it
Removing Exchange 2003 from the Directory:
Go to the "Remove the Exchange Server 2003 server from Active Directory" section of this link for how to remove Exchange 2003 from the directory:
http://support2.microsoft.com/kb/833396/en-us
One note from Ed Crowley, Exchange MVP - "Do not remove the Exchagne 2003 administrative groups unless you want free-busy problems, leave them there forever."
This should leave you with a system that has no Exchange 2003 and Exchange 2010 is running smoothly with no issues.

Remove a domain from Exchange 2003, now other domains cannot send to the old domain error 5.1.1

We have a single Exchange 2003 server. We have multiple mail domains on the server, but are slowly moving to a hosted email solution. I moved the first domain, I will call it
domainABC, to our hosted solution. I have removed all exchange mailboxes from the users, and deselected the domain from Recipient Policies. I then ran the policy.
Whenever I send an email to anyone on Domain ABC from any other domain on the Exchange server, I get the 5.1.1 message. I am not sure what to do next - any help would be appreciated...
Brian

Hi Brian,
Could you post the detail information for the NDR message?
When you migrate all the users to the host email server, did you change mx record point to the new server?
You also can use this tool to help you check for the inbound email test (for Domain ABC).
Exchange Remote Connectivity Analyzer
https://www.testexchangeconnectivity.com/
Thanks,
Evan Liu
TechNet Subscriber Support in forum
If you have any feedback on our support, please contact
[email protected]
Evan Liu
TechNet Community Support

Exchange 2003 Permissions Error when attempting to forward emails

Server 2003 R2 (fully patched as of 11/2013) running Exchange 2003 SP2 (Built 7638.x2) on ESXi 4.1; WinXP clients and Server 2003 Terminal Servers running Outlook 2003; Domain and Forest are running at 2008 Functional Levels.
Occasionally, some users are receiving this error message: "You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator" intermittently when attempting
to 1) forward email both to and from senders/recipients inside and outside the domain, 2) When attempting to modify the subject of a previously received email (I didn't know you could do that), 3) When attempting to open received attachments.
There is no discernible pattern to the users or the original senders of the emails.
Most of the results I've found when searching relate to NTFS permissions or a ReadOnly propery on items in the users's profile folder, or sending on behalf of another user - these either do not apply or have been verified as not the cause.
During the initial rash of problems when there was a problem with an attachment and we absolutely needed it, I was able to connect to OWA using a special administrative account with access to the mailbox, open the attachment and log out. Once I had
done so with this account, the end user was able to open the attachment on their own without a warning.
Changes made to the environment prior to this issue that may be related (nobody remembers when exactly this started, so I can't state that it definitively happened after this change):
All servers were virtualized on ESXi 4.1 in late 2011; subsequently converted and migrated to Hyper-V Server 2012 in early 2013 (with the exception of the Exchange and SQL servers).
All 2003/R2 domain controllers demoted and removed; DFL/FFL raised to 2008; SYSVOL replication was migrated from FRS to DFS-R.
Troubleshooting steps:
Exchange server and affected client computers have been restarted several times; the various exchange services have been restarted; permissions on the mailboxes and AD objects have been verified; event logs are generally clean with the exception of ActiveSync
errors for a single user not currently affected by forwarding emails, there are no other errors reported.
Per recommendations on another forum, I had enabled several diagnostic logs in the diagnostic logging tab of the server. Unfortunately not much was found in the Application log even after filtering out the basics. There were occasional errors
referencing User A failed to modify an item in User B's mailbox because access was denied; however, I was unable to correlate these errors to any reported incidence of the above message.
I created a new mailbox database on the same server and migrated all the mailboxes to the new database, there was no change; users immediately began seeing these errors.
Over a holiday weekend, I then spun up a new Win 2003 R2 server, with a fresh installation of Server 2003 R2 (also fully patched through 11/2013) running the same version of Exchange 2003 SP2 this time running as a virtual guest on Hyper-V Server 2012.
I migrated all mailboxes from the original mail server to the new mail server and it appeared that the problem was remedied; however, it has slowly started up again and is starting to become more frequent.
I'm really at my wits end with this problem and would like to get it resolved before we purchase and install our new Exchange Server later this year.

Updates
Users have reported that they can forward the email from OWA; even after doing so, they are unable to forward from Outlook. So either my previous notes on the issue were wrong, or this is just more of the "intermittent" nature of the problem.
I will have to investigate what logging options are available to me at the Outlook client level - any thoughts on that subject are also welcome.
Users have now reported that a previous (rarely used) workaround (the administrative account opening the email in OWA) no longer enables them to view attachments or forward emails in Outlook.
I'm still adjusting the various diagnostic logging settings to see if I can spot an event which corresponds to a reported occurrence. The most unusual warning reported is the following:
Source:MSExchangeIS Mailbox Store
Category: Access Control
Event ID: 1029
[email protected] failed an operation because the user did not have the following access rights:
'Delete' 'Read Property' 'Write Property' 'Create Message' 'View Item' 'Create Subfolder' 'Write Security Descriptor' 'Write Owner' 'Read Security Descriptor' 'Contact'
The distinguished name of the owning mailbox is /O=DOMAIN/OU=FIRST ADMINISTRATIVE GROUP/CN=RECIPIENTS/CN=USER_B. The folder ID is in the data section of this event.
However odd these occasional warnings are, they do not appears to correlate to the reported permissions issue. Everytime I've seen one of these events, I've inquired with "user_A" to see if they've recently seen the popup and in each case they have
not.

Error moving mailbox from 2003 Exchange to 2010 Exchange

Hi everyone
I am having some trouble moving a mailbox from our Exchange 2003 server and over to our Exchange 2010 server. at this point i have moved 300 users, but this one here is causing some grief. It stops at 10% Any ideas????
23/06/2012 21:35:28 [VMPRIEXCH] 'ad.DNSArrow.co.uk/Admin Accounts/RJ Admin' created move request.
23/06/2012 21:35:28 [VMPRIEXCH] 'ad.DNSArrow.co.uk/Admin Accounts/RJ Admin' allowed a large amount of data loss when moving the mailbox (250 bad items).
23/06/2012 21:35:30 [VMPRIEXCH] The Microsoft Exchange Mailbox Replication service 'VMPRIEXCH.ad.DNSArrow.co.uk' (14.2.247.1 caps:07) is examining the request.
23/06/2012 21:35:30 [VMPRIEXCH] Connected to target mailbox 'Primary (c8e0ea6b-eec7-4da0-8ea5-e031a91cc984)', database 'SHAREDMBDB', Mailbox server 'VMPRIEXCH.ad.DNSArrow.co.uk' Version 14.2 (Build 247.0).
23/06/2012 21:35:30 [VMPRIEXCH] Connected to source mailbox 'Primary (c8e0ea6b-eec7-4da0-8ea5-e031a91cc984)', database 'EX01\SG2\Mailbox Store SG2 C', Mailbox server 'ex01.ad.DNSArrow.co.uk' Version 6.0 (Build 7654.0).
23/06/2012 21:35:41 [VMPRIEXCH] Request processing started.
23/06/2012 21:35:41 [VMPRIEXCH] Mailbox signature will not be preserved for mailbox 'Primary (c8e0ea6b-eec7-4da0-8ea5-e031a91cc984)'. Outlook clients will need to restart to access the moved mailbox.
23/06/2012 21:35:41 [VMPRIEXCH] Source mailbox information before the move:
Regular Items: 189917, 5.272 GB (5,660,371,162 bytes)
Regular Deleted Items: 2491, 135 MB (141,547,842 bytes)
FAI Items: 2490, 0 B (0 bytes)
FAI Deleted Items: 0, 972 B (972 bytes)
23/06/2012 21:35:49 [VMPRIEXCH] Fatal error MapiExceptionNotFound has occurred.
Error details: MapiExceptionNotFound: Unable to GetSearchCriteria. (hr=0x8004010f, ec=-2147221233)
Diagnostic context:
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=48]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=98][latency=0]
Lid: 23226 --- ROP Parse Start ---
Lid: 27962 ROP: ropGetSearchCriteria [49]
Lid: 31418 --- ROP Parse Done ---
Lid: 45095 EMSMDB.EcDoRpcExt2 called [length=53]
Lid: 61479 EMSMDB.EcDoRpcExt2 returned [ec=0x0][length=48][latency=15]
Lid: 23226 --- ROP Parse Start ---
Lid: 27962 ROP: ropLtidFromId [67]
Lid: 17082 ROP Error: 0x8004010F
Lid: 17505
Lid: 21921 StoreEc: 0x8004010F
Lid: 31418 --- ROP Parse Done ---
Lid: 22753
Lid: 21817 ROP Failure: 0x8004010F
Lid: 30894
Lid: 24750 StoreEc: 0x8004010F
Lid: 29358
Lid: 27950 StoreEc: 0x8004010F
Lid: 29310
Lid: 23998 StoreEc: 0x8004010F
Lid: 29329
Lid: 19729 StoreEc: 0x8004010F
Lid: 23185
Lid: 25233 StoreEc: 0x8004010F
at Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, SafeExInterfaceHandle iUnknown, Exception innerException)
at Microsoft.Mapi.MapiContainer.GetSearchCriteria(Restriction& restriction, Byte[][]& entryIds, SearchState& state)
at Microsoft.Exchange.MailboxReplicationService.LocalFolder.Microsoft.Exchange.MailboxReplicationService.IFolder.GetSearchCriteria(RestrictionData& restriction, Byte[][]& entryIds, SearchState& state)
at Microsoft.Exchange.MailboxReplicationService.FolderWrapper.<>c__DisplayClass19.<Microsoft.Exchange.MailboxReplicationService.IFolder.GetSearchCriteria>b__18()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.FolderWrapper.Microsoft.Exchange.MailboxReplicationService.IFolder.GetSearchCriteria(RestrictionData& restriction, Byte[][]& entryIds, SearchState& state)
at Microsoft.Exchange.MailboxReplicationService.FolderRecWrapper.EnsureDataLoaded(IFolder folder, FolderRecDataFlags dataToLoad, ReportBadItemsDelegate reportBadItemsDelegate)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.<>c__DisplayClass4`1.<LoadFolders>b__0()
at Microsoft.Exchange.MailboxReplicationService.ExecutionContext.Execute(GenericCallDelegate operation)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.LoadFolders[TFolderRec](FolderRecDataFlags dataToLoad, PropTag[] additionalPtags, GenericCallDelegate abortDelegate, ReportBadItemsDelegate reportBadItemsDelegate)
at Microsoft.Exchange.MailboxReplicationService.MailboxWrapper.GetFolderMap[TFolderRec](FolderRecDataFlags dataToLoad, PropTag[] additionalPtags, GenericCallDelegate abortDelegate, ReportBadItemsDelegate reportBadItemsDelegate)
at Microsoft.Exchange.MailboxReplicationService.MailboxCopierBase.GetSourceFolderMap(GetFolderMapFlags flags, FolderRecDataFlags dataToLoad, GenericCallDelegate abortDelegate)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.<CreateFolderHierarchy>b__2d(MailboxMover mbxCtx)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.ForeachMailboxContext(MailboxMoverDelegate del)
at Microsoft.Exchange.MailboxReplicationService.MoveBaseJob.CreateFolderHierarchy(Object[] wiParams)
at Microsoft.Exchange.MailboxReplicationService.CommonUtils.CatchKnownExceptions(GenericCallDelegate del, FailureDelegate failureDelegate)
Error context: --------
Operation: IFolder.GetSearchCriteria
OperationSide: Source
Primary (c8e0ea6b-eec7-4da0-8ea5-e031a91cc984)
Search folder: 'MS-OLK-BGPooledSearchFolder28E6C24EFE39F845A1C7309FF139D54F', entryId [len=46, data=00000000ED492DE46CCB2941A6EFC600B0DC8ABD010062EB1CE91779304984F59E79C254E5430000033BC7BF0000], parentId [len=46, data=00000000ED492DE46CCB2941A6EFC600B0DC8ABD010062EB1CE91779304984F59E79C254E54300000015852B0000]
23/06/2012 21:35:50 [VMPRIEXCH] Removing target mailbox 'Primary (c8e0ea6b-eec7-4da0-8ea5-e031a91cc984)' due to an offline move failure.
23/06/2012 21:35:50 [VMPRIEXCH] Relinquishing job.
Regards
Ronnie
Ronnie Jorgensen | MCTS Windows Server 2008

Hi ,
Maybe we can configure BadItemLimit for it .
New-MoveRequest:
http://technet.microsoft.com/en-us/library/dd351123.aspx
More information for your reference.
Can not move Exchange 2003 mailboxes to Exchange 2010:<//span>
http://social.technet.microsoft.com/Forums/en-US/exchangesvrmigration/thread/89902f00-4b84-4f10-b909-121a81241c85/
Wendy Liu
TechNet Community Support
Hi Wendy
BadItemLimit is already set to 250 mails and with accept data loss
New-MoveRequest -Identity 'vquotes' -TargetDatabase "DB06" -BadItemLimit 250 -AcceptLargeDataLoss
So that is not the problem :)
Ronnie Jorgensen | MCTS Windows Server 2008

Removing old exchange 2003 routing groups from Exchange 2010.

I have migrated over to Exchange 2010(server2008) from Exchange 2003(SBS2003). I've also already run the uninstall for exchange 2003 on the old SBS 2003 server. The old server itself is still running but exchange has been removed and once I get this fixed
I plan to fully remove the old SBS server.
I now get event ID 5020 and 5006 throughout the day on the new server. From what I've read, this happens because the old routing group connectors still exist.
If I run Get-ExchangeServer I get
Name                Site                 ServerRole Edition     AdminDisplayVersion
SERVER                                   None
Standard    Version 6.5 (Bui...
SERVER2008          hr.local/Configur... Mailbox,... Standard    Version 14.0 (Bu...
Am I correct in assuming that the way to fix this now is to go into ADSI edit and delete records under CN=First Administrative Groups? As in delete CN=Routing Groups and CN=Servers and everything under both of those? I'd try this myself but I'm not aware
of any way to restore those records easily if I'm wrong.
Event ID 5006
Cannot find route to Mailbox Server CN=SERVER,CN=Servers,CN=first administrative group,CN=Administrative Groups,CN=HR,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hr,DC=local for store CN=Public Folder Store (SERVER),CN=First Storage Group,CN=InformationStore,CN=SERVER,CN=Servers,CN=first
administrative group,CN=Administrative Groups,CN=HR,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hr,DC=local in routing tables with timestamp 27/09/2014 1:57:43 PM. Recipients will not be routed to this store.
Event ID 5020The topology doesn't contain a route to Exchange 2000 Server or Exchange Server 2003 server.hr.local in Routing Group CN=first routing group,CN=Routing Groups,CN=first administrative group,CN=Administrative
Groups,CN=HR,CN=Microsoft Exchange,CN=Services,CN=Configuration,DC=hr,DC=local in routing tables with the timestamp 27/09/2014 1:57:43 PM.

Get-RoutingGroupConnector shows nothing. As for the servers group. It has the old server under it as shown in the image I posted above. That's actually what stops me from just deleting it because other guides have said not to delete it if an old server
is listed.
Is the SBS2003 server listed because I haven't ran DCPROMO to remove it from the network yet? I am planning to do this but was waiting till I cleaned up all the errors before transferring the 5 FMSO roles and running DCPROMO on the old server.
DCPROMO isn't related to this, no.
So you removed Exchange already? How? With setup? It should have removed the Exchange Server object then.
It is supported to remove Exchange 2003 manually if required with adsiedit:
http://support2.microsoft.com/kb/833396
Twitter!: Please Note: My Posts are provided “AS IS” without warranty of any kind, either expressed or implied.

Moving public folders from exchange 2003 to exchange 2010 error while moving replicas

Dear All,
i am in the process of migrating from Microsoft Exchange 2003 to Exchange 2010,
i am done with moving all the mailboxes 300 mailbox almost with a 1.5 TB DB with no issues
when i tried all the processes, procedures, instructions and forums to move the public folder or
to use move all replicas from Exchange 2003 to Exchange 2010 i always get errors , now when i try
to open PF Management console from the exchange 2010 server i get it but it is disconnected
then i can choose to coneect to the new server name EXCHANGE2010 with no issues
when i try to expand the default folder and system folder i get the following error.
OAB is set on the new server as default.
when i try to add replica using power shell i get this error:
WARNING: An unexpected error has occurred and a Watson dump is being generated: Object reference not set to an inst
of an object.
Object reference not set to an instance of an object.
+ CategoryInfo : NotSpecified: (:) [Get-PublicFolder], NullReferenceException
+ FullyQualifiedErrorId : System.NullReferenceException,Microsoft.Exchange.Management.MapiTasks.GetPublicFolder
following error when trying to expand PF on EXCHANGE 2010
Microsoft Corporation
Microsoft® Windows® Operating System
6.0.6000.16386
Unexpected error [0x7653450B] while executing command 'get-publicfolder -getchildren -identity '\' -server 'Exchange2010.ptdubai.com''.
Microsoft.Exchange.Configuration.MonadDataProvider.CommandExecutionException: Unexpected error [0x7653450B] while executing command 'get-publicfolder -getchildren -identity '\' -server 'Exchange2010.ptdubai.com''. ---> System.NullReferenceException: Object
reference not set to an instance of an object.
at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.GetMapiPublicFolderDatabasesIdentities(ADSystemConfigurationSession configurationSession, ADObjectId serverId, TaskErrorLoggingDelegate errorHandler)
at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.ValidateServerContainsPFDatabase(Server server, ADSystemConfigurationSession scSession, TaskErrorLoggingDelegate errorHandler)
at Microsoft.Exchange.Configuration.Tasks.MapiTaskHelper.ResolvePublicFolderServerAndUserLegacyDNs(ADSystemConfigurationSession scSession, ServerIdParameter serverIdParameter, String& serverLegacyDN, String& userLegacyDN, Fqdn& serverFQDN,
TaskErrorLoggingDelegate errorHandler)
at Microsoft.Exchange.Configuration.Tasks.GetMapiObjectTask`2.CreateSession()
at Microsoft.Exchange.Configuration.Tasks.DataAccessTask`1.InternalStateReset()
at Microsoft.Exchange.Configuration.Tasks.GetTaskBase`1.InternalStateReset()
at Microsoft.Exchange.Management.MapiTasks.GetPublicFolder.InternalStateReset()
at Microsoft.Exchange.Configuration.Tasks.Task.ProcessRecord()
at System.Management.Automation.CommandProcessor.ProcessRecord()
--- End of inner exception stack trace ---
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.ClosePipeline(MonadAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadPipelineProxy.InternalEndInvoke(IAsyncResult results)
at Microsoft.PowerShell.HostingTools.PipelineProxyBase.EndInvoke(IAsyncResult results)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadCommand.EndExecute(MonadAsyncResult asyncResult)
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataReader.Close()
at Microsoft.Exchange.Configuration.MonadDataProvider.MonadDataReader.Dispose(Boolean disposing)
at System.Data.Common.DbDataAdapter.FillInternal(DataSet dataset, DataTable[] datatables, Int32 startRecord, Int32 maxRecords, String srcTable, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable[] dataTables, Int32 startRecord, Int32 maxRecords, IDbCommand command, CommandBehavior behavior)
at System.Data.Common.DbDataAdapter.Fill(DataTable dataTable)
at Microsoft.Exchange.Management.SystemManager.DataTableLoader.Fill(RefreshRequestEventArgs e)
at Microsoft.Exchange.Management.SystemManager.DataTableLoader.OnDoRefreshWork(RefreshRequestEventArgs e)
at Microsoft.Exchange.Management.SystemManager.RefreshableComponent.worker_DoWork(Object sender, DoWorkEventArgs e)
at System.ComponentModel.BackgroundWorker.WorkerThreadStart(Object argument)
mscorlib, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.ManagementConsole, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
MMCFxCommon, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Configuration, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Xml, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Windows.Forms, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
System.Drawing, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Management.PublicFolders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Management.SystemManager, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Core, Version=3.5.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Common, Version=14.0.631.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.ManagementGUI, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.ObjectModel, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Data, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089
Microsoft.Exchange.Diagnostics, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.Data.Directory, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Drawing.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Microsoft.Exchange.ManagementGUI.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Management, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Isam.Interop, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Transport, Version=14.0.631.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.PowerShell.HostingTools, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
BPA.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
BPA.UserInterface, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.adsiis, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Interop.Migbase, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.DKM.Proxy, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.AirSync, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Approval.Applications, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.CabUtility, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Cluster.Replay, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.RedirectionModule, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.ApplicationLogic, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Mapi, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Providers, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.Storage, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.EdgeSync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.EdgeSync.DatacenterProviders, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Extensibility.Internal, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.InfoWorker.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Live.DomainServices, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MailboxReplicationService.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MessageSecurity, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.MessagingPolicies.Rules, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Net, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Rpc, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.ExSearch, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Search.Native, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Security, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.StoreProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Agent.AntiSpam.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Agent.SenderId.Core, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Logging.Search, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Sync.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Transport.Sync.Worker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.UMCommon, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.UM.UmDiagnostics.Common, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Rtc.Collaboration, Version=3.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Rtc.Media, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
MSExchangeLESearchWorker, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management.Automation, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Core.Strings, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Core.Strings.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.HelpProvider, Version=14.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
pspluginwkr, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
System.Management, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.DirectoryServices, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
System.Design, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
Accessibility, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a
MMCEx, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35
Anonymously Hosted DynamicMethods Assembly, Version=0.0.0.0, Culture=neutral, PublicKeyToken=null
Microsoft.Exchange.Data.Directory.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Data.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
Microsoft.Exchange.Configuration.ObjectModel.resources, Version=14.0.0.0, Culture=en, PublicKeyToken=31bf3856ad364e35
i will be thankful for any assistant.
PF DB is arounf 90 GB with alot of public folders and sub-folders. around 60 mail PF and too many subfolders.

First and the most important thing you need to do is, upgrade exchange 2010 to SP2 and RU5.
Exchange 2010 RTM support is long gone.
http://www.microsoft.com/en-us/download/details.aspx?id=36768
http://www.microsoft.com/en-us/download/details.aspx?id=41480
Your exchange 2010 is still in stogeage ;)
Cheers,
Gulab Prasad
Technology Consultant
Blog:
http://www.exchangeranger.com    Twitter:
  LinkedIn:
   Check out CodeTwo’s tools for Exchange admins
Note: Posts are provided “AS IS” without warranty of any kind, either expressed or implied, including but not limited to the implied warranties of merchantability and/or fitness for a particular purpose.

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!!

Oracle Application Server Provider for Microsoft Exchange 2003 Error

Hi, i´m trying to install Exchange portlet in my portal. I passed each step of this manual (http://www.oracle.com/technology/products/ias/portal/point/exchange2003/installation.html), but I get an error in the following step:
6. Test the ASP page access to the sample Exchange 2003 mailbox
When I try to access the .asp through the internet explorer I get this error:
Tipo de error:
Objeto Server, ASP 0177 (0x800401F3)
Cadena clase no válida
/exchange/test.asp, línea 13
The asp code is:
<%
Option Explicit
Dim objLogon
Dim objSession
Dim sUser
Dim sDomain
Dim sPassword
Dim sMailBox
Dim sExchangeServer
Dim lngToken
Dim msgCount
'RETRIEVE EXCHANGE CREDENTIALS FROM REQUEST
sMailBox = Request.QueryString("MBox")
sExchangeServer = Request.QueryString("ExServer")
sUser = Request.QueryString("UName")
sDomain = Request.QueryString("UDomain")
sPassword = Request.QueryString("UPwd")
If Len(Trim(sPassword)) = 0 Or Len(Trim(sMailBox)) = 0 Or _
Len(Trim(sExchangeServer)) = 0 Or Len(Trim(sUser)) = 0 Or _
Len(Trim(sDomain)) = 0 Then
Response.write "ERROR"
Else
Set objLogon = Server.CreateObject("LoginAdmin.ImpersonateUser")
lngToken = objLogon.ImpersonateToken(sUser, sPassword, sDomain)
If lngToken = 0 Then
Response.write "ERROR"
Else
Set objSession = server.CreateObject("MAPI.Session")
objSession.Logon ,,,,,,sExchangeServer & vblf & sMailBox
msgCount = objSession.Inbox.Messages.Count
'SUCCESSFUL AUTHENTICATION
Response.write "VALID"
objSession.Logoff
Set objSession = Nothing
End If
objLogon.Logoff
Set objLogon = Nothing
End If
%>
Thanks for your help,
Regards.

Hello Chino,
Have a look here
Collaboration Portlets: calendar, task, email, contact
Thanks
Neeraj Sidhaye

Error 0xc1037986 during Exchange 2003 std remove

Similar Messages

Maybe you are looking for