1.

1 Contents
1.1

Contents........................................................................................................................ 1

1.2

Event Log Errors............................................................................................................ 3

1.2.1

Event 3, 4................................................................................................................ 3

1.2.2

Event 10.................................................................................................................. 4

1.2.3

Event 14.................................................................................................................. 5

1.2.4

Event 57.................................................................................................................. 7

1.2.5

Events 70, 521........................................................................................................ 8

1.2.6

Events 1015, 1001, and 1004...............................................................................10

1.2.7

Event 1008............................................................................................................ 12

1.2.8

Event 1501............................................................................................................ 14

1.2.9

Event 2137............................................................................................................ 15

1.2.10 Event 2138............................................................................................................ 17

1.2.11 Event 3041............................................................................................................ 18
1.2.12 Event 3759............................................................................................................ 19
1.2.13 Event 3351............................................................................................................ 20
1.2.14 Event 3355............................................................................................................ 21
1.2.15 Event 3760............................................................................................................ 22
1.2.16 Event 5187............................................................................................................ 24
1.2.17 Event 5533............................................................................................................ 25
1.2.18 Event 5538............................................................................................................ 26
1.2.19 Event 5586............................................................................................................ 27
1.2.20 Event 6143............................................................................................................ 31
1.2.21 Event 6398............................................................................................................ 32
1.2.22 Event 6481............................................................................................................ 37
1.2.23 Event 6482............................................................................................................ 38
1.2.24 Event 6644............................................................................................................ 42
1.2.25 Event 6772............................................................................................................ 43
1.2.26 Event 6801............................................................................................................ 44
1.2.27 Event 6803, 6110.................................................................................................. 45
1.2.28 Event 6857............................................................................................................ 46
1.2.29 Event 6872............................................................................................................ 47
1.2.30 Event 6875............................................................................................................ 48
1.2.31 Event 7043............................................................................................................ 49
1.2.32 Event 7363............................................................................................................ 51
1.2.33 Event 8031............................................................................................................ 52
1.2.34 Event 8059............................................................................................................ 53
1.2.35 Event 8213............................................................................................................ 55

1.2.36 Event 8088............................................................................................................ 56

1.2.37 Event 8306............................................................................................................ 57
1.2.38 Event 8311............................................................................................................ 58
1.2.39 Event 8313............................................................................................................ 59
1.2.40 Event 10016.......................................................................................................... 60
1.2.41 Event 41734.......................................................................................................... 61
1.2.42 Event 17187.......................................................................................................... 62
1.2.43 Event 18056.......................................................................................................... 63

1.2 Event Log Errors

1.2.1 Event 3, 4
Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

Please follow the following links to resolve the issue:

http://technet.microsoft.com/en-us/library/ff519520%28v=office.14%29.aspx
https://speverything.wordpress.com/2012/05/07/fim-user-profile-synchronizationservice-issue-resolved/comment-page-1/

Servers Affected

Error

GIISTGSPAPP1

COMMENTS/RECOMMENDATIONS

There are timeout settings for FIM, try to extend the certain timeouts. Please take a
backup copy of configuration files you edit. Please follow the following link to resolve
the issue:

https://social.technet.microsoft.com/forums/sharepoint/en-US/cb84fd06-ec12-41f9-ac01f8b56d2b66ff/event-id-3-source-forfront-identity-manager

The issue could be related with host TCP configuration (virtual machine in VMWare). You
can try to turn off in system registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\synattack
protect (0) and
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\EnableTC
PChimney (0) and then check for the error.

1.2.2 Event 10

Servers
Affected

Error

SharePoint01

COMMENTS/RECOMMENDATIONS

Refer to the following link to resolve the issue:

HTTP://SUPPORT2.MICROSOFT.COM/KB/2545227

1.2.3 Event 14
Servers Affected
AIHASPAPP

Error

COMMENTS/RECOMMENDATIONS

Refer to the following links to resolve this issue:

o http://www.adventuresinsharepoint.co.uk/index.php/2014/05/07/event-id-14-thestart-address-cannot-be-crawled/
o https://social.technet.microsoft.com/Forums/en-US/ce47ce64-fb71-422d-89b40096ab06f9f4/sharepoint-foundation-event-id-14-start-address-cannot-becrawled?forum=sharepointadminprevious
o http://www.expertsexchange.com/OS/Microsoft_Operating_Systems/Server/SBS_Small_Business_Ser
ver/Q_26388695.html

1.2.4 Event 57

Servers Affected

Error

SharePoint01

COMMENTS/RECOMMENDATIONS

From the error message, it seems a connection attempts when server is not ready to
process a new local connection, possibly due to overload. Firstly, please check your SQL
servers performance. Secondly, check if you have installed any third party tool (for
example antivirus tool) on your SQL server, if so, temporarily remove them, then
monitor for a while.

1.2.5 Events 70, 521

COMMENTS/RECOMMENDATIONS

Most probably the Sharepoint configuration wizard was not run after installation of an
update. Please refer to the links below for issue and its resolution if it still persists:
o https://social.technet.microsoft.com/Forums/en-US/94c5f178-f020-4d0f-ba7c11c415d0d862/manually-running-psconfig-is-required-after-installing-sharepointfoundation-2010-updates
o http://blogs.technet.com/b/sbs/archive/2011/07/06/potential-issues-afterinstalling-sharepoint-foundation-2010-sp1.aspx

1.2.6 Events 1015, 1001, and 1004

Servers
Affected
AIHASPAPP

Error

COMMENTS/RECOMMENDATIONS

These three events together indicate a permission problem on the server that can
cause problems with the User Profile Synchronization service. The NETWORK SERVICE
account needs permission to the C:\Program Files\Microsoft Office Servers\14.0\Service
folder.

1.2.7 Event 1008

Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

Please follow the following links to resolve the issue:

http://technet.microsoft.com/en-us/library/cc774913%28v=ws.10%29.aspx
http://www.techtask.com/sharepoint/troubleshooting/resolve-bits-and-wmiaprpl-errorson-sharepoint-server-2013/

The Open Procedure for service "WmiApRpl" in DLL

"C:\Windows\system32\wbem\wmiaprpl.dll" failed.
Performance data for this service will not be
available. The first four bytes (DWORD) of the Data
section contains the error code.
The Open Procedure for service "BITS" in DLL
"C:\Windows\System32\bitsperf.dll" failed.
Performance data for this service will not be
available. The first four bytes (DWORD) of the Data
section contains the error code.
The Open Procedure for service
"FIMSynchronizationService" in DLL "C:\Program
Files\Microsoft Office Servers\15.0\Synchronization
Service\Bin\mmsperf.dll" failed. Performance data
for this service will not be available. The first four
bytes (DWORD) of the Data section contains the
error code.

Follow the links below to resolve the

issue:
https://technet.microsoft.com/enus/library/cc774913(v=ws.10).aspx

http://www.techtask.com/sharepoint/tr
oubleshooting/resolve-bits-andwmiaprpl-errors-on-sharepoint-server2013/

https://social.technet.microsoft.com/Fo
rums/sqlserver/en-US/7c585ad8-4fae452b-b18b-506fc41e29e4/perfliberrors
Also, load the dlls again:
At the command prompt, type

The Open Procedure for service ".NETFramework"

in DLL "C:\Windows\system32\mscoree.dll" failed.
Performance data for this service will not be
available. The first four bytes (DWORD) of the Data
section contains the error code.

ID

lodctr /e:<DLL name> and then press

ENTER, where <DLL name> is the
name of the library

Source

Message

Resolution

1010

MicrosoftWindowsPerflib

The Collect Procedure for the

"C:\Windows\System32\winspool.drv"
service in DLL "Spooler" generated an
exception or returned an invalid
status. The performance data returned
by the counter DLL will not be
returned in the Perf Data Block. The
first four bytes (DWORD) of the Data
section contains the exception code or
status code.

All these errors should

get resolved while fixing
above errors and using
the following link:
https://social.technet.micr
osoft.com/Forums/sqlserv
er/en-US/7c585ad8-4fae452b-b18b506fc41e29e4/perfliberrors

1018

MicrosoftWindowsPerflib

Disabled performance counter data

collection for this session from the
"ASP.NET_2.0.50727" service because
the performance counter library for
that service has generated one or
more errors. The errors that forced this
action have been written to the
application event log.

1021

MicrosoftWindowsPerflib

Windows cannot open the 32-bit

extensible counter DLL
ASP.NET_2.0.50727 in a 64-bit
environment. Contact the file vendor
to obtain a 64-bit version.
Alternatively, you can open the 32-bit
extensible counter DLL by using the
32-bit version of Performance Monitor.
To use this tool, open the Windows
folder, open the Syswow64 folder, and
then start Perfmon.exe.

If the issue does not get

resolved now, we may
have to disable the
counters:
http://kx.cloudingenium.c
om/microsoft/servers/shar
epoint/sharepoint2013/sharepoint-2013error-windows-cannotopen-the-32-bitextensible-counter-dllasp-net_2-0-50727-in-a64-bit-environmentcontact-the-file-vendorto-obtain-a-64-bitversion-alternatively-youcan-open/

1.2.8 Event 1501

Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

Please follow the following links to resolve the issue:

HTTP://BLOG.SQLAUTHORITY.COM/2009/08/20/SQL-SERVER-FIX-ERROR-CANNOT-OPEN-DATABASEREQUESTED-BY-THE-LOGIN-THE-LOGIN-FAILED-LOGIN-FAILED-FOR-USER-NT-AUTHORITYNETWORK-SERVICE/

1.2.9 Event 2137

Servers Affected

Error

AIHASQL2008

COMMENTS/RECOMMENDATIONS

F: and G: drives on AIHASQL2008, which are being used to store databases data and
log files will be soon low on disk. Consider upgrading the disk size and shrinking the
database files.

Check the size of database data & log files and the free space on the server.

COMMENTS/RECOMMENDATIONS

The PSconfig utility must be run manually. Refer to the link:

http://support.microsoft.com/kb/2580174

1.2.10

Event 2138

Servers Affected

Error

SharePoint01

COMMENTS/RECOMMENDATIONS

Check the size of database data & log files and the free space on the server.

1.2.11

Event 3041

COMMENTS/RECOMMENDATIONS

The log file mentioned that Database 'SharePoint_Config' will not be backed up because it
does not have its recovery model set to Full or BulkLogged. But, in the article at
http://technet.microsoft.com/en-us/library/cc678868.aspx, Microsoft recommends that the
configuration database be set to the simple recovery model and all content databases be
set to the Full recovery model. However, this hinges on there being a disaster recovery
model in place that backs up and shrinks the content database log files at least each night.
If this is not in place, the log files will continue to grow until the server runs out of disk
space.

1.2.12

Event 3759

Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

Please follow the following links to resolve the issue:

http://technet.microsoft.com/en-in/library/ee513066%28v=office.14%29.aspx

http://blogs.technet.com/b/wbaer/archive/2009/10/06/intermittent-database-serverconnectivity-and-microsoft-sharepoint-products-and-technologies.aspx

1.2.13

Event 3351

SQL database login

for
'SharePoint_Config'
on instance
'Baboon\SS2K12'
failed. Additional
error information
from SQL Server is
included below.
Login failed for
user
'LPCORP\svccorpb
u'.

Follow the link

below to check the
permissions for the
user and grant it
correct permissions:
https://technet.micr
osoft.com/enus/library/ee513059
(v=office.14).aspx

Additional links:
http://www.expertsexchange.com/Software/Server_Software/Micros
oft_Server_Applications/Q_27758587.htmlhttps:
//msdn.microsoft.com/enus/library/jj551781(v=nav.70).aspx
http://tekrecipes.com/2014/03/19/sqldatabase-sharepoint_config-on-sql-serverinstance-not-found/

http://answers.flyppdevportal.com/categories/s
harepoint2010/sharepoint2010setup.aspx?
ID=b7ba6c51-3248-4dc2-a476-49cdd4267210
http://blog.blksthl.com/2012/04/26/login-forsharepoint_config-login-failed-for-userdomaincomputername-scom-agent/

1.2.14

Event 3355

Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

Most of the database related problems seem to be arising due to outdated version of
Sharepoint. Please update the farm to latest version by applying SP1 and cumulative
updates. Please follow the following links to resolve the issue, if you face any similar
thing while upgrading:
http://wscheema.com/blog/Lists/Posts/Post.aspx?ID=15

Please check your SQL servers performance. Secondly, check if you have installed any
third party tool (for example antivirus tool) on your SQL server, if so, temporarily
remove them, then monitor for a while

1.2.15

Event 3760

Servers Affected
AIHASPAPP

Error

COMMENTS/RECOMMENDATIONS

Refer to the following link for more details about the error:
http://technet.microsoft.com/en-us/library/ee513043(v=office.14).aspx
http://technet.microsoft.com/en-in/library/ee513043%28v=office.14%29.aspx
http://blogs.msdn.com/b/allengeorge/archive/2012/07/10/event-id-3760-is-logged-onthe-server-as-the-timer-job-is-trying-to-locate-a-non-existent-database.aspx

1.2.16

Event 5187

Servers Affected

Error

HQVMSPWEB22

COMMENTS/RECOMMENDATIONS

This error indicates that while personal site creation is enabled, it will not work because
there is not an available content database to store the site collections. Either a new
content database should be created or an existing database should be configured to
allow more site collections.

1.2.17

Event 5533

COMMENTS/RECOMMENDATIONS

This event occurs when the SharePoint Timer Job "User Profile to SharePoint Full
Synchronization" fails. The "User Profile to SharePoint Full Synchronization" job runs
every hour by default. The most common reason for this job to fail is inconsistent user
profile data between the user profile service, and the content database. This
inconsistency can occur when content databases are deleted or incorrectly moved.
Refer to the following link for resolution:
http://support.microsoft.com/kb/2771190

This can also occur when a site collection or a content database is moved from one web
application to another without running the Preparetomove command first.
Refer to the following link for resolution:
http://blogs.technet.com/b/vinitt/archive/2009/09/03/application-event-viewer-gettingfilled-with-event-id-7888-and-5553-every-one-hour.aspx

1.2.18

Event 5538

Servers Affected

Error

AIHASPAPP

COMMENTS/RECOMMENDATIONS

This error appears to indicate a problem with the blob cache. A good first step is to
clear out the cache and let it refresh. If this does not resolve the problem, additional
research would be required.

1.2.19

Event 5586

Servers Affected

Error

AIHASQL2008

COMMENTS/RECOMMENDATIONS

Increase the size of SQL Server Database. Refer to the following link for more details:
http://technet.microsoft.com/en-us/library/ee513056(v=office.14).aspx

Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

Please follow the following links/solutions to resolve the issue:

http://blog.sqlauthority.com/2009/05/21/sql-server-fix-error-provider-named-pipesprovider-error-40-could-not-open-a-connection-to-sql-server-microsoft-sql-server-error/

Turn off the Usage and Data Collection by navigating to your Central Administration >
Monitoring > Configure usage and health data collection. Uncheck both Enable usage
data collection and Enable health data collection, assuming they are checked, and click
OK. Once this is done restart the SharePoint 2010 Timer service. Then re-enable Usage
and Data Collection by checking those same items again. The error should stop
appearing in the logs now.

https://social.technet.microsoft.com/Forums/sharepoint/en-US/ddfcb44b-3321-4b369531-8e4348f44367/cannot-connect-to-the-configuration-database

COMMENTS/RECOMMENDATIONS

The event 6398 may be related to this and the problem may lie on the timer job and/or
SQL Server. Refer to the following Microsoft Library articles, it will help in determining
the correct issue and its resolution:
Event ID 6398: http://technet.microsoft.com/en-us/library/cc561011(office.12).aspx
Event ID 5586: http://technet.microsoft.com/en-us/library/cc561042(office.12).aspx

1.2.20

Event 6143

Servers Affected

Error

AIHASPAPP

COMMENTS/RECOMMENDATIONS

Refer to the following link for more details on the issue and its resolution:
http://technet.microsoft.com/en-us/library/ff519267(v=office.14).aspx

1.2.21

Event 6398

Servers Affected

Error

AIHASPAPP
AIHASPWEB

COMMENTS/RECOMMENDATIONS

Event 6398 is a generic error for timer job execution failures. There are over 2500 such
events over the last month. These should be further investigated with the aid of the
monitoring tools in SharePoint to determine where there may be problems that can be
remedied.

Servers Affected
BFH-SPFESVR01

Error

COMMENTS/RECOMMENDATIONS

The Configuration Cache needs to be rebuilt. Please follow either of the following links
to resolve the issue:
HTTP://SHAREPOINT2020.BLOGSPOT.IN/2013/10/SHAREPOINT-2013-EVENT-ID-6398-UPDATE.HTML
HTTP://SHAREPOINTCHERIE.BLOGSPOT.IN/2013/06/SHAREPOINT-2013-EVENT-ID-6398-UPDATE.HTML

COMMENTS/RECOMMENDATIONS

Refer to the link for resolution:

https://social.technet.microsoft.com/Forums/en-US/cb02f4d7-9aed-4273-8bcd95f807bf9216/critical-error-with-user-profile-synchronization-timer-job?
forum=sharepointadminprevious

Also, grant read access to the sp_admin and Network Service account to the C:\Program
Files\Microsoft Office Servers\14.0 folder.
http://www.experts-exchange.com/Software/Microsoft_Applications/Q_27513349.html

COMMENTS/RECOMMENDATIONS

Open Central Administration site; navigate to: Application Management > Web
Applications > Manage Web Applications; selected each web application and then
reviewed its General Settings in turn: Set the Enable Customer Experience
Improvement Program to No.

If this does not resolve the issue, follow the instructions on the following link:
http://technet.microsoft.com/en-in/library/ee513069(v=office.14).aspx

HTTPS://TECHNET.MICROSOFT.COM/EN-US/LIBRARY/CC561011%28OFFICE.12%29.ASPX

The Execute method of job definition

Microsoft.Office.Server.Search.Administration.Spellin
gDictionaryUpdateJobDefinition (ID 868fb523-119d42ec-8af2-d922e3702bdc) threw an exception. More
information is included below.
Failed to run flow Microsoft.ContentAlignmentFlow.
Correlation Id: 67f1e89c-d203-f0f4-f161073e5125ba70.

6398

83333

The Execute method of job definition

Microsoft.SharePoint.Administration.SPAppS
tateQueryJobDefinition (ID b5c0bb4b-476142f7-97c0-d1b874335313) threw an
exception. More information is included
below.
One or more app state queries have failed.
Fast revocation part of the Execute method
of the app upgrade/killbit timer job
definition
Microsoft.SharePoint.Administration.SPAppS
tateQueryJobDefinition failed 3 times in a
row. This failure requires on-call engineer
attention from both SharePoint and
SharePoint Store teams.

The issues is solved by Index Reset

and Full Crawl.
But the search itself is not properly
set up.
https://social.technet.microsoft.com/F
orums/sharepoint/en-US/8141a5a5b4c9-44e5-926bacfc6b30e897/sharepoint-searchadministration-exceptions-in-eventlog?forum=sharepointadmin

The cause could be the Customer

Experience Improvement Program
(CEIP) failing to contact the CEIP
servers.
1. Go to the SharePoint Central
Administration
2. Click Monitoring
3. Then click Review job definitions in
the Timer Jobs section
4. Find the "CEIP Data Collection
(Customer Experience Improvement
Program)" timer job.
5. Click the job and click Disable
https://sarfrazahmed.wordpress.com/
2015/01/04/event-viewer-id-6398the-execute-method-of-job-definitionmicrosoft-sharepoint-administrationspappstatequeryjobdefinition-idguid-threw-an-exception-moreinformation-is-included-below/

1.2.22

Event 6481

Servers Affected

Error

AIHASPAPP
AIHASPWEB

COMMENTS/RECOMMENDATIONS

Refer to the following links for more details on this error:

o http://h10025.www1.hp.com/ewfrf/wc/document?
docname=c01931790&cc=ca&dlc=en&lc=es
o http://support.microsoft.com/kb/939308

1.2.23

Event 6482

Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

Please follow either of the following links to resolve the issue:

HTTP://WWW.SOCIAL-POINT.COM/SHAREPOINT-2010-EVENT-ID-6482-APPLICATION-SERVERADMINISTRATION-JOB-FAILED-FOR-SERVICE-INSTANCE-MICROSOFT-OFFICE-SERVER-SEARCHADMINISTRATION-SEARCHSERVICEINSTANCE
HTTP://BLOGS.MSDN.COM/B/BKR_SHAREPOINT/ARCHIVE/2014/06/09/SHAREPOINT-2013-SEARCHTOPOLOGY-ACTIVATION-ERROR-QUOT-UNABLE-TO-RETRIEVE-TOPOLOGY-COMPONENT-HEALTH-STATES-THISMAY-BE-BECAUSE-OF-THE-ADMIN-COMPONENT-IS-NOT-UP-AND-RUNNING-QUOT.ASPX

COMMENTS/RECOMMENDATIONS

Refer to the following link for resolution

https://social.technet.microsoft.com/Forums/sharepoint/en-US/a389456d-25cf-46f0a1df-09d7f3103ad4/event-id-6482-and-6398

COMMENTS/RECOMMENDATIONS

Keep monitoring the search for your site. If it does not work fine, then we may have to
recreate it.

Application Server Administration job failed for service

instance
Microsoft.Office.Server.Search.Administration.SearchSe
rviceInstance (25e4f5d3-e394-4d20-9c39fd1b11c4e16c).

Please follow either of the

following links to resolve the issue:
http://sharepoint.stackexchange.co
m/questions/125263/applicationserver-administration-job-failed-forservice-instance-microsoft-offi

Reason: I/O error occurred.

Technical Support Details:
System.IO.IOException: I/O error occurred.
at
Microsoft.Office.Server.Search.Administration.SearchSe
rviceInstance.Synchronize()
at
Microsoft.Office.Server.Administration.ApplicationServe
rJob.ProvisionLocalSharedServiceInstances(Boolean
isAdministrationServiceJob)

http://www.socialpoint.com/SHAREPOINT-2010EVENT-ID-6482-APPLICATIONSERVER-ADMINISTRATION-JOBFAILED-FOR-SERVICE-INSTANCEMICROSOFT-OFFICE-SERVERSEARCH-ADMINISTRATIONSEARCHSERVICEINSTANCE
https://latenightsp.wordpress.com/
2011/03/16/sharepoint-configcache/

1.2.24

Event 6644

Servers Affected

Error

HQVMSPWEB20
HQVMSPWEB22

COMMENTS/RECOMMENDATIONS

It appears that Analysis Services may not be installed correctly. This should be further
reviewed.

1.2.25

Event 6772

Servers Affected

Error

AIHASPAPP
AIHASQL2008

COMMENTS/RECOMMENDATIONS

This error is benign and may be safely ignored. Refer to link

http://support.microsoft.com/kb/2483007

This issue can also appear when the hard disks do not have empty space, which is not
the case with your farm.

COMMENTS/RECOMMENDATIONS

Truncate the database transaction logs and it will get fixed.

1.2.26

Event 6801

Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

Please follow the following links to resolve the issue:

http://sharepoint.stackexchange.com/questions/58575/fim-throwing-massive-errors-onad-synchronization
http://support.microsoft.com/kb/2520394
http://support.microsoft.com/kb/2536599?wa=wsignin1.0

1.2.27

Event 6803, 6110

Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

Please follow the following links to resolve the issue:

http://blogs.technet.com/b/sharepoint_me_in_the_right_direction/archive/2014/01/14/sh
arepoint-2013-profile-pictures-no-longer-display-in-mysites-after-moving-mysite-url-orchanging-web-applications.aspx

1.2.28

Event 6857

Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

Please follow the following links to resolve the issue:

http://technet.microsoft.com/en-us/library/cc560961%28v=office.12%29.aspx
http://www.expertsexchange.com/Software/Server_Software/Email_Servers/Exchange/Q_26702237.html

1.2.29

Event 6872

Servers Affected

Error

AIHASPAPP
AIHASPWEB

COMMENTS/RECOMMENDATIONS

This error is indicating that the SMTP email drop folder is not configured on the server.
This is needed in order for incoming email to SharePoint to work.

1.2.30

Event 6875

COMMENTS/RECOMMENDATIONS

Did you deploy some code using a solution package? If so? Are there any errors
reported in the solution managed for this particular package? Please verify that the
actual DLL of your event receiver successfully got installed on each server. You should
see it on the GAC of each one. Given the error, it seems like it can't find the DLL on
your server.

1.2.31

Event 7043

Servers Affected

Error

AIHASPAPP
AIHASPWEB

COMMENTS/RECOMMENDATIONS

This Taxonomy Picker control error can be safely ignored.

Servers Affected
HQVMSPWEB20
HQVMSPWEB22

COMMENTS/RECOMMENDATIONS

Error


NWLOnlineComponents.ascx is a control deployed by Nintex Workflow. This appears to
indicate a problem with that products configuration with the web application. Further
research is required to determine if Nintex is aware of this issue and if they have a fix
available.

1.2.32

Event 7363

Servers
Affected

Error

AIHASPAPP

COMMENTS/RECOMMENDATIONS

Refer to the following links to resolve this issue:

o http://jantjesworld.blogspot.com/2012/04/event-id-7363-sharepoint-2010.html
o http://www.sharepointchick.com/archive/2010/10/06/resolving-the-super-useraccount-utilized-by-the-cache-is.aspx

1.2.33

Event 8031

Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

Please follow the following links to resolve the issue:

http://www.sharepointtechs.com/sharepoint-2010-event-id-8031-the-uri-endpointinformation-may-be-stale

1.2.34

Event 8059

Servers
Affected
AIHASPAPP

Error

COMMENTS/RECOMMENDATIONS

Event 8059 is a generic error for alternate access mapping issues. It appears that
users are using the URL http://webportal.aiha.org, https://fanqiangti.appspot.com/ to
access the Sharepoint dev.sp2010.admin.aiha.org80 web application. If this is a valid
URL for the site, then it should be added as an alternate access mapping.

1.2.35

Event 8213

Servers Affected

Error

SharePoint01

COMMENTS/RECOMMENDATIONS

Refer to the following links to resolve the issue:

HTTP://WWW.NO-DUMPING.COM/2011/01/24/SHAREPOINT-ERROR-EVENT-ID-8213/
HTTP://ANDRET503.WORDPRESS.COM/2012/03/01/VOLUME-SHADOW-COPY-SERVICE-ERROR/

1.2.36

Event 8088

Servers
Affected

Error

AIHASPAPP

COMMENTS/RECOMMENDATIONS

Refer to the following link to resolve the issue: http://technet.microsoft.com/enus/library/ff383250(v=office.14).aspx

1.2.37

Event 8306

Servers
Affected

Error

AIHASPAPP

COMMENTS/RECOMMENDATIONS

Restart the app pool for security Token Services on the server which is affected and
check the logs again. Refer to the following links for more information on
troubleshooting and resolving the issue:
o http://blogs.technet.com/b/sykhad-msft/archive/2012/02/25/sharepoint-2010nailing-the-error-quot-the-security-token-service-is-unavailable-quot.aspx
o http://underthehood.ironworks.com/2011/05/sharepoint-2010-an-exceptionoccurred-when-trying-to-issue-security-token-the-server-was-unable-to-p-1.html

1.2.38

Event 8311

Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

Include the specific SSL certificate in the SharePoint trusted certificates list. Please
follow the following links to resolve the issue:
HTTP://SHAREPOINT.STACKEXCHANGE.COM/QUESTIONS/111163/AN-OPERATION-FAILED-BECAUSE-THEFOLLOWING-CERTIFICATE-HAS-VALIDATION-ERRORS
HTTP://BLOGS.TECHNET.COM/B/PRAVEENH/ARCHIVE/2011/05/11/EVENT-ID-8311-CERTIFICATEVALIDATION-ERRORS-IN-MSS-2010.ASPX

1.2.39

Event 8313

Servers Affected

Error

HQVMSPWEB20
HQVMSPWEB22

COMMENTS/RECOMMENDATIONS

Event 8313 is a generic error for service application access issues. There are about 150
such events over the last month. They are mostly related to the managed metadata
and search service and nearly always from the timer service as opposed to the web
application. Additional research would be required to determine what the problem is
and how to resolve it.

1.2.40

Event 10016

COMMENTS/RECOMMENDATIONS

DCOM Permissions need to be updated for the IIS Admin WAMREG Service (this is
always needed after installing SharePoint, same for MSI Server DCOM permissions).

MicrosoftWindowsDistributedC
OM

The application-specific permission settings do

not grant Local Activation permission for the
COM Server application with CLSID
{61738644-F196-11D0-9953-00C04FD919C1}
and APPID
{61738644-F196-11D0-9953-00C04FD919C1}
to the user LPCORP\svcsp_farm2013 SID (S-1-521-72706444-1898000729-941251304-198822)
from address LocalHost (Using LRPC) running in
the application container Unavailable SID
(Unavailable). This security permission can be
modified using the Component Services
administrative tool.

Please follow the links

(both) below to resolve the
issue:
http://blog.ronnypot.nl/?
p=843
http://answers.microsoft.co
m/enus/windows/forum/window
s_8-performance/event-id10016-the-applicationspecificpermission/9ff8796f-c3524da2-9322-5fdf8a11c81e

1.2.41

Event 41734

Servers Affected

Error

BFH-SPFESVR01

COMMENTS/RECOMMENDATIONS

The Muhimbi PDF Converter which is being used on the environment does not seem to
be installed and configured properly. Please do the installation and configuration
properly.

1.2.42

Event 17187

COMMENTS/RECOMMENDATIONS

This error can be neglected as it is merely telling you that a client tried to connect to
SQL Server before SQL Server had fully started.

1.2.43

Event 18056

COMMENTS/RECOMMENDATIONS

This kind of issue occurs when the SQL resources are tightly busy with the existing
connections & its operations that performing against on the database level or overall
your resource crunch.
The memory on DB server is 32 GB so there should not be an issue.