hi guys, heres my situation. We have 2 exchange server. Exchange A the original one and we recently added a new one for our VPN clients ExchangeB. Problem is user with mail boxes on Exchange B can not access their mailboxes from Exchange A thru //exchangeA/exchagne. Bigger problem is by using //exchangeB/ exchange i can access mailboxes on exchange A but can not access mailboxes on exhange B the local server. Havnt yet tested from outside cause i think it should work internally first. Now i made Exchange B as the front end server as i could not make Exchange A the front end server cause of Reciepent Update Services running on it. Wht am I missing here ppl.. is there a virtual directory i need to make on Exchange A so it will relay to Exchange B. which i do not think is problem cause if relays fine for mailboxes on B from A... or is it an IIS issue ?? Please help me .. clients are getting impatient Thanks in advance,
Outlook Web access error HTTP/1.1 503 Service Unavailable
4 posts
• Page 1 of 1
- ASP
- wxWindows
- MS EXCEL
- sharepoint
- Microsoft publisher
- mysql
- printer
- unix
- fireworks
- Table PC
Jump to:
- 1. OWA and Address book
Hi When clicking on the Address Book icon in OWA, I can display names from the GAL. Further double-clicking on a name will give me the details (or properties) of that name. On one PC (w/ Win XP SP2, IE6), I have no problem opening the properties of a name. On another PC (w/Win XP SP2, IE7), I can't open the properties. It gives me an error: "Internet Explorer Script Error: An error has occurred in the script on this page. Line: 997 Char : 3 Error: Object doesn't support this property or method Code: 0 URL: https://ourdomain/exchange/... Do you want to continue running the scripts on this page ? YES or NO" I ran all updates and everything. How can I solve this ? Thanks Steve - 2. Operation Failed
Users are reporting that when they try to send an email they get an Operation Failed error message. That's all the error says and then after a few minutes they will be able to send email again. If you try to send email to other users while this is happening the emails will go through. Thanks in advance. - 3. OWA 2003 Virtual Directories
I'm running OWA on the same box as my Exchange 2003 server. I am wondering how I can move the virtual directories, or perhaps alter the IIS config, so that I don't have to type the "/exchange" in the URL. I would think this is very common, but I can't find any docs on it. Thanks. J
Next
Outlook Web access error HTTP/1.1 503 Service Unavailable
by k_vanjara » Wed, 15 Aug 2007 06:57:32 GMT
Re: Outlook Web access error HTTP/1.1 503 Service Unavailable
by Ed Crowley [MVP] » Wed, 15 Aug 2007 11:24:01 GMT
If ExchangeB is not a front-end server, it will try to redirect the session to ExchangeA. If ExchangeB is a front-end server it cannot host mailboxes. If you have two mailbox servers and want just one server to handle all OWA requests, that server will have to be front-end server ExchangeC. -- Ed Crowley MVP - Exchange "Protecting the world from PSTs and brick backups!"
Re: Outlook Web access error HTTP/1.1 503 Service Unavailable
by k_vanjara » Thu, 16 Aug 2007 06:46:31 GMT
Thanks for the reply. . Let me see wht changes to make .. can u answer another small question. suppose i have to exchange servers like i mentioned but dint have the front end / back end senario. can i log in one server names //exchangeA/ exchange and access mailboxes on ExchangeB ? if yes how.. Thanks again.
Re: Outlook Web access error HTTP/1.1 503 Service Unavailable
by Ed Crowley [MVP] » Thu, 16 Aug 2007 07:16:24 GMT
Your users can log on as http://exchangea/exchange, or http://exchangeb/exchange, and Exchange will redirect the session to the other server if the mailbox is there. If you expect to do this from the Internet, then you're going to have to have some name resolution method to allow the client to get from one to the other. That could be as simple as entries in the hosts file (even if that's a pain to manage). If you have a front-end server, all users can log on to http://frontend/exchange and the URL will stay the same regardless of the mailbox server. -- Ed Crowley MVP - Exchange "Protecting the world from PSTs and brick backups!"
Similar Threads:
1.Outlook Web access error HTTP/1.1 503 Service Unavailable
hi guys, heres my situation. We have 2 exchange server. Exchange A the original one and we recently added a new one for our VPN clients ExchangeB. Problem is user with mail boxes on Exchange B can not access their mailboxes from Exchange A thru //exchangeA/exchagne. Bigger problem is by using //exchangeB/ exchange i can access mailboxes on exchange A but can not access mailboxes on exhange B the local server. Havnt yet tested from outside cause i think it should work internally first. Now i made Exchange B as the front end server as i could not make Exchange A the front end server cause of Reciepent Update Services running on it. Wht am I missing here ppl.. is there a virtual directory i need to make on Exchange A so it will relay to Exchange B. which i do not think is problem cause if relays fine for mailboxes on B from A... or is it an IIS issue ?? Please help me .. clients are getting impatient Thanks in advance,
2.Outlook Web Access - HTTP/1.1 503 Service Unavailable
3.That HTTP/1.1 503 Service Unavailable frustrating error!
I have a new installation of 4 Windows Server 2003 servers with Exchange 2003 running on them. One is a front-end server and the rest are back-end servers. I try to logon to the Outlook Web Access of the front-end and it works only for mailboxes of one of the back-end servers. When I try a mailbox which is on either of the two remaining back-end servers it gives me the famous HTTP/1.1 503 Service Unavailable error. If I try to logon directly to the OWA of either of the two back-end severs not working it works fine. I have read lots of newsgroups on the subject but I could not find a solution. Does anyone know how this problem can be resolved?
4.HTTP/1.1 Error 503 Service Unavailable
Hi everybody I have this problem in Exchange 2000/SP3, when i try to open the public folder in exchange system manager : <The HTTP service used by Public Folders is not available, possible causes are that Public stores are not mounted and the Information Store service is not running.> ID no: c1030af3 Exchange System Manager The IIS, IS, DATABASES is running and mounted. The exchange virtual directory is working fine, but the public not (HTTP/1.1 SERVICE ANAVAIBLE ERROR 503). When i create a new public folder in exchange console and the iis, is working fine. I was run the isinteg to recover any error. I make a defrag in databases Everything is ok, but i think that i messed up with permissions in folders (inetpub\wwwroot, c:\program files\exchange, c:\documends and settings) Any help i'll appreciate, thanks nikos.
5.HTTP/1.1 503 Service Unavailable error...Once again!
6. HTTP/1.1 503 Service Unavailable Errors Changing Password in OWA
4 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 79 guest