Skip to main content

Posts

Showing posts with the label Exceptions

The XSS Auditor refused to execute a script in http://default.aspx because its source code was found within the request. The auditor was enabled as the server sent neither an 'X-XSS-Protection' nor 'Content-Security-Policy' header in SharePoint 2013

The XSS Auditor refused to execute a script in http://default.aspx because its source code was found within the request. The auditor was enabled as the server sent neither an 'X-XSS-Protection' nor 'Content-Security-Policy' header in SharePoint 2013 Recent google chrome update may breaks the sharepoint layout pages and other custom development pages due to XSS Auditor. I have added the HTTP Response Header  to the SharePoint Web Front End Servers  and then it worked fine.    

The content database has a schema version which is not supported this version

How to copy you production SharePoint  database to development environment. I had my production environment as SharePoint 2013 SQL Server 2012 and I want to move the instance to another environment , which is freshly installed and different environment and different KBs Share Point 2013 SQL Server 2016 How to migrate SharePoint 2013 , SQL Server 2012 Content Database to SharePoint 2013 SQL Server 2016. Method 1. This is a general method, which is used for upgrading your content database. 1 . Get the back up of the current Content Database 2. Copy SQL backup to new environment 3. Restore the SQL Back Up in to the new environment 4. Go to the Security Login section and grant permission to content database for existing SharePoint Users.   5. You need to select the User mapping and DBO for the content database. 6 Then, execute below PS in SharePoint PowerShell. Make sure you executed as Run as Administrator 7 Firstly, You need to Update the content database. 8. then, mount the usi...

The underlying connection was closed: Could not establish trust relationship for the SSL/TLS secure channel in SharePoint 2013 Server environment

Issue Could not establish trust relationship for the SSL/TLS secure channel with authority Environment: SharePoint 2013 Farm with multiple nodes connected to connected to load balancer have a Service Oriented architecture to connect other services from SharePoint app servers SharePoint Nodes are connected to  other services using services oriented services using endpoint defined   Symptoms :   SharePoint servers are communicate with Remote service using https protocol using   SSL. When I check the validity of the remote certificate from the browser It depicts it is valid. Resolution I took while me to figure this out. It is true it is about the certificate but it is not the  end certificate. certificate chain is broken in the Intermediate level. You can find this easily by checking details from Certificate. Then navigate to Certification Path You should see these Root and Intermediate as verified. If they are not valid or expired, you will see a wa...

Configuring Application Server Role, Web Server (IIS) Role Error in Installing SharePoint 2013 in Windows Server 2012

Issue This error appeared when I'm configuring the SharePoint 2013  farm Pre Requisites using the installer. Use AutoSPInstaller and it will end with below error 2019-01-22 09:48:02 - Return code (2) 2019-01-22 09:48:02 - It is recommended that you keep your Windows operating system up to date on http://windowsupdate.microsoft.com When you try SharePoint prerequisites installer (prerequisiteinstaller.exe) it ends with below error. Application Server Role, Web Server (IIS) Role: configuration error How to solve this issue There are numerous reasons where you will encounter this issue. Resolution 1 Try to execute the installer using Admin Account and you should be a local admin on your sever. Resolution 2 Install the .Net components manually using server manager. Add Roles and Features and then Skip until you  reach Features , And install .NET 3.5 and 4.5 as described. You might need to insert Source Path for installing 3.5 Framework.  Resolution 3 Sometimes installer cou...

AppFabric installation failed because installer MSI returned with error code : 1603

Issue AppFabric installation failed because installer MSI returned with error code : 1603 Symptoms Installing SharePoint using  Off Line method using Auto SP Installer. Installing SQL server before in the same server , this is happening when you set up a Test server where you install everything in the same server. Install or manual installing App Fabric with out going thorough prerequisites installer. Manually updating existing App fabric installation with all features.   Resolution There could be many reason behind this problem. But most common problems due to manual installation and having incorrect system variable for the PowerShell path. How to Resolve Method One Just uninstall the existing installation from the control panel and re-run the SharePoint prerequisites installer or Auto SP Installer Method Two Change the System Variable to correct value if it is wrong. for this go to the  PC Properties then Advanced System Properties and Environment Variables Then check ...

TypeError: Cannot read property 'replace' of undefinedTypeError: Cannot read in SharePoint 2013

TypeError: Cannot read property 'replace' of undefinedTypeError: Cannot read property 'replace' of undefinedTypeError: Cannot read property 'replace' of undefined TypeError: Cannot read property 'replace' of undefinedTypeError: Cannot read property 'replace' of undefinedTypeError: Cannot read property 'replace' of undefinedTypeError: Cannot read property '_events' of null This is a common error you might receive based on very common actions that you performed as an Administrator How This might occur when you did a Patch Update Copy your content database from another SharePoint environment Installing Security Updates Reason Main reason behind the error is localize content in your list. This error occurs most of the time with lists that has multi local content Solution Check the Localization updates and versions installed in the source server Download the relat...

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 Then 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 a...

Add-SPSolution : This solution contains one or more assemblies targeted for the global assembly cache

Exception Add-SPSolution : This solution contains one or more assemblies targeted for the global assembly cache. You should use a strong name for any assembly that will be in the global assembly cache. At line:1 char:1 + Add-SPSolution + ~~~~~~~~~~~~~~ + CategoryInfo : InvalidData: (Microsoft.Share...dletAddSolution:   SPCmdletAddSolution) [Add-SPSolution], SPException + FullyQualifiedErrorId :Microsoft.SharePoint.PowerShell.SPCmdletAddSolutIon   I have encountered this error when I deploy my SharePoint solution (wsp) to SharePoint farm as a global assembly. This error is due to not singing the project before deploy. Solution: Go to project properties of the SharePoint project. Then select an existing signing key or create a new one to sign and build the project. Now you can Build the project again and try using Add-SPSolution, which should work fine.

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 mod...

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.

You are being redirected to the following url that was not registered as the app launch url

“You are being redirected to the following url that was not registered as the app launch url https://xx?SPHostUrl=xx&SPLanguage=enSPClientTag=0&SPProductNumber=xx&SPAppWebUrl=xx&{AppContextToken} If you trust this url, click here to proceed to the app now. Otherwise go back to the previous page or close this page." It is common that you may have encountered this kind of an error when you are accessing an App that you have developed and published to the SharePoint 2013. There can be many deep reasons behind the message such as Not provisioning the app web correctly Errors on App management service But most of the time it is because of not registering your app in the SharePoint. You can simply follow following steps to register your app in the current SharePoint site. First go to Appreg.aspx page which used to register the app in http:// xxx/_layouts/15/Appreg.aspx . Then you will find a following interface where you can register your app wit...

Insufficient SQL database permissions for user 'Name: doman\SP_UserProfiles SID:

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 Searc...