Re: SEVERE! Microsoft Exchange Server computer is not available!

[strauss]

** A proper Outlook profile for the Exchange server does contain a full qualified domain name for the actual mail server.  It also needs to be the default profile for Outlook while logged in to the AR Server as the email account. Christopher Strauss, MSLS Remedy Database Administrator University of North Texas Computing Center http://remedy.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Kaiser Norm E CIV USAF 96 CG/SCWOE Sent: Thursday, May 04, 2006 3:42 PM To: arslist@ARSLIST.ORG Subject: SEVERE! Microsoft Exchange Server computer is not available! ** Hi everyone:   My email engine has mysteriously stopped working.  I am running Remedy 5.1.2 on Windows 2003 Server SP2 with the Outlook 2003 client.  I have Outgoing and Incoming entries set in the Mailbox Configuration form.  I am using MAPI and my mail server is a Microsoft Exchange 5.5 server.  The problem is, when I start the E-mail Engine service, the service starts fine, but I get errors in the stderr.log:    May 3, 2006 5:09:38 PM com.remedy.mail.mapi.MAPINative getStore SEVERE: The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. javax.mail.MessagingException: The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.             at com.remedy.mail.mapi.MAPINative.getStore(Native Method)             at com.remedy.mail.mapi.MAPIStore.connect(MAPIStore.java:145)             at com.remedy.mail.mapi.MAPIStore.connect(MAPIStore.java:165)             at com.remedy.arsys.emaildaemon.ReceiverModule.initializeIncommingMailbox(ReceiverModule.java:1093)             at com.remedy.arsys.emaildaemon.ReceiverModule.initialization(ReceiverModule.java:285)             at com.remedy.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:263)             at java.lang.Thread.run(Unknown Source) May 3, 2006 5:09:38 PM com.remedy.mail.mapi.MAPINative getTransport SEVERE: The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. javax.mail.MessagingException: The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.             at com.remedy.mail.mapi.MAPINative.getTransport(Native Method)             at com.remedy.mail.mapi.MAPITransport.connect(MAPITransport.java:411)             at com.remedy.mail.mapi.MAPITransport.connect(MAPITransport.java:423)             at com.remedy.arsys.emaildaemon.SenderModule.openTransport(SenderModule.java:110)             at com.remedy.arsys.emaildaemon.CreatorModule.doWork(CreatorModule.java:360)             at com.remedy.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:267)             at java.lang.Thread.run(Unknown Source) May 3, 2006 5:09:38 PM com.remedy.mail.mapi.MAPINative getStore SEVERE: The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. javax.mail.MessagingException: The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.             at com.remedy.mail.mapi.MAPINative.getStore(Native Method)             at com.remedy.mail.mapi.MAPIStore.connect(MAPIStore.java:145)             at com.remedy.mail.mapi.MAPIStore.connect(MAPIStore.java:165)             at com.remedy.arsys.emaildaemon.ReceiverModule.initializeIncommingMailbox(ReceiverModule.java:1093)             at com.remedy.arsys.emaildaemon.ReceiverModule.initialization(ReceiverModule.java:285)             at com.remedy.arsys.emaildaemon.ReceiverModule.doWork(ReceiverModule.java:127)             at com.remedy.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:267)             at java.lang.Thread.run(Unknown Source) May 3, 2006 5:09:38 PM com.remedy.mail.mapi.MAPINative getStore SEVERE: The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance. javax.mail.MessagingException: The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.             at com.remedy.mail.mapi.MAPINative.getStore(Native Method)             at com.remedy.mail.mapi.MAPIStore.connect(MAPIStore.java:145)             at com.remedy.mail.mapi.MAPIStore.connect(MAPIStore.java:165)             at com.remedy.arsys.emaildaemon.ReceiverModule.initializeIncommingMailbox(ReceiverModule.java:1093)             at com.remedy.arsys.emaildaemon.ReceiverModule.doWork(ReceiverModule.java:153)             at com.remedy.arsys.emaildaemon.ThreadBase.run(ThreadBase.java:267)             at java.lang.Thread.run(Unknown Source) May 3, 2006 5:09:38 PM com.remedy.mail.mapi.MAPINative getStore SEVERE: The Microsoft Exchange Server computer is not available.  Either there are network problems or the Microsoft Exchange Server computer is down for maintenance.   So it appears to me that the E-mail Engine service is not able to locate the Exchange server, which is a mystery because using MAPI there is no way for me to specify the name of the Exchange server.  Isn't that discovered through the email profile?   I have logged on with the NT domain account that owns Remedy's mailbox and am able to open the mailbox using the appropriate Outlook profile just fine.  I also sent a message from that mailbox just to be sure.  No problem.   Here's the real interesting part--STARTEMAIL.BAT works just fine! That is, I stop the Email Engine service, double click STARTEMAIL.BAT, and email starts flowing just as it's supposed to.  I kill STARTEMAIL.BAT and restart the service and get the same errors in the error log.  So the problem MUST be with the Email Engine service.   What's changed recently? My Exchange administrators recently completed a mailbox migration from the old email server where the Remedy mailbox used to live to a new server with a new name.  To account for that, I deleted the old Outlook profile and recreated it.   Also, I just recently upgraded the JRE from 1.4.2_01 to 1.4.2._10--HOWEVER, that was weeks ago and the email engine has been running fine since.   I strongly suspect the problem is tied to the mailbox move from the old email server to the new, but I don't know how to research that theory since I can't specify the server name anywhere when using MAPI.   I know several folks have experienced this problem before because I've seen postings for it, but I haven't found any responses with possible solutions   Thanks, Norm __20060125_______________________This posting was submitted with HTML in it___ __20060125_______________________This posting was submitted with HTML in it___