SharePoint 2016: UserProfileApplicationProxy Proxy is null

Hi all!

After a looong time without installing a new SharePoint farm, yesterday it was the day 🙂 I needed to install a new farm, so I started doing it and it was everything so simple. After I installed the farm I was reveiwing the Event Viewer in order to see any errors, and I realize that the farm was throwing a lot of errors complaining about “UserProfileApplicationProxy Proxy is null”

The error itself, makes sense since I did not provisioned the User Profile Service Application, so what can I do? Disable the timers of course 🙂

  1. Log in to Central Administration
  2. Click the Monitoring link on the left and then under Timer Jobs click Review job definitions
  3. On the left click Job History
  4. Change the View from All to Failed Jobs
  5. Click the link for the failed job – in my case I am disabling the following jobs:- UserProfileApplicationProxy – Per Database User Profile to SharePoint Full Synchronization
    – UserProfileApplicationProxy – Unified Group Processing High Performance Job
  6. Click Disable

And that’s all, problem solved and not more errors in the event viewer. To the next thing!


Access denied creating a Site Collection

A colleague was creating a site collection from the SPO admin center and he was receiving an access denied message.

An access denied message in SPO admin center? Yes you’re reading well. First thing I propose, was to check the credentialed and the role assigned in O365 center. Everything seems correct.

Second thing, was to try to access another time to O365, but this time in private, only to check if he was having something weird in the navigator, nothing.

How I was watching the URL, by chance I tried to access to this URL, and for my surprise, this SPO URL was existing in a O365 group, so the mistery was solved!

I suggested to check the permissions of the group and to chende the managed path of O365 groups to /teams instead of /sites

Silly misconfigurations leads to big mistakes…


Internal Server Error while creating SharePoint Online Team Site

Today I bring a weird error, it has been hard to follow the error and reproduce it, but finally I have been able to solve it. The error was the following:

  • The user tries to create a SharePoint Team Site from the portalCTS
  • The user selects a Team Site and starts to fill the parametersCTS2
  • The problem here, is that it stucks on the “Checking” action to verify if the site exists wether or not, and after a few moments it shows a message to exit from the creation site page. In case the user selects “Stays on this webpage” the system does nothing, but in case the user selects “Exit from this page” it automatically fires the following error:CTS3
  • 500 Internal Server Error, a great error take into account that we are talking about SharePoint Online…

Things that I checked before finding a solution…

  • Check if the problem was reproduced with other navigators… I tested with IE, Edge, Chrome, Firefox and SAfari, all of them had the same behaviour.
  • Check if the client has configured a group to restrict the creation of O365 groups
  • Check if it happens with all the users, yes it happens
  • Check if it happens with global administrators, nop the GA were able to create the groups

After digging a lot, I decided to check the traces with Fiddler, after that I was able to see a kind of redirection in the traces, so I decided to go to the Home of SharePoint tenant and check the site collection features at that level.

I was reviewing which features were activated, in order to try to clarify what was the point of that error. After checking all the features, I decided to deactivate the feature “Limited-access user permission lockdown mode”


I remember that this feature gave me some problems in the past while I was involved in OnPremises projects were we were deploying anonymous portals, so I decided to deactivate the feature.

After deactivating the feature, I checked the creation of SharePoint Team Sites with the user that was giving me problems at the beginning…. and BAM! problem solved!! Wiiiiiii

So I wonder that this SharePoint Team Site Creation Page has something related with anonymous permissions or something like that. It has been a weird problem, but finally the mistery has been resolved.

Disconnect inactive RDP sessions

While I’m working in a project that needs to log in into a server I usually leave my user session opened (yes I know that it s not a good practice, but I always forget to log off).

So when an admin needs to connect to the server there are either no free sessions or probably the openend sessions are consuming resources that could be slowing down the server.

So as a power user, I discovered the following command to execute in PowerShell (remember to execute it as administrator) to try to list and free the unused sessions:

If you only want to see the sessions, you can execute only this:

query user | select -Skip 1 | ? {($_ -split “\s+”)[-4] -eq ‘Disc’}

To disconnect all these sessions at once, you can execute this command inside an elevated PowerShell window:

query user | select -Skip 1 | ? {($_ -split “\s+”)[-4] -eq ‘Disc’} | % {logoff ($_ -split “\s+”)[-5] /v}

And then all disconnected RDP sessions are forced logoff and the resources are free.

Till next time!

ADFS 4.0 idpinitiatedsignon Error

Hi all,

The other day I was creating an ADFS lab in order to test some features and configurations, as you will probably know, a quick way to test an ADFS deployment is to access the idpinitiatedsignon sign page.

After I deployed my ADFS farm, I tried to access and I received the following error message: “The resource you are trying to access is not available. Contact your administrator for more information.”

At the beginning it was annoying, because I was thinking that I did someone incorrectly, so I spend some time thinking about what I did wrong, I checked the event log and I saw the following:

Encountered error during federation passive request.

Additional Data

Protocol Name:
Relying Party:
Exception details:
Microsoft.IdentityServer.Web.IdPInitiatedSignonPageDisabledException: MSIS7012: An error occurred while processing the request. Contact your administrator for details.
at Microsoft.IdentityServer.Web.Protocols.Saml.IdpInitiatedSignOnRequestSerializer.ReadMessage(WrappedHttpListenerRequest httpRequest)
at Microsoft.IdentityServer.Web.Protocols.Saml.HttpSamlMessageFactory.CreateMessage(WrappedHttpListenerRequest httpRequest)
at Microsoft.IdentityServer.Web.Protocols.Saml.SamlContextFactory.CreateProtocolContextFromRequest(WrappedHttpListenerRequest request, ProtocolContext& protocolContext)
at Microsoft.IdentityServer.Web.Protocols.Saml.SamlProtocolHandler.CreateProtocolContext(WrappedHttpListenerRequest request)
at Microsoft.IdentityServer.Web.PassiveProtocolListener.GetProtocolHandler(WrappedHttpListenerRequest request, ProtocolContext& protocolContext, PassiveProtocolHandler& protocolHandler)
at Microsoft.IdentityServer.Web.PassiveProtocolListener.OnGetContext(WrappedHttpListenerContext context)

So, indeed what it is saying is that the idpinitiatedsignon property is disabled. So, to check if it is this, you can execute the following PS command in the ADFS farm:

Get-AdfsProperties | fl *idpinitiatedsignon*


As you can see in the picture, it was disabled, so in order to solve this problem, just run the following command:

Set-AdfsProperties -EnableIdpInitiatedSignonPage $true

After that, all my problems were solved 😊

Error on manage user properties page–your search encountered an error

Hi all!

A colleague, told me that he was facing an strange error in when he tried to modify some user properties in a SharePoint Server 2013 – he got the following message “Your search encountered an error. If the problem persists, contact the portal site administrator”

Firstly, I checked search but I saw no errors in there – it seems that the error description is not really guiding you in the correct direction. The solution was as simply as starting the ForeFront Identity Manager Service in the services CMD.


Search not working – Query component failed status

Hi all!

I still don’t know if it’s related or not, but after changing the time in our UTC zone, all the query search in a SharePoint farm suddenly stopped working.

At the beginning with the errors that I had, I was thinking in the Index component, but when I accessed to the components, I was able to see that the query component was in red, so it was the first indicator that something was not working fine.

My first thought was to check the logs to see If was able to see anything, and in fact I found a lot of errors related with the query component, some of them like the following:

SearchServiceApplicationProxy::Execute–Error occured: System.ServiceModel.FaultException`1[System.ServiceModel.ExceptionDetail]: Tried IMS endpoints for operation Execute: Operation sent to IMS failed: Resource saturation, try again later. (Fault Detail is equal to An ExceptionDetail, likely created by IncludeExceptionDetailInFaults=true, whose value is: Microsoft.SharePoint.SPException: Tried IMS endpoints for operation Execute: Operation sent to IMS failed: Resource saturation, try again later. at
WcfSendRequest: RemoteAddress: ‘net.tcp://servername/97C247/QueryProcessingComponent1/ImsQueryInternal’ Channel: ‘Microsoft.Office.Server.Search.Query.IImsService’ Action: ‘’ MessageId: ‘urn:uuid:86db249c-bb2a-427f-bbbb-219f0d00e87c’ f861b39d-b40f-b033-363b-cc73f6b053c4
Ims::Execute–Error occured: System.ServiceModel.EndpointNotFoundException: There was no endpoint listening at net.tcp://servername/97C247/QueryProcessingComponent1/ImsQueryInternal that could accept the message. This is often caused by an incorrect address or SOAP action. See InnerException, if present, for more details. Server stack trace: at System.ServiceModel.Channels.ConnectionUpgradeHelper.DecodeFramingFault(ClientFramingDecoder decoder, IConnection connection, Uri via, String contentType, TimeoutHelper& timeoutHelper) at

So… at the beginning I was thinking what can I do with this errors? My first thought was to check available disk free space.

Everything was fine, so.. next thing to check, the following thing I checked was the SharePoint cache, everything was fine, but just in case I cleaned SharePoint cache, then I checked the components of Search and was still in red, so the problem started to be big.

But, suddenly It pops out of my mind that something in the logs, so my next move was to restart the search services. In first case the host controller service. I restarted the service, once it was restarted I checked again the components and were all in green. Yihaaa!

I checked the search results on the portal and I was able to perform queries and all the WP configured were working.

I stopped investigating what was the root cause of the problem, but for next time I know what to do first.

Till nex time!

How to disable IPv6 with Powershell

In some scenarios, working with IPv6 causes a lot of issues, because the request is made to IPv6 rather than IPv4, so the DNS lookup just fails. Typically, IPv6 is not deployed but if you’re in the same boat as me, do the following:

New-ItemProperty -Path HKLM:SYSTEMCurrentControlSetservicesTCPIP6Parameters -Name DisabledComponents -PropertyType DWord -Value 0xffffffff
Restart-Computer -ComputerName $env:computername -Force

And that’s all!

The search application “SEARCH SERVICE APPLICATION” on server did not finish loading

Hi folks,

Recently, I came across with the following issue, I Opened the Search Service Application in one of the Servers in the farm, and when I click on Content Sources I was getting:

The search application ‘XXXX’ on server XXXX did not finish loading. View the event logs on the affected server for more information.

After spending some time to fix the problem I found the following command:

Psconfig -cmd secureresources


It takes a couple of minutes to finish it.After doing this I was able to enter again to Content Sources in the Search Application

Hope it helps!


SharePoint Apps: “Sorry, something went wrong with adding the app. Click to retry.”

I was configuring a dev onpremises farm in SharePoint 2013 to support apps, I followed the guide in

But, everytime I tried to add the app to a site I received thhe following error:

“Sorry, something went wrong with adding the app. Click to retry.”

The first thing I did, it was an iisreset, but that didn’t work, so I started to figure out what was happening at all. Suddenly I remembered that the SPTimer Service would need to be restarted.

Once I did this, it started working like a charm. So, take into account that any change on SharePoint configuration, will be very smart to restar the SpTimer service.

Hope this helps someone out there getting the same error… if you are sure you did everything right in the configuration – you might actually be correct! Just remember to restart services for them to pick up your changes…