?
Solved

Corrupt Public folder store/Offline address book/how do I remove old exchange server info from ESM?

Posted on 2010-01-05
28
Medium Priority
?
2,266 Views
Last Modified: 2012-05-08
This problem started with seeing a bunch of Event ID 8206 and 8207's in the app event log. After seeing this: http://support.microsoft.com/default.aspx?scid=kb;en-us;905813 I took a look at the properties to see that it has my Exchange 2003 and 2007 servers listed (good, current servers) but it also has my old Exchange 2003 box listed as well that i decommissioned when I upgraded to 2007. People are still able to create and delete appointments in the public calendar, I just need to stop of the errors in the log. I also have the old Exchange 2003 information in my ESM from the decommissioned server, how do I get rid of it once and for all? I transfered all of the roles DC roles before I got rid of it, but I have a feeling there are some exchange roles that didn't get transfered and for whatever reason are just now becoming a problem.
0
Comment
Question by:j_crow1
  • 13
  • 9
  • 4
26 Comments
 
LVL 74

Expert Comment

by:Glen Knight
ID: 26182735
If the server that is offline is still in Exchange System Manager just right click on it and select delete.  This will remove all te information for that server from Exchange and Active Directory
0
 

Author Comment

by:j_crow1
ID: 26182846
I think I know my problem - When I try to view public folders in ESM(2003) it gives me the following error:

The HTTP service used by Public Folders is not available, possible causes are that Public stores are not mounted and the Information Store service is not running.

ID no: c1030af3
Exchange System Manager

I don't think the public store got transferred when I decommissioned my older exchange 2003 box. Does anyone know how to rebuild it from scratch?
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 26182873
If the public shore was not replicated and your server has been decomissioned then you will need to remove it completely and create a new one.
0
Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

 

Author Comment

by:j_crow1
ID: 26183122
It moved it to the 2007 server, on the 2007 server it was still trying to replicate to the old exchange 2003 so I changed that to the 2007. Now my 2003 that is still working is trying to send updates through a conntector, how do I remove a server from the "update" list?
0
 

Author Comment

by:j_crow1
ID: 26183150
Alright in the server properties of the old server, under the Public Folder Referrals tab, I selected  'Use Custom List' and selected my 2007 mail server so it leaves the other one alone. I will see how this works and report back.
0
 

Author Comment

by:j_crow1
ID: 26185245
still having the same problem. I finally followed: http://support.microsoft.com/kb/840182/en-us but when I try to modify that attribute it gives me the following error: The attribute cannot be modified because it is owned by the system' - anyone know how to get around this?
0
 

Author Comment

by:j_crow1
ID: 26185460
@dematzer: Is that safe to do? My Exchange 2007 box has been working beautifully for the past 5 months with no hiccups, and then all of a sudden yesterday after a reboot I started getting these errors on my 2003 box. When i try to delete the old 2003 box from ESM it gives me a big scary message saying I could loose funtionality because FREE/BUSY will begone. Should I proceed? There is no way I can get the old 2003 box up, its gone.
0
 
LVL 16

Expert Comment

by:Narayan_singh
ID: 26189515
That attribute in that Kb is backlink you will not be able to remove it directly ther is a different way to do that...i dont think you need to remove that attribute.that is basicaaly responsible for PF mailflow.

If you exchange 2007 server still trying to update no more existing Ex 2003 ....
Go to exchange management console > toolbox > PF management tool
and go to the properties of each pf and subfolder and system folder and go to replicationtab and see if that OLD server is still listed there ... if it is listed remove it just keep ur current servers there.

Do the same in Exchange 2003 as well see if old server is added in replica tab of any public folder subfolder and system folder.

You can use PFDAVadmin to remove it from bulk PF's property.

When you try to remove that server it gave u an error that you could loose FB.

Go to ESM 2003 > admin group > Folder > public folder > right click on public folder and click view system folder > go to SCHEDULE+ FREE BUSY.
There you will see a folder like "EX:/o=Organization_Name/ou=Administrative_Group_Name "
Go to properties of that folder and if you have your any current server listed in there ( which i am sure you have) You can safely remove the exchange server from ESM and if it doesnt allow from ESM then remove it from ADSIedit

Post back for any clarification.
0
 

Author Comment

by:j_crow1
ID: 26190465
Narayan: In ESM of my 2003 box, when I try to go to public folder I get the following error: The HTTP service used by Public Folders is not available, possible casuses are that Public stores are not mounted and the Information Store service is not running. ID no: c1030af3 Exchange System Manager" and the FREE/BUSY folder is never displayed.
0
 
LVL 16

Expert Comment

by:Narayan_singh
ID: 26190812
Exchange system manager, on real-exchange server- > protocols -> HTTP ->
Exchange Virtual Server -> Public -> Right click, properties -> Access -> make sure
read, write, script source access and directory browsing are checked.
Then go to authentication and make sure that Integrated Windows and Basic
Authentication are checked..

The above error is because IIS is not updated (DS2MB) dismount the PF store in Ex 2003 and then mount restart IIS services

You can even check the replica in Exchange 2007... use PFdavadmin and see the replicas its ...
since that server doesnt exist at all i there is nt any problem in removing that server.
0
 

Author Comment

by:j_crow1
ID: 26191023
Should I change the replicas of the StoreEvents, schema-root, and schema folders as well? The old server is still listed in there. Do i put BOTH current servers, or just 1?
0
 

Author Comment

by:j_crow1
ID: 26191096
(I am using PFDAVAdmin by the way)
0
 
LVL 16

Expert Comment

by:Narayan_singh
ID: 26191451
Where ever you have old server WHERE EVER remove it.
Public folder , Subfolders, system folders whereever you see it remove it or else again store will try to replicate the PF with OLD server.
0
 

Author Comment

by:j_crow1
ID: 26191958
Alright ive done all of them except SCHEDULE+FREE BUSY because when I check the replica list it says "Exception: The remote server returned an error: (404) Not Found."
0
 

Author Comment

by:j_crow1
ID: 26192275
I reset IIS and everything, but when I try to connect to my exchange 2003 box with PFDAVAdmin I get the following error:

An error occurred while trying to establish a connection to the exchange server. Be sure that port 443 (for SSL) or port 80 (for non-ssl) can be reached. If you are connection to public folders, be sure that the public store is mounted. If you are connection to mailboxes and the progress bar shows a particular mailbox, be sure that the user has at least one email address"

My users in that office (with the 2003 box) can use their public folders just fine, no problems. But OWA is showing service unavailable when you try to connect to it. I am stumped, its like my 2003 box doesnt see its own public folder.
0
 
LVL 16

Expert Comment

by:Narayan_singh
ID: 26197330
Check this

Exchange system manager, on real-exchange server- > protocols -> HTTP ->
Exchange Virtual Server -> Public -> Right click, properties -> Access -> make sure
read, write, script source access and directory browsing are checked.
Then go to authentication and make sure that Integrated Windows and Basic
Authentication are checked..
0
 

Author Comment

by:j_crow1
ID: 26202062
Fixed it - The system log was shooting a bunch of DCOM permission errors from a certain GUID so I got into component services and went to that specific GUID which happened to be the ExchangeIS service, checked the permissions, they were wipped out. I repopulated the permissions with administrators, auth users, and system and then restarted the Information Store server and all is well again. Thanks for the help.
0
 
LVL 16

Expert Comment

by:Narayan_singh
ID: 26203049
i dont think that DCOM error has got anything to do with event 8207 which is related to MSExchUpdateFB.
More over DCOm events were about MsexchangeIS had it been for SA it could be considered but not for IIS.
Those permission in GUID basiclly hamper the startup of information store.

The event 8207 was due to your old server still listed in Public folders and in system folders.and these folders were trying to replicate with ur old server which doesnt exist.

Event 8207 is never caused due to permission issue it is network issue, communication issue which is wat was happening in your case.

By the way happy to hear that your issue is resolved.
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 26203090
What are you objecting to?
0
 
LVL 16

Expert Comment

by:Narayan_singh
ID: 26207405
DCOM Error for MsexchangeIS cannot cause Free busy problem.... IS is no where related to FB. thats what i am objecting to .....

Author's last comment cannot be accepted as a solution . Thats what i am objecting to ..... delete the question rather....

0
 
LVL 16

Expert Comment

by:Narayan_singh
ID: 26208901
If you dont wanna give the points.....
0
 
LVL 74

Expert Comment

by:Glen Knight
ID: 26208947
The fact the author followed these steps and it resolved the problem indicates it could well be the cause of it.
Who are we to decide if it did or not?

From what I can tell there is nothing to award points to and the question should be closed as per the original request by the author.
0
 
LVL 16

Expert Comment

by:Narayan_singh
ID: 26209281
If it is just about closing the question close it the way you want .... but if it is about right solution or not....that cannot be the solution....

DCOM permiison on ExchangeIS is no where related to the actual problem.....FB is taken careof by SA (MADFB) is part of system attendant.....IS doesnt come in picture at all....

I thought of rasing concern just because the solution isnt the appropriate.... and you can not gurantee that ..that solution solved it....

it takes time to replicate the things .... after removing faulty PF you need to wait some time to see the result or restart the services.

0
 

Author Comment

by:j_crow1
ID: 26209303
Narayan:

exchangeIS service also is in charge of starting the public folder store, if there is no system login information to start the public store (which is what happened here) then it could absolutly cause problems with Free/Busy access. This also caused the original errors in the application log due to the caldendar events not being saved (since the Caldenar wasn't being turned on, how COULD it save events?) I stand by my request to accept my own answer as the solution. As soon as MSexchangeIS was started properly, all problems were resolved and has been wiling fine ever since.
0
 
LVL 16

Expert Comment

by:Narayan_singh
ID: 26209450
There isnt anything as "started properly"... it is either started or stopped.....

If it was permission those permission would cause not to start the IS service at all.....but in your case as stores were mounted that mean the service was started thats it... nothing beyond that....

After you mount the store.... PF store will do the replication Updation and evertyhting and if you have faulty thing there as in your case .. you bound to get the errors..

What i am trying to tell here is you trying to co-relate two irrelevant things....
0
 

Accepted Solution

by:
j_crow1 earned 0 total points
ID: 26213454
Enough with the semantics...the service started without any warnings or errors in the event logs.

Alright then we will walk through this step by step....The following is the error from the system event log:

Event Type:      Error
Event Source:      DCOM
Event Category:      None
Event ID:      10016
Date:            1/5/2010
Time:            3:24:08 PM
User:            NT AUTHORITY\SYSTEM
Computer:      EXCHANGE2003 SERVER
Description:
The application-specific permission settings do not grant Local Launch permission for the COM Server application with CLSID
{9DA0E106-86CE-11D1-8699-00C04FB98036}(MSExchangeIS)
 to the user NT AUTHORITY\SYSTEM SID (S-1-5-18).  This security permission can be modified using the Component Services administrative tool.

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

If the Public Calendar is inaccessible, it causes the original EventID's in the application log (Since the public calendar if effectively offline, no one can post to it).

I followed the following information at eventid.net:

To correct this error do the following:
1. Open Component Services, go to Computers -> My Computers -> DCOM Config.
2. Expand DCOM config until you get down to the CLSID, they appear after the named items.
3. Right click the CLSID, check the launch parameters; they will probably be set to custom and not containing any accounts.
4. Use the SID in the event log item, run it against PsGetSid, to get which account is needed.
5. Put that account in and configure the necessary requested launch permissions.

The CLSID in this case was the MSExchangeIS service on the local computer. This service is used to start the public store, without it, OWA will not work (which is what originally alerted me to the problem) and when users try to access OWA you will get a Services Unavailable error. FREE/BUSY is ALSO located in the Public Folders as well as Offline Address book which is what threw me off at first to make me think it was a replication problem to my old exchange server. When you upgrade to 2007 from a 2003 box with multiple exchange servers in your organization, 2007 takes care of they other servers and lets them know the old box is gone and not to send IS updates to it anymore by creating new routing groups.

I hope that you get the correlation now...if a service cant start, it cannot be accessible.

I hope that this helps anyone else with this funky problem. While I do appreciate your help Narayan, this ticket needs to be closed.


0

Featured Post

Hire Technology Freelancers with Gigs

Work with freelancers specializing in everything from database administration to programming, who have proven themselves as experts in their field. Hire the best, collaborate easily, pay securely, and get projects done right.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

You finally migrated Public Folders to Office 365, decommissioned the Public Folder mailbox database and since then, when you send an email from on-premise to mail-enabled Public Folders, you get the following error: "Misconfigured public folder mai…
Among the most obnoxious of Exchange errors is error 1216 – Attached Database Mismatch error of the Jet Database Engine. When faced with this error, users may have to suffer from mailbox inaccessibility and in worst situations, permanent data loss.
To show how to create a transport rule in Exchange 2013. We show this process by using the Exchange Admin Center. Log into Exchange Admin Center.: First we need to log into the Exchange Admin Center. Navigate to the Mail Flow >> Rules tab.:  To cr…
Planning to migrate your EDB file(s) to a new or an existing Outlook PST file? This video will guide you how to convert EDB file(s) to PST. Besides this, it also describes, how one can easily search any item(s) from multiple folders or mailboxes…
Suggested Courses
Course of the Month8 days, 13 hours left to enroll

621 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question