Ошибка 6398 sharepoint

I think I probably figured out what is my issue,  I know that someone having this issue because of other reason, but my reason is, the FeedCacheService.BulkLMTUpdate: Region not found
happened all the time when I restart my 2012 server, because I’m doing development, so I need to restart server everyday, every time when restart server, the AppFabric Caching Service restart, and the cache region will rebuild, and there is no
LMT region, and then this exception happened.

so if you look at the code in FeedCacheService.BulkLMTUpdate, it will

call FeedCacheImplementation.BulkLMTUpdate, in FeedCacheImplementation.BulkLMTUpdate, it calls 

this.PutInLMTRegion(CacheIdentifier, this.GetCacheLMTTTL(LastModifiedUtcTime), null);

this cause the region not found exception, and it throw SPDistributedCacheRegionNotFoundException exception, and try to call another method to recreate the LMT region:

this.EnsureAndRepopulateLMTRegion(false);

after the LMT region recreated. and the region not found event will never happened, unless the AppFabric Caching Service restart.

I just don’t understand why MS developers assuming the LMT region always be there, how about the first running of the cache service after the fresh installation? just like my case. and also sometime I got another 6398 error, said the cache cluster is
probably down, I believe this is also related with the AppFabric Caching Service, looks like AppFabric Caching Service is not stable.

some links about Distributed Cache service in SharePoint Server 2013

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

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

and here is the code BulkLMTUpdate:

internal bool BulkLMTUpdate(Guid callerID, List<KeyValuePair<FeedCacheEntity, LMTEntry>> lastModifiedTimes)
{
    bool flag;
    if (lastModifiedTimes == null)
    {
        throw new ArgumentNullException(«lastModifiedTimes»);
    }
    using (new SPMicroblogUsageMonitoredScope(«FeedCacheImplementation.BulkLMTUpdate», SPMicroblogUsageField.FeedCacheImpl_Duration))
    {
        try
        {
            foreach (KeyValuePair<FeedCacheEntity, LMTEntry> pair in lastModifiedTimes)
            {
                this.PutInLMTRegion(pair.Key.CacheIdentifier, pair.Value, this.GetCacheLMTTTL(pair.Value.LastModifiedUtcTime), null);
                AddToLocalUrls(pair.Key);
            }
            this.LMTCacheWrapper.Put(callerID.ToString(«N»), new LMTEntry(DateTime.UtcNow).Serialze(), FeedCacheManager.Constants.ConfigTTLTimeSpan, this.LastModifiedTimeRegionName);
        }
        catch (Exception exception)
        {
            if (exception is SPDistributedCacheRegionNotFoundException)
            {
                ULS.SendTraceTag(0x10645f, ULSCat.msoulscat_SPS_FeedCache, ULSTraceLevel.Medium, «FeedCacheImplementation.BulkLMTUpdate() — LMT region missing»);
                this.EnsureAndRepopulateLMTRegion(false);
                try
                {
                    foreach (KeyValuePair<FeedCacheEntity, LMTEntry> pair2 in lastModifiedTimes)
                    {
                        this.PutInLMTRegion(pair2.Key.CacheIdentifier, pair2.Value, this.GetCacheLMTTTL(pair2.Value.LastModifiedUtcTime), null);
                    }
                    this.DataCacheWrapper.Put(callerID.ToString(«N»), new LMTEntry(DateTime.UtcNow).Serialze(), FeedCacheManager.Constants.ConfigTTLTimeSpan, this.LastModifiedTimeRegionName);
                    goto Label_01C1;
                }
                catch (Exception exception2)
                {
                    ULS.SendTraceTag(0x20178c, ULSCat.msoulscat_SPS_FeedCache, ULSTraceLevel.High, «FeedCacheImplementation.BulkLMTUpdate() — Unexpected exception while trying to update LMT in bulk: {0}», new
object[] { exception2 });
                    throw;
                }
            }
            ULS.SendTraceTag(0x151821, ULSCat.msoulscat_SPS_FeedCache, ULSTraceLevel.High, «FeedCacheImplementation.BulkLMTUpdate() — Unexpected exception while trying to update LMT in bulk: {0}», new object[] { exception });
            throw;
        }
    Label_01C1:
        flag = true;
    }
    return flag;
}

	Номер ошибки:	Ошибка 6398
Название ошибки:	Microsoft Sharepoint Error 6398
Описание ошибки:	Ошибка 6398: Возникла ошибка в приложении Microsoft Sharepoint. Приложение будет закрыто. Приносим извинения за неудобства.
Разработчик:	Microsoft Corporation
Программное обеспечение:	Microsoft Sharepoint
Относится к:	Windows XP, Vista, 7, 8, 10, 11

Описание «Microsoft Sharepoint Error 6398»

Это наиболее распространенное условие «Microsoft Sharepoint Error 6398», известное как ошибка времени выполнения (ошибка). Разработчики программного обеспечения, такие как Microsoft Corporation, обычно принимают Microsoft Sharepoint через несколько уровней отладки, чтобы сорвать эти ошибки перед выпуском для общественности. Ошибки, такие как ошибка 6398, иногда удаляются из отчетов, оставляя проблему остается нерешенной в программном обеспечении.

После установки программного обеспечения может появиться сообщение об ошибке «Microsoft Sharepoint Error 6398». В случае обнаруженной ошибки 6398 клиенты могут сообщить о наличии проблемы Microsoft Corporation по электронной почте или сообщать об ошибках. Затем программисты могут исправить эти ошибки в коде и включить исправление, которое можно загрузить с их веб-сайта. Если есть запрос на обновление Microsoft Sharepoint, это обычно обходной путь для устранения проблем, таких как ошибка 6398 и другие ошибки.

Сбой во время запуска Microsoft Sharepoint или во время выполнения, как правило, когда вы столкнетесь с «Microsoft Sharepoint Error 6398». Причины сбоев обработки можно отличить, классифицируя ошибки 6398 следующим образом:.

Ошибка 6398 Crash — Номер ошибки вызовет блокировка системы компьютера, препятствуя использованию программы. Обычно это происходит, когда Microsoft Sharepoint не может распознать, что ему дается неправильный ввод, или не знает, что он должен производить.

Утечка памяти «Microsoft Sharepoint Error 6398» — этот тип утечки памяти приводит к тому, что Microsoft Sharepoint продолжает использовать растущие объемы памяти, снижая общую производительность системы. Есть некоторые потенциальные проблемы, которые могут быть причиной получения проблем во время выполнения, с неправильным кодированием, приводящим к бесконечным циклам.

Ошибка 6398 Logic Error — логическая ошибка возникает, когда компьютер производит неправильный вывод, даже если вход правильный. Неисправный исходный код Microsoft Corporation может привести к этим проблемам с обработкой ввода.

Microsoft Corporation проблемы файла Microsoft Sharepoint Error 6398 в большинстве случаев связаны с повреждением, отсутствием или заражением файлов Microsoft Sharepoint. Обычно, установка новой версии файла Microsoft Corporation позволяет устранить проблему, из-за которой возникает ошибка. В некоторых случаях реестр Windows пытается загрузить файл Microsoft Sharepoint Error 6398, который больше не существует; в таких ситуациях рекомендуется запустить сканирование реестра, чтобы исправить любые недопустимые ссылки на пути к файлам.

Распространенные проблемы Microsoft Sharepoint Error 6398

Частичный список ошибок Microsoft Sharepoint Error 6398 Microsoft Sharepoint:

• «Ошибка программного обеспечения Microsoft Sharepoint Error 6398. «
• «Недопустимый файл Microsoft Sharepoint Error 6398. «
• «Microsoft Sharepoint Error 6398 столкнулся с проблемой и закроется. «
• «Не удается найти Microsoft Sharepoint Error 6398»
• «Microsoft Sharepoint Error 6398 не может быть найден. «
• «Ошибка запуска в приложении: Microsoft Sharepoint Error 6398. «
• «Не удается запустить Microsoft Sharepoint Error 6398. «
• «Ошибка Microsoft Sharepoint Error 6398. «
• «Ошибка в пути к программному обеспечению: Microsoft Sharepoint Error 6398. «

Обычно ошибки Microsoft Sharepoint Error 6398 с Microsoft Sharepoint возникают во время запуска или завершения работы, в то время как программы, связанные с Microsoft Sharepoint Error 6398, выполняются, или редко во время последовательности обновления ОС. Важно отметить, когда возникают проблемы Microsoft Sharepoint Error 6398, так как это помогает устранять проблемы Microsoft Sharepoint (и сообщать в Microsoft Corporation).

Создатели Microsoft Sharepoint Error 6398 Трудности

Проблемы Microsoft Sharepoint Error 6398 могут быть отнесены к поврежденным или отсутствующим файлам, содержащим ошибки записям реестра, связанным с Microsoft Sharepoint Error 6398, или к вирусам / вредоносному ПО.

Более конкретно, данные ошибки Microsoft Sharepoint Error 6398 могут быть вызваны следующими причинами:

• Недопустимый Microsoft Sharepoint Error 6398 или поврежденный раздел реестра.
• Вирус или вредоносное ПО, повреждающее Microsoft Sharepoint Error 6398.
• Microsoft Sharepoint Error 6398 злонамеренно удален (или ошибочно) другим изгоем или действительной программой.
• Другое программное приложение, конфликтующее с Microsoft Sharepoint Error 6398.
• Microsoft Sharepoint/Microsoft Sharepoint Error 6398 поврежден от неполной загрузки или установки.

Продукт Solvusoft

Загрузка
WinThruster 2022 — Проверьте свой компьютер на наличие ошибок.

Совместима с Windows 2000, XP, Vista, 7, 8, 10 и 11

Установить необязательные продукты — WinThruster (Solvusoft) | Лицензия | Политика защиты личных сведений | Условия | Удаление

I just found this morning that there are a lot of critical errors since 9/9/2015 in SharePoint, all of them being the Event ID 6398. Here’s the error:

The Execute method of job definition Microsoft.Office.Server.UserProfiles.UserProfileImportJob (ID 9c4b1113-cc57-46e0-83c4-75c1c64f909a) threw an exception. More information is included below.

Operation is not valid due to the current state of the object.

When I go see which job is causing this issue (with the id), it points right toward the User Profile Service Application - User Profile Incremental Synchronization job. And in fact, when I go see users in SharePoint, I can see that they’re not up-to-date since about a week (surely since 9/9/2015).

I tried to search for solutions, but they were more «Disable the faulty job» than anything else and I don’t think disabling this job is a solution.
I also found a solution that would be to restart the SharePoint Timer Service on the server, but I’m quite hesitant about this, since I don’t know the impacts of restarting the service (even if I don’t think it would cause any problem).

I’m using SharePoint 2013 if it can be of any help.

Is anyone ever faced this problem and maybe have a solution?

Thanks.

Several features of the Microsoft SharePoint Foundation rely on scheduled background processes known as timer jobs. The status of timer jobs can be configured, scheduled, and viewed by the Administrator by using the Web site of SharePoint Central Administration.

But sometimes the SharePoint fails and starts throwing various errors. speaking of errors one such error is the event id 6398 error in SharePoint. 

So, if you are the one encountering the Service Instance timer execution failed – Event 6398 in SharePoint 2010 then keep reading the article to learn more about the error and ways to fix event id 6398.

Symptoms of the Event 6398 in SharePoint

• This event appears in the event log: Event ID: 6398 The Execute method of job definition <Job Definition Name> (ID Job ID) threw an exception. More information is included below. %n%n <Job Details>

Most Common Job Definitions:

• • SPPasswordManagementJobDefinition

Purpose:   Sends e-mail and logs events for expiring passwords and password changes. Managed passwords are changed before they expire is ensured by a timer job.

• • SPGeneratePasswordJobDefinition

Purpose:   Generates a new password for an account, updates the account password, and then launches jobs to deploy the new password to everything that uses it.

• • SPAdminAppPoolCredentialDeploymentJobDefinition

Purpose:   Credentials are updated for the administration of the Internet Information Services (IIS) 7.0 application pool on the farm.

• • SPContentAppPoolCredentialDeploymentJobDefinition

Purpose:   Updates the credentials for a content IIS application pool on all servers in the farm.

• • SPWindowsServiceCredentialDeploymentJobDefinition

Purpose:   Updates the credentials for a Windows service on every PC in the farm where service is running.

• • SPMasterPassphraseDeploymentJobDefinition

Purpose:  Tells all the front-end Web applications the new passphrase-derived key. This job is run when the administrator decides to change the passphrase of the farm.

Causes of the SharePoint 2010 Event  6398 Error

• The third-party timer job cannot be found or is corrupt.
• The MS SharePoint Foundation 2010 timer job cannot be found or is corrupt.
• Most Common Job Causes:
  • SPPasswordManagementJobDefinition

Issue:   Password change timer jobs (SPGeneratePasswordJobDefinition) has not been scheduled or updated for farm credentials. Any additions or changes made recently to the password change schedules for any credentials in the farm will not be updated to match the changes until the successful completion of this job.

• • SPGeneratePasswordJobDefinition

Issue:   Creating a new password is a scheduled timer job for a farm credential failed. The current credential value might no longer be valid and has to be manually updated in the Active Directory account. This timer job should be restarted if the credentials for the account are still valid.

• • SPAdminAppPoolCredentialDeploymentJobDefinition

Issue:   The new credentials for the Central Administration Web application pool have not been updated on the local machine to match the current value that was configured for the farm. This might prevent the Central Administration Web application from starting.

• • SPContentAppPoolCredentialDeploymentJobDefinition

Issue:   The new credentials for the application pool have not been updated on the local machine to match the current value that was configured for the farm. This might prevent the application pool from starting.

• • SPWindowsServiceCredentialDeploymentJobDefinition

Issue:   The new credentials for service have not been updated on the local machine to match the current value that was configured for the farm. This might prevent the service from starting.

• • SPMasterPassphraseDeploymentJobDefinition

Issue:   The master passphrase for the farm has not been updated on the local machine to match the current value that was configured for the farm. Decryption or encryption of the farm might be prevented with this encryption key until it is updated locally.

• Review the job definition name found in the event description to determine the appropriate resolution:
  • SPPasswordManagementJobDefinition

Resolution:   Restart this timer job.

• • SPGeneratePasswordJobDefinition

Resolution:   Restart this timer job to manually force a password reset.

• • SPAdminAppPoolCredentialDeploymentJobDefinition

Resolution:   Restart this timer job to run administrator deployment jobs locally, in order to manually force a password reset.

• • SPContentAppPoolCredentialDeploymentJobDefinition

Resolution:   Restart this timer job to run administrator deployment jobs locally, in order to manually force a password reset.

• • SPWindowsServiceCredentialDeploymentJobDefinition

Resolution:   Restart this timer job to run administrator deployment jobs locally, in order to manually force a password reset.

• • SPMasterPassphraseDeploymentJobDefinition

Resolution:   Restart this timer job to run administrator deployment jobs locally, in order to manually force a password reset.

Alternate Solution to Fix Event ID 6398 SharePoint 2010 Error

1. Start Central Administration
2. Then go to Application Management > Web Applications > Manage Web Applications
3. Next, choose the target web application.
4. Then on the Web ribbon from the General Settings dropdown > choose General Settings > scroll down to the bottom.
5. And Lastly set Enable Customer Experience Improvement Program to No.

Hope this works for you to fix SharePoint 2010 Event ID 6398 error, but if you are still encountering the Event 6398 error then run the automatic tool.

Automatic Solution to Fix SharePoint Service Instance Timer Execution Failed – Event 6398

If you are still encountering the SharePoint 2010 Event ID 6398 error then feel free to run the SharePoint File Repair tool. It is designed specifically to fix and recover several SharePoint errors.

It comes with an advanced algorithm that scans your entire SharePoint objects and helps you in fixing the issues and corruption. This is a multifunctional tool that just by scanning once detect and fix the SQL server errors. It not only repairs the files but also recovers entire crucial information stored on your SharePoint Server.

This tool also allows the user to retrieve the SharePoint database like tables, documents, labels, etc. this software is incorporated with a simple and rich graphical user interface to offer easy SharePoint recovery.

Steps to Run the SharePoint Repair Tool

• Firstly, download, install, and launch the SharePoint Recovery Tool.
• The interface screen displays two options to recover SharePoint data: ‘Complete Repair‘ and ‘Document Recovery‘. Select as per your requirement.

• If you choose ‘Complete Repair‘, the screen will show the options for selecting and searching SQL Server (.MDF) files. Click on ‘Browse‘ to select a SharePoint database for repair.
• If you do not know the actual path of the database which you want to repair, click on the ‘Find‘ to locate the MDF file in a specific drive.
• After selecting the desired file initiate the scanning process.

• After finishing the scan, the software would generate a tree of all SharePoint database tables and will display it in the left pane. You can select the table in the tree and can have the entire preview in the right pane. Then click on ‘Repair‘ to begin repairing for the selected database.
• After clicking on ‘Repair‘, this dialog box will appear. Specify the SQL Server name or Instance name and the desired destination path.
• Click on the ‘Browse‘ option to choose the destination path. And select the ‘OK‘ button.
• Once this process gets completed, you would find a dialog box that displays this message ‘Recovered file saved at the desired location.” This shows that Recovery Process has successfully completed’.
• Select the ‘OK‘ button.
• You would find another dialog box that asks whether you want to attach the repaired database to the web application. If you click on the ‘Yes‘ button, the above dialog box will be displayed.
• In the web application type URL, the name of the corrupt database and SQL Server Instance name.
• Then select the ‘OK‘ button and proceed.
• When the process gets finished, you would be able to access the repaired database by opening the web application.

Conclusion

So, this is all about “service instance timer execution failed – Event 6398” SharePoint 2010 error. I tried my best to list down the best possible solution fixes to get rid of the Event 6398 error in SharePoint.

Follow the solutions given to fix the Event ID 6398 error, hope the article works for you. Moreover, you can also fix the error easily by running the SharePoint Repair Tool.

If there is anything that I missed out or you are having any comments, queries, or suggestions, then share it with us on Facebook and Twitter. Also, if you like this article, then share it with the users going through the same issue.