The specified user username is a local account. Local accounts should only be used in stand alone mode error in SharePoint 2013

This error comes in the configuration wizard where it ask for Database server name, database name, domain user name and password. The error comes as: "The specified user "Domain\UserName" is a local account. Local accounts should only be used in stand alone mode”.

To resolve this issue open SharePoint 2013 management PowerShell and run New-SPConfigurationDatabase command.

Once you run the command, it will ask you about the database name, database server name, farm credentials and Passphrase as shown in the fig below:

Then it will create the database, Then you can start the SharePoint Configuration wizard again. Then it will open the Modify server farm settings. Here it will autopopulate the Database server and Database name. 

Here select "Do not disconnect from this server farm" option. check the fig below:

Click on Next and the installation will complete.

Missing server file or server configuration issues. Web part Errors:

Missing server file or server configuration issues.
Web part Errors:
The following web part(s) are referenced by the content, but they are not installed on the web server

•Id = 72818beb-d38f-ce20-ad03-17a569674760, Type = Unknown, Reference = 29, Status = Missing             
•Id = b0361b90-8e73-425f-bcbc-2b2469198a00, Type = Unknown, Reference = 14, Status = Missing             
•Id = 19060b95-1c73-5a5b-875c-2e2c7d7cd355, Type = Unknown, Reference = 4, Status = Missing             

Steps to fix the errors
1.Logon to Database server and Run following SQL query on the content database for the Support site:

SELECT * FROM [WebParts] WITH(NOLOCK)where tp_WebPartTypeId =’ID’             
Example: SELECT * FROM [WebParts] WITH(NOLOCK)where tp_WebPartTypeId ='72818beb-d38f-ce20-ad03-17a569674760'             
            

From the results pane copy the tp_PageUrlID . These are the ids of the urls which has reference to the missing webparts .

2.Now run following query:

SELECT * FROM Alldocs WITH(NOLOCK)where id='80A251DD-1452-4199-A0BA-05120A7286EC'            

(ID is the value of the tp_PageURLID)

You will get DirName and LeafName corresponding to that PageURLID

3.Repeat step-2 for all the PageURL Ids to get complete URLs for a particular webpart ID. Step-1 and Step-2 needs to be performed multiple times to get a list of all the URLs where we need to fix the webpart error.
4.Now go to the URL, example :http://abc.amd.com/test/pages/test.aspx?contents=1
5.Check-out the page , delete the error web part and check-in/publish the page
6.To test if the issue is fixed run the below query again:

SELECT * FROM Alldocs WITH(NOLOCK)where id='80A251DD-1452-4199-A0BA-05120A7286EC'

again.

You should not get any results if all the URLs are fixed.

Ref Link: https://amritatalreja.wordpress.com/2011/08/02/preupgradecheck-errors-part-1/

How to Remove Missing WebPart during SharePoint Upgrade

If you are upgrading SharePoint 2007 to SharePoint 2010 and getting “MissingWebPart” error when using the Test-SPContentDatabase cmdlet in PowerShell, this tip will help you diagnose the issue.

Following is the original error:

Category: MissingWebPart

Error: True

UpgradeBlocking : False

Message: WebPart class [8c8bca43-cbc1-da50-d518-54614c79b3f5] is referenced [1] times in the database [WSS_Content], but is not installed on the current farm. Please install any feature/solution which contains this web part.

Remedy: One or more web parts are referenced in the database [WSS_Content], but are not installed on the current farm. Please install any feature or solution which contains these web parts.

As you can see, the error message gives you a WebPart GUID [8c8bca43-cbc1-da50-d518-54614c79b3f5] and the name of the content database [WSS_Content]. What we need to find out is on which page it is referenced in the database. For this we can run a SQL SELECT query on the “AllDocs” table in the content database exhibiting the problem. For example, you would run the following command to find details of the web part with the class ID “8c8bca43-cbc1-da50-d518-54614c79b3f5″:

select AllDocs.SiteId, WebId, Webs.Title as‘Web Title‘, ListId, DirName, LeafNamefrom AllDocs innerjoin WebParts on AllDocs.Id = WebParts.tp_PageUrlID innerjoinWebs on AllDocs.WebId = Webs.Id where WebParts.tp_WebPartTypeID =’8c8bca43-cbc1-da50-d518-54614c79b3f5′

It will list a very useful output, as shown in this example:

To remove the web part, type the page URL in the browserformat as “http://<SiteURL>/<DirName>/<Leafname>?contents=1″. In this example, type the following URL in the browser:

http://mossdev/default.aspx?contents=1

The screenshot below shows a web part maintenance page, you can delete the missing WebParts on the page.

Ref Link: http://www.boostsolutions.com/blog/how-to-remove-missing-webpart-during-sharepoint-upgrade/

Download a WSP Solution File from SharePoint 2010 Farm with PowerShell

Download a WSP Solution File from SharePoint 2010 Farm with PowerShell

$farm = Get-SPFarm
$file = $farm.Solutions.Item("extendeddiagnosticproviders.wsp").SolutionFile
$file.SaveAs("c:\temp\extendeddiagnosticproviders.wsp")