Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

Exchange 2003 permissions problem...

Posted on 2009-02-15
8
Medium Priority
?
306 Views
Last Modified: 2012-05-06
Hi there,

Since this morning all users are receiving the following error in outlook when they try and send emails:

"You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator"

the server is a SBS and I don't beleive that anyone has changed any of the folder/exchange permissions so i'm at a bit of a loss as to what's happened. Also no users are receiving inbound emails. All the appropriate exchange services are running correctly and the exchange database is mounted correctly. Also outlook web access is not sending or receiving.

Any assistance would be greatly appreciated. Thanks in advance!
0
Comment
Question by:aussiecomp
8 Comments
 
LVL 7

Expert Comment

by:manu4u
ID: 23647371
0
 
LVL 17

Expert Comment

by:Suraj
ID: 23647580
Ensured that the SendAs permission is intact on the mailbox which needs an owner
(SendAs).
· Referred - Users cannot send e-mail messages from a mobile device or from a
shared mailbox in Exchange 2000 Server and in Exchange Server 2003
<http://support.microsoft.com/kb/912918/en-us> and restarted the Information Store
service and forced the AD replication
0
 
LVL 9

Expert Comment

by:abdulzis
ID: 23647848
Run ExBPA in the Health check mode and Permissions check mode and see if it reports any critical errors or warnings such as Permission inheritance disabled, etc.
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 

Author Comment

by:aussiecomp
ID: 23655491
Thanks for your help guys but am still having the problem.

Firstly I tried manu4us solution but all the permissions were correct and this did not resolve this issue.
I could not really understand x-sams solution, none of the mailboxes are shared
I ran the exbpa tool and there were no permission errors.

Does anyone have any more ideas? thanks in advance :)
0
 

Accepted Solution

by:
aussiecomp earned 0 total points
ID: 23656422
On further investigation I discovered that that the exchange database had become corrupted.
Even through the database was mounted correctly, apparently it was having major problems. To resolve, I had to dismount the database, stop the store service, create a backup of the database and run eseutil /h to repair the database then move the database back to it's original location.
Then remounted the database and all was good. I will run a defrag after hours.

Wierd symptoms and strange that the best practices tool didn't pick up on it... anyway resolved in the end. Thanks for all your help!
0
 
LVL 3

Expert Comment

by:nskurs
ID: 23656967
Hello  aussiecomp,

You mentioned Weird symptoms and strange that the best practices tool 

The Truth is EXBPA will not check the Exchange database logical corruption. You have to enable ISINTEG (with right Switch) to check the Logical corruption of database.
Logical corruption to Exchange Server is a very common problem. It could occur due to corruption problems with Information Store, Tables, Keys, and Indexes or sometimes to whole database.
Logical database corruption is more problematic and difficult to identify than the physical database corruption. The database administrator and users are generally unaware of logical corruption incidence. Unluckily Exchange Server does not contain any in-built utility to diagnose it.

There are so many reasons due to which the logical corruption can take place
1.      Deletion of Edb.log File
2.      Write Back Cache
3.      Also with Eseutil/p which incompetent disk space
Regardless of the cause of logical database corruption, the ultimate result would be the inaccessible Exchange Server database and the loss of data.

Most of the time below error pops-up due to Permission or DB corruption issue.  What we have to look for?

The Eseutil repair mode corrects database problems at the page and Extensible Storage Engine (ESE) table levels but not at the application level.

After repairing a database using Eseutil, ISInteg should be run to repair the database at an application level.

In short, Eseutil looks at each Exchange database page and table and ensures consistency and integrity within each table. ISInteg, recommended to be run after Eseutil, repairs a database at the application level and ensures the integrity of the relationships between tables.

ISINTEG: The Information Store Integrity (ISInteg) utility can be used to perform this Exchange application-level analysis and repair.

ISINTEG is aware of the relation between database tables and records that turn them into folders and messages.

- After you run ISINTEG FIX, you will see many warnings but you can safely ignore these messages. You should only pay attention to the end of ISINTEG. There should be zero errors reported. If there is an error, run ISINTEG again.

NOTE: Always use ESEUTIL/P as last option, since its repairs and rearranges the physical pages of database. Use these tools with caution when you want to repair your information store. It is always a good idea to make a backup before you use ESEUTIL to repair your Exchange databases.

"You do not have sufficient permission to perform this operation on this object. See the folder contact or your system administrator"
0
 
LVL 17

Expert Comment

by:Suraj
ID: 23658666
If you dont mind can you share the resolution you found out for this issue ...
0

Featured Post

Transaction-level recovery for Oracle database

Veeam Explore for Oracle delivers low RTOs and RPOs with agentless transaction log backup and transaction-level recovery of Oracle databases. You can restore the database to a precise point in time, even to a specific transaction.

Question has a verified solution.

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

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.
There are literally thousands of Exchange recovery applications out there. So how do you end up picking one that’s ideal for your business & purpose? By carefully scouting the product’s features, the benefits it offers you, & reading ample reviews f…
The basic steps you have just learned will be implemented in this video. The basic steps are shown to configure an Exchange DAG in a live working Exchange Server Environment and manage the same (Exchange Server 2010 Software is used in a Windows Ser…
A short tutorial showing how to set up an email signature in Outlook on the Web (previously known as OWA). For free email signatures designs, visit https://www.mail-signatures.com/articles/signature-templates/?sts=6651 If you want to manage em…
Suggested Courses

580 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