Thanks for the reply Eli.
It wasn't working before, I figured out the problem though. I don't have
access to the box, have to work on it through someone else. They had put
the wrong Application Service password in when we installed. Had them
change the Application Service password to match the one they put in for
the email install and it started working heh.

------------- 

Dylan Wheeler
Production Control Analyst Principal 
IT Operations 
Downey Savings & Loan Association, F.A. 
Email: [EMAIL PROTECTED]



-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Eli Schilling
Sent: Wednesday, December 12, 2007 9:39 AM
To: [email protected]
Subject: Re: 7.0.1 Email Authentication Problems


Dylan,
 
Did it stop working before or directly after the re-install?  In the
installation log are there any errors that mention something like
temp.arx failed to import...something about unique key constraint
(sorry, I can't remember the exact verbiage).
 
During the re-install it creates serveral import files that it uses to
create the AR_IN and AR_OUT mailbox records in the AR System Email
Mailbox Configuration form.  If you didn't delete these records prior to
the re-install it will fail to import them.  Its possible something was
corrupted and you need to re-create your config records in the
aforementioned form.
 
Cheers!
Eli

________________________________

From: Action Request System discussion list(ARSList) on behalf of
Wheeler, Dylan
Sent: Wed 12/12/2007 9:29 AM
To: [email protected]
Subject: 7.0.1 Email Authentication Problems


** 
I'm trying to track down an authentication problem with my dev server.
Up until this week it was working fine. I had to reinstall the email
engine this week and now it wont send out any emails. 
 
I verified that the service is starting as the AD user.
I send an email to the AD user, log in to the server as the AD user and
I am able to open outlook and see the mail I verified that my email
configuration shows the right profile inside of Remedy.
 
This is what i see in stderr.log
 
Dec 12, 2007 10:45:40 AM com.remedy.arsys.emaildaemon.LoggingModule
doWork
SEVERE: Authentication failed 
Dec 12, 2007 11:15:40 AM com.remedy.arsys.emaildaemon.LoggingModule
doWork
SEVERE: Authentication failed 
Dec 12, 2007 11:45:40 AM com.remedy.arsys.emaildaemon.LoggingModule
doWork
SEVERE: Authentication failed 
Dec 12, 2007 12:15:40 PM com.remedy.arsys.emaildaemon.LoggingModule
doWork
SEVERE: Authentication failed
 
7.0.1 Patch 5 on Windows
 
Any ideas where it's getting the bad auth info? 

------------- 

Dylan Wheeler
Production Control Analyst Principal 
IT Operations 
Downey Savings & Loan Association, F.A. 
Email: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]>  

This message and any attachments are for the intended recipient(s) only
and may contain privileged, confidential and/or proprietary information
about Downey Savings or its customers, which Downey Savings does not
intend to disclose to the public. If you received this message by
mistake, please notify the sender by reply e-mail and delete the message
and attachments.

 
__20060125_______________________This posting was submitted with HTML in
it___ 

________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum
Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"

Reply via email to