Event 3760 – SQL Database on SQL Server Instance not found in Event Log in SharePoint Server

Problem :The event log on my WFE is filled with errors every hour complaining that a database on my SharePoint SQL instance is not found.

Cause: This was caused by me creating and deleting a service application, and then going into SQL Management Studio and manually deleting the associated service application database. SharePoint still had a record of the database in its config database.

Solution : Delete the record of the orphaned database using PowerShell

1. Open SharePoint Management Shell
2. Type: Get-SPDatabase | fl name, id
3. Find the database you wish to remove and select its ID.
4. Type: $pp = get-spdatabase <id>
5. Type: $pp.delete()

SharePoint’s record of the database is now deleted and it should no longer complain that the database is not found.

Changing Password in SharePoint 2013 by powershell

Follow these steps to change the password for SharePoint :
 

·         Open up the SharePoint PowerShell command prompt
 

·         Set-SPManagedAccount - UseExistingPassword -Identity DOMAINA\SPSAdmin
 

·         Where DOMAINA\SPSAdmin is service account that had it's password changed in the AD
 

·         You will then be prompted for the existing\new password for "DOMAINA\SPSAdmin"
 

·         Run "Repair-SPManagedAccountDeployment" to verify
 

·         the passwords are now in sync •Next do an IISRESET command
 

·         Run Repair-SPManagedAccountDeployment to verify that you do not get this message: Repair-SPManagedAccountDeployment : The password for the account DOMAINA\spsadmin, as currently stored in SharePoint, is not the same as the current password for the account within Active Directory. To fix this with PowerShell, run Set-SPManagedAccount -UseExistingPassword
 

·         the Set-SPManagedAccount -UseExistingPassword command will update the config database and service using by this account.

SQL Query to check timer job lock

To check which server is taking care of running timer jobs in ShaerPoint Farm, we need to run this query on content database in SQL and we can manage this settings at manage content database in central admin.

 

select a.lockedby, b.name

 

from WSS_Content_JCES_Manfacturing.dbo.TimerLock a inner join SharePoint2013_ConfigDB_Aug30.dbo.Objects b

 

on a.lockedby = b.Id

Enable SharePoint PowerShell Commandlets in the PowerShell ISE

To get the snap in loaded you'll need to add the snap-in in your PowerShell ISE profile. Here's a quick script to get this done from within the ISE, just type this in the ISE command window:

if (!(test-path $profile )) 
{ 
    new-item -type file -path $profile -force 
} 
 

$cmd = 'if((Get-PSSnapin | Where-Object {$_.Name -eq "Microsoft.SharePoint.PowerShell"}) -eq $null) 
{ 
    Add-PSSnapIn "Microsoft.SharePoint.Powershell" 
}'

out-file -FilePath $profile -InputObject $cmd -Append

 

Run the commands then close and open the ISE. You now should have the SharePoint snapin loaded and you should get the friendly auto complete functionality you're used to in the SharePoint PowerShell command window.

Challenges During SharePoint Migration

1) SharePoint Customizations:

The complexity begins with the availability of SharePoint customizations, also commonly known as web parts. Apart from being a very noticeable feature of SharePoint, these web parts actually prohibit you from performing a standard migration and result in an unsuccessful migration process. An unsuccessful or failed data migration can cause loss of data and eventually business.

2) SharePoint Application Inventory:

 

A SharePoint Application Inventory would typically gather the following information:

• List of all SharePoint Farms, Servers, Server hardware details, Application Install path, Services running on server, etc.
• Inventory of Web application, Site collection, Custom solutions like Web Parts, Features, Event handlers, etc.
• List of Users, Groups and Application Level permissions details
• Size and Complexity of the applications
• While gathering the SharePoint Application inventory, you may categorize and group them, based on Business, Technical & Design parameters, which may not be always, correct.

 

3) Size & Complexity of the Application

 

• SharePoint OOB (out-of-box) template based applications are simple & easy to migrate. The complexity comes when you have SharePoint Custom developed application to be migrated.
• A SharePoint application will be complex to migrate, if it has one or more of the following design elements:
• Heavy customized Master Pages & Page Layouts User Interface.
• Custom Solutions like Web Parts, Features, Event handlers, Site templates, List template, Pages & User controls, JavaScript, CSS, CAS, Content Types, InfoPath form etc.
• Workflows with complex functionality.
• Custom Search scopes, external content sources.
• Integration with external systems (SAP, Oracle and etc.)
   
  4) Post Migration Challenges
   
  Once the Migration is complete based on selected migration approach. In case of Database-attach approach you may face many challenges post Migration as many SharePoint design elements are not migrated successfully. Here one should be ready with all the Post migration steps and work around if no out-of-box solution is available.
  Depending on the customization of the SharePoint application, this could potentially result in a lot of post migration related activities. Typically, these would include moving 14 hive folders like images, js, css, etc., master page customisation, visual upgrades, update web.config, resolve absolute URL issues, resetting views for List view Web part, configuring search scopes, etc.
  Some Design elements will have challenge to migrate:
• Email Enables Lists.
• The “In Progress” workflow tasks, will have challenge to migrate.
• SharePoint Web Analytics system is not available in the newer version now. It’s been replaced by new 2013 search service. The previous analytics reports will not be imported into new version.
• Some of Templates are removed and not supported in the newer version
   
  5) Migration Planning Challenges
   

• SharePoint Migration Project becomes complex if you have Applications/Sub sites to be migrated in hundreds/thousands, and content size is huge, you need to better plan such migration projects. Large migration projects are generally distributed in smaller migration lots for ease in migration, but managing multiple migration-lots with multiple migration-teams is another challenge.
• SharePoint Web Application Migration prioritization is a big question – whether to migrate complex application lot first, which will increase the confidence of the migration team and user community, or Plan for simple SharePoint OOB template base application migration, which will migrate quickly and can be released to user community. Normally this decision is driven by business or User requirements.
• Setting up the environment for Migration & Testing is a challenge. If requirement is for migrating multiple multilingual applications, than you need to verify Migration Tool capability for such requirements.
• Consider content Migration Time for large Content database with large size attachments, this typically takes significant time while migrating content with Migration Tool.
• As Migration progresses, you need to plan for Farm Design & Topology, Taxonomy, Capacity Planning, Scalability Requirement, Backup and Disaster management, User Training etc.