Strange UI Effect

Question

Hi - we've started testing adding the Exchange component to users' portal and get this strange effect that started at the same time:-

Top picture is the page as it first loads
Bottom picture is the page as soon as the Exchange section loads - all the links suddenly go crazy.

We are still working our way through the minimal permissions in Exchange (excessive mailbox access is even worse than excessive AD access!) so it could be related to that, but interested if you've even seen this before?

Rgds

Comments

Hello,

Try clearing the browser cache and then loading the page again.

Also, what web browser are you using?

---

Hi,

We are using both IE and Firefox, primarily IE.

I have tried clearing the cache and still have the issue.

This wasn't happening originally, it only started a few days ago. I'm currently asking around if anything has changed elsewhere.

I had (and still do somewhat) thought this was\is related to permissions somehow, as I had evaluated using a 'superuser' account, and the problem first occured when I then re-logged in using a standard user account (which doesn't have view Computer access within Adaxes). Now I have tried the permissioned account again and the problem is still present however.

Let me hunt around and try and few things - I'm sure it's not a server-side\application problem really, but was interested if you had any ideas as to what it may point to as a root cause when the page renders in the browser.

Rgds

---

FYI Def permissions related.

Something to do with having partial mailbox access. If I view an account who has not had Adaxes added as a mailbox adminthere is no UI corruption, but if I view an account that has we get the issue.

In this event, even though we have granted mailbox access we get the following error under the Delegation tab (which strangely we don't get when the service account hasn;t been granted the access rights):-

"Failed to get mailbox rights. Some or all identity references could not be translated."

I'm checking whether this is because there are references to our parent domain in the delegation list (where Adaxes is not permissioned), and/or something else.

To help track down any issues, can you confirm the minimal rights that the Adaxes service account needs in Exchange? Currently we are granting full access on a per-mailbox basis during the testing, and the Adaxes service account is also a member of the Exchange organisation admins account.

Many Thanks

---

Hello,

As to Web Interface corruption, the most probable reason is that you have either an HTML-formatted MailTip or an Out-of-Office (OOF) Reply message specified for the users that you are experiencing issues with, and that HTML message is corrupted. For example, it doesn't have all the tags closed or something like that. When Adaxes loads such an improperly formatted HTML message, it corrupts the whole of the page displayed by the Web Interface.

To check this, you can, for example, try disabling MailTip for one of the users and see if it helps.

As to the Delegation tab issue, can you specify your Exchange version so we can troubleshoot the issue?

---

Thanks,

We're Exchange 2007 SP3. One thing I can check is the the version of the management tools is the right version as it's possible the server and tools may be slightly off.

You are in the right ballpark with the UI corruption - if I turn off any OOO messages the issues vanish. When I turn them on - even if the message boxes are blank we have the issues.

Rgds

---

We're Exchange 2007 SP3. One thing I can check is the the version of the management tools is the right version as it's possible the server and tools may be slightly off.

To help us reproduce the issue, can you enable tracing of PowerShell commands execution and send the trace file to us for investigation? To do this:

1. Open the folder that your Adaxes service is installed to, which is C:\Program Files\Softerra\Adaxes 3\Service\ by default.
2. Locate the file named Softerra.Adaxes.Service.exe.Config and open it with any text editor.
3. Find the following line:
4. Change false to true.
5. Save the file.
6. Restart Adaxes service.
7. Try performing the same operation that you did when you got the error message and on the same user.
8. Change true back to false (this will stop growing of the trace file as it can grow to enormous sizes).
9. Restart Adaxes service again for changes to take effect.
10. When tracing is enabled, Adaxes outputs messages from all PowerShell commands to the file named exchange.powershell.trace.txt located in the same directory as the Softerra.Adaxes.Service.exe.Config file. Send the file to adaxes@softerra.com.

You are in the right ballpark with the UI corruption - if I turn off any OOO messages the issues vanish. When I turn them on - even if the message boxes are blank we have the issues.

The thing is that Exchange does not allow to save the properties of an Exchange recipient if the OOF feature is enabled, but the message text is empty. So, we think that there is some text. Most probably, it is an unclosed tag that is not visible in the message editor (since it does not have text in it), but corrupting the Web Interface page.

To resolve the issue, we can suggest the following:

1. Open Adaxes Administration Console.
2. In the Console Tree, navigate to and select one of the users that is causing the issue.
3. Right-click the user, select Exchange Tasks, and then Exchange Properties in the context menu.
   
4. Activate the Automatic Replies (OOF) tab.
5. Select the Send automatic replies (OOF) option.
6. Activate the Inside My Organization tab.
7. Place the cursor in the message editing field.
8. Press Ctrl+A to select the whole text, and then press Delete.
9. Type some message in the message editing field.
   
10. Click OK.
11. Check whether the issue reappears for this specific user.

---

Was there ever a resolution to this issue? We are getting this same error (Some or all identity references could not be translated.) when accessing various Exchange mailboxes but not all Exchange mailboxes.

---

Hello,

Since firegoblin did not follow up on this thread, we never actually got to the problem. To help us troubleshoot the issue, can you do the following:

1. Enable tracing of PowerShell commands sent to your Exchange Server.
2. Get the Some or all identity references could not be translated. error.
3. Send the PowerShell trace file to support@adaxes.com.