Keith Smith - My Blog

Failure trying to synch web application Event ID 5555

Wednesday, April 19, 2017 - Posted by Keith A. Smith, in SharePoint

One of the errors I got after upgrading sharepoint that I couldn’t shake until recently.

Failure trying to synch web application , ContentDB Exception message was Microsoft.Office.Server.UserProfiles.UserProfileApplicationNotAvailableException: No User Profile Application available to service the request. Contact your farm administrator. at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_ApplicationProperties() at Microsoft.Office.Server.Administration.UserProfileApplicationProxy.get_PerfmonInstanceHandle() at Microsoft.Office.Server.UserProfiles.ContentDBSynchronizer..ctor(ELogType logType, SPContentDatabase cdb, SPJobState jobState) at Microsoft.Office.Server.UserProfiles.WSSProfileSyncJob.Execute()

Run from the sharepoint bin directory in a cmd prompted

Stsadm -o sync -listolddatabases 2 Stsadm -o sync -deleteolddatabases 2

Finally, and I’m not sure if this is necessary, but I read that you should change timer job “Timer Service Recycle” (Central Administration –> Job Definitions) to run at 06:30 PM. This last step can be done through Central Administration. After doing this my errors went away. I did however need to run a full user profile synchronization by going to Central Administration –> Manage Profile Service: SharedServicesSearch_UserProfile –> Start Profile Synchronization

-End

0 Comments
Share Post

Full list of Failure Reasons for event 4625

Wednesday, April 19, 2017 - Posted by Keith A. Smith, in Security

Windows Domain Controller - Event Viewer Security Status and Sub-Status values

SUB_STATUS

	DESCRIPTION
0XC000006D	This is either due to a bad username or authentication information
0XC000006D	This is either due to a bad username or authentication information
0XC000006E	Unknown user name or bad password.
0XC000006E	Unknown user name or bad password.
0XC0000193	account expiration
0XC000006E	Unknown user name or bad password.
0XC000006D	This is either due to a bad username or authentication information
0XC000006D	This is either due to a bad username or authentication information
0XC000018C	The logon request failed because the trust relationship between the primary domain and the trusted domain failed.
0XC000005E	There are currently no logon servers available to service the logon request.
0XC00000DC	Indicates the Sam Server was in the wrong state to perform the desired operation.
0XC0000224	A user is required to change password at next logon
0XC0000192	An attempt was made to logon, but the netlogon service was not started.
0XC0000413	Logon Failure: The machine you are logging onto is protected by an authentication firewall. The specified account is not allowed to authenticate to the machine.

-End

0 Comments
Share Post

DNS Benchmark – Advanced and accurate DNS performace benchmark tool

Tuesday, April 18, 2017 - Posted by Keith A. Smith, in Network

When it comes to DNS servers, the response speed is not the only standard to measure its performance. Certainly the response time should be as short as possible, but the stability and security is also important factors. A DNS server without stability (intermittent) will cause web page loading problems even it has very fast response.

DNS Benchmark is a unique, comprehensive, accurate freeware for Windows (and Linux/Wine) designed to measure the exact performance of local and remote DNS servers . . .

DNS Benchmark not only comes with a lot of popular, outstanding DNS servers, also has a set of algorithm which was designed to analyze the reliability of DNS servers.

-End

0 Comments
Share Post

Access is denied. Verify that either the Default Content Access Acc

Sunday, April 9, 2017 - Posted by Keith A. Smith, in SharePoint

Access is denied. Verify that either the Default Content Access Account has access to this repository

Error: Censored

Access is denied. Verify that either the Default Content Access Account has access to this repository, or add a crawl rule to crawl this repository. If the repository being crawled is a SharePoint repository, verify that the account you are using has "Full Read" permissions on the SharePoint Web Application being crawled.

Reason:
This error will occur, at the time of crawling the SharePoint application content. because, you may have provided a URL to access the SharePoint web application like https://portal.KeithIT.com (just an example).
When the search engine tried to crawl the content using the portal.KeithIT.com (just an example) URL, the server will reject the request. because, it will take the request as "LoopBackRequest".

Solution: Thumbs Up

So you need to disable the LoopBackRequest in registry. To do this, just follow my instructions:

1. Go to command window and type regedit.exe
2. Once opened the registry editor, just navigate to "HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa"
3. Right click on "Lsa" and create a new 32bit DWORD value
4. Rename it as "DisableLoopbackCheck" (Note: you cannot rename it actually. so, once created the DWORD value, directly paste/type as "DisableLoopbackCheck".
5. Then again modify the value of "DisableLoopbackCheck" as "1"
6. Close the registry editor.
7. Now start to crawl the content.

-End

0 Comments
Share Post