phone 983-651-5611
Home > Event Id > Event Id 6037 Sharepoint

Event Id 6037 Sharepoint

Event ID: 6037 Source: LsaSrv Source: LsaSrv Type: Error Description:The program svchost.exe with the assigned process ID 708 could not authenticate locally by using the target name RestrictedKrbHost/ A target name should refer to one of the local computer names, for example, the DNS host name. Thank you and the dude you found this from. Chad is found in the Microsoft public Newsgroups for SBS If you repost there, I'll see if I can get Chad to look in on it and Check This Out

Lets do it the right way This posting is provided "AS IS" with no warranties, and confers no rights! Bye Reply Randy says: December 1, 2012 at 4:32 pm I installed SharePoint 2013 and received the http 401 error after creating aweb application and this solution you proposed helped a How to limit the Exchange 2010 mailboxes databasesize → Leave a Reply Cancel reply Enter your comment here... Tuesday, October 04, 2011 10:31 AM Reply | Quote 0 Sign in to vote Hi, Just checked some servers on this; When the OpsMgr Agent is disabled (or rather, the System

thanks Sunday, March 04, 2012 5:15 PM Reply | Quote 0 Sign in to vote I made the two registry settings recommended by Alexey and we are stillgetting LsaSrv 6037 events After investigating the ULS logs I saw some ‘401’ errors appearing. I am trying to get a remote login possibility for the customer so i can test some things.

Reply Matt Richardson01-25-12 Excellent! It prevents to access to a web application using a fully qualified domain name (FQDN). Archives June 2012 November 2011 October 2011 September 2011 June 2011 April 2011 March 2011 February 2011 January 2011 December 2010 November 2010 August 2010 April 2010 March 2010 February 2010 Also i was not able to find any related errors in the eventlogs unfortunately, so i am at a complete loss here.

Regards, rik Friday, October 14, 2011 8:57 AM Reply | Quote 0 Sign in to vote Hi rick, We see the same problems with lsaSrv on a few 2008R2 servers, stopping read more... Here is what i get from the command setspn -l "myservername": In addition to the http entry I added a dns entry, like what I have for my .. Thanks Man!

On the front-end server, log in as a local or domain administrator. 2. I am glad it helped you. In Registry Editor, locate and then click the following registry key: HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa\MSV1_0 Right-click MSV1_0, point to New, and then click Multi-String Value. Tags64bit Adwords ASP .Net controls name attribute Assembly awesomeness bootstrap Crystal Reports CSS design DevExpress GAC grab xml request grid HTML5 IE6 Compatibility JavaScript JQuery localhost Microsoft.Jet.OLEDB.4.0 Microsoft outlook photoshop

After many attempts IIS returns HTTP 401.1 – Unauthorized: Logon Failed Event ID: 6037 The program w3wp.exe, with the assigned process ID 8260, could not authenticate locally by using the target navigate to these guys So http://WEBSITENAME was added to the Alternate Access Methods in SharePoint 2010 for this web application. I started checking other Windows Event logs and found this: Log Name:      System                  Source:        LsaSrv Date:          12/10/2010 1:49:45 PM Event ID:      6037                          Task Category: None Level:         Warning                        Keywords:      Classic User:          In the Value data box, type the HLB Alias for the sites that are on the local computer, and then click OK.

On the front-end server, log in as a local or domain administrator. 2. his comment is here Kind of odd. Reply Leroy Senst says: July 7, 2012 at 10:38 pm I take pleasure in, cause I discovered just what I was having a look for. Try a different target name.

Still the same error occurred, yet authentication was successful if the http://MOSSSERVER URL was used. S a r v e s h, I also tried what you suggested, but it didn't work. A target name should refer to one of the local computer names, for example, the DNS host name. this contact form Right click MSV1_0 > New > Multi-String Value 3.

In the mean time, have you implemented the fix for the SharePoint 2436 error? Cheers, Rik Friday, March 02, 2012 9:53 AM Reply | Quote 0 Sign in to vote Alexey I have the same issue in a Lync deployment on Windows 2008 R2 virtual This completely solved our issue!!!!!!!

Type ‘BackConnectionHostNames' 4.

Privacy Policy Support Terms of Use Home Content RSS Log in Applogix Dev Blog (DotNetPulse) Practical commentary on development… Search for: Home Abouttest w3wp.exe unable to authenticate on target name May Search for: Recent Posts Exchange 2010 Search Mailbox query doesn’t support the “FW” & “RE” in SubjectQuery USB CD/DVD ROM or USB Token for E-banking notwork DISM/MDT 2010 failed to add About the question of "Any changes before the errors occured" ; not that i know of. Account Login Username Password Sign in Forgot your password?

Right-click BackConnectionHostNames, and then click Modify. Right-click "MSV1_0", create a new "Multi-String Value" named "BackConnectionHostNames". 5. But angry at Microsoft for such a complicated install. navigate here PRTG is easy to set up &use.

Close Not a member yet? Thanks. I noticed that the host name that appears in the event is the correct FQDN, but with a backslash on the end. Contact info Celox Group Pty Ltd 78/330 Wattle Street, ULTIMO 2007 NSW  +61 (02) 9045 1897 +61 (02) 9194 3340 [email protected] Copyright © 2010-2015 Celox Group Pty Ltd.

I try to give Chad a heads up. set DisableLoopbackCheck=1 both ways described in kb Proposed as answer by PvDro Thursday, October 09, 2014 12:21 PM Wednesday, March 07, 2012 2:26 PM Reply | Quote 0 Sign in to See example of private comment Search: Google - Bing - Microsoft - Yahoo - EventID.Net Queue (0) - More links... Connect with top rated Experts 16 Experts available now in Live!