Tuesday, January 2, 2018

The breakpoint will not currently be hit. No symbols have been loaded for this document. In SharePoint Development or Deploying SharePoints wsp

These symbols, Dlls can be belongs to same project or any other references from other projects.

There are various reasons for this. I will explain few tips that you can try.

Check for multiple solutions

If the same reference libraries are referred from other solution and if it is in open in a visual studio solution, assemblies might being held with file lock by other visual studio; that cause not to deploy reference assemblies to GAC (global assembly cache).   

Full Debug Information

This is first to try.  Check the project build information and make sure full debug information is specified.
Go to properties for SharePoint Project.

Then go to build and advanced section.

  Then check for debug information and make sure it is set to full.

 Check Load Symbols in debug mode

This is a quiet a handy way to check the symbols debug files.  First press F5 or start debugging your project.
Then you can find the Module Menu under Debug -> Windows -> Module Menu.

There you can find the symbol load information and loading path.

As you can see you will find Loaded Symbols and path, there is a Load Symbol button there you can load symbols and change the path. Or else you can copy symbols to specified path. But sometime it might say that debug information are not matching with image, meaning debug information and assemblies deployed are not identical.

Enable Just My code

Tools – Option -> debugging - . general > un tick just my code

This is well explained here.

You can configure Visual Studio to automatically step over system, framework, and other non-user calls and collapse those calls in the call stack window. The feature that enables or disables this behavior is called Just My Code. This topic describes how to use Just My Code in C#, Visual Basic, C++, and JavaScript projects.

Package the libraries

Seems like your code is not package with the solution

You need to package the assemblies to deploy with the package. Generally runtime will use the available packages in the GAC unless it is packaged.

You can go to project properties.

Then go to advanced settings
Package - > advance - > bind the assemblies

Add the assembly to the package.

Monday, October 16, 2017

There are no products affected by this package installed on this system when you try to update the SharePoint

There are no products affected by this package installed on this system when you try to update the SharePoint

This a quiet a common massage that you can experienced with while you are trying to install updates in SharePoint.

These updates can be

 -  Hot fixes
-  SharePoint Updates
-  KBs.

AS message indicates, its giving a feeling that it is been installed in the environment, But when you check in the Central Admin you might wonder it is not installed yet.

How to check the Updates are installed in the SharePoint Environment

-  Open Central Admin
-  Navigate to Upgrade and Migration

You can check those info from Central Admin -> Upgrade and Migration


Select the View Farm where you can examine all the patches in the SharePoint environment.

Here you can see whether particular patch is really installed or not. IF it is not installed and you are getting the message there is something else to check on. There could me various reasons for this.

But most of the times pending windows updates are the root.

How to check windows updates and install the updates

There are many ways that you can check updates, I’m describing a common way which can be applicable for most scenarios

-  Go to control panel

-  Then click on check for updates to confirm that is there any pending updates in the system

Check products and patch installation status.

For my issue is there are pending updates in windows updates in control panel.

You can install pending updates from here itself.

After installing the updates you can restart (this is optional) the machine to give a fresh try.

Tuesday, September 12, 2017

Insufficient SQL database permissions for user 'Name: doman\SP_UserProfiles SharePoint 2013 User Profile

Insufficient SQL database permissions for user 'Name: doman\SP_UserProfiles SID: S-1-5-21-2738186777-3937669245-3595685374-1123 ImpersonationLevel: None' in database 'SharePoint_Config' on SQL Server instance 'ADXWSQL.adxweb.ae'. Additional error information from SQL Server is included below.

The EXECUTE permission was denied on the object 'proc_putObjectTVP', database 'SharePoint_Config', schema 'dbo'.

This is a caused by not having permission to database objects of using least privileges configuration in farm configuration. Thus you need to give permission exclusively to this Object.
First you need to Connect to SharePoint Database using privileged account.
Then go the SharePoint Config Database and security section. Then go to Roles and find WSS_Content_Application_Pools under the Database Roles section.

Double click (or Right Click -> Properties) the item and select the Securable section in the modal window.

And click Search.. and select Object Type in the Window and Click OK.

Then click on Object Types and select the Stored Procedure.

 Type proc_putObjectTVP  in Object names section and check names for select the item.

and select the item and Click Ok.

Then you can see the item in the securable and give the execute permission to the object.

Tuesday, August 8, 2017

The URL is invalid, it may refer to a nonexistent file or folder or refer to a valid file that is not in the current Web in SharePoint 2013


This is common error when you are working with SharePoint.

This is can be due to various reasons but most common erros are due to Database issues.

1. Not Enough Space

Check your database related to SharePoint including

  • SharePoing Content Database
  • SharePoint Contect Database Logs
  • Temp Database Logs
  • SharePoint Service Databases
  • SharePoint Service Databases Logs
  • SharePoint Service Databases Temp Logs


check these databases have enough space to perform actions.


2.Not sufficient permision

Other reson is for not having enough permision to SharePoint Content Datase. YOu can find the related content databases from browsing through the cetral admin.


Go to application management and then click on Manage content databases.


Then you will find the related content database for the web applicaton. So make sure those databases having db_owner permision fo SharePoint Farm Account.