/build/static/layout/Breadcrumb_cap_w.png

I'm receiving OverrideNameValue errors

I have just a couple of machines that have AMPAgent version 9.0.167 installed. Everytime the AMPWatchDog script is run with the -k switch (Konea checker) they send emails reporting the following errors:

[​2​0​1​9​-​0​4​-​0​1​.​0​9​:​2​8​:​2​9​]​[​A​M​P​W​a​t​c​h​D​o​g​:​O​v​e​r​r​i​d​e​N​a​m​e​V​a​l​u​e ] AgentConfig::OverrideNameValue - Invalid input name: ampport
[​2​0​1​9​-​0​4​-​0​1​.​0​9​:​2​8​:​2​9​]​[​A​M​P​W​a​t​c​h​D​o​g​:​O​v​e​r​r​i​d​e​N​a​m​e​V​a​l​u​e ] AgentConfig::OverrideNameValue - Invalid input name: crto
[​2​0​1​9​-​0​4​-​0​1​.​0​9​:​2​8​:​2​9​]​[​A​M​P​W​a​t​c​h​D​o​g​:​O​v​e​r​r​i​d​e​N​a​m​e​V​a​l​u​e ] AgentConfig::OverrideNameValue - Invalid input name: rto
[​2​0​1​9​-​0​4​-​0​1​.​0​9​:​2​8​:​2​9​]​[​A​M​P​W​a​t​c​h​D​o​g​:​O​v​e​r​r​i​d​e​N​a​m​e​V​a​l​u​e ] AgentConfig::OverrideNameValue - Invalid input name: wto


I'm not sure what the error is or where the Emails are being generated. Is this familiar to anyone?


Thank you, Q


0 Comments   [ + ] Show comments

Answers (1)

Answer Summary:
Posted by: SMal.tmcc 5 years ago
Red Belt
1

Top Answer

compare the C:\ProgramData\Quest\KACE\amp.conf file with a good machine.  Sounds  like that file may be incorrect.


Comments:
  • those are degraded entries that no longer exist in 9.x client - SMal.tmcc 5 years ago
    • Thank you! I'm going to look into that. - AndrewQ 5 years ago
      • That is exactly what the issue was. We are going to update our installs now to reflect the latest amp.comf. - AndrewQ 5 years ago
    • that is why I have this CIR
      ShellCommandTextReturn(cmd.exe /c type C:\programdata\quest\kace\amp.conf) - SMal.tmcc 5 years ago
 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ