The On-Screen Keyboard keeps appearing on a server everytime i log on.
Go to Control Panel -> Ease of Access Center -> Use the Computer without a mouse or keyboard
Untick the option Use On-Screen Keyboard
And now the on-screen keyboard will not appear upon logon.
Last week i encountered an issue where the Web Front Ends were not displaying the main Web Application.
I triple checked all the servers including that the database servers were online, and then proceeded to check if i could access the Central Admin website on the Central Admin server. I then tried to access the Central Admin website from the Web Front Ends and was not able to resolve which means its a DNS issue.
Solution:
The Central Admin server network adapter was set to automatic. Changed it back to static IP Address and performed an IISreset on the Web Front Ends and the Web Application was restored.
Tonight, tried to clone a new virtual machine using vCloud Director when I got the following error:
Failed to publish configuration on vShield Edge. Error code VIX_E_TIMEOUT_WAITING_FOR_TOOLS was returned by VIX API.
Solution:
Restarting the vShield server resolved the issue.
Last week I encountered an issue where the workflows setup in our SharePoint 2010 environment were failing.
It turns out that the September 2018 patches were to blame. Mainly a .NET Framework one. Basically it removes the trusted assemblies from the web.config files which means that the Web Application dont trust the assemblies when they are called.
The patch is rolled out to all versions of .NET Framework and all Operating Systems. A full list of the KBs can be found here
Error:
Server was unable to process request —> Failed to publish workflow…….
System.CodeDom.CodeBinaryOperatorExpression is not marked as authorized in the application configuration file.
Solution:
There has been no talk about a new patch to fix this issue, but the workaround is to re-add the trusted assemblies back into web.config.
On the SharePoint Web Front Ends, go to the web application that has the Workflow issues and navigate to the web.config file.
If you have multiple Web Front Ends, dont forget to repeat for all.
Within the Web.config, find the below and added the authorized assemblies below the
<configuration>
<System.Workflow.ComponentModel.WorkflowCompiler>
Add authorized type code here.
SharePoint 2007 and 2010
<authorizedType Assembly=”System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeBinaryOperatorExpression” Authorized=”True” />
<authorizedType Assembly=”System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodePrimitiveExpression” Authorized=”True” />
<authorizedType Assembly=”System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeMethodInvokeExpression” Authorized=”True” />
<authorizedType Assembly=”System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeMethodReferenceExpression” Authorized=”True” />
<authorizedType Assembly=”System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeFieldReferenceExpression” Authorized=”True” />
<authorizedType Assembly=”System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeThisReferenceExpression” Authorized=”True” />
<authorizedType Assembly=”System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodePropertyReferenceExpression” Authorized=”True” />
SharePoint 2013 and 2016
<authorizedType Assembly=”System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeBinaryOperatorExpression” Authorized=”True” />
<authorizedType Assembly=”System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodePrimitiveExpression” Authorized=”True” />
<authorizedType Assembly=”System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeMethodInvokeExpression” Authorized=”True” />
<authorizedType Assembly=”System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeMethodReferenceExpression” Authorized=”True” />
<authorizedType Assembly=”System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeFieldReferenceExpression” Authorized=”True” />
<authorizedType Assembly=”System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeThisReferenceExpression” Authorized=”True” />
<authorizedType Assembly=”System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodePropertyReferenceExpression” Authorized=”True” />
Nintex Workflow
There is an additional assembly that needs to be added into the web.config for Nintex Workflow to work.
SharePoint 2007 and 2010
<authorizedType Assembly=”System, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeTypeReferenceExpression” Authorized=”True” />
SharePoint 2013 and SharePoint 2016
<authorizedType Assembly=”System, Version=4.0.0.0, Culture=neutral, PublicKeyToken=b77a5c561934e089″ NameSpace=”System.CodeDom” TypeName=”CodeTypeReferenceExpression” Authorized=”True” />
Now you should be able to run your workflows without an issue.
For more information, Rodney Viana (MSFT for Microsoft SharePoint) first reported the issue here.
Recently deployed a SharePoint 2016 Farm into a Dev environment, which consisted of a 2x Web Front Ends, 1x Central Administration and 2x Application servers.
Deployed a new Web Application. Went to the Web Front End server and tried to access the new Web App and got prompted for user credentials.
The user logged into the server has Site Collection Admins permissions to the new Web App.
Authenticated using the credentials, but for end users this will be a major pain, as well as not getting
The reason this occurs is because the URL isn’t being classified in the Intranet Zone.
To check, go to the URL. Select File from the Internet Explorer menu then click Properties.
If the File menu is hidden, right click on the internet explorer banner and click File Menu.
You can see below under Zone that it is sitting in Trusted Sites zone.
Resolution:
In Group Policy, navigate to User Configuration > Policies > Administrative Templates > Windows Components > Internet Explorer > Internet Explorer Control Panel > Security Page.
Edit the Site to Zone Assignment List and add the URL into the list and set the zone as 1.
Then click ok.
By default it takes about 90 minutes for the Group Policy to be updated on the clients.
To verify, repeat the above process and confirm that the zone sits in the Intranet zone.
1 Giant Nerd 