Showing posts with label Event ID. Show all posts
Showing posts with label Event ID. Show all posts

Thursday, May 7, 2015

Event 6398 in SharePoint



Event 6398 in SharePoint

Event ID:   6398

Summary:   Several features of Microsoft SharePoint Foundation 2010 rely on scheduled background processes called timer jobs. Administrators can configure, schedule, and view the status of timer jobs by using the SharePoint Central Administration Web site.

I found a very good article from MS. Please find below

  https://technet.microsoft.com/en-us/library/ee513069%28v=office.14%29.aspx?f=255&MSPPError=-2147217396


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Thursday, March 26, 2015

Unknown SQL exceptions - Event 5586



Unknown SQL exceptions - Event 5586

Alert Name:   Unknown SQL exceptions

Event ID:   5586

Summary:   Microsoft SharePoint Foundation uses Microsoft SQL Server 2008 databases to store configuration settings and most of the content for the Web site. For example, all pages in the site, files in document libraries, files attached to lists, and information in lists are stored in the content database, and security and permission settings along with other configuration settings are stored in the configuration database in SQL Server 2008.
Microsoft SharePoint Foundation uses a service account to communicate with the database on behalf of a user request. This service account can be either a specific user name or password (domain name and password), or a predefined system account, such as Local System or Network Service. When a SQL Server database is created, a value for the maximum database size is set. Each database has a separate database size setting. Note that a Web application might be associated with one or many databases.

Symptoms:   The following symptom might appear:

·         This event appears in the event log: Event ID: 5586 Description: Database full error on SQL Server instance <instance name> in database <database name>. Additional error information from SQL Server is included below. <SQL error message>.

Cause: The issue is because of many reasons, below are some of the reasons
1.    Insufficient SQL Server database permissions
2.    SQL Server database is full
3.    Incorrect MDAC version
4.    SQL Server database not found
5.    Incorrect version of SQL Server
6.    SQL Server collation is not supported
7.    Database is read-only

Solution: The issue could be of many reasons so it has many different solutions that should implement to resolve the issue. One of the solution would be your saver.
Please check the link below from MS to get the solutions.

 https://technet.microsoft.com/en-us/library/ee513056%28v=office.14%29.aspx

 


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Tuesday, November 11, 2014

Event ID 6398,6396,7037



Event ID 6398,6396,7037

Issue: The Execute method of job definition %1 (ID %2) threw an exception. More information is included below.

Solution: Check the link Below from MS which provides solution.

6398:

6396:

7037: 

 http://technet.microsoft.com/en-us/library/cc561034%28v=office.12%29.aspx


I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Monday, September 15, 2014

Event ID 2138 Re-occurring on SharePoint



Event ID 2138 Re-occurring on SharePoint

Issue: Event ID 2138 occurring every hour. gives details that DB has grown larger than normal.

Resolutions: Please find the below steps to resolve the issue.

Resolution1:   Free disk space on the server computer

1.    Verify that the user account that is performing this procedure is a member of the Administrators group on the local computer.
2.    Run the Disk Cleanup tool to free disk space on the server computer.

Resolution 2:   Decrease the number of days to store log files

1.    Verify that the user account that is performing this procedure is a member of the Farm Administrators group.
2.    On the Central Administration Home page, click Monitoring.
3.    On the Monitoring page, in the Reporting section, click Configure diagnostic logging.
4.    On the Diagnostic Logging page, in the Trace Log section, in the Number of days to store log files box, type a smaller number.
5.    Click OK.

The issue is you see this is because, have a server with lots of physical ram.  SharePoint calculates this multiplies by 5 times and expects that amount of free space on your C drive even though SharePoint is probably not on your C drive.

·         Go into the SharePoint configuration.
·         Go into monitoring
·         Go into review rule definitions
·         Scroll down into the drives are running out of free space
·         Pull it up and edit it
·         Unclick the enabled box and save.
 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

Friday, August 29, 2014

SharePoint 2013 SP1 installation failed



SharePoint 2013 SP1 installation failed

Issue: SharePoint 2013 SP1 installation failed with event id: 1000, “Faulting application name: MsiExec.exe”

Event: Log Name: Application
Source: Application Error
Event ID: 1000
Task Category: (100)
Level: Error
Keywords: Classic
User: N/A
Computer: *****
Description:
Faulting application name: MsiExec.exe, version: 5.0.9600.16384, time stamp: 0x5215f49e
Faulting module name: KERNELBASE.dll, version: 6.3.9600.16408, time stamp: 0x523d557d
Exception code: 0xe06d7363
Fault offset: 0x000000000000ab78
Faulting process id: 0x1718
Faulting application start time: 0x01cf58bdd3e6f830
Faulting application path: C:\Windows\System32\MsiExec.exe
Faulting module path: C:\Windows\system32\KERNELBASE.dll
Report Id: 7b39da05-c4b1-11e3-80c1-1803732dc367

Solution: Ensure to check the below Registry entries and delete any entries under those if  present

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\PendingFileRenameOperations 

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Session Manager\FileRenameOperations

 

I hope the above information will help you to resolve the issue, in case of any queries/questions regarding the above mentioned information then please let me know. I would be more than happy to help you as well as resolves your issues, Thank you.

ShareThis

X