This issue might occcur in SharePoint on premise versions 2013, 2016 and 2019.
Images do not load properly or load with full size that is without rendition. This can happen if Blob Cache is corrupted on one of the Web Front end or web front ends are not synced between each other.
The default max size for an image when using Image Renditions is 40 mega pixels. Should you want to modify this value you will need to add the imageRenditionMaxSourcePixels parameter. For example: <BlobCache location="C:\BlobCache\14" path="\.(gif|jpg|jpeg|jpe|jfif|bmp|dib|tif|tiff|themedbmp|themedcss|themedgif|themedjpg|themedpng|ico|png|wdp|hdp|css|js|asf|avi|flv|m4v|mov|mp3|mp4|mpeg|mpg|rm|rmvb|wma|wmv|ogg|ogv|oga|webm|xap)$" maxSize="10" imageRenditionMaxSourcePixels="100000000" enabled="true" />
Error message: I was not able to identify an error message but users complained that intranet page seems weird and images are displaying over text and etc
How to fix:
Try flushing blob cache with below PowerShell command , this will not recycle the IIS so you can do it during day as well but always good to do it outside office hours.
2. It is not necessary that above will fix the issue, in our case we identified that this did not fix the issue because cache was not getting updated in one of the web front end and time stamp was quite old.
How can you check if it is old and it’s not getting updated?
Visit the folder location of Blob cache on Web front end and each web app will have it’s own folder, check last modified date, you can also compare with other web front ends.
If your issue as explained below then do like this but make sure you have web front end outside of load balancer or you are doing in outside of office hours.
Disable blob cache temporarily: You can make the flag false in web.config file of the IIS which has issues, the line in web.conifg looks like below
Before you start reading this I would like to mention that steps mentioned here are to create a Virtual Machine in Azure for demo, development or labs purpose.
I decided to write this blog as I faced some difficulties while installing SharePoint 2019 on Azure Virtual Machine, I never faced these while installing it on Physical machines or company provided Virtual Machines.
Click on the menu and select “Virtual Machines” and then click Add from top
2. Once you get to the page you will have lots of tabs to filled in, I have highlighted few fields which are required and needs to be filled in, rest of it can be left as is.
Important field which we need to select is “Image” that is we need a Windows Server etc, for easy installation I will be selecting a Windows server with SQL Server 2016 already installed in it so that we don’t have to do that manually.
3. Select “Browse all public and private images” and search for SQL server 2016 and select Standard SP 2 version, for size I recommend 4 CPU and 16 GB memory else the server runs very slow as SQL and SharePoint both are running on the same server.
4. Next step is to create an Admin account so pick a name and password which you can remember. After that you can click “Review + Create”, although there are lot of other things which can be filled in but sake of simplicity I will just leave them as is.
5. Once on the Review tab, click “Create” to create the Virtual Machine. It will start the deployment process and might take 10 minutes. You can check the progress while it deploys.
6. After creation you can check the Virtual Machine in the list, click on the name to access it.
7. Click on the name and you will get to a window as show below, to connect to the machine we should RDP it, so click Connect and chose RDP. It will download a file which can be used to connect to machine using the Admin account you have created. This finishes step for creating Virtual Machine.
Add domain servcies to Virtual Machine
Initially I had thought that this steps is not needed but it does not work if Virtual Machine is not connected to a domain, you will get an error at the end of SharePoint 2019 installation that is Search Service Application will not be created successfully. You may get errors like below
The SDDL string contains an invalid sid or a sid that cannot be translated.Parameter name: sddlFormSystem.ArgumentException: The SDDL string contains an invalid sid or a sid that cannot be translated.Parameter name: sddlForm at System.Security.AccessControl.RawSecurityDescriptor.BinaryFormFromSddlForm(String sddlForm) at System.Security.AccessControl.RawSecurityDescriptor..ctor(String sddlForm) at
Errors were encountered during the configuration of the Search Service Application. System.ArgumentException: The SDDL string contains an invalid sid or a sid that cannot be translated. Parameter name: sddlForm at System.Security.AccessControl.RawSecurityDescriptor.BinaryFormFromSddlForm(String sddlForm) at Microsoft.SharePoint.Win32.SPNetApi32.CreateFileShareWithSecurity(String name, String description, String path, String sddl) at Microsoft.Office.Server.Search.Admi.nistration.AnalyticsAdministration.CreateAnalyticsUNCShare(String dirParentLocation, String shareName) at Microsoft.Office.Server.Search.Administration.AnalyticsAdministration.ProvisionAnalyticsShare(SearchServiceApplication serviceApplication) at Microsoft.Office.Server.Search.Administration.AnalyticsAdministration.CreateDefaultStoreLocation(SearchServiceApplication serviceApplication) at Microsoft.Office.Server.Search.Administration.AnalyticsAdministration.ProvisionRawEventStore(SearchServiceApplication serviceApplication) at Microsoft.Office.Server.Search.Administration.AnalyticsServiceAdministration.Provision() at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.Provision() at Microsoft.Office.Server.Search.Administration.SearchAdminUtils.UpdateIgnoreSPUpdatedConcurrencyException(String description, SearchAdminUtilsUpdateDelegate updateDelegate, SearchAdminUtilsRefreshObjectDelegate refreshObjectDelegate) at Microsoft.Office.Server.Search.Administration.SearchConfigWizard.CreateSearchApp() at Microsoft.Office.Server.Search.Administration.SearchConfigWizard.ProvisionSearchServiceApplication() at Microsoft.Office.Server.Search.Administration.SearchConfigurationJobDefinition.ExecuteTimerJob()
Once that is done you have got rid of other error which will come as now you will be using a domain account and not local account to install SharePoint 2019.
The specified user “username” is a local account. Local accounts should only be used in standalone mode.
Check SQL Server settings :
Open SQL Server Management Studio which should be installed already as we had got server with SQL server already installed.
The account which will install SharePoint 2019 should have required access like below, this account is same as what you had created while creatin Virtual Machine. You can find it under Logins and make sure you have selected “dbcreator” and “securityadmin”. This will make sure the account has correct access to create databases while installing SharePoint 2019.
3. Another thing we need to do is to make sure the account which you updated above has name as “domain\username”, initially it will have name as “computername\username”, since we when we created Virtual Machine with SQL server there was no domain it will remain as is. If you miss this step then you will have issues while creating Search Service Application. So remember to change name as suggested by right clicking and rename. Error message while installing SharePoint 2019 will be like below
The service application “Search Service Application” could not be created because of the following error: System.Data.SqlClient.SqlException (0x80131904): Windows NT user or group
Once downloaded first step is to install pre-requisites, make sure you have an internet connection else it will not work. Click on “Pre-Requisites”, you will the installation happening
4. Once that is done successfully double click “setup” to installing SharePoint 2019, it will start the installation, check pictures below to understand the steps, in the step 2 make sure you use the same account you had created before with format as “domain\username”, in step 3 select “Single Farm”.
Once the above steps are done a IE window will open to configure further, you can chose to perform rest of the steps manually or run the wizard, I chose to run wizard.
So this should finish your SharePoint 2019 installation and you are ready to use it.
This based on my experience with a customer I have worked with for many years.
I would like to create “Product Catalog” to display 3D images for the product and display relevant documents related to the Product.
To set some context: Large product / euiqpment manufacturing comapanies such as mining, construction or vechiles upload there marketing material for sales people to be accessed internally and share externally for sales pitch when needed on portal sites.
In general in these portal sites you will find images of the product and documents related to it in OOB user interface or custom user interface.
Companies also have product 3D images but they don’t show on intranet as SharePoint Spaces was not available so not so practical I would say.
Now we have set the context let’s check how easy is to use SharePoint Spaces.
First of all you need a SharePoint Site preferably a Communication site as it will give you more space in screen to create SharePoint Spaces.
Spaces is not available automatically and feature needs to be enabled in “Manage Site Features” called “Spaces”.
Once you have enabled it you will see below option in “New”
Select a structure , input a name to create a Space Design page which will look like below depending on which structure you have selected
Click on “+” to add 360 degree image, video etc shown as below
I will be adding a two Product groups like Trucks and Cars, which will take user to two different Spaces page which will contain different Trucks and Cars, you can imagine this as Product group and when you click you go to different Products available under that group.
I will add a 3D Object with Podium , please check below screen shots
The properties which I have used are “Podium”, “Link to another space” , “Alternate text” and “Description”.
The “Link to another space or link” is great option as you can hierarchy and structure around Spaces.
I will be adding another Space which display multiple Products and then each product will also link to another Space which will have a Document Library attached
This will complete our Product Catalog so it works like this Product Group –> Products –> Document Library (Space)
Now let’s see the whole set up in action
During the process of creating this I found some improvement areas or issues
If you have only folders in a document library then the SharePoint Spaces cannot load it
If you want to connect a object to a folder in library you have to use a “Link” option and the link to Folder will not be recognized which you get from “Copy Link” option so you have to construct on your own which will also be not recognized but it will work
If you have done connections using SharePoint Spaces then the page does not reload but Space area reloads which is good but it will be good to have some kind of hirearchy navigation which can help in contructing structures
Another thing I would like to add is that it works in Microsoft Teams as well
I think SharePoint Space has lot of practical usage you just need to think in different way and visualize.
Let me know what you think and what pratical usages to you can see.
One of the things in which a lot of people were interested and I also get to know was about Private Channels in Microsoft Teams. Currently we are able to create Channels but they are not private and can be accessed by all Team members.
Apparently this is the most sough after feature in Teams in User Voice. Latest information I got from two guys from Microsoft in a session about Teams was Private Channel will be available in end-October and might be available in Nov to Tenants
Interestingly the Private Channel will have it’s own SharePoint site collection and not as a folder in existing SharePoint site as it happens now. It will only have four Apps available to be used in beginning for rest of Apps you have to go to main Team.
As explained to me is that idea is to get the Private Channel usage going and then later more Apps will be made available.
Some people were concerned with new Site Collection being created for each Private Channel but this seems to be logical as we do not want permission broken folder in our library as it will be a nightmare for future and having a site collection of it’s own makes it scalable.
If your organization has decided to split your company or rename or for any other reason domain needs to be changed then SharePoint will be impacted. In the first part I had explained how to do user migration from SharePoint point of view.
Next step is to do Server Migration of SharePoints in new domain.
What is the recommended way to do this?
Note that Microsoft does not support chaning domain in same existing servers. It means you have to create a new farm in new domain with new service accounts and then do a data migration.
Broadly these are the steps to do it
Create a new farm same as previous one or an upgraded one(scale) if needed.
Create new service accounts in new domain to be used in new farm. Use these accounts to create and configure new farm.
Migrate all Service Applications like Managed metadata service, Search service, User profile service, Workflow manager etc
Create web applications same as previous farm
Deloy any custom code WSP from the previous farm to new one
Use database attach upgrade process to migrate content databases and attach to newly created web applications.
Configure any SharePoint hosted app or provider hosted app
Test and verify that all data has been migrated and also custom code as working as expected
Above are very broad steps, if you have done any upgrade such as SharePoint 2010 to 2013 or SharePoint 2013 to 2016 then you will find the steps familiar.
Although you always expect these steps to be done smoothly you know it will never be like this.
Below are some things you might experience or not experience but I am listing then down from our experience
We were doing a SharePoint 2013 Server domain migration in which we had to migrate Workflow Manager as well.
After migration, Workflow Manager 2013 did not work fine in new environment so we had to attached old environment server to new farm with the old domain account. You can call this as a temporary work around.
All SharePoint Workflow 2013 stopped working and were getting “cancelled” whenever they were running.
Tasks were not getting created by Workflow 2013 in Task list and workflow failed or canceled.
First issue was resolved by using the same link posted earlier and I will say half of the workflows worked fine
Second issue was complex and I was not able to find a resolution but one of my colleague found resolution, I was able to only collect error messages which was also important as we were not able to pin point root cause
You may see following error messages in the SharePoint ULS logs, the key issue for us was the ones highlighted in bold
Trusted provider is missing. Provider: ‘00000003-0000-0ff1-ce00-000000000000’
Request does not have SPBasePermissions.UseRemoteAPIs permission. Need to check it when each API is accessed
SocialRESTExceptionProcessingHandler.DoServerExceptionProcessing – SharePoint Server Exception [System.UnauthorizedAccessException: Attempted to perform an unauthorized operation. at Microsoft.SharePoint.Client.ServerStub.CheckRequiredResourceRight(ProxyContext proxyContext, String memberName, ResourceRight right) at Microsoft.SharePoint.Client.ServerStub.CheckBlockedGetProperty(String propName, ProxyContext proxyContext) at Microsoft.SharePoint.ServerStub.SPContextServerStub.GetStaticProperty(String propName, ProxyContext proxyContext) at Microsoft.SharePoint.Client.ServerStub.GetStaticPropertyWithMonitoredScope(String propertyName, ProxyContext proxyContext)]
Throw UnauthorizedAccessException instead of SPUtilityInternal.Send401 for client.svc request.
So what does this mean? It means that API calls are failing and not reachable when workflows are running. In our set up due to domain migration we had two https url and one of them was default. We observed that the API calls via default urls were always failing so we decided to dig deeper.
We found out that in web application web.config file if you have below attributes and have urls under it then API calls are working only for those urls so first we thought we can add all the urls but it seems you cannot add two https url and it is not supported, bascially we are talking about host headers we had three host headers in IIS but only two here.
To fix this and allow all the traffic what you can do is to have only one https url or host header which I will say is ideal way of running SharePoint 2013. Note that SharePoint 2016 or 2019 are not expected to have these issues
Other way is to change config like below and allow all urls
Let’s start with a question, can megamenu be enabled on all site templates?
Well answer is No, it is available only on SharePoint Hub sites which are associated with Microsoft teams or on Communication sites.
What is a megamenu in SharePoint Online?
In the traditional navigration structure you could only have two levels of navigation but now in MegaMenu you can have multiple levels spanning horizontally and vertically.
How it works?
You can create MegaMenu from Site Settings –> Change the look –> Navigation. Note that MegaMenu is default type in Communication sites but if you need to change it follow below steps
MegaMenu can be used to create multi-level horizontal and vertical menus as shown below.
To start with you need to click Edit on right side and Under any heading, when you hover you will see a line with plus symbol to add a menu. Use that to add headers or links depending on what you need.
Once done you can “Make sub link” to make it appear under it
Sample final outcome
How about Security trimming and Audience targeting in MegaMenu in Hub Site Navigation?
There is no security trimming in MegaMenu in Hub Site Navigation, I will say that purpose of Hub site really does not make sense to have MegaMenu security trimmed but at same time it can be debatable.
Audience targeting can be a good thing and it is under work as of May 2019, you can refer here
So that’s about MegaMenu in Hub site, if you have any questions or remarks please contact us via our Contact Us page or via our Facebook page or via Twitter
I think I must have missed the Hub Sites in SharePoint buzz but a blog from my side anyhow.
What is a Hub Site?
Firstly, it is not a template like Communication or Team site, you can register an existing team site or communication site as a Hub Site so if you want to create a Hub site from scratch please create a site preferably a modern one and then register it as Hub Site which can only be done SharePoint Admin in Central Admin link.
Hub site is used to facilitate Intranet in organizations which can have other sites as “Association” or “Navigation” links. You can roll up information from associated and linked sites to the main Hub site by using Apps available.
You can think this of a container site but physically it does not contain any sites but can only be associated.
What makes it unique?
Something like this was not available before but I believe everyone wanted something like this as working with Site Collections and the Sub sites structure is rigid and difficult to change later on.
Hub sites introduce us a flat structure which can be moved easily as sites are just associated and not created under them.
So, uniqueness is in the flat structure which can be implemented easily.
Difference between the Hub site-based structure and the traditional structure is as below
Hub sites vs Sub sites
Hub site based
Traditional – Site collections – sub sites
Hierarchy based structure
Sites are associated and not created under it
Sites are created under a main site
Access permissions do not have any impact in
Access permissions are inherited by default or needs to be managed separately
Easy to move around sites and change structure or associations
No easy ways to change the structure
How to utilize or use Hub Sites?
Hub site should be used to bunch sites together, create an intranet or roll up information together. Bunching or associating sites together should be done based on departments, organizations, key features, team or based on keywords or location etc. or if you want to roll up specific information from different sources.
Hub site can only be really useful if you will be rolling up information and two most easy ways to use OOB of Apps called “Highlighted Content” and “Sites” which can fetch different information from associated sites and show them beautifully.
On modern pages just add a section layout and then select add App using “+” symbol and select Highlighted Content or Sites depending on your needs, I would recommend Highlighted Content as it is really powerful and can roll up almost all data. Refer to screenshots below
As you can view you have following options
Select a source: can select all hub sites or some or specific one
Type of source: can be document, news, lists etc.
Filter and sort to organize your content
Different options for a Layout to support your needs
Other things you should consider while creating and managing Hub sites:
Naming convention of Hub sites so that it can be easily recognized
Name information which needs to roll up also properly so that easy to roll up later
Consider the audience before you start creating hub sites
Consider search scopes while deciding on the association of Hub sites
Also note that you can put a link to non-associated site
How to create Hub sites?
As pointed out earlier there is no template like Hub Site, you have to create a site collection using template either team site or communication. Communication template is recommended one from Microsoft.
Create a site a then select option mark it is a Hub site, you need to SharePoint admin to do all this
After the site is created you can register this as Hub site
Once this is done you can view extra navigation at the top
So that’s about Hub site, if you have any questions or remarks please contact us via our Contact Us page or via our Facebook page or via Twitter
Search can return this error due to various reasons “Search has encountered a problem that prevents results from being returned. If the issue persists, please contact your administrator” but this will be certainly come if there is an error in one of the search components.
If you check in ULS log you will see this error ” Cannot plan query for index system. Index fragment ‘0’ has no available cells.”
This error indicates that there is an error in index partition and you should see a yellow warning exclamation in Central Admin as shown below
If your error meets all these criteria then you have the same issue. If you look at other articles regarding then 90% of articles will mention to do an index reset and do a full crawl which will definitely fix the issue but this should be your last option and not the first one in a production environment.
To fix the issue we should look at clearing configuration cache on the server where index partition is being stored.
The steps to clear configuration cache is very well documented and can be found below
But doing these steps might not fix the issue so follow below instructions
Try first clearing configuration cache and check if error gets fixed
If not then again do the same steps but this time also restart SharePoint Search Service before you restart the SharePoint Timer Service
If this also does not work then try to restart the server after step 1, restarting server in Production environment is not advisable during office hours so do it in planned manner
If this also does not work then we are left with no other option but do an index reset and do a full crawl, use steps documented on Microsoft site Perform index reset
Also note that during these operations if any incremental or full crawl was going on you need to let it finish to make a call if above has fixed the issue. We observed that issue goes away only when crawl has finished.
Above strategy should work in most cases if not then reach out to us and we can help.
There can be situations when your organizations decides to change name due to mergers, acquisitions or splits. In this case quite often users are migrated from one active directory to other. This will definetely have impact on SharePoint users, servers and configurations.
Generally active directory migrations are done in two steps
Migrate users and computers
Migrate servers and service accounts
This post will cover the first point, second one will be covered in second post.
Generally when users are migrated in active directory you would expect that Microsoft products will be handled automatically but strangely that is not the case with SharePoint due to the reason User Profile service works in SharePoint. Reason is that User Profile Service does not work with Secuirty Identifier (SID history).
Before you migrate the users another thing which needs to be taken care is that all the Web Applications needs to allow new domain to do that please refer to below TechNet article