Go Premium for a chance to win a PS4. Enter to Win

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 317
  • Last Modified:

Exchange 2003

Hi

Starting yesterday, my iphone users started reporting their email was down. Upon logging onto the server, I could see all services were up and running.

In the event log, I found 100's of these

Unexpected Exchange mailbox Server error: Server: [servername.domain.uk] User: [user@domainname.uk] HTTP status code: [503]. Verify that the Exchange mailbox Server is working correctly.

Upon restarting the System Attendant, everything started working.

This morning, same thing happened.

Stop/Start System Attendant, all is well.

Need to fix this by tomorrow am, any ideas why this keeps happening?

ta
Dai
0
daiwhyte
Asked:
daiwhyte
  • 7
  • 6
1 Solution
 
daiwhyteAuthor Commented:
Would it make any difference that we have just replaced two iphone 4s with iphone 5s?
0
 
ToonCooijmansCommented:
Are you using a SBS2003 installation?

Did you use this: https://www.testexchangeconnectivity.com/ ?

Are all your mobile devices iPhones, and are they all affected?

Ow, and in my experience, iPhone 4 or 5 work alike, no difference in ActiveSync...
0
 
daiwhyteAuthor Commented:
No its Windows Server 2003

No, I have not used the url you have suggested

All devices are Iphones.

I will try the url now.
0
VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

 
ToonCooijmansCommented:
Please do, let us know what results you're getting.
0
 
daiwhyteAuthor Commented:
ExRCA is testing Exchange ActiveSync.  
  The Exchange ActiveSync test failed.
   Test Steps
   Attempting to resolve the host name servername.domainname.co.uk in DNS.
  The host name resolved successfully.
   Additional Details
  IP addresses returned: xx.xx.xx.xx
 
 Testing TCP port 443 on host servername.domainname.co.uk to ensure it's listening and open.
  The specified port is either blocked, not listening, or not producing the expected response.
   Tell me more about this issue and how to resolve it
   Additional Details
  A network error occurred while communicating with the remote host.
 
 
Above is what the test website found.
We dont use port 443, we only use port  80 and have done so for the past 5 years.

Why would this issue pop up in the last two days?
0
 
ToonCooijmansCommented:
If i'm not mistaken, you can tell the Connectivity Analyzer to ignore SSL, perhaps it will also try on port 80...
0
 
daiwhyteAuthor Commented:
Tred that and its still reporting the same??
0
 
ToonCooijmansCommented:
Hrm, so that's not it...

If you visit http://<your external hostname or ip>/oma with a regular web-browser, what response do you get?
0
 
daiwhyteAuthor Commented:
Server Error in '/OMA' Application.
--------------------------------------------------------------------------------

Runtime Error
Description: An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.

Details: To enable the details of this specific error message to be viewable on remote machines, please create a <customErrors> tag within a "web.config" configuration file located in the root directory of the current web application. This <customErrors> tag should then have its "mode" attribute set to "Off".


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="Off"/>
    </system.web>
</configuration>
 

Notes: The current error page you are seeing can be replaced by a custom error page by modifying the "defaultRedirect" attribute of the application's <customErrors> configuration tag to point to a custom error page URL.


<!-- Web.Config Configuration File -->

<configuration>
    <system.web>
        <customErrors mode="RemoteOnly" defaultRedirect="mycustompage.htm"/>
    </system.web>
</configuration>
0
 
ToonCooijmansCommented:
Could you check if restarting the System Attendant resolves the issue with OMA?
0
 
daiwhyteAuthor Commented:
Ive never used OMA, we have only ever used OWA.

Restarting the system attendant has made no difference??
0
 
ToonCooijmansCommented:
Perhaps this URL: http://support.microsoft.com/kb/817379 is of use?

Happy Newyear :)
0
 
daiwhyteAuthor Commented:
Happy New year also. thank you.
0

Featured Post

Windows Server 2016: All you need to know

Learn about Hyper-V features that increase functionality and usability of Microsoft Windows Server 2016. Also, throughout this eBook, you’ll find some basic PowerShell examples that will help you leverage the scripts in your environments!

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now