locked
Exchange 07 to 13 OWA Error after mailbox move. RRS feed

  • Question

  • I have an Exchange 2007 – Exchange 2013 Sp1 environment set up and coexistence is working properly. The issue I am seeing is sometimes when we do a migration from 07 to 2013 sporadic users cannot access OWA on 2013, they get an error..

    X-OWA-Error: ClientError;exMsg=_u is not defined;file=_y.$LE@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:155BootViewModelsComponent.prototype.$1XA/<@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:305920_js.$Zn.prototype.$8J@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60174_js.$Zn.prototype.$E@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59797$4pj@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57816_js.$2.prototype.$6JC@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:58309BootViewModelsComponent.prototype.$1XA/<@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:306788_js.$Zn.prototype.$8J@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60174_js.$Zn.prototype.$E@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59797$4pj@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57816_js.$2.prototype.$6JC@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:58309ApplicationAppComponent.prototype.$1XA/r<@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.1.mouse.js:1:1141362_js.$Zn.prototype.$8J@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:60174_js.$Zn.prototype.$E@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:59797$4pj@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:57816_js.$2.prototype.$6JC@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:58309Program.main@https://XXXXX/owa/prem/15.0.847.32/scripts/boot.0.mouse.js:91:663573invokeMain@https://XXXXX/owa/:549:17owastart/<@https://XXXXX/owa/:601:15:1

    X-OWA-Version: 15.0.847.32

    X-FEServer: SERVER1

    X-BEServer: null

    Date: 1/2/1601 3:14:04 PM

    It doesn’t happen for everyone just a few people, if we move them to different database in the same DAG on a different server they can access OWA.

    What logs can I look at to help find the root cause of this error?  Or has anyone seen this before?

    Thanks!

    Joe  


    Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP Practice Manager Artemis Technology LLC

    Thursday, October 30, 2014 5:47 PM

Answers

  • Hi Joe,

    Please confirm if the issue happens to all users in this specific database. Also check if the Mailbox server is installed in a separate server with CAS server.

    Please access the OWA on the CAS server to have a try. please check whether all the files are present in the following locations:

    C:/Program Files/Microsoft/Exchange server/V15/Clientaccess/owa/prem/15.0.847.32/scripts

    C:/Program Files/Microsoft/Exchange server/V15/Clientaccess/owa/prem/15.0.847.32/ext

    We can restart IIS service on all servers by running IISReset /noforce from a Command Prompt window to check whether the issue persists.

    Regards,


    Winnie Liang
    TechNet Community Support

    Sunday, November 2, 2014 2:23 PM
  • Hi Winnie,

    I was able to find the root cause, the second mailbox server was missing more than 80% of the files required for IIS.

    I will be running a repair on the mailbox server tonight.

    Thanks for your help!

    Joe


    Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP

    Monday, November 3, 2014 5:07 PM

All replies

  • Hi Joe,

    Please confirm if the issue happens to all users in this specific database. Also check if the Mailbox server is installed in a separate server with CAS server.

    Please access the OWA on the CAS server to have a try. please check whether all the files are present in the following locations:

    C:/Program Files/Microsoft/Exchange server/V15/Clientaccess/owa/prem/15.0.847.32/scripts

    C:/Program Files/Microsoft/Exchange server/V15/Clientaccess/owa/prem/15.0.847.32/ext

    We can restart IIS service on all servers by running IISReset /noforce from a Command Prompt window to check whether the issue persists.

    Regards,


    Winnie Liang
    TechNet Community Support

    Sunday, November 2, 2014 2:23 PM
  • Hi Winnie,

    Thank you for responding.  The mailbox and cas servers are separate, and I have rebooted and reset IIS multiple times.   What I have come to find out is if I access the OWA from an older browser it doesn’t switch to OWA light, a newer browser will not have this problem and can get in with the problem mailbox.  If I specify the light directory owa/?layout=light I can get in to the problem mailbox with no issues.   It seems like the local client can’t process the script that will force the client to use OWA light.

    Thanks!

    Joe


    Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP

    Monday, November 3, 2014 12:16 AM
  • Hi Winnie,

    Thank you for responding.  The mailbox and cas servers are separate, and I have rebooted and reset IIS multiple times.   What I have come to find out is if I access the OWA from an older browser it doesn’t switch to OWA light, a newer browser will not have this problem and can get in with the problem mailbox.  If I specify the light directory owa/?layout=light I can get in to the problem mailbox with no issues.   It seems like the local client can’t process the script that will force the client to use OWA light.

    Thanks!

    Joe

    Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP

    Hi Joe,

    According to youe further description, the issue seems to be related to browser. Please update your browser to the latest version or set the Internet Explore to Compatibility view to have a try.

    Regards,


    Winnie Liang
    TechNet Community Support

    Monday, November 3, 2014 12:46 PM
  • Hi Winnie,

    I was able to find the root cause, the second mailbox server was missing more than 80% of the files required for IIS.

    I will be running a repair on the mailbox server tonight.

    Thanks for your help!

    Joe


    Joseph Noga MCITP, MCSE, MCSA, MCTS CCNA,CCDA,CCVP

    Monday, November 3, 2014 5:07 PM