Within SharePoint 2019 Central Administration, you can choose to delete a site collection. You can select whether to remove the content database and IIS entry as well.
If you choose to do this and then shortly afterward start receiving TLS errors or destination unreachable type issues, it is important to look to IIS first. When this occurs, I’ve found that for some reason, the SSL cert to other sites sometimes becomes unselected. Simply reselecting the SSL cert on the site binding having issues will fix the problem. An IIS reset is required after.
After migrating data through ShareGate, we needed to change the temporary URL for all sites back to their original. For example, https://sp.domain.com is migrated as https://new-sp.domain.com. We’ll needed to change it back to production URL after migrating from 2010 to SharePoint 2019. Here is the process for doing so:
- Open SharePoint Central Administration
- Under Central Administration, go to System Settings – Configure alternate access mappings
- Click on the domain that you wish to change (ex. https://new-sp.domain.com)
- Change the URL to the desired new URL (ex. https://new-sp.domain.com >> https://sp.domain.com) and leave the Zone set to Default
- Click the OK button to accept the change.
- Open IIS on your new SharePoint server, select the site that you’re changing the URL for and click the Bindings button on the right side.
- Highlight the binding you wish to change and click the Edit button.
- Change the URL to match the one that you set in SharePoint’s alternate access settings and then click the OK button. You’ll have to change both the HTTP and HTTPS bindings if you have them.
- Back in the IIS home window, right click on your site and then Manage Website >> Restart
- Your new URL should now be live.
To provide a system account (ex. DOMAIN\Username) access to SharePoint site crawling, it’s pretty easy to accomplish.
- Open Central Administrator
- Under Application Management, click Manage Web Applications
- Highlight the application that you want to add rights for and click the User Policy button in the ribbon bar.
- In the Policy for Web Application window, click on Add Users
- Leave default of All Zones selected and click the Next button
- Add the user account to add rights for, select the rights level and click the Finish button
When administering a SharePoint farm, you’re bound to have a situation come up where you’re low on diskspace for a site with increasing content. You may want to move a content database to another drive on your SQL server in order to gain some free space back. Fortunately, this isn’t too hard to accomplish using the following steps and should work in SharePoint 2010 or 2013:
1. Quiesce the Farm – This stops people from being able to make changes to your system while you are working on it. To quiesce SharePoint 2010, use stsadm: stsadm -o quiescefarm -maxduration n
2. Backup any database that you are moving
3. Turn off SharePoint Services to unlock the databases You can either stop the services through the Central Administration or you can do it in the Services Console. To stop the connections to the existing databases, stop the following services: Office SharePoint Search Service Windows SharePoint Services Administration Windows SharePoint Services Search Windows SharePoint Services Timer Windows SharePoint Services Tracing World Wide Web Publishing Service
4. After the services are stopped, detach the database(s) that you are looking to move.
5. After detaching the database(s), copy them to your new location.
6. Reattach your database(s)
7. Restart the services
8. Unquiesce the farm: To unquiesce SharePoint 2010, use stsadm: stsadm -o unquiescefarm
* Some of this content is sourced from Microsoft Technet
As a CRM administrator, you may come across the following error in your CRM Event Logs: “Query execution time of XX seconds exceeded the threshold of 10 seconds”
This is said to merely be informational. If you’d like to see the setting in your CRM’s SQL database, run the following script against your CRM’s database:
SELECT IntColumn FROM MSCRM_CONFIG..ServerSettingsProperties WHERE ColumnName=’LongQueryThresholdInSeconds’
It should return the value you had seen in the warning. To lengthen the timeout to stop the error, you can run the following script against your database:
UPDATE MSCRM_CONFIG..ServerSettingsProperties SET IntColumn = ’20’ WHERE ColumnName=’LongQueryThresholdInSeconds’
This will double the timeout threshold to 20 seconds.
We had a need to send custom workflow emails that included all attachments from the Notes section of Opportunities in Dynamics CRM 2015. This is not an out of the box functionality. It requires the development of a plugin that must be registered in CRM to achieve the desired results. I’ll try to be thorough in my explanation, because I know it can be tough to put together the bits of information that you will find on this topic if you’re just starting out developing for CRM. Continue reading “Dynamics CRM 2015 – Adding All Opportunity Notes Attachments to Workflow Emails”
Recently, I ran in to an issue where SharePoint would error out when trying to save a page edit. Even if you just went to edit mode and clicked to save and close, it would error out and provide a correlation ID without having made a change.
Using ULS Viewer, I took a look at the correlation ID to find that the error was, “The SPListItem provided is not compatible with a Publishing Page.”
This was a new error to me, so I started looking for more information. Googling it, I found several references and explanations on what needed to be done, but not many sources really explained the process of fixing it clearly.
To fix this issue, you need to disable and re-enable the Publishing service for SharePoint, using Powershell.
Open Powershell on the SharePoint server as an administrator. Type the following commands:
Disable-SPFeature –Identity Publishing –url http://Site_Name_Here
Wait for the process to complete successfully, then re-enable it:
Enable-SPFeature –Identity Publishing –url http://Site_Name_Here
Assuming the process completes successfully, you should be able to edit and check-in the page again without any problems. It is unclear to me what causes this issue, but at least it’s an easy fix.