You may receive the following error events in the Application log:
Log: Application Type: ErrorEvent ID: 108Source: EXOLEDB Description: Microsoft Exchange OLEDB was unable to either create an event sink object or get necessary interface(s) from the sink class specified by ExSchema.XmlPromotion.1, HRESULT = 0x80070005.
Log: Application Type: ErrorEvent ID: 114Source: EXOLEDB Description: Microsoft...
22 September 2011
Thursday, September 22, 2011
Application Error ID: 108 and 114 Source: EXOLEDB
21 September 2011
Wednesday, September 21, 2011
Application Error ID: 1000 Source: Windows SharePoint Services 2.0
Symptoms:
The following event ID is logged (one or more times) in the Application log on the server:
Log: Application Type: ErrorEvent ID: 1000
Source: Windows SharePoint Services 2.0
Description: #50070: Unable to connect to the database DatabaseName on SQLServerComputerName. Check the database connection information and make sure that the database server is running
Cause:
This issue...
20 September 2011
Tuesday, September 20, 2011
Application Warning ID: 213 Source: LicenseService
Symptoms:
After you demote the first domain controller in a site, the following error message appears in the target server's application log:
Log: Application
Type: Warning
Event ID: 213
Source: LicenseService
Description: Replication of license information failed because the License Logging Service on server ServerName could not be contacted.
Cause:
The licensing computer for the site...
Tuesday, September 20, 2011
Application Error ID: 9646 Source: MSExchangeIS
Cause:
The Microsoft Exchange Server Analyzer Tool reads the following registry entry to determine whether the default maximum number of folder views that can be opened per MAPI session:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\MaxObjsPerMapiSession\objtFolderView or objtFolder or objtStream.
By default, Exchange Server 2003 and Exchange Server 2007...
16 September 2011
Friday, September 16, 2011
System Error ID: 10016 Source: DCOM
Cause:
The CLSID displayed in the message, tried to start the DCOM server by using the DCOM infrastructure. Based on the security ID (SID), this user does not have the necessary permissions to start the DCOM server.
Resolution:Verify that the user has the appropriate permissions to start the DCOM server.
To assign permissions:
1. Using Regedit, navigate to the following registry value: HKEY_CLASSES_ROOT\CLSID\{CLSID...