« November 2006 | Main | January 2007 »
December 08, 2006
'Microsoft Exchange Server' reported error (0x8004010F)
Issue
I started getting an error popup this morning while checking Exchange.
Task 'Microsoft Exchange Server' reported error (0x8004010F) : 'The operation failed. An object could not be found.'
RESOLUTION
Use this method to resolve this problem when you view Properties in the Address lists setting in Exchange System Manager:
1. In Exchange System Manager, expand the Recipients container.
2. Click the Offline Address Lists container.
3. In the right pane, right-click the offline address list object, and then click Properties.
4. On the General tab, verify that a valid address list is populated under Address lists. If a valid address list is not populated under Address lists, you must add one.
*Note The default address is the global address list.*
5. Click OK.
6. Right-click the offline address list object again, and then click Set as New Default if the offline address list object is not set.
7. If you made any changes, right-click the offline address list object again, and then click Rebuild.
Next I got a new error. OALGen encountered error 8004010f while initializing the offline address list generation process. RESOLUTION 1. Click Start, click Run, type %SystemRoot%\system32\mapisvc.inf, and then click OK. **Note The Mapisvc.inf file contains a 6603001f entry and a 6603001e entry. When you follow these steps, do not delete the 6603001e entry.** Steve Whitcomb
To resolve this problem, follow these steps:
2. Locate the [MSEMS_DSA_Admin] section.
3. Locate and then delete the following entry:
6603001f = Server_Name
Visionpace-IT
www.Visionpace-IT.com
swhitcomb@visionpaceit.com
Posted by Doug Bliss on December 8, 2006 | Permalink | Comments (6)
December 07, 2006
Exchange issues when Symantec or any anti-virus program quarantine’s the Exchange log
Exchange issues when Symantec or any anti-virus program quarantine’s the Exchange log.
From time to time I run into a issue when a anti-virus programs (usually Symantec) real time protection will quarantine the log files for Exchange. This can happen when someone forgets to set the exception for the Exchange folders for the real time scanning, but I have seen it just happen for no good reason. Here is what I do to correct the issue.
Problem:
E00.log was quarantine
E00193B.log is required for the database to mount
Run Eseutil:
Make sure you are in the exchsrvr\bin folder Type:
eseutil /p "d:\Program files\exchsrvr\mdbdata\priv.edb" | more eseutil /p "d:\Program files\exchsrvr\mdbdata\pub.edb" | more
Perform offline defrag
110% free space is required
eseutil /d "d:\Program files\exchsrvr\mdbdata\priv.edb" /t"X:\tempdfg.edb"
eseutil /d "d:\Program files\exchsrvr\mdbdata\pub.edb" /t"X:\tempdfg.edb"
X: drive there is 110% free space.
Check:
eseutil /mh "d:\Program files\exchsrvr\mdbdata\pub.edb" -> clean shutdown or dirty shutdown eseutil /mh "d:\Program files\exchsrvr\mdbdata\priv.edb" -> clean shutdown or dirty shutdown
Copy the log files to another drive
Mount the database
Dismount the database
Run Isinteg:
isinteg -s sever2 -fix -test alltests
select 1 as an option for private information store isinteg -s server2 -fix -test alltests select 2 as an option for public store
Mount the information stores and test.
Here is a KB article for the process
http://support.microsoft.com/?id=328804
Travis Davies
Sr Network Architect
Visionpace IT
URL: www.visionpaceit.com
EMAIL: tdavies@visionpaceit.com
Posted by Travis Davies on December 7, 2006 | Permalink | Comments (0)




