简体   繁体   English

SWJOBENGINEWORKER2.EXE - 我的 SQL 服务器出了什么问题?

[英]SWJOBENGINEWORKER2.EXE - What's hitting my SQL server?

I'm new to using DPA - while monitoring some alerts, I found that we had repeated attempts for a "login failed for user 'domain\User': attempting to use an NT account name with SQL Server Authentication [CLIENT: local machine]"我是使用 DPA 的新手-在监视一些警报时,我发现我们反复尝试“用户 '域\用户'登录失败:尝试使用带有 SQL 服务器身份验证的 NT 帐户名 [客户端:本地计算机] "

After doing a bit of research, we have identified that the attempted logins were coming from a Task Manager Detail with a PID associated to SWJobEngineWorker2.exe that runs every 5 minutes, and everything I've found seems to be that this is related to NPM.经过一番研究,我们发现尝试登录来自任务管理器详细信息,其 PID 与每 5 分钟运行一次的 SWJobEngineWorker2.exe 相关联,我发现的一切似乎都与 NPM 有关.

There are also 3 other Detail/Services that are constant: SWJobEngineSvc2.exe, and 2 instances of SWJobEngineWorker2x64.exe还有 3 个其他 Detail/Services 是不变的:SWJobEngineSvc2.exe 和 SWJobEngineWorker2x64.exe 的 2 个实例

We do not have any stored credentials in Solarwinds for this particular domain\User, and it doesn't appear that we're using AppInsights to monitor, and nothing seems to be failing, as DPA is monitoring the SQL server just fine.我们在 Solarwinds 中没有针对此特定域\用户存储的任何凭据,而且我们似乎没有使用 AppInsights 进行监控,而且似乎没有任何问题,因为 DPA 正在监控 SQL 服务器就好了。

How can I remove/change this process or adjust the credentials/connection settings it is using?如何删除/更改此过程或调整它正在使用的凭据/连接设置?

NOTE: There are NO services on this particular server that use this domain\User account and the only SW service running is 'SolarWinds Agent' using LogOnAs Local System, and there is nothing to uninstall from Control Panel.注意:此特定服务器上没有使用此域\用户帐户的服务,并且唯一运行的 SW 服务是使用 LogOnAs Local System 的“SolarWinds Agent”,并且没有可以从控制面板卸载的内容。

SOLVED!解决了!

In Solarwinds, under the "Product Specific Settings > SAM Settings", the account 'domain\User' was attempting to use an incorrect Authentication Type and likely an incorrect password (not sure how long ago this was set up in our environment).在 Solarwinds 中,在“产品特定设置 > SAM 设置”下,帐户“域\用户”试图使用不正确的身份验证类型,并且可能使用了不正确的密码(不知道这是多久前在我们的环境中设置的)。

After changing the account and authentication type, we were able to quiet the false alerts.更改帐户和身份验证类型后,我们能够消除错误警报。

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM