Application Error ID: 108 and 114 Source: EXOLEDB

You may receive the following error events in the Application log:

Log: Application
Type: Error
Event ID: 108
Source: 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: Error
Event ID: 114
Source: EXOLEDB
Description: Microsoft Exchange OLEDB has disabled the event binding due to the problems in the event sink. Binding ID = {CD16762F-654A-4874-A34B-0D0046BD9B08}. You may need to contact the event sink author and get a fixed or updated copy.

Cause:

This issue may occur when the following conditions are true:

·         In the DCOM Configuration utility (Dcomcnfg.exe), the default permissions have been modified. They have been modified in the Default Access Permissions area of the Default Security tab in the DCOM Configuration utility.

·         The System account and the Interactive special group have not been explicitly added. They must be granted Allow Access permissions.

Resolution:

To resolve the problem, add the system account and the Interactive special group. Grant them Allow Access permissions. To do this, follow these steps:

1.    From the Start menu, click Run and type Dcomcnfg.exe in the Open box, and then click OK.

2.    In Component Services, click Console root, expand Component Services, expand Computers, and then click My Computer

3.    On the Action menu, click Properties

4.    Click the Default Security tab, and then click Edit Default under Default Access Permissions.

5.    Click Add to add SYSTEM and INTERACTIVE and to grant them Allow Access permissions.

6.    Click OK.

Related Articles:

·         http://support.microsoft.com/default.aspx?scid=kb;en-us;324645

·         http://www.microsoft.com/technet/support/ee/transform.aspx?ProdName=Exchange&ProdVer=6.5.6940.0&EvtID=114&EvtSrc=EXOLEDB&LCID=1033

·         http://www.eventid.net/display.asp?eventid=114&eventno=2548&source=EXOLEDB&phase=1

·         http://www.eventid.net/display.asp?eventid=108&eventno=2547&source=EXOLEDB&phase=1

Read More

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: Error
Event 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 may occur if the user account to which the Windows SharePoint Services Timer Service is configured to log on does not have permissions to the configuration database.

Resolution 1:

To resolve this issue, synchronize the Windows SharePoint Services Timer Service together with the new user account information. To do this, follow these steps:

1.    Start Windows SharePoint Services Central Administration.

2.    On the Windows SharePoint Services Central Administration page, click Configure virtual server for central administration under Server Configuration.

3.    On the Configure Administrative Virtual Server page, click Use an existing application pool, click the existing application pool that you are already using, and then click OK

Resolution 2: (work for me)

The "SharePoint Timer Service" service was running Log On As "NT AUTHORITY\NETWORK SERVICE".

This was changed to the service account to Log On As "Local System".

The problem is now gone.

Related Articles:

·         http://support.microsoft.com/kb/900498

·         http://www.eventid.net/display.asp?eventid=1000&eventno=3491&source=Windows%20SharePoint%20Services%202.0&phase=1

Read More

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 cannot be contacted by the server on which the event is generated.

Resolution:

1. Open Active Directory Sites and Services.

2. Click the site on which the server is located.

3. In the details pane, click License Site Settings.

4. On the Action menu, click Properties.

5. Under Licensing Computer, select a different site license server, and then click Change.

Related Articles:

·         http://support.microsoft.com/default.aspx?scid=kb;en-us;296681

·         http://www.eventid.net/display.asp?eventid=213&eventno=52&source=LicenseService&phase=1

Read More

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 limit the number of open folder views to 500. When a MAPI client tries to open more than 500 folder views, the following event is logged in the application event log on the Exchange Server computer that contains the client's mailbox:

Log: Application
Type: Error
Event: 9646

Source: MSExchangeIS

Description: Mapi session "/o=First Organization/ou=First Administrative Group/cn=Recipients/cn=<account name>" exceeded the maximum of <number> objects of type "<type>".

Resolution:

Open a registry editor.

Navigate to: HKLM\System\CurrentControlSet\Services\MSExchangeIS\ParametersSystem\MaxObjsPerMapiSession

Delete the objtFolderView or objtFolder or objtStream registry values.

Close the registry editor and restart the Microsoft Exchange Information Store service for the change to take effect.

Alternatively, if you want to use the objtFolderView and objtFolder and objtStream registry values, instead of deleting, adjust them.

Related Articles:

·         http://technet.microsoft.com/en-us/library/aa996193(EXCHG.80).aspx

·         http://www.eventid.net/display.asp?eventid=9646&eventno=3449&source=MSExchangeIS&phase=1

Read More

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 in the event message}
to find out friendly name of this component.

2. Go to Component Services via Start | Control Panel | Administrative Tools | Components Services. Expand the Component Services branch then expand Computers | My Computer | DCOM Config. Right-click on your CLSID represent and choose Properties. Click on the Security tab and under Launch and Activation Permissions.
- select Use Default. Click OK or
- select Customize, and then click Edit. Add the user to the permissions list, and give the user the appropriate permissions.

Related Articles:

·         http://technet.microsoft.com/en-us/library/bb643195.aspx

·         http://www.eventid.net/display.asp?eventid=10016&eventno=4718&source=DCOM&phase=1

Read More