Sign in
 
HomeOnline20132010Other VersionsLibraryForumsGalleryEHLO Blog
TechCenter >
> 
> 
Problems with OAB after migration

Unanswered Problems with OAB after migration

  • Tuesday, August 07, 2012 4:04 PM
     
     
    Sign In to Vote
    0

    We are running a small hosted solution and were recently on Exchange 2007.  After installing Exchange 2010 w/ SP2, we migrated all the client DB's to the new server, however, whenever I shut down the Exchange 2007 box, the clients who were on the 2007 server get an error about not being able to access the Offline Address Book.

    After running Get-OfflineAddressBook -Identity "Hosted Company OAB" | fl I get the following result:

    Server                           : 2010Servername
    AddressLists                     : {\Hosted Company AL}
    Versions                         : {Version2, Version3, Version4}
    IsDefault                        : False
    PublicFolderDatabase             : 2007ServerName\Second Storage Group\Public Folder Database
    PublicFolderDistributionEnabled  : True
    GlobalWebDistributionEnabled     : False

    As you can see, the issue seems to be that the Public Folder DB is still pointing to the OLD 2007 server.  I probably should know how to move it, but can't seem to find a setting anywhere.

     

All Replies

  • Wednesday, August 08, 2012 9:50 PM
     
     
    Sign In to Vote
    0

    Try this

    http://technet.microsoft.com/en-us/library/bb125184.aspx

    DJ Grijalva | MCITP: EMA 2007/2010 SPA 2010 | www.persistentcerebro.com

     
  • Thursday, August 09, 2012 7:01 PM
     
     
    Sign In to Vote
    0

    Tried it, but this is the result:

    The offline address book "COMPANY OAB" can't be moved because it is already generated on the target server Servername.

     
  • Wednesday, August 15, 2012 6:08 PM
     
     
    Sign In to Vote
    1
    Create a new OAB, assign it to the users who need it with an ABP and ignore the old one.
     
  • Thursday, August 16, 2012 12:46 PM
     
     
    Sign In to Vote
    0

    I did what Greg suggested and users now get this:

    7:25:53 Microsoft Exchange offline address book

    7:25:53           Not downloading Offline address book files.  A server (URL) could not be located.

    7:25:53  0X80004005

     
  • Thursday, August 16, 2012 3:19 PM
     
     
    Sign In to Vote
    0
    Use Outlook to check autodiscover (test email autoconfig from teh tray icon) and make sure you are getting the correct OAB url back.
     
  • Friday, August 24, 2012 2:05 PM
     
     
    Sign In to Vote
    0
    When running the test, it's trying to hit it http://localserver address/OAB/path and not https?.?  Should it be HTTPS or should it be the External path of https://publicURL/oab?
    • Edited by TBone1985 Friday, August 24, 2012 2:09 PM
    •  
     
  • Friday, August 24, 2012 2:57 PM
     
     
    Sign In to Vote
    0

    Ok, so you get pack paths (which is good), but the client can't connect to them (which is an easier issue to fix).

    So the internalURL on the OAB Virtual Directory will be what clients inside the firewall use to get the OAB, and the externalURL value, the value external clients, outside the firewall will use.

    If you are publishing exchange through some kind of load balancer and only allowing SSL connections (which you should), then just add the extra s to the externalURL path and make sure that path makes it through the firewall and to the CAS.

    Get-OabVirtualDirectory | Set-OABVirtualDirectory -Externalurl https://domain.com/OAB

    for example.

     
  • Friday, August 24, 2012 3:02 PM
     
     
    Sign In to Vote
    0

    Thanks for the quick reply.

    I've already got the external URL and internal URL correct, but still get the error:

    InternalUrl                     : http://servername.hosted.local/OAB
    InternalAuthenticationMethods   : {WindowsIntegrated}
    ExternalUrl                     : https://mail.publicurl.com/OAB
    ExternalAuthenticationMethods   : {WindowsIntegrated}

     
  • Friday, August 24, 2012 3:32 PM
     
     
    Sign In to Vote
    0

    Using a browser on the client, go to https://mail.publicurl.com/OAB/(whatever the guid is in the autodiscover xml)/oab.xml - does it get to the CAS and show you the content of an xml file? or does it get stuck somewhere? Cert warning? Auth prompts? Something else? You should get one auth prompt, no cert errors, then the xml file.

    What is between the client and the CAS? Firewall?

     
  • Friday, August 24, 2012 3:41 PM
     
     
    Sign In to Vote
    0

    This is what I get when pathing to the URL:

    Server Error in '/' 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>
     

    Yes, there is a firewall between the client and the server with 443 open.
    • Edited by TBone1985 Friday, August 24, 2012 3:41 PM
    •  
     
  • Friday, August 24, 2012 3:47 PM
     
     
    Sign In to Vote
    0

    Ok then, the OAB Vdir isn't happy. What has been happening in IIS? Have you set up an IIS redirects on the site (so / goes to /owa for example) ?

     
  • Friday, August 24, 2012 3:59 PM
     
      Has Code
    Sign In to Vote
    0

    / doesn't go anywhere.  It actually gives an error page like the one above.  OWA is correct.

    Server Error in '/' 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>

     
  • Friday, August 24, 2012 4:15 PM
     
     
    Sign In to Vote
    0

    Your CAS isn't happy. What happened in IIS? Any changes? There were some, there must have been.

    Do you have another CAS installed?

    Do you have active users on the system? What works?

     
  • Friday, August 24, 2012 4:19 PM
     
     
    Sign In to Vote
    0

    Well it's a CAS, HUB, and Mailbox server combined.  We migrated from one 2007 server to a new 2010 server and this is the result.  I have all my users on this new server and have been for a while. 

    Think it's worth a call to MS support?

     
  • Friday, August 24, 2012 4:22 PM
     
     
    Sign In to Vote
    0

    Yes. Troubleshooting it this way is very hard. Get an engineer on the phone and they can figure out what went wrong.

    Good luck.