Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Unable to delete a public folder

152 views
Skip to first unread message

Robert

unread,
Dec 9, 2006, 8:48:01 PM12/9/06
to
There is a public folder that we need to delete.
---
E2k3 SP2
W2k3 SBS SP1
All updates applied.
---
When I click to delete the folder from the Folders hive in ESM I get the
following error
" The targe principal name is oncorrect.
ID no: 80090322
Exchange System Manager"

Then when I try to get properties of the folder I get the following error:
" An operation was attempted on something that is not a socket.

Facility: Win32
ID no: c0072736
Exchange System manager"

Then when I try to open other folders in the ESM Folders hive I get the same
error as the last one.

I've defragged and run Isinteg -fix -test alltests. No improvement.

Here is another twist. If I try to open the store with MFCMAPI I get an error
"MAPI spooler could not be started. Close and then restart all mail-enabled
applications.

MAPO 1.0 [000004C7]"

Error: MAPILononEX call failed!
Code: MAPI_E_CALL_FAILED == 0x80004005
Function
File E:\MFCMAPI\5.0.18\MainDlg.cpp
Line 743


NeitherExperts at exchange nore Microsoft have any information on either of
the first two errors. I don't have any way to explore the last one.

Oh, here's another thing. The folder does not exist when using ADSIEdit and
looking at the Domain hive \Microsoft Exchange System Object. In fact it
looks like several of them are missing.

TIA,

Robert

norbertnellen

unread,
Feb 16, 2007, 3:57:16 AM2/16/07
to
I think it is a problem of the rights in AD.

I have this problem on an exchange server that
is often used for testing and i rollback an image of that server very often! I have some trouble with my domain, too! OWA is working fine Mail is also OK,
Public Folder:
Same problem on my Exchange 2003 SP2 Test system!
If I try to view the system folders under Public Folders in Exchange System Manager I get the same error I tried to repair the exchange server but no effect -> the same problem appears again.
Befor the problem appears I have a big problem to start the first informationstore ( My ExOrg has two storeage groups! ) so i killed the first database completely and start with a clean one but after this the problem appears. It must be a problem of the rights! Is it possible that you have a second exchange server? If so i think the pub depends on the second exchange server? Did you use the Exchange2003-KB895949-x86.exe hotfix? All servers in your EXORG must have the same version of infostore!Did you check the AD rights in AD? Did you changed the default rights in AD for Exchange Store? Did you remove the second exchange server without completing the synchronisation of public and system folders?

EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com

0 new messages