Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Monday, June 24, 2013 11:38 PM
We have just configured Search and PerformancePoint on a New SharePoint 2013 server built on Windows 2012 and connecting to a SQL server 2012.
There are now multiple errors in the Error logs and the server has needing to be rebooted a few times this week.
The majority of the errors are: 6482, 6398, with a few PerformancePoint ones.
As you can see below the error descripts are also missing - so any help there might get me going!
Any ideas, please let me know.
The description for Event ID 6482 from source Microsoft-SharePoint Products-SharePoint Server cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
Microsoft.Office.Server.Search.Administration.SearchServiceInstance
dd12a35a-9f3e-4be1-85cf-e1ed7ea66645
An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by XXX\yyy, in the OWSTIMER (1740) process, on machine SP13. View the tracing log for more information about the conflict.
Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SearchDataAccessServiceInstance was updated by XXX\yyy, in the OWSTIMER (1740) process, on machine SP13. View the tracing log for more information about the conflict.
at Microsoft.Office.Server.Search.Administration.SearchServiceInstance.Synchronize()
at Microsoft.Office.Server.Administration.ApplicationServerJob.ProvisionLocalSharedServiceInstances(Boolean isAdministrationServiceJob)
The description for Event ID 6398 from source Microsoft-SharePoint Products-SharePoint Foundation cannot be found. ......
Microsoft.SharePoint.Administration.SPLicenseRenewalJobDefinition
5a6341cf-e9c4-4675-917d-0b709066dd30
An update conflict has occurred, and you must re-try this action. The object SPLicenseRenewalTimerJobPersistedInformation Name=SPLicenseRenewalTimerJobPersistedInformation79b29236-e2e2-48b1-841a-aa5371458bc8 was updated by XXX\yyy, in the OWSTIMER (1740) process, on machine SP13. View the tracing log for more information about the conflict.
The description for Event ID 6398 from source Microsoft-SharePoint Products-SharePoint Foundation cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Microsoft.Office.Server.UserProfiles.LMTRepopulationJob
ac30b77e-1a1b-4c84-a450-c5067f7a1cdb
Unexpected exception in FeedCacheService.IsRepopulationNeeded: Unable to create a DataCache. SPDistributedCache is probably down..
The description for Event ID 1101 from source Microsoft-SharePoint Products-PerformancePoint Service cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
An exception occurred while rendering a Web control. The following diagnostic information might help to determine the cause of this problem:
Microsoft.PerformancePoint.Scorecards.BpmException: The request has timed out or been aborted. Additional details have been logged for the administrator.
PerformancePoint Services error code 20700.
The description for Event ID 1139 from source Microsoft-SharePoint Products-PerformancePoint Service cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Any ideas, please let me know.
Ruth, UK
All replies (5)
Tuesday, June 25, 2013 7:07 AM ✅Answered | 8 votes
Hi Ruth,
Resolution:
The file system cache on all FE’s on which the timer service is running needs to be cleared.
:
- Stop the Windows SharePoint Services Timer service (Found in Windows Services)
- Navigate to the cache folder In Windows Server 2008, the configuration cache is in the following location: Drive:\ProgramData\Microsoft\SharePoint\Config In Windows Server 2003, the configuration cache is in the following location: Drive:\Documents and Settings\All Users\Application Data\Microsoft\SharePoint\Config Locate the folder that has the file “Cache.ini” (Note: The Application Data folder may be hidden. To view the hidden folder, change the folder options as required)
- Back up the Cache.ini file.
- Delete all the XML configuration files in the GUID folder. Do this so that you can verify that the GUID folder is replaced by new XML configuration files when the cache is rebuilt.
- Note When you empty the configuration cache in the GUID folder, make sure that you do not delete the GUID folder and the Cache.ini file that is located in the GUID folder.
- Double-click the Cache.ini file.
- On the Edit menu, click Select All. On the Edit menu, click Delete. Type 1, and then click Save on the File menu. On the File menu, click Exit.
- Start the Windows SharePoint Services Timer service
- Note The file system cache is re-created after you perform this procedure. Make sure that you perform this procedure on all servers in the server farm.
- Make sure that the Cache.ini file in the GUID folder now contains its previous value. For example, make sure that the value of the Cache.ini file is not 1.
Regards,
karim
Please remember to mark your question as "answered" if this solves your problem.
Monday, June 20, 2016 2:34 PM
Hi,
I have been facing the same issue, and the scenario was the same.
I followed your advice @KarimSP and did the cache reset, I went through all of your steps specifically, This did stopped the errors 6482 and 6398 from occuring again, but it didn't fix the search application.
My search application still doesn't work and is prompting sorry something went wrong.
Any advice on this please.
rafi qureshi
Thursday, June 30, 2016 8:39 AM | 1 vote
Hi,
It seems after upgrade you did not execute the psconfig command or previous upgrade was failed..
Execute below command in sharepoint powershell and schedule the down time.
"PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources"
refer below sites for more info
Karim... Please remember to mark your question as answered, if this solves your problem.
Monday, April 17, 2017 5:34 PM
If we see multiple GUID, how do we choose the right folder? there is one with all 0s but then i see another one with random letters and numbers. Two of the folders have a Cache.ini file. The two files differ in regards to the text that is inside them. For instance one has 7255 and the other has 581856.
Thank you for your help!
Monday, April 9, 2018 1:32 PM
this worked on me. thanks