aussiecomp
asked on
Exchange 2003 permissions problem...
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!
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!
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
(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
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.
ASKER
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 :)
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 :)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
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"
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"
If you dont mind can you share the resolution you found out for this issue ...
http://support.microsoft.com/kb/839531