6037 Lsasrv Error
Contents |
(עברית)المملكة العربية السعودية (العربية)ไทย (ไทย)대한민국 (한국어)中华人民共和国 (中文)台灣 (中文)日本 (日本語) Home2012Previous VersionsLibraryForumsGallery Ask a question Quick access Forums home Browse forums users FAQ Search related threads Remove From My Forums Answered event id 6037 lsasrv could not authenticate locally by: Event 6037, lsasrv System Center - Operations Manager
The Program Lsass Exe With The Assigned Process Id Could Not Authenticate Locally
> Operations Manager - General Question 2 Sign in to vote Hi, Environment: SCOM 2007 could not authenticate locally by using the target name rpcss/ R2 with CU 5. I'm getting the following error in the System Eventlog every 4 hours on all clients i installed the SCOM 2007 agent
Could Not Authenticate Locally By Using The Target Name Termsrv
on: The program svchost.exe, with the assigned process ID 4152, could not authenticate locally by using the target name HOST/.. The target name used is not valid. A target name should refer to one of the local computer names, for example, the DNS host name. Try a different target name. event id 6037 lsasrv exchange 2010 The process ID varies, but always points to the Remote Registry service on the local machine. I have seen posts of people having the 6037 error, but always related to a target name http:/ which could not be resolved to a SPN. This would not apply here, because A: the error occurs on ALL servers i install the SCOM client to B: this error doesn't point to a specifice service like http or w3wp, just to HOST/.. This issue seems exactly like this post , too bad i cannot find any followup on it. Anyone have any ideas? Thanks, Edited by Rik van Berendonk Thursday, September 29, 2011 9:53 AM Thursday, September 29, 2011 9:50 AM Reply | Quote Answers 5 Sign in to vote This settings should fix it: HKLM\system\CurrentControlSet\Services\Lanmanserver\parameters DisableStrictNameChecking:DWORD=1 HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa DisableLoopbackCheck:DWORD=1 http://OpsMgr.ru/ Proposed as answer by Jay Pounds Thursday, March 01, 2
size Print view FAQ MembersRegister Login LsaSrv event 6037 - target name HOST/. Unleash the power of System Center for vSphere and Hyper-V | Veeam Task Manager for Hyper-V Post a reply 10 posts • Page 1 of 1 LsaSrv event 6037 - target name HOST/. by jofuc »
Hkey_local_machine\system\currentcontrolset\control\lsa\msv1_0
Thu Jan 19, 2012 4:15 pm people like this post Hello,we recently implemented nworks MP 5.7
Could Not Authenticate Locally By Using The Target Name Http
and everything works fine. We only have one issue - after installation of the MP into SCOM 2007 R2 following events started to appear in disableloopbackcheck the system log of all hosts with SCOM agents installed (W2K8R2), not limited only to nworks Collector:"The program svchost.exe, with the assigned process ID 1234, could not authenticate locally by using the target name HOST/.. The target name used is not https://social.technet.microsoft.com/Forums/systemcenter/en-US/05cedf19-cd02-4c26-9651-4b5d5f46d58b/event-6037-lsasrv?forum=operationsmanagergeneral valid. A traget name should refer to one of the local computer names, for example, the DNS host name.Try a different target name.Source: LsaSrvEventID: 6037Level: Warning..."The warnings appear regularly about every 4 hours. When uninstalling the nworks MP the events disappear. We checked SPNs and found nothing unusual. How to prevent this? jofuc Lurker Posts: 2 Liked: never Joined: Fri Dec 02, 2011 8:06 am Full Name: Josef Fucik Private message Top Re: LsaSrv event 6037 - target name HOST/. by Eag1E https://forums.veeam.com/veeam-management-pack-for-microsoft-system-center-f1/lsasrv-event-6037-target-name-host-t10214.html » Tue Jan 31, 2012 2:09 pm people like this post I have also seen exactly the same issue in previous versions as well.I originally logged a call with MS but they traced it to one of the nworks discoveries.Doesnt seem to have any impact other then flaging this error constantly. Eag1E Novice Posts: 5 Liked: never Joined: Fri Sep 24, 2010 8:19 am Full Name: Mark Edwards Private message Top Re: LsaSrv event 6037 - target name HOST/. by Alec King » Thu Feb 09, 2012 6:48 am people like this post Hi Guys,We have not seen this here. We do have a new discovery in nworks 5.7 that runs in all SCOM Agents; this is checking whether each Agent is actually running inside a VMware VM (by looking in the registry for VMware BIOS details). If the agent is running in VMware, we create an object 'VMware Virtual Machine' that we use for a further discovery target, to create the relationship between the VM and the Agent running inside.Are you running those discoveries? Are they successful? (first discovery is enabled by default; second is disabled by default)For full details see Operations Guide starting page 13 'VM and Ops Mgr Agent integration'Regarding the error, we have not seen this in QA. Possibly an issue with the Action Account permissions when trying to read the registry? Alec King VP, Product Management Posts: 657 Liked: 109 times Joined: Sun Jan 01, 2006 1:01 am Pri
Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services https://community.hpe.com/t5/Systems-Management-OpenView-OP/Agent-on-Win2008R2-causes-LsaSrv-error/td-p/5392663 All Services Products Integrated Systems Composable Systems Converged Systems Hyper http://www.networksteve.com/exchange/topic.php/Event_ID_6037_Source_LsaSrv/?TopicId=3606&Posts=7 Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software as a Service (SaaS) Software-Defined Data could not Center Storage Management All Software Servers Rack Servers Tower Servers Blade Servers Density Optimized Mission Critical Servers Servers for Cloud Server Management All Servers Storage All-flash and Hybrid Storage Midrange and Enterprise Storage Entry Storage Systems Data Availability, Protection and Retention Software Defined Storage Management and Orchestration Storage Networking All Storage could not authenticate Networking Switches Routers Access Points and Controllers Wireless LAN Campus and Branch Networking Data Center Networking Wide Area Network Software Defined Networking Network Functions Virtualization Network Management All Networking About UsSupportClearType to search2086159Solutions Transform to a Hybrid Infrastructure Protect Your Digital Enterprise Empower the Data-Driven Organization Enable Workplace Productivity Cloud Security Big Data Mobility Infrastructure Internet of Things Small and Medium Business Service Providers All Solutions Services Advise, Transform and Manage Financing and Flexible Capacity IT Support Services Education and Training Services All Services Products Integrated Systems Composable Systems Converged Systems Hyper Converged Systems Blade Systems Infrastructure Management Software Application Lifecycle Management Application Delivery Management Big Data Analytics DevOps Enterprise Security Hybrid and Private Cloud Information Governance Information Management IT Service Management Operations Management Server Management Software as a Service (SaaS) Software-Defined Data Center Storage Management All Software Servers Rack Servers Tower Servers Blade Servers Density Optimized Mission Critical Servers Servers for Cloud Se
Based upon other posts it looks to be an issue with SPN or AutoDiscover. I recently got my AutoDiscover working correctly without any errors or issue but this event has been logging prior to and after my AutoDiscover issues were resolved. Any help would be greatly appreciated. May 10th, 2010 7:19pm Always post the complete event log entry. -- Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." . "BizlogicIT" wrote in message news:19f7ce4c-0493-4788-b5a8-63b59fc86a53... I getting this event logged about every hr sometimes sooner. I have searched the net regarding this issue but have yet to find a solution. Based upon other posts it looks to be an issue with SPN or AutoDiscover. I recently got my AutoDiscover working correctly without any errors or issue but this event has been logging prior to and after my AutoDiscover issues were resolved. Any help would be greatly appreciated. Ed Crowley MVP "There are seldom good technological solutions to behavioral problems." Free Windows Admin Tool Kit Click here and download it now May 11th, 2010 1:28am Sorry, forgot: Log Name: System Source: LsaSrv Date: 5/10/2010 3:35:02 PM Event ID: 6037 Task Category: None Level: Warning Keywords: Classic User: N/A Computer: BIZSRV.bizlogic.local Description: The program w3wp.exe, with the assigned process ID 4620, could not authenticate locally by using the target name HTTP/remote.bizlogic.org. The target name used is not valid. A target name should refer to one of the local computer names, for example, the DNS host name. Try a different target name. Event Xml: