Episode #125 of the Stack Overflow podcast is here. We talk Tilde Club and mechanical keyboards. Listen now

Hot answers tagged

14

I got the same error and i did the following steps and worked for me. Go To services.msc Restart the SQL Server (SharePoint) & SQL Server Agent (SHAREPOINT) Check the web site, It'll work. Hope this will help to any one.


5

This issue would occur if the user account "UserAccountName" or "Administrator" doesn’t have enough permission in the SQL server contents databases of SharePoint site collections in your machine. So, add the "UserAccountName" in to your MSSQL server by following the below steps: 1) Go to that server and open the SQL SharePoint instant using Management ...


5

I can't see that you have run the SharePointBAC.ps1 in your script, which is downloaded from the Codeplex page SharePoint Backup Augmentation Cmdlets. The scripts Get-SPBackupCatalog Set-SPBackupCatalog Remove-SPBackupCatalog Export-SPBackupCatalog is not out-of-the-box native cmdlets in SharePoint Management Shell or PowerShell ISE with the reference of ...


4

The Backup-SPFarm command should use a network share where The service accounts, Farm accounts and SQL Server service accounts have Full Control access to the share. This is because SharePoint uses SQL commands for running parts of the backup and these execute in SQL Server's context. More information: Prepare to back up and restore farms in SharePoint ...


4

This happens because your DCWebTemplate is a module. You can't use a module to deploy to farm. If you check your spi-file you can see the attribute SupportedDeploymentScopes is only web and site. <ProjectItem Type="Microsoft.VisualStudio.SharePoint.Module" SupportedTrustLevels="All" SupportedDeploymentScopes="Web, Site" xmlns="http://schemas.microsoft....


4

While recommended to install security updates as soon as possible, you will need to evaluate the security risk of not installing a particular security patch. This is something we will not be able to help you with. You do not need to install the Cumulative Update if you do not wish to install it. Yes, some non-CUs increment the farm build number due to an ...


4

You already found out a lot of stuff regarding security updates, CUs and version number increments. There's nothing wrong in your post, but i would like to add some comments especially to your questions: It is valid to install security-patches for Windows including SharePoint specific security-updates (if there's one available that month). Theoretically ...


4

According to MS, SharePoint does not have a single, specific build version (https://blogs.technet.microsoft.com/stefan_gossner/2016/08/23/sharepoint-does-not-have-a-build-version-full-stop/). The reason is due to SharePoint being made up of different sub products. Some update the farm version, others update the version in the config db and others simply ...


4

There is no "official" recommendation from Microsoft to always install the latest CU for SharePoint. SQL Server has such an advice. BUT: If you open a Microsoft Support Case, you will get told to patch your SharePoint-Farm before the case will continue. If you really ask for "maximum damage": A completely broken farm and the need to fully restore the farm ...


4

To register a workflow service to a specific site collection you should run Register-SPWorkflowService cmdlet that requires providing the below parameter values -SPSite it denotes to the site collection URL that you need to use the workflow service on it. Note: It seems that each site collection needs to be registered with workflow service. But ...


4

The Backup-SPFarm command should use a network share where The service accounts, Farm accounts and SQL Server service accounts have Full Control access to the share. This is because SharePoint uses SQL commands for running parts of the backup and these execute in SQL Server's context. More information: http://www.adventuresinsharepoint.co.uk/2015/01/11/...


3

That is not an official SP commandlet You can download it on codeplex https://sharepointbac.codeplex.com/ After downloading you install it by running the "SharePointBAC.ps1" included in the download Further Documentation


3

You should use the Add-SPShellAdmin Cmdlet to grant such permissions for users on content DBs. You can remove the permissions via Remove-SPShellAdmin, or list the granted users via Get-SPShellAdmin.


3

WebTemplate isn't allowed in Farm scoped features. See Elements by Scope even though it's for SP2010 it can be used as a guideline for SP2013. The best you can do is WebApplications scope


3

You can find a list of possible values for the Microsoft.SharePoint.Administration.SPServerRole enumeration in the corresponding MSDN article. These are: Invalid: Specifies that the server does not have a registered role in the configuration database. WebFrontEnd: Specifies that the server is a front-end Web server within the SharePoint Foundation ...


3

if you ask for the best practice then: Create the SQL_Admin: The SQL Server service account is used to run SQL Server. It is the service account for the following SQL Server services: MSSQLSERVER SQLSERVERAGENT. SQL Admin on the SQL Server. it should be domain user with Local Administrator on the SQL Server. read more about the best practice: SharePoint ...


3

The farm couldn't have been 'upgraded', but the databases certainly could have. For the Content Databases, you can run the following T-SQL query: SELECT * FROM Versions (NoLock) That will tell you the version history in the Version column.


3

There is no risk to applying the SP3 on the SQL server 2008. But you have to plan it.I would apply the patches in the following order. Schedule a Downtime for the SharePoint I will stop the IIS & timer services so that no connection should make to SQL server while patching. (In one of farm I shut down the server) Apply the Patch to SQL server, test and ...


3

Sharepoint add-on is new standard and MSFT encourage all the customer to adopt that one. Main reason (there are many others)is Office 365, if your company want to move Office 365 then you have to rewrite all customs solutions as add-on. In O365 no farm solution deployment at all. And you know this feature already on the path of death, so why not start with ...


3

If you have wsp file then you can install it to other farm (I am assuming 2nd farm is also on same sharepoint version). Also make sure you follow the same deployment steps as you did in your 1st farm. 1 thing, I noticed sometime developer use the hard coded URL in the code...so u have to make sure no hard coded URL in ur wsp.


3

As farm is not configured then best way is install the latest updates then configure it. Yes there is change in sharepoint 2016 patching, For SP 2016 MSFT release two files every month. You have to install both files (any order, does not matter). After this configure the farm.


3

There should be no impact rather you will fix the issue with SharePoint. Time zone settings should be same across all SharePoint servers otherwise you will face timer service sync issue. I think that's what you are are seeing in your case. Check this link, https://support.microsoft.com/en-us/help/2655727/sharepoint-all-servers-in-the-farm-should-be-in-...


2

You are correct! http://office.microsoft.com/en-001/windows-sharepoint-services-it/managing-the-configuration-database-HA001160814.aspx The farm can contain several servers, applications and so on.. But it's all defined in THE configuration database.


2

You should get the search benefits right away, you won't get some of the UI components until the visual upgrade is done. I remember being in a BA Insight presentation a couple months ago where they talked about upgrading to get the backend services like search but stay on the 2010 UI until ready.


2

AFAIK, in short there's no way to recover the passphrase. WHY? Because it was intended this way in the first place for security reasons. The answers that you find from other sites/people are all right to CHANGE the passphrase, not to recover them. So if you've forgotten your passpharse, the best you can do is to create a new one. Hope this helps you.


2

I dont do this, even you can rename the DB while restoring the from backup but still you are on your production server. Just think, more pressure on the SQL Server, resource fighting, and just a single mistake blow up your production Data. I would go for separate SQL server for this test.


2

In my case the user account under which apppool for web application was running was locked. unlocking the user account solved the issue.


2

There is no farm level timer job. A custom timer job will only be installed on Web application/Site Collection level. So it's impossible to deploy a custom timer job definition on farm level. Edit: But, you can have a custom timer job code which is deployed to the farm but it is installed/register on a Web Application level.


2

No this is not possible. one server can have only SharePoint farm. But you have to mutliple farm's database on single SQL server.


Only top voted, non community-wiki answers of a minimum length are eligible