XI R2 SP4 and Exchange 2007

[Former Member]

Hi, our networking group recently upgraded exchange from 2003 to 2007 and we've been having big problems with emailing object instances since then. I realize 2007 may not be a supported data source, but the supported platforms document does not have a section on supported platforms for SMTP purposes. Or, if it does it is VERY unclear where in that document this information is at.

Anyway, the situation is this. Previously we had a number of crystal reports that every two week "run" and create an email with an attachment in a pdf, text, or excel format and emails it to email addresses outside of my company. Since the cutover to 2007 we can only send emails to "internal" email address. In other words, just to emails that are user@ourdomain. Any attempt to mail outside returns a failure with address error. CrystalEnterprise.Smtp: SMTP_E_MAILBOX_UNAVAILABLE_2(550).

The group in charge of exchange can't find anything wrong with relaying or permissions for the WinAD account being used by BOE to log in to the mail server but we're still getting this problem no matter what they tweak. I'm hoping someone here can help.

Also, can anyone point me to how to actually create a support incident (or whatever SAP/Business Objects calls it)? I clicked on what I thought was a link to do so and was taken to these forums. The only other obvious looking choice was to something about reporting an error and that didn't look right either.

[Former Member]

My company is in the process of migrating to Exchange 2007. Since the process started, I cannot distribute reports via e-mail to internal e-mail addresses with our BOE XI R2 installation. I am receiving the error SMTP_E_MAILBOX_UNAVAILABLE_2(550). I have tested this with an e-mail account set up specifically for sending e-mails and attachments from BOE. I have also tested with my own e-mail account. In both cases, these mailboxes are accessable outside of BOE. When using them with authentication set to "Login" I am receiving the 550 Mailbox unavailable error.

Any information on this issue would be appreciated.

[Former Member]

Charles,

reporting an error 

-- Yes, that's how you submit a trouble ticket.

Back to your problem, can you sign in as the WinAD account and simulate sending an e-mail with attachment? If so, does that work? In your troubleshooting steps, have you also contacted Microsoft to see if they can shed any light? Why did you all upgrade to Exchange 2007 (I'm sure you're wondering why about now too)?

Good luck!

John

[Former Member]

Hi, well I ended up finding just a little farther down a post about sending email from Crystal Enterprise. The problem seemed sort of similar and in there was a link to a SMTP test at http://support.microsoft.com/kb/323350 which gave us a result of "550 5.7.1 Unable to relay" when we gave it an external email address. So we knew it wasn't a BOE problem for sure. It turns out that our networking group found that exchange 2007 handles SMTP a little different than 2003 and that while the built in listening function for outside SMTP traffic works just fine for that, we had to create a new receiving listener for internal SMTP traffic for relaying to outside addresses. Once they created that, everything worked great. As far as the upgrade reason, our company has a policy of hardware/software refresh every 3 years, and it's been 3 years+ apparently since the last upgrade (I recently started here).

[BasicTek]

Thanks for the detailed explanation Charles. I was typing a response of using a packet scanner like wireshark to verify if the SMTP requests were being sent by the job server. I guess the answer to that was yes. Good to know.

[Former Member]

Yes actually our networking group already tried a packet sniffer before this. I'm not all that familiar with how smtp works so I'm not sure what they should have been seeing, but when sending an external email which was failiing due to the relay they saw no traffic at all. As expected, internal emails which did work generated lots of traffic. Even stranger was we could put "internal email; external email" in the To: field and an email would go out to the internal address and BOE would register the instance as a success, but nothing would go out externally. So it was like BOE was saying well one worked so it went out and give it a status of "success".

[Former Member]

I have a simple document on SMTP setup and testing.mail me - anils.bo at gmail dot com