SharePointSupport

I had a task to create a proof of concept environment for SharePoint 2013 for a presentation to a top level exec. Installed and Configured a SharePoint 2013 farm on couple of VM's with dedicated WFE/APP and SQL Server boxes, as this will be used as a POF and the reqcuirements were not clear how long the boxes will be used. MS has released the deployment guide for 2013 must read before thinking of creating a new farm. Created a new web application on the new farm and a root level Site Collection based on Team Site Template. Till this moment everything was looking good. On accessing the Site got the following error : SharePoint returned the following error: Invalid URI: The URI is empty. Contact your system administrator for help in resolving this problem. My first encounter with an issue on 2013 on a vanilla environment, thought it would be good to have this as a reference. To resolve this, I had to create and configure my site i.e. Created a new web app for my site C...

Error : "Cannot add the specified assembly to the GAC in SharePoint 2010" We had a solution deployed numerous times as it houses a line of business process in SharePoint 2010. On performing Upgrade Solution via  stsadm  or  Update-Solution  via Power Shell , encountered the error: cannot add the specified assembly to the GAC. We started by created a test solution package and deployed it on the environment which worked fine to identify whether the issue was with the Package or environment. On updating the LOB Solution , it couldn’t add the assembly to the GAC for LOB WSP, on one of the WFE servers. Performed an IISRESET and restarted the timer service on the failing WFE, deployed the WSP package again, it did work but when we tried updating it again at the later stage, got the same error. Solution  : I had to rely on  Process Explorer  to figure out what process was using the  DLL  and from where. The beauty of this tool is, it...