15

I resolved the issue. It appears based on the Microsoft Knowledge Base information that: Some document-conversion services in SharePoint Server are not secure when they run in a particular environment In order to allow the services to continue to run, the following registry key needs to be added: Name: AcknowledgedRunningOnAppServer Type: DWORD Value: 1 ...


12

I think you are trying to install Stand alone deployment and using the config wizard to create the configuration database using the local account. In this case you have to create the powershell command to create config DB 1st then run the config wizard. Run this command. New-SPConfigurationDatabase Hit Enter and it will ask couple of question i.e Database ...


11

This forum article helped me but I have to substitute for the missing "C:\Program Files\Microsoft Office Servers\15.0\Data\Office Server" - C:\Program Files\Windows SharePoint Services\15.0\Data\Analytics_{some guid} Hi All, Recently an issue was reported to me where some of my site admins were facing an issue in setting up a SharePoint 2013 stand ...


4

How many Servers in the Farm? Web site mentioned in the error ( ****.local80) still exist and working? If you have more than one server in farm, simply copy the web.config file from other server for same Virtual directory and re ran the Config wizard. Or Simply delete the Web Application( i am sure your web app not working as missing web.config) or re ...


4

Try the following: clear configuration cache http://blogs.msdn.com/b/jamesway/archive/2011/05/23/sharepoint-2010-clearing-the-configuration-cache.aspx Find current pv value using: stsadm -o getproperty -pn command-line-upgrade-running if -pv value is yes, change to No. If no change to Yes stsadm -o setproperty -pn command-line-upgrade-running -pv No re-run ...


4

You can run SharePoint Products Configuration Wizard in a second way: Via PSConfig.exe utility. Start a SharePoint PowerShell with elevated permissions and execute the following command to get your CumulativeUpdate-Installation finished: PSConfig.exe -cmd upgrade -inplace b2b -wait -cmd applicationcontent -install -cmd installfeatures -cmd secureresources -...


3

You will not find the file web.config in this folder C:\inetpub\wwwroot\wss\VirtualDirectories\…local80\web.config' The reason is your web.config file is deleted in your port 80. You have to have web.config file in this folder otherwise you will face this problem. I have the problem in port 40786. The solution is delete the website from your iis server ...


3

In best practice scenario, it is true. Dont use this wizard to configure all the services applications. You use the Config wizard very 1st time when you configure a farm and on first server to provision the state services(unchecked all other services applications). Once it completed then on all remaining server don't run it. Once Farm configured then you ...


3

First As per my experience i would highly recommend don't to use the farm configuration wizard for provisioning all services apps. I always run it 1st time for state service. Yes you can close it, it will not effect the anything. You can check the progress from Check Running job status section of Monitoring it really doesn't matter under which account you ...


3

This may occur in case, You have select Standalone Server Type Instead of Complete Server Type during the installation phase. So the Specifying configuration Database and database server dialog and Pass Phrase will be skipped. The limitation of Standalone Server Type You cannot extend the farm to add a new server, it's only standalone server. No domain ...


3

The answer for the first question really differs if you ask different SharePoint-Guys. I prefer psconfig.exe, where over my colleague prefers the Products Configuration Wizard (psconfigui.exe). Stefan Goßner also prefers psconfigui.exe and also explains why. A detailled description on every parameter can be found on Technet. It's for 2010, but still ...


3

This issue usually occurs in case of: The Database Server is not reachable from the SharePoint Application Server. The SQL Server port is closed and is not accessible from SharePoint Application Server. Please check How to Check SQL Server Instance Connectivity from the application server to database server for a specific user. SQL Server Service is ...


2

as you are installing as standalone, service running under Network Service account in workgroup environment is not supported. check these two blogs and fix the issue. http://kancharla-sharepoint.blogspot.com/2012/07/service-running-under-network-service.html http://kancharla-sharepoint.blogspot.com/2012/07/the-sddl-string-contains-invalid-sid-or.html


2

As per the error Failed to call GetTypes on assembly Microsoft.Office.InfoPath.Server, Version=14.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c. Could not load file or assembly 'Microsoft.Office.InfoPath, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c' or one of its dependencies. office 2013 is your problem. the assembly ...


2

It may be necessary to grant permissions to the container in the AD, please see Track SharePoint 2010 Installations by Service Connection Point (AD Marker)


2

I resolved the issue. I used the command: psconfig -cmd upgrade -inplace v2v -passphrase <passphrase> -wait Details available here


2

If you run the Configuration wizard one of the server in the farm, it will create the Config DB and Admin DB for Central admin( ugly name with GUID), you cant roll back it. Only thing is re run the config wizard and disconnect the server to farm( all the server which already joined to the farm), once you will do this, it will delete everything...Now check ...


2

Once you create the configuration database - you create the "farm". So in this case you want to create a new "farm". Re-run the wizard and disconnect from the farm. Then Delete your existing databases. Now you can start from 0.


2

I was still having the same error, even after adding the registry entries. It turns out that the Net.Tcp Port Sharing Service was disabled, once I enabled it and started, I re-ran the Configuration Wizard again and it went past stage 5.


2

I would do the following things Install the SharePoint + SP1 + Latest CU on all servers in the farm( App server and WFEs). Run the Config wizard on the central admin server and build a farm. Configure the state service. Now Run the Config wizard on the WFEs one by one and join them in the farm. once all server in the farm, now I will start configuring the ...


2

The Configuration Wizard (aka PSConfig) does the following steps: Initialize SharePoint products and technologies configuration Create Configuration database. Install help collections Secure SharePoint resources Register SharePoint Services (install) Register SharePoint features (install) Provision Central Administration Web application and ...


2

It's giving you an error regarding the database itself, not the credentials, make sure that the name of the database server is correct, if you have an instance, you need to provide the instance name. Make sure that the SharePoint server (the server you're working on right now) can ping and connect to SQL server.


2

Please have a look to your Windows Services console. Maybe the "IIS Admin Service" has startup type "Disabled". Set it to automatic and start the service. Just to make sure: Perform an IISRESET Start Products Configuration Wizard again


2

from the error, it is giving the hint that their is problem with SQL server connection from your SharePoint server. Couple of things to check. Make sure their is no firewall block between SharePoint and SQL Make sure port 1433 is not blocked by any software or firewall. All the required SQL services are up and running on SQL server Account you using to ...


1

this kind of issue likely due to connectivity with database; possible firewall issue - firewall blocking communication. But as you mentioned Firewall disabled and everything on same server then i am guessing it is related to TCP IP and Names pipes. Make sure it is enabled, if not enable them then restart the server. Check below blogs for more ...


1

​15.0.4641.1001 is for ​August 2014 CU while ​15.0.4667.1000 is for ​November 2014 CU. Check from Here So what i think, you installed the Aug 2014 CU on the Live servers while on staging Server You install the Correct the CU. to fix this, simply download the Nov 2014 CU for SharePoint Server and Install on all servers in farm than Run the Config wizard. ...


1

This is a common problem and there isn’t one solution for all. Try below steps if it works for you Logon to the SharePoint Web Front End(s). The Web Front End procedures described here must be performed on every server that participates in the farm. To open Services, click Start, click Control Panel, double-click Administrative Tools, and then double-click ...


1

go to IIS and check Central Administration web application pool.. check its user identity and change this user to another one u r sure it is enabled.. and then restart IIS


1

The following steps can be taken to move the SQL Server on which SharePoint databases are stored: Prepare the new SQL Server. Add the logins used for the SharePoint databases to the new instance. These can be copied from the old server with the same server roles. The DB permissions will be added when the DBs are migrated. Shut down all of the SharePoint ...


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