Cannot Start Microsoft Outlook

Users with delegation access to multiple mailboxes are randomly but frequently getting the following error when opening Outlook 2013:

Cannot start Microsoft Outlook. Cannot open the Outlook window. the set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance.

Microsoft had us create a new throttling policy with an RCA Max Concurrency of 500 to raise the limit of allowed connections and assign it to the end-user.

This allows the end-user to close and re-open Outlook when necessary, but the error will reoccur if Outlook is closed and reopened repeatedly, which would max out the number of allowed connections again. Each delegate mailbox takes up as many connections as the main mailbox.

[PS] C:\>New-ThrottlingPolicy -Name ThrottleTest -RcaMaxConcurrency 500 -ThrottlingPolicyScope Regular

Name                                    ThrottlingPolicyScope                   IsServiceAccount
----                                         ---------------------                             ----------------
ThrottleTest                          Regular                                           False

[PS] C:\>Set-ThrottlingPolicyAssociation -Identity mailboxUserName -ThrottlingPolicy Throttletest

Outlook Security Certificate Error after Directing Website to CPanel Host

By default when you enter credentials into Outlook it first searches for yourdomain/autodiscover/autodiscover.xml - if this file doesn't exist on your website it will move on to the O365 record.

However, if your website, yourdomain.com, is pointed to a host managed with CPanel, your Outlook users may start getting one of these errors:

Error: "Information you exchange with this site cannot be viewed or changed by others. However, there is a problem with the site's security certificate."

Error: "The security certificate was issued by a company you have not chosen to trust. View the certificate to determine whether you want to trust the certifying authority."

Error: "The name on the security certificate is invalid or does not match the name of the site.
The security certificate has expired or is not yet valid."

Log into the CPanel, scroll down to Email, and click on MX Entry.

Select Remote Mail Exchanger and click Change. This will stop Outlook from finding the autodiscover.xml file from your CPanel Email, and it will then move on to the O365 location instead.

InfoPath (Not Responding) with Citrix VDA 7.8 or Higher

Upgrading to any Citrix VDA after version 7.6 results in InfoPath consuming all memory and going into a “not responding” state when opening a file.

After a lot of dumps and screenshots Citrix Support narrowed the issue down to the CitrixvirtualSmartcardCsp.dll, which is a new Smart Card feature added to the VDA after version 7.6.

In Process Explorer, right click the application that is consuming the CPU and click properties. Under Threads, select the thread that is consuming the CPU and click stack to view the running DLLs.

As long as you're not using the Smart Card feature, it can be disabled to allow InfoPath to function properly.

Change the Type key to 0 under HKLM\SOFTWARE\Microsoft\Cryptography\Defaults\Provider\CitrixVirtualSmartcardCsp

A reboot is not needed. This will take effect immediately.

WSUS Console: Unexpected Error. Please Try Again.

After installing patches on the WSUS server this month (June 2016), the WSUS console wouldn't start, giving a vague message:

 

Unexpected Error. Please reset the server node and try again.

 

Event logs also show vague 507 and 7034 messages:

 

 

Event 7053 also shows up, however deleting everything from the %appdata%\Microsoft\MMC\ folder does not fix the issue.

 

 

Installing KB3159706 turned out to the cause, and completing the post-installation steps on that page fixes the issue and the console loads normally again.

1. Run "C:\Program Files\Update Services\Tools\wsusutil.exe" postinstall /servicing from elevated cmd prompt.
2. Install Roles/Features, .NET Framework 4.5 Features, under WCF Services, check HTTP Activation.
3. Restart WSUS service.