7

You can remove this feature from the farm, by doing the following: Download SharePoint Feature Administration and Clean Up Tool. Open this tool and reload the web apps > Click on Find Faulty Feature in the farm. Then click yes to remove Faulty Features in your farm Another solution, Try to run Test-SPContentDatabase as the following: Test-...


3

From your command, looks like their is some error.You have to provide the complete path of PSConfig and also use -ArgumentList instead of ps-ArgumentList. Start-Process "path of file\PSConfig.exe" -ArgumentList "-cmd upgrade -inplace v2v -passphrase FarmPassPhrase -force -wait" -Wait If their is not such requirement then you can directly run the psconfig ...


3

It's unsupported because that isn't the only place the connection string resides. There are a few SharePoint Objects that would also have to be updated (including making direct changes to the Configuration database). This is unsupported in and of itself. You'll need to use cliconfg to create a SQL Alias or rebuild the farm.


2

if you are behind the from the Microsoft CU then server will complain about the upgrade required. I.e you are Jan 2015 CU but MSFT release the Nov CU, in this case you are behind couple of cu. It will not be a problem but i would install the latest CU and run config wizard if i am way behind.


2

This is probably not the recommended, nor the supported way to do it. The best would probably be to reinstall Windows Server 2008. However, in my case, it solved the problem and could be used as a last resort if you can’t reinstall the server. I opened the regedit and searched for ”14.0.0.0” and found these interesting posts: I updated the path from 14 to ...


2

There is no supported way to change the Language of central admin.by default, the language of central admin is the language of sharepoint version installed. If you want to change it then re install the sharepoint with correct language version. To change language in web table is not supported and will end support contract with MSFT. But if it is ur Dev ...


2

You can simply use the SharePoint Management Shell instead which has pathing for psconfig, but instead, use PowerShell. Initialize-SPResourceSecurity is the replacement for that specific command.


2

This issue was resolved by removing the below patches: This issue was resolved by removing the installed following patches: "KB4015550 KB4015547 KB4012213 KB3205400 - 5401 KB3297873 KB3192392"


2

If you get an error message in PSConfig because of a service is offline, you need to start PSConfig again and make sure you have a successful run. Also verify that you have the target build version in Manage servers in this farm (http://CA-url:port/_admin/FarmServers.aspx) and Check product and patch installation status (http://CA-url:port/_admin/PatchStatus....


1

So, I was able to finally get into central admin by using the central admin application pool identity. Being that the Authentication Provider for central admin was still 'Windows' I had to add the install account and myself back into the permission policy as domain\user since all users had the i:0#.w| prefix. The install account was then able to run the ...


1

Issue :- This error happens because a list or library was created in your SharePoint site based on a given list template that is no longer available. A common scenario for this type of error is a list that was created with a template defined by a feature that has since been uninstalled. This makes the list invalid because the template no longer exists. ...


1

Run SharePoint 2013 products configuration wizard in all SharePoint servers. Or you can run the following PowerShell on all SharePoint servers: PSConfig.exe -cmd upgrade -inplace b2b -wait -force -cmd applicationcontent -install -cmd installfeatures -cmd secureresources You don't need to backup the farm before running this command.


1

Run as Administrator "SharePoint 2013 Management Shell" and try: PSConfig.exe -cmd upgrade -inplace b2b -force -cmd applicationcontent -install -cmd installfeatures


1

You would not change this. There is no reason to.


1

Yes, it is safe to re-run these at any time. You must run these on each SharePoint server. You can always just re-execute the full psconfig command, instead. Or run the Config Wizard.


1

Upon closer investigation of this exception stated in the ULS log ( posted above ). MsiOpenProduct {90150000-1015-0409-1000-0000000FF1CE} failed with 1612 A failure of 1612 means that previously installed patch files have become corrupted or have been removed from the %windir%\installer\ directory. …also indicated by this ULS exception: Exception:...


1

I encountered this behavior every single time we applied a CU to our SharePoint farms (2007 and 2010). When running the wizard a second time it ran through all steps in 99.99% of all cases. Hope that helps.


1

@Christian, to enable the Feature also worked in our Environment, I don´t know whats the case, but it worked. Also Folks, be Aware that I could be that you have to manually start w3svc Service during the wizard is working though the tokenservice might not be available for the upgrade process.! Greetings Andre


1

We had the same problem here. CustomTiles is a standard SharePoint Feature. It's neither missing nor faulty. It seems that the feature upgrade code has a bug though. The upgrade doesn't work if the hidden CustomTiles lists have never been created. These lists get created when you enable the feature. So what you have to do is enabling the CustomTiles feature ...


1

I would recommend you to reinstall SharePoint in english language. Just changing the CA's language won't change the language of ULS-Logs and other stuff. This makes troubleshooting much more challenging, as there is no german-speaking SharePoint community.


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