Hi,

I have a problem with OWA on Exchange 2013

When typing username/password in the login dialog box and click "Log on" I get an error: Will you open or save UserSpecificResourceinjector.js - Able to select open/save or cancel. When selecting one of them OWA will open.

When putting the Site link under "Trusted Sites" the error is gone. But this is not a solution because of using workstation without permission to add site to "Trusted Sites"

Exchange Environment: One F5 Load Balancer - Two Exchange 2013 CU9 Exchange Servers

Hope to find a solution

Best Regards - Kim F. Agersten

What you're describing is really an IE issue.  Perhaps you can add this to the trusted sites using a GPO.

Hi,

Please confirm whether the issue happens to all users or specific users to narrow the issue to client side or server side. 

According to your description, the issue is solved when add OWA site to "Trusted sites".

We can try to use other browser like Chrome and check if the issue persists.

As Ed said, we can change GPO to add the site to the trusted sites as a workaround.

Regards,

David

Hi,

Thank you for the answers.

I know that GPO is a solution but not an opportunity. If you are using an external workstaion outside the domain at a hotel you dont see the domain/gpo.

I have not seen the problem when using Firefox

When I try to use Chrome I got an error -> Cache Manifest and a lot of parameteres

The problem is periodically. I'm trying to see if the error comes from both Exchange Servers or only from one of them

Hi,

Thank you for the answers.

I know that GPO is a solution but not an opportunity. If you are using an external workstaion outside the domain at a hotel you dont see the domain/gpo.

I have not seen the problem when using Firefox or IE10 and older

When I try to use Chrome I got an error -> Cache Manifest and a lot of parameteres

The problem is periodically. I'm trying to see if the error comes from both Exchange Servers or only from one of them (Come from both servers)

This is from the file UserSpecificResourceInjector.js:

var blockToAdd;userScriptResources[userScriptResources.length] = { "fileName": "prem/" + sver + "/scripts/globalize/globalize.culture.da-dk.js", "layout": LT_ANY};

styleResources[styleResources.length] = { "fileName": "prem/" + sver + "/resources/images/0/sprite1.mouse.css", "layout": LT_MOUSE};

styleResources[styleResources.length] = { "fileName": "prem/" + sver + "/resources/styles/0/boot.mouse.css", "layout": LT_MOUSE};

setupUserSpecificResources('15.0.1104.5', 'base', 'da-DK', 'da', false, null, null, '0', 'c9QD+S5gx2HKEpO20rkJDJpkLA0=', ["OwaPublicFolders"], 3);

userSpecificsLoaded = true;

• Edited by Kim F. Agersten Thursday, July 16, 2015 11:36 AM

Hi,

Thank you for the answers.

I know that GPO is a solution but not an opportunity. If you are using an external workstaion outside the domain at a hotel you dont see the domain/gpo.

I have not seen the problem when using Firefox or IE10 and older

When I try to use Chrome I got an error -> Cache Manifest and a lot of parameteres

The problem is periodically. I'm trying to see if the error comes from both Exchange Servers or only from one of them (Come from both servers)

This is from the file UserSpecificResourceInjector.js:

var blockToAdd;userScriptResources[userScriptResources.length] = { "fileName": "prem/" + sver + "/scripts/globalize/globalize.culture.da-dk.js", "layout": LT_ANY};

styleResources[styleResources.length] = { "fileName": "prem/" + sver + "/resources/images/0/sprite1.mouse.css", "layout": LT_MOUSE};

styleResources[styleResources.length] = { "fileName": "prem/" + sver + "/resources/styles/0/boot.mouse.css", "layout": LT_MOUSE};

setupUserSpecificResources('15.0.1104.5', 'base', 'da-DK', 'da', false, null, null, '0', 'c9QD+S5gx2HKEpO20rkJDJpkLA0=', ["OwaPublicFolders"], 3);

userSpecificsLoaded = true;

• Edited by Kim F. Agersten Thursday, July 16, 2015 11:36 AM

See Later reply

See my reply

Hi,

I think the exchange server seems normal. 

I suggest we can contact with Microsoft to report the issue and check if it is a bug:

https://support.microsoft.com/en-us/contactus

Regards,

David