Re: Remedy 8.1 Email Engine - ERROR (623)
yea, resetting it in the server config only changes the server password, doesn't update any of the clients to tell them what the password is :). On Wed, Nov 26, 2014 at 10:21 AM, Sanford, Claire < claire.sanf...@memorialhermann.org> wrote: > ** > > Thanks LJ!! > > > > That is what I did. I hard set it in the emaildaemon.properties file and > it worked! I had reset it several times in the server config area. I > think for some reason it was not talking to or updating the > emaildaemon.properties file. > > > > Sometimes all you have to do is ask the world the question and you figure > it out! > > > > Claire > > > > > > *From:* Action Request System discussion list(ARSList) [mailto: > arslist@ARSLIST.ORG] *On Behalf Of *LJ LongWing > *Sent:* Wednesday, November 26, 2014 11:12 AM > *To:* arslist@ARSLIST.ORG > *Subject:* Re: Remedy 8.1 Email Engine - ERROR (623) > > > > ** > > Claire, > > The authentication failed message is simply that the password it's trying > is not correct (obviously), so, you could try re-setting the password in > the server config to what you think it should be, and if that doesn't work, > you can reset the password in the emaildaemon.properties file > > > > https://docs.bmc.com/docs/display/public/ars81/EmailDaemon.properties+file > > > > Follow the directions in that link, utilizing the -p parameter to reset > the password the daemon is trying to utilize. > > > > On Wed, Nov 26, 2014 at 10:01 AM, Sanford, Claire < > claire.sanf...@memorialhermann.org> wrote: > > ** > > I have 8.1 installed on my new test/prod server and the email engine > starts, but it does not authenticate. > > > > I have checked the user name and password in the service and it still > won’t authenticate. > > > > I have looked in the “normal” areas. > > > > Config.properties > > Ar.cfg > > Armonitor.cfg > > emaildaemon.properties > > > > And found nothing out of the ordinary. I made sure everything matched > what is in my current (working) emaildaemon.properties file matched in the > non-working one. > > > > This is the content of my mail logs: > > STOUT.log > > > > Checking connection to server: REMEDYAPP1.mh.org ... > > ERROR (623): Authentication failed; > > > > Cannot connect. > > Checking connection to server: REMEDYAPP1.mh.org ... > > > > Cannot connect. > > > > > > > > STDERR.log > > ERROR (623): Authentication failed; > > at > com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source) > > at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source) > > at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown > Source) > > at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source) > > at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source) > > at > com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299) > > at > com.bmc.arsys.emaildaemon.LoggingModule.setUserInfo(LoggingModule.java:767) > > at > com.bmc.arsys.emaildaemon.EmailDaemon.startLoggingModule(EmailDaemon.java:125) > > at > com.bmc.arsys.emaildaemon.EmailDaemon.(EmailDaemon.java:96) > > at > com.bmc.arsys.emaildaemon.EmailDaemon.newInstance(EmailDaemon.java:161) > > at > com.bmc.arsys.emaildaemon.EmailDaemon.startMonitor(EmailDaemon.java:903) > > at > com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:609) > > at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324) > > ERROR (623): Authentication failed; > > at > com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source) > > at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source) > > at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown > Source) > > at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source) > > at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source) > > at com.bmc.arsys.api.ARServerUser.login(Unknown Source) > > at > com.bmc.arsys.emaildaemon.MonitorModule.checkServer(MonitorModule.java:307) > > at > com.bmc.arsys.emaildaemon.MonitorModule.doWork(MonitorModule.java:99) > > at com.bmc.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:302) > > at > com.bmc.arsys.emaildaemon.MonitorModule.run(MonitorModule.java:26) > > at java.lang.Thread.run(Unknown Source) > > ERROR (623): Authentication failed; >
Re: Remedy 8.1 Email Engine - ERROR (623)
Thanks LJ!! That is what I did. I hard set it in the emaildaemon.properties file and it worked! I had reset it several times in the server config area. I think for some reason it was not talking to or updating the emaildaemon.properties file. Sometimes all you have to do is ask the world the question and you figure it out! Claire From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of LJ LongWing Sent: Wednesday, November 26, 2014 11:12 AM To: arslist@ARSLIST.ORG Subject: Re: Remedy 8.1 Email Engine - ERROR (623) ** Claire, The authentication failed message is simply that the password it's trying is not correct (obviously), so, you could try re-setting the password in the server config to what you think it should be, and if that doesn't work, you can reset the password in the emaildaemon.properties file https://docs.bmc.com/docs/display/public/ars81/EmailDaemon.properties+file Follow the directions in that link, utilizing the -p parameter to reset the password the daemon is trying to utilize. On Wed, Nov 26, 2014 at 10:01 AM, Sanford, Claire mailto:claire.sanf...@memorialhermann.org>> wrote: ** I have 8.1 installed on my new test/prod server and the email engine starts, but it does not authenticate. I have checked the user name and password in the service and it still won’t authenticate. I have looked in the “normal” areas. Config.properties Ar.cfg Armonitor.cfg emaildaemon.properties And found nothing out of the ordinary. I made sure everything matched what is in my current (working) emaildaemon.properties file matched in the non-working one. This is the content of my mail logs: STOUT.log Checking connection to server: REMEDYAPP1.mh.org<http://REMEDYAPP1.mh.org> ... ERROR (623): Authentication failed; Cannot connect. Checking connection to server: REMEDYAPP1.mh.org<http://REMEDYAPP1.mh.org> ... Cannot connect. STDERR.log ERROR (623): Authentication failed; at com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source) at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source) at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source) at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source) at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source) at com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299) at com.bmc.arsys.emaildaemon.LoggingModule.setUserInfo(LoggingModule.java:767) at com.bmc.arsys.emaildaemon.EmailDaemon.startLoggingModule(EmailDaemon.java:125) at com.bmc.arsys.emaildaemon.EmailDaemon.(EmailDaemon.java:96) at com.bmc.arsys.emaildaemon.EmailDaemon.newInstance(EmailDaemon.java:161) at com.bmc.arsys.emaildaemon.EmailDaemon.startMonitor(EmailDaemon.java:903) at com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:609) at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324) ERROR (623): Authentication failed; at com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source) at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source) at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source) at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source) at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source) at com.bmc.arsys.api.ARServerUser.login(Unknown Source) at com.bmc.arsys.emaildaemon.MonitorModule.checkServer(MonitorModule.java:307) at com.bmc.arsys.emaildaemon.MonitorModule.doWork(MonitorModule.java:99) at com.bmc.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:302) at com.bmc.arsys.emaildaemon.MonitorModule.run(MonitorModule.java:26) at java.lang.Thread.run(Unknown Source) ERROR (623): Authentication failed; at com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source) at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source) at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source) at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source) at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source) at com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299) at com.bmc.arsys.emaildaemon.EmailDaemon.setUserInfo(EmailDaemon.java:947) at com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:619) at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324) Nov 26, 2014 10:24:06 AM com.bmc.arsys.emaildaemon.LoggingModule doWork SEVERE: Authentication failed _ARSlist: "Where the Answers Are" and have been for 20 years_ _ARSlist: "Where the Answers Are" and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archive
Re: Remedy 8.1 Email Engine - ERROR (623)
Claire, The authentication failed message is simply that the password it's trying is not correct (obviously), so, you could try re-setting the password in the server config to what you think it should be, and if that doesn't work, you can reset the password in the emaildaemon.properties file https://docs.bmc.com/docs/display/public/ars81/EmailDaemon.properties+file Follow the directions in that link, utilizing the -p parameter to reset the password the daemon is trying to utilize. On Wed, Nov 26, 2014 at 10:01 AM, Sanford, Claire < claire.sanf...@memorialhermann.org> wrote: > ** > I have 8.1 installed on my new test/prod server and the email engine > starts, but it does not authenticate. > > I have checked the user name and password in the service and it still > won’t authenticate. > > I have looked in the “normal” areas. > > Config.properties > Ar.cfg > Armonitor.cfg > emaildaemon.properties > > And found nothing out of the ordinary. I made sure everything matched > what is in my current (working) emaildaemon.properties file matched in the > non-working one. > > This is the content of my mail logs: > STOUT.log > > Checking connection to server: REMEDYAPP1.mh.org ... > ERROR (623): Authentication failed; > > Cannot connect. > Checking connection to server: REMEDYAPP1.mh.org ... > > Cannot connect. > > > > STDERR.log > ERROR (623): Authentication failed; > at > com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source) > at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source) > at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown > Source) > at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source) > at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source) > at > com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299) > at > com.bmc.arsys.emaildaemon.LoggingModule.setUserInfo(LoggingModule.java:767) > at > com.bmc.arsys.emaildaemon.EmailDaemon.startLoggingModule(EmailDaemon.java:125) > at > com.bmc.arsys.emaildaemon.EmailDaemon.(EmailDaemon.java:96) > at > com.bmc.arsys.emaildaemon.EmailDaemon.newInstance(EmailDaemon.java:161) > at > com.bmc.arsys.emaildaemon.EmailDaemon.startMonitor(EmailDaemon.java:903) > at > com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:609) > at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324) > ERROR (623): Authentication failed; > at > com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source) > at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source) > at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown > Source) > at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source) > at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source) > at com.bmc.arsys.api.ARServerUser.login(Unknown Source) > at > com.bmc.arsys.emaildaemon.MonitorModule.checkServer(MonitorModule.java:307) > at > com.bmc.arsys.emaildaemon.MonitorModule.doWork(MonitorModule.java:99) > at com.bmc.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:302) > at > com.bmc.arsys.emaildaemon.MonitorModule.run(MonitorModule.java:26) > at java.lang.Thread.run(Unknown Source) > ERROR (623): Authentication failed; > at > com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source) > at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source) > at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown > Source) > at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source) > at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source) > at > com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299) > at > com.bmc.arsys.emaildaemon.EmailDaemon.setUserInfo(EmailDaemon.java:947) > at > com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:619) > at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324) > Nov 26, 2014 10:24:06 AM com.bmc.arsys.emaildaemon.LoggingModule doWork > SEVERE: Authentication failed > > _ARSlist: "Where the Answers Are" and have been for 20 years_ ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
Remedy 8.1 Email Engine - ERROR (623)
I have 8.1 installed on my new test/prod server and the email engine starts, but it does not authenticate. I have checked the user name and password in the service and it still won't authenticate. I have looked in the "normal" areas. Config.properties Ar.cfg Armonitor.cfg emaildaemon.properties And found nothing out of the ordinary. I made sure everything matched what is in my current (working) emaildaemon.properties file matched in the non-working one. This is the content of my mail logs: STOUT.log Checking connection to server: REMEDYAPP1.mh.org ... ERROR (623): Authentication failed; Cannot connect. Checking connection to server: REMEDYAPP1.mh.org ... Cannot connect. STDERR.log ERROR (623): Authentication failed; at com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source) at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source) at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source) at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source) at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source) at com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299) at com.bmc.arsys.emaildaemon.LoggingModule.setUserInfo(LoggingModule.java:767) at com.bmc.arsys.emaildaemon.EmailDaemon.startLoggingModule(EmailDaemon.java:125) at com.bmc.arsys.emaildaemon.EmailDaemon.(EmailDaemon.java:96) at com.bmc.arsys.emaildaemon.EmailDaemon.newInstance(EmailDaemon.java:161) at com.bmc.arsys.emaildaemon.EmailDaemon.startMonitor(EmailDaemon.java:903) at com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:609) at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324) ERROR (623): Authentication failed; at com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source) at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source) at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source) at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source) at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source) at com.bmc.arsys.api.ARServerUser.login(Unknown Source) at com.bmc.arsys.emaildaemon.MonitorModule.checkServer(MonitorModule.java:307) at com.bmc.arsys.emaildaemon.MonitorModule.doWork(MonitorModule.java:99) at com.bmc.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:302) at com.bmc.arsys.emaildaemon.MonitorModule.run(MonitorModule.java:26) at java.lang.Thread.run(Unknown Source) ERROR (623): Authentication failed; at com.bmc.arsys.apitransport.ApiProxyJRpcBase.verifyStatus(Unknown Source) at com.bmc.arsys.apitransport.ApiProxyJRpcBase.a(Unknown Source) at com.bmc.arsys.apitransport.ApiProxyJRpcBase.arCall(Unknown Source) at com.bmc.arsys.api.ProxyJRpc.ARVerifyUser(Unknown Source) at com.bmc.arsys.api.ARServerUser.verifyUser(Unknown Source) at com.bmc.arsys.emaildaemon.EmailUtil.createARServerUser(EmailUtil.java:1299) at com.bmc.arsys.emaildaemon.EmailDaemon.setUserInfo(EmailDaemon.java:947) at com.bmc.arsys.emaildaemon.EmailDaemon.executeComandLine(EmailDaemon.java:619) at com.bmc.arsys.emaildaemon.EmailDaemon.main(EmailDaemon.java:324) Nov 26, 2014 10:24:06 AM com.bmc.arsys.emaildaemon.LoggingModule doWork SEVERE: Authentication failed ___ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
