Ultimate Solutions

Hi Friends, As you know that SharePoint 2016 beta 2 has been released. I decided to make my hands dirty on this buggy version. My setup was as follow. SharePoint Box-  16 GB RAM - 120 GB HDD- Windows Server 2012 R2 SQL 2012 --- 8 GB RAM - 120 GB HDD -- Windows Server 2012 R2 I started installation with Prerequisite installer. You do not believe it gave error from first basic step. The tool was unable to install Application Server Role, Web Server (IIS) Role The issue was setup was not able to install .NET framework 3.5. Server manager also unable to install it. I ran the following command and issue was just ran away. Dism /online /enable-feature /featurename:NetFx3 /All /Source:D:\sources\sxs /LimitAccess Somehow tool was able to install IIS and its components. Later it gave error on following components  vc_redist.x64 for 2015 vc_redist.x64 for 2012 I manually downloaded it form Microsoft website and finally all prerequisites installed.

Hi Friends, Its over a year since we met each other. I am back guys. Lets start the post. This time i am going to describe one stupid error in SharePoint web part deployment. The developer came to me today with a issue . A Web Part or Web Form Control on this Page cannot be displayed or imported. The type YourNameSpace.YourPart, YourPart, Version=1.0.0.0, Culture=neutral, PublicKeyToken=SomeToken could not be found or it is not registered as safe. When you closely see , error itself shows some assembly is not added in safe control list. This is an unusal behaviour. When you deploy any solution , SharePoint does take care about adding safe control values in web.config. But what goes wrong here?? Web Part namespace was diffrent than specified in solution. It mayy possible that code is taken from some one or copied from another location If you have a web part, you will have a .webpart file. Open it up. You will want to ensure that the type name references your namespace and ty