Exchange 2007 Internal Error

[Heiko]

Hi

When we want to do an U-AIR with Exchange 2007 Sp3 we get the following error:
Unable to access mailbox:
The remote server returned an error: (500) Internal server error

Look at the following articles:
http://www.veeam.com/forums/viewtopic.php?f=2&t=5349

http://tigermatt.wordpress.com/2009/05/ ... ox-access/ (Removed the Deny access via powershell only)
Logged a support call with Veeam but we seem not to come to an solution.

Configurations:
Application Group with DC (DNS, GC, DHCP) and mail server. When we enable the script for testing the Active Directory boots up 100% but exchange fails with the following error: Mail Server script, path VmConnectionTester.exe, ErrCode 10061
If we disable the script testing an boot the server all works 100%. When we log onto the restored lab server via vCenter we are able to access the mailboxes via OWA (used the logged on admin account mailbox). Means exchange does start up.

Veeam B&R version 5.0.2 with theExchange U-ARI version 5.0.2.235.

Can anyone please advise on what else we could troubleshoot?

Thank you

[Gostev]

Sounds like firewall issue, or custom SMTP port used. Just go ahead and disable script testing, as this is not really required for U-AIR (only necessary for SureBackup).

Please note that you must include support case ID when posting about any technical issues, otherwise your post will be deleted, as explained when you click New Topic.

Thanks.

[Heiko]

Exchange is installed on Windows 2003 64bit Enterprise and firewall is off.
The receive connector is on port 25. Am able to telnet to port 25

Suport ID#5131753

[atifhanif]

I worked with Veeam Support, we made the following changes which helped us get passed this issue

1. Removed the script test to get passed the issue "VMConnectionTester.exe ErrCode:10061" so the environment does not get shutdown & stays up for further testing

2. Proceed and Test Application object restore specifying the CAS Server using the FQDN i.e. server.domain.local rather than the IP or ServerName, this worked for us, Make sure you Domain Controller is part of the App Group and ensure you have good communication between the Exchange VM & the DC VM i.e. ping, nslookup etc

3. Increase the timeout for the Application Group - Edit VM Guest\Startup Options\I am currently trying Max allowed boot time set to 3000 & app init timeout at 720

Hope this helps you

[Gostev]

Thanks for the update!