I tried to copy the content DB from Prod to Dev server for the first time in my SP 2016 environment. Both the environments build versions are same (16.0.4705.1000). However in the prod under "Manage Patch Status" I see one extra Feature Pack 2 patch (16.0.4588.1001).
https://support.microsoft.com/en-us/help/4011127/descriptionofthesecurityupdateforsharepointserver2016september12-2017
Now when I am doing Mount-SPContentDatabase, I get the following error.
Mount-SPContentDatabase : An extension defined in the database is not registered with the farm.
In the ULS I see the following information. It says the project server database extensions are missing.
Following are my questions,
Is this because I have installed Feature Pack 2(link above) in Prod which has security updates for Project server? We don't have project server enabled in either of the environments.
Can I install the Feature Pack 2 in Dev now even though it has higher security update already installed? Isn't the later patch includes everything that was released in the previous patches?
This is just for my understanding. In the manage patch status why does the Install Status for feature pack 2 shows as "Superseded" even though I have other later patches?
Tried Restore-SPsite as well but getting error "The extension set does not match."
Had the same problem during the migration from 2016 -> 2019.
My solution:
Register the missing extension https://techcommunity.microsoft.com/t5/sharepoint-support-blog/upgrading-a-content-db-from-sharepoint-2016-to-sharepoint-2019/ba-p/1374209 (look at the bottom of the post)
remount the contentDB
Required code to perform the registration in step 1:
Check extensions in old farm
$contentservice=[Microsoft.sharepoint.Administration.SPwebservice]::ContentService
$contentservice.RegisteredDatabaseExtensionTypes >> SP2016Farm_registered_Extn.txt
Check extensions in new farm
$contentservice=[Microsoft.sharepoint.Administration.SPwebservice]::ContentService
$contentservice.RegisteredDatabaseExtensionTypes >>SP2019Farm_registered_Extn.txt
Register missing extension in new farm
$svc = [Microsoft.SharePoint.Administration.SPWebService]::ContentService
[System.Reflection.Assembly]::LoadWithPartialName("Microsoft.Office.Project.Server.Database.Extension") | FL
$svc.RegisteredDatabaseExtensionTypes.EnsureAdded([Microsoft.Office.Project.Server.Database.Extension.ProjectDatabaseExtension])
$svc.Update($true)
In my case i did the steps below before i have registered the missing extension, but i think/hope there is no need to do that.
Powershell: Enable-ProjectServerLicense (Trail License)
Check running Sharepoint CA > ProjectServer Service
Check/create Sharepoint CA > ProjectServer Application
Related
I am getting an alert in Sharepoint Central Admin that The SharePoint Health Analyzer has detected some critical issues.
On checking, I found the alerts like:
[MissingSetupFile] File [Features\xxxx\xxxx\xxx] is referenced 1 times in the database [PROD01_Content_xxxx], but exists only under Microsoft SharePoint Foundation 2010 setup folder. Consider upgrading the feature/solution which contains this file to the latest version. One or more setup files are referenced in the database [PROD01_Content_xxxx], but are not installed on the current farm. Please install any feature or solution which contains these files.
[MissingFeature] Database [PROD01_Content_xxxx] has reference(s) to a missing feature: Id = [f99f774c-6160-4bb6-8519-10e30b02d5b3]. The feature with Id f99f774c-6160-4bb6-8519-10e30b02d5b3 is referenced in the database [PROD01_Content_xxxx], but is not installed on the current farm. The missing feature may cause upgrade to fail. Please install any solution which contains the feature and restart upgrade if necessary.
[MissingWebPart] WebPart class [a9bc1035-cf56-e003-8a4d-fff0bb3da148] (class [Microsoft.Office.Server.Search.WebControls.SearchApplicationSystemStatus] from assembly [Microsoft.Office.Server.Search, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c]) is referenced 1 times in the database [PROD01_SharePoint_AdminContent], but is not installed on the current farm. Please install any feature/solution which contains this web part. One or more web parts are referenced in the database [PROD01_SharePoint_AdminContent], but are not installed on the current farm. Please install any feature or solution which contains these web parts.
I followed the link:
http://get-spscripts.com/2011/06/removing-features-from-content-database.html
But unfortunately, on running the script, it shows the feature does not found.
One thing I would like to mention is: I've deployed the sharepoint 2010 wsp on 2013 version.Is this the reason for getting [MissingSetupFile] error?
What can I do? Any help will be appreciated.
Thanks,
Pay attention to the first message that says "but exists only under Microsoft SharePoint Foundation 2010 setup folder" . This means that you have deployed a 2010 solution into a 2013 farm. But is only installed to 14 hive. for the solution to work properly in the 2013 farm, it needs to be installed to the 15 hive also.
Here is the PowerShell that installs to both 14 and 15 hive.
Install-SPSolution -Identity 'your custom solution.wsp' -GACDeployment -CompatibilityLevel {14,15} -AllWebApplications –force
The link below provides the solution.
Worked for me.
http://sharepointsoldiers.wordpress.com/2013/04/22/sharepoint-2013missing-serverside-dependencies/
Our Sharepoint 2013 Application failed to install and is stuck in a odd state. I followed the recommended approach for deleting the application using powershell commands on the hosted Sharepoint server, but it doesn't execute properly.
Visual Studio Deployment/Retract Reports:
Skipping the uninstall step because the app for SharePoint is in an invalid state and cannot be uninstalled.
PowerShell Commands
$instances = Get-SPAppInstance -Web http://mysite/sites/collection
$instance = $instances | where {$_.Title -eq 'Application.Title'}
Uninstall-SPAppInstance -Identity $instance
Executing this PS command throws...
The System Account cannot perform this action.
There is no option from the Sharepoint UI to remove the application, and retrying the install also fails. I've tried other user accounts to execute this powershell command (other than the system account), but no dice. I will have to delete the developer site collection if there is no other solution.
I'm faced this problem before on my Office 365 SharePoint Online when deploy SharePoint Hosted App. Then I submit Microsoft Service request and work with MS Technical Support Team on this issue. This problem seem to be something error in SharePoint backend database by itself (I'm not sure to consider it is SharePoint defect).
Did you check the app details installation error report? If you get the message:
"The content database on the server is temporarily unavailable."
Need help: Error 'Install App for SharePoint': An instance of this App already exists at the specified location., I'm quite not understand the answer but there is one comment from Jeremy Thake which seem to be deleted on this thread, he said that:
"…so I actually just restarted the whole environment and when Windows
came back up and I went to the SharePoint Site…the App was gone ;-)"
So here is my advice before you commit to delete your site collection:
Try to deploy your to the another developer site collection and check whether this problem still occur as the same.
Try to increase your app version or change app name/title/id and deploy to the same site collection and check whether this problem still occur as the same to your new app instance.
For SharePoint Server, try to restart IIS/Window Server if you're able to do that. Also install any latest SharePoint Update/CU.
For Office365 - SharePoint and have you have license account, you should submit the service request, if not you should wait about several day and try to remove this app instance again through UI.
Hope you can remove your app and know the root cause exactly.
I have faced this issue some times in on-premises SharePoint.
But for solving this I gave another account (or you can use 1 that you have) shell admin rights.
Note this account CAN'T be marked as a System account on SharePoint!!
Then with this different shell admin account you execute the same script. That always worked for me (I also got some strange installation behavior and needed do remove the app).
I am in need of help getting Local Development STS running. I just started with MSDN tutorials and got stuck when trying to build WCF service using WIF. So far I did following:
Installed "Identity and Access Tools" in my Visual Studio 2012
Created new WCF Service project in new solution
Right clicked projects name and selected "Identity and access..."
Selected "Use the Local Development STS" option on first tab and changed token
type to "SAML 2.0" on "Local Development STS" tab
Clicked "Ok"
I end up with following that informs me about problems with certificate:
I verified that the file is there physically.
I verified access to it - System, Administrators and my user have full access to it (only last option is unchecked)
I tried to install the certificate manually, but it is protected with password and I cant find it anywhere
I tried to toy around with "Identity and Access..." wizard
I tried to google the answer
I tried to check if I have certificate like that installed, there are tree Personal certificates in my Local Machine store, but I have no idea how to check their subject or whatever else
So far I wasn't successful. Could anyone advise how to fix the situation, so I can be sure I have proper certificate installed, I would be eternally grateful.
Erchi
Are you using the .NET 4.5 tutorials - WIF Code Sample Index?
To check the subject:
Start / Run / mmc
File / Add - Remove Snap In
Certificates - Add.
My User Account - Finish - OK
Expand the tree as required - double click on certificate - Details.
I am using SharePoint 2010 Foundation and I have a prolem with the search on there. Everytime I search for something I get the response of The search request was unable to connect to the Search Service.
I have spent alot of time looking at this and I cannot seem to see what is causing the issue. The SharePoint Foundation Search service is started but there are no services listed on the server for search other than the 'Help Search'.
Also, if I look into my content databases under the 'Manage Database Upgrade Status' it telling me that the database is too old...
Could anyone point me in the right direction as to how to resolve these issues as it is sending me mad!!
Many Thanks in advance...
Luke
Execute this command in SharePoint 2010 Management Shell (run as administrator)
psconfig -cmd upgrade
It will initiate standard SharePoint Products update and upgrade all databases which are in either "version mismatchm, upgrade is recommended" or "old, upgrade is required" status. The tool runs in command line and gives your updates about installation progress, like this.
PS C:\Users\Administrator> psconfig -cmd upgrade
SharePoint Products Configuration Wizard version 14.0.6009.1000. Copyright (C) M
icrosoft Corporation 2010. All rights reserved.
Performing configuration task 1 of 4
Initializing SharePoint Products upgrade...
Waiting to get a lock to upgrade the farm.
Successfully initialized SharePoint Products upgrade.
Performing configuration task 2 of 4
Initiating the upgrade sequence...
Successfully initiated the upgrade sequence.
Performing configuration task 3 of 4
Upgrading SharePoint Products...
Successfully upgraded SharePoint Products.
Performing configuration task 4 of 4
Finalizing the SharePoint Products configuration...
Successfully completed the SharePoint Products configuration.
Total number of configuration settings run: 4
Total number of successful configuration settings: 4
Total number of unsuccessful configuration settings: 0
Successfully stopped the configuration of SharePoint Products.
Configuration of the SharePoint Products has succeeded.
PS C:\Users\Administrator>
After some further research into this I found it was a simple case of needing to upgrade some of my databases (the search database being one of them).
To view the databases that needed upgrading I used the Powershell Commands:
Get-SPDatabase | ?{$_.NeedsUpgrade -eq $true} | Select Name
AND
Get-SPContentDatabase | ?{$_.NeedsUpgrade -eq $true} | Upgrade-SPContentDatabase
This allowed me to identify all databases that needed this (pretty much the same as using the Health Analyzer in Central Admin). I then ran the following PSCONFIG command through the powershell command windows to perform the upgrade:
psconfig -cmd upgrade -inplace -b2b -force -wait
Finally I ran the Products and Technologies wizard and all worked fine (including the search).
This is my experience:
For every time a fresh new install SharePoint 2010, the search service is good and working. When the 2008 server runs the auto update and found some update patches for SharePoint and get loaded automatically, then the SharePoint search will failed afterward with the message "The search request was unable to connect to the Search Service".
It looks like the auto loaded SharePoint patches will so something inference the search service but not do the work in a clean way.
I have used the "psconfig -cmd upgrade" command first but search is not work at first.
Then, I go to Central Administration -> System Settings -> Manage services on server, stop the "SharePoint Foundation Search" service, this will remove all search index. Start it up again. Afterward, the search works again.
I just created a Windows Azure account. When I try to deploy from VS2010 I get the following messages that just keep repeating on and on:
2:17:43 PM - Warning: All role instances have stopped
2:18:23 PM - Instance 0 of role MvcApplication1 is busy
2:18:59 PM - Instance 0 of role MvcApplication1 is stopped
2:18:59 PM - Warning: Instance 0 of role MvcApplication1 appears to be cycling and unable to start.
2:32:44 PM - Warning: All role instances have stopped
2:33:17 PM - Warning: All role instances have stopped
2:33:49 PM - Instance 0 of role MvcApplication1 is busy
Does anyone know how I can debug or find out what's wrong? I don't know what to do at this point.
I ran into this problem myself. Mine had to do with not having the assemblies packaged in my service when publishing. Use the following steps to resolve this:
1-Get all of the Deployable Dependencies into your project
Use the "Add Deployable Dependencies" feature from VS2010 SP1 and alluded to here in Scott Hanselman's blog post about BIN Deploying (see "Interesting Note" at the bottom of the post).
Essentially, right click on your project and you'll see it within the "Add" section. A dialog box will pop up with 3 choices (in my case 2 were accessible). After selecting them, a new folder will be added to your project called "_bin_deployableAssemblies" which will contain any assemblies your project needs to run in the cloud which the References you have are dependent upon.
If you don't have VS2010 SP1, then go ahead and follow the advice in Scott's blog post (which essentially does what the feature does, just you're doing it).
2-Check your References for Copy Local = true
Once you've done this, if you still have problems, start checking your reference assemblies for any References you have which are not expected in the cloud OS you are targeting, and make sure to set Copy Local = true.
3-Check your References for the Windows Azure assemblies
Because I created my Web Project first, I had to manually add the Windows Azure assemblies to my Web Project that was the target of the Web Role. (Microsoft.WindowsAzure.Diagnostics, Microsoft.WindowsAzure.ServiceRuntime, Microsoft.WindowsAzure.StorageClient)
4-If you're using MVC 3, use the workaround
Take David Makogon's advice and follow the steps on Steve Marx' blog post.
Debugging Azure apps which get stuck in this loop is hard.
The cause is normally that your role simply won't start because of a build problem.
In this particular case, I'd guess that maybe you haven't included one or more of the MVC assemblies inside your package - check that the MVC references are marked with Copy Local - e.g. see http://msdn.microsoft.com/en-us/library/dd410407.aspx (and other links depending on which MVC release you are using!)
If your MVC application is MVC3, the newest MVC libraries are not installed in the Windows Azure guest OS image yet. See Steve Marx' blog post for two easy ways to install the MVC3 libraries.