Re: Activesync by Air not working after adding second Sharepoint Site!

Hi Fahlis,

Thank you for your update.

As you are unable to visit the OMA site from IE, it appears that this is a
server side issue reside in your Exchange server. It may be Exchange HTTP
virtual service has some problem and something is misconfigured. So OMA is
unable to work as expected. It appears that the Exchange server OMA
component is unable to provide valid information and the client cannot get
any valid data.

As it may be difficult for us to find the corrupted point, I think the
efficient way for this issue is to completely reset all the information. We
can remove and reinstall IIS and Exchange to reset all the information
regarding OMA. Prior to this, data backup is required.

Please try the following steps.

1. Back up all the SBS Exchange related information including mailboxes and
public folders. Refer to the following articles:

Backing Up and Restoring Windows Small Business Server 2003:
http://download.microsoft.com/download/b/d/8/bd8e1a40-d202-429a-8eb7-26300d6
2bcc9/BKU_BkupRstr.doc

2. Remove and reinstall IIS.

887305 How to reinstall Internet Information Services 6.0 in Windows Small
http://support.microsoft.com/?id=887305

In addition, if you have an additional SharePoint site there, you need to
back up it.

Please feel free to let me know if you have any questions or if you need
further assistance.

Best regards,

Crina Li (MSFT)

Microsoft CSS Online Newsgroup Support

Get Secure! - www.microsoft.com/security

=====================================================
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
=====================================================

This posting is provided "AS IS" with no warranties, and confers no rights.
--------------------
| From: Tony <>
| Subject: Re: Activesync by Air not working after adding second Sharepoint
Site!
| Date: Sun, 22 May 2005 08:15:38 +0200
| | Newsgroups: microsoft.public.windows.server.sbs
| | Hi again Crina,
|
| Ok,tried all your suggestions, results below.
|
| 1. Double Verify the Exchange server default Web site listener. Launch
| IIS
| >Manager, and open the properties of the Default Web Site. On General
tab,
| >make sure that it listen on "All Unassigned" IP addresses.
|
| It is listening on all unassigned IP´s.
|
----------------------------------------------------------------------------
-----
| 2. Check if you are able to visit the OMA site from a client with IE.
| You
| >can use http://server/oma to access OMA from IE. You may receive the
| >message to indicate an unsupported browser but you can click OK to check
| >further. Please let me know if you are able to view OMA information
| >successfully in IE.
| Cannot access oma this way,tried i t from our member TS Server.
| http://server/oma gave the result "http 400 unsupported request"
|
| whereas https://server/oma first gave me a logon window, after I logon
| it gives this " A System error has occurred while processing your
| request. Please try again. If the problem persists, contact your
| administrator"
|
----------------------------------------------------------------------------
------------
| 3. Please let me know if you have change the following information of
| the
| >OMA folder: Home directory and Authentication. Please verify if the home
| >directory path is pointing to the correct path and if basic
authentication
| >is enabled for the OMA folders.
|
| No change in Home Folder, authentication is set to basic (password is
| sent in clear" and on the line standarddomain I have our netbios name,
| about that sometimes on other servers I have seen the netbios name
| exchanged with a "/"...why is that?
| And is worth to try?
|
| I am leaning towards calling PSS but I´ll await your reply on this
| first to see if any more hints came up from the above information.
|
| thx much / Tony
|
|

.

Relevant Pages

  • Re: can access oma via browser, but mobile device wont work
    ... We have clients with larger networks and Exchange ... two addresses were the only addresses allowed to connect to the oma ... oma virtual directory is there and it has been set up by the wizard. ... that I am supposed to rebuild the server to fix this... ...
    (microsoft.public.windows.server.sbs)
  • RE: OMA
    ... To access the contents of a user's mailbox in Exchange Server 2003, ... It appeared meaningful for my problem, in fact the error was raised by OMA ... > invokeAttr, Binder binder, Objectparameters, CultureInfo culture, Boolean ...
    (microsoft.public.exchange.setup)
  • Re: Since sp2 installation, users are no longer able to access OMA on exchange 2003
    ... we are running an exchange 2003 cluster on windows 2003 servers front ... All are up to date with sp2 installed, starting with the front end server, ... Yes we are using blackberries to access OMA, although even when I am trying ... > And you aren't using BES or Blackberry desktop redirector BECAUSE... ...
    (microsoft.public.exchange2000.general)
  • RE: OMA not accessible
    ... If this is not the case, your Exchange ... Microsoft Outlook or Microsoft Outlook Web Access to create your user ... This problem may occur if the Exchange Server 2003 computer is heavily ... the OMA virtual directory may corrupted on SBS. ...
    (microsoft.public.windows.server.sbs)
  • Re: OMA will not work, argh!!! Please HELP
    ... the "URL that OMA builds"? ... that mail is my server and not mail.mycompany.com? ... > If you have modified the HTTP identities then make sure you either go back ... >> Request from user XXX@xxxxxxx resulted in the Microsoft ...
    (microsoft.public.exchange.setup)