To resolve this issue, follow these steps: Run the OutlookSearchRepair utility. For more information about how to get and run the utility, go to the Mac Outlook Support Utilities blog on the Microsoft TechNet website.; If you recently created a new Outlook Profile in Outlook 2016 for Mac, or a new Identity in Outlook for Mac 2011, added a new account, or if you recently imported new data from. 2017-4-6 Guys!Some of my clients are reporting that they cant open Excel files on any latest Mac iOS, so researched a woraround for such users who are having this permissions related issue.There is nothing wrong with file and you can open it on windows or may be on any other Mac as well.T. View Only: Your account. doesn't allow editing on a Mac. To learn more, contact your admin about your Office plan. I have an Office 365 Business license that I can't get successfully activated on my Mac, so I'm no longer able to edit any documents in Word.
-->by Apurva Joshi
Tools Used in this Troubleshooter:
- NA
This material is provided for informational purposes only. Microsoft makes no warranties, express or implied.
Overview
View state is a feature in ASP.NET that allows pages to automatically preserve state without relying on server state (for example, session state). However, issues relating to view state can be difficult to debug. In most cases, when problems with view state occur, you receive the following error message in the Web browser, with little indication of what might be causing the issue:
This article describes some techniques that can be used for debugging and for resolving problems with view state.
Scenarios and Troubleshootings
Verify that you are not running into issues that have been fixed
A number of view state issues were fixed with ASP.NET 1.0 hotfixes and service packs, and those fixes are also part of ASP.NET 1.1. Make sure that you have applied the latest fixes before tracking issues that have already been resolved. You can obtain the latest Microsoft .NET Framework updates from the following Microsoft Developer Network (MSDN) Web site:
Set the validationKey attribute if you are running in a Web farm
In a Web farm, each client request can go to a different machine on every postback. Because of this behavior, you cannot leave the validationKey attribute set to AutoGenerate in the Machine.config file. Instead, you must set the value of the validationKey attribute to a fixed string that is shared by all the machines on the Web farm.
For more information about this issue, click the following article number to view the article in the Microsoft Knowledge Base:
Do not store dynamically generated types in view state in a Web farm Microsoft remote desktop mac configuration.
When ASP.NET compiles files dynamically, the files are built into assemblies with essentially random names (for example, a file name might be jp395dun.dll). If you are running a Web farm, the same files will be compiled into assemblies with different random names. Normally, this is not a problem because no one makes assumptions on those assembly names. But if you ever put a dynamically compiled type into view state by using binary serialization, the name of the assembly will be included as part of the view state data. When that view state is later sent to a different server in the Web farm, the view state cannot be deserialized because it uses different assembly names.
The best fix to this problem is to avoid using binary serialization. Binary serialization uses many resources even when you do not run into this problem. Instead, limit what you put in view state to a combination of Arrays, Pairs, Triplets, and simple types (for example, strings, int, and other types). System.Web.UI.Pair and System.Web.UI.Triplet are simple wrapper types that the view state engine can efficiently process.
An alternative fix to avoid this problem is to move the types that you are storing in view state into a precompiled assembly, either in your Bin folder or in the Global Assembly Cache. This fix does not address performance, but it guarantees that the assembly has the same name on all computers.
Note If you store complex data types in view state and experience this issue, the call stack information will contain stacks that are similar to the following:
Determine whether the problem is related to the view state MAC feature
The purpose of the view state machine authentication code (MAC) feature is to make it impossible for clients to send a request that contains a malicious view state. By default, this feature is enabled in the following flag in the Machine.config file.
The simplest way to determine whether the issue you are dealing with is related to the MAC feature is to turn off the feature. To do this, change the flag in the Machine.config file to the following code.
If you no longer get view state errors, the problem is related to the MAC feature.
Important
Mac View Only Microsoft Issue 1
Only turn off the view state MAC feature to help diagnose the problem. You should not keep the view state MAC turned off to work around the issue. If so, you could introduce security holes
In general, Microsoft recommends that you not turn off the view state MAC feature unless you are completely confident that you have either disabled view state for all controls that do not HTML encode their output (for example, DataGrid controls, DataList controls, Label controls, and other controls) or that you are always explicitly setting their values on each request to something known to be safe.
Determine exactly what exception occurs when you receive the error message
Unfortunately, the invalid view state error message that is mentioned in the 'Overview' section of this article is not very informative. The error message is generally caused by some exception being thrown when the view state is being processed. The problem is that the exception is being consumed, and its details are lost in the error message.
By using a debugger, you can determine the original exception. To do this, you must attach a debugger to the ASP.NET process (Aspnet_wp.exe or W3wp.exe), and then set it to catch all exceptions. You can even configure Debug Diagnostics 1.2 tool to capture managed exceptions.
Try storing the view state in the session
By default, the view state is round-tripped by means of an <INPUT type=hidden> field that is sent to the browser. The browser then sends the field back to the server on the next request. In some cases, this view state can get quite large and be a potential source of problems. Some browsers cannot handle such a large hidden field (and the resulting large request), and the browsers may truncate the view state. Truncating the view state causes a 'view state corrupted' error message. This behavior is most likely to occur in simpler browsers. For example, this behavior may occur in a browser on a PDA.
To determine whether you may be running into such an issue, try storing the view state in the session. The following example demonstrates how to do this.
The following line of code is only needed in ASP.NET 1.0, to work around a bug. In ASP.NET 1.1 plus, it is not necessary.
Determine whether the problem is caused by worker process recycling
Consider the following scenario.
- You are running ASP.NET under Microsoft Internet Information Services (IIS) 6.0.
- The application pool is running under an identity other than the Local System account, the Network Service account, or an administrative-level account.
- The validationKey attribute of the <MACHINEKEY> element is set to AutoGenerate in the configuration file.
In this scenario, the following procedure will cause a view state error to occur:
- A user browses a page.
- The worker process that hosts the ASP.NET application recycles.
- The user posts back the page.
The workaround for this scenario is to use an explicit validationKey attribute in the configuration file.
Other Resources
Updated: April 4, 2019
Latest issues added or updated
Server update
Without Skype for Business Server 2015 CU4 (build 9319.272 or later) or Lync Server 2013 CU8 HF1 (build 8309.973 or later), Skype for Business on Mac requires Mobility enablement on the server side. After updating to builds 9317.272 or 8309.973 or later, Mobility enablement will no longer be required.
Mac View Only Microsoft Issue Page
You can download these updates at Updates for Skype for Business Server 2015 and Updates for Lync Server 2013.
You can also find more information at FAQ - Skype for Business on Mac.
Known issues
Issue | Comment |
---|---|
Outlook integration | Requirements for Skype for Business and Outlook integration on Mac:
Troubleshooting Outlook integration in case Contacts don’t show presence, online meetings fail to schedule, or there is no dial-in information in meeting invitation:
|
Can’t see users’ Skype for Business presence in Outlook 2016 for Mac | If you have Lync for Mac 2011 installed on the same Mac device, Lync for Mac might have changed the configuration. Recommend that you reinstall Skype for Business on Mac. |
Can't search Skype directory | Skype for Business on Mac users can't search the Skype directory, although you've enabled this functionality for your organization. However, Skype for Business on Mac users can communicate with Skype users if they know the Skype user's Microsoft account. See Add a contact in Skype for Business |
Side-by-side installation | Side-by-side installation of Skype for Business and Lync is not supported on Mac. We recommend that you perform a clean uninstall of Lync for Mac 2011 prior to installing Skype for Business. |
Cannot sign in to Skype for Business | Some Lync profiles might be different from Skype for Business on Mac profiles and can cause a discrepancy. See How to Perform a Clean Uninstall of Lync for Mac 2011 for more information. |
Mobility Policy required | With the release of Skype for Business Server 2015 CU4 and Lync Server 2013 CU8 HF1, we will support Skype for Business on Mac as a desktop application. This means that having a mobility policy assigned to Mac users will not be required. Until these server updates, Mobility enablement on the server side is required. |
Meeting invitations only display a single dial-in number | Fix: Update to Outlook 2016 for Mac build 15.32 or later. |
Single/tabbed window experience not available | By default, if your topology meets the following requirements, all conversations will be shown in a single/tabbed window. However, there are cases when the client can’t detect if server-side conversation history is enabled and it will not default to single window view. This can be remedied by updating settings in Preferences. Requirements for single/tabbed window experience:
Troubleshooting if single window mode is not available, check the following:
|
Adding a distribution group that has more than 100 contacts will result to 100 contacts only | Workaround: To view the full member list of distribution group, use Outlook to expand the group. |
Skype for Business on Mac fails to sign-in (Skype for Business Server Online, Exchange Server Online, Identity managed on-premises with ADFS 3.0 and WIA authentication enabled for wiasupporteduseragents-Mozilla/5.0) | Workaround:
Note: Skype for Business on Mac gets represented by the underlying ADAL library as user agent Mozilla/5.0 (no option to set it from the app), and Windows Integrated Authentication is generally used only for Windows clients and therefore not supported by ADAL library on Mac. |
Contact Management, including Delegate Management, is only supported on Skype for Business Server 2015 with UCS disabled | Users on Skype for Business Server 2015 cannot modify their contacts list in Skype for Business if a user account is enabled by the Skype for Business administrator for the Unified Contact Store (UCS) for Exchange. If the users are hosted on Lync Server 2013, Contact Management is not supported. Users can make changes to their contacts list in Outlook. Delegate Management can be done by the Lync or Skype for Business administrator using the SEFAUtil administrative tool. Skype for Business Server 2015 with UCS disabled is the only currently supported Contact Management. |
While in a peer-to-peer session between a Windows Skype for Business client and a Mac Skype for Business client, and sharing is started by the Mac Skype for Business client, the Windows Skype for Business client will not be able to see the Mac user's desktop if VBSS is disabled in the environment. | Desktop viewing is currently not supported in this Skype for Business scenario for Windows on-premises users. Workaround:
|
Enhanced 911 (E-911) support | Support for E-911 emergency calls made from Skype for Business on Mac has the following requirements for on-premises servers:
|
Instant messaging (IM) notification for emergency calls not sent to a distribution list | For users of Skype for Business Server 2015, sending an IM notification of an emergency call placed from Skype for Business on Mac to a distribution list (as specified by the the notification URI in the location policy) requires the July 2018 update. |
In Outlook, cannot join a meeting from a non-federated organization | Users cannot join a meeting from another organization that isn’t federated with your organization when users click the join links in Outlook. Workaround: Join the meeting from the Meetings tab inside the app (version 16.11.149 and later). |
Large PowerPoint files cannot be shared in a meeting | PowerPoint files that are larger than 30 MB can't be shared in a meeting from Skype for Business on Mac. Workaround: Open the PowerPoint file on the computer and share the screen in the meeting. |
Contact card information for the signed-in user is out of date | When contact details for the signed-in user change, the contact card in Skype for Business on Mac may not show the current information. For Skype for Business Online users:
For Skype for Business Server 2015 or 2019 users: sign in from Skype for Business app on Windows. A fix will be available in a future server update that does not require the Windows app. |
'Chat not available' in a meeting if no message is sent or received for 1 hour | If no messages are sent in the meeting for 1 hour, UCWA disconnects the client from the IMMCU on user inactivity. The disconnection is not visible until the Mac user attempts to send a message. Workarounds: - Send an instant message within 1 hour. - Rejoin the meeting. |
Features not available in this release | If you have Skype for Business Server 2015, see the Skype for Business on Mac column in Client comparison tables for Skype for Business Server 2015. If you have Lync Server 2013, see the Skype for Business on Mac column in Client comparison tables for Lync Server 2013. |
Related Topics
Mac View Only Microsoft Issue 2017
What's new in Skype for Business on Mac?
Office Insider releases for Skype for Business on Mac
Skype for Business help