July 15th, 2014
If you are having issues changing the URL of a sub site through the site settings page, this may be because you have document libraries that contain over the amount of items specified via the list throttling setting.
You can overcome this by using powershell, an example is shown below:
Get-SPWeb "https://yoursite.com/Sub-Site" | Set-SPWeb -RelativeUrl "New-Sub-Site"
A variety of errors could be shown when trying to change the Site name via the UI.
- SharePoint 404 page
- List throttling error
July 3rd, 2014
If you get an error when trying to load Dynamics CRM 2011 / 2013 that displays “Invalid Action” from the web UI or from the Outlook Client, the following worked for me to resolve:
- Start/Restart Microsoft CRM Asynchronous Processing Service
- Start/Restart Microsoft CRM Asynchronous Maintenance Processing Service
- do an IISRESET from the command prompt
I am not sure what caused this but it hasn’t come back since, if it does I will investigate further and update this post with more details.
March 28th, 2014
If you receive the following error when trying to install the SharePoint 2013 Pre-Requisites then hopefully this article will be of help.
Error when enabling ASP.NET v4.0.30319
Error: The tool was unable to install Application Server Role, Web Server (IIS) Role.
The common solution to this problem is that you need to get the latest updates from Microsoft Update, not from WSUS.
Step 1 – Run MMC
Step 2 – Add the Local Policy Editor Snap-In
Step 3 – Update WSUS Setting
Select “Specify Settings for optional component installation and component repair”
Enable “Contract Windows Update directly to download repair content instead of Windows Server Update Services (WSUS)”
Step 4 – Re-Run Pre-Requisite Installation
That should hopefully solve your problem
October 16th, 2013
Below is a list of Dynamics CRM Build and Version numbers as a quick reference.
January 17th, 2013
Please don’t hesitate to get in touch if you have any projects you wish to discuss, we would be happy to assist.
January 17th, 2013
Andrew, the founder of Didsbury Design has now successfully achieved the Microsoft Certified Professional Developer: SharePoint 2010. This is just part of our goal to provide better solutions for Business’ looking to harness the value that SharePoint can provide when configured, and customised effectively.
Please don’t hesitate to get in touch if you have any SharePoint or Dynamics CRM projects you wish to discuss, we would be happy to assist.
January 17th, 2013
Andrew, the founder of Didsbury Design has now successfully achieved the Umbraco Certified Developer award at level 2. This is just part of our journey to being able to better provide solutions for business’ looking for a professional Content Management System.
Please don’t hesitate to get in touch if you have any projects coming up you wish to discuss.
September 29th, 2012
So you have decided to go with Umbraco as your CMS (good choice).
After you have installed Umbraco and created a published page via the administration area you should be able to view your site. If you can view the site, this post is not for you!
If you are getting redirected to the installation page even though you have published content then please check that in the web.config you have the following value set to your version of Umbraco:
<add key="umbracoConfigurationStatus" value="4.9.0" />
Sometimes if the permissions were not correct for the web.config file during install you will find the connection string you used upon installation is not persisted and also this version number is not set.
Once you set this value you should be able to view your content.
Hopefully this will save you some time if your having this problem.
April 23rd, 2012
Every now and then, with Dynamics CRM 2011 (and CRM 4), you can end up with two default views for the same Entity. It seems to occur when you import a solution with certain customizations to an entity.
I think in our case it occurred when we renamed the Account entity to be Organisation. A supported way of resolving this is outlined below.
- Create a new view on the same entity called ‘fix’ and assign some filter criteria (it doesn’t matter what)
- Set the new view as the default
- Publish your changes
- Open the new view, go to more actions and delete it. You can’t delete it from the main list of views as you will get an error “You cannot delete a default view until you have specified another view as the default”
- Publish your entity again
You should now only have one default view and no more problems!