Tag Info

Hot answers tagged

7

Sounds like you have done a stand alone installation when you installed the bits. This changes everything. You should always do a Server Farm install, even if you are putting everything on a single machine. The only way to repair this is to uninstall SharePoint and install it using the Server Farm installation.


7

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 ...


5

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 ...


4

Here are the instructions for moving the databases for: Sharepoint 2007 SharePoint 2010 Also, it is a Best Practice to use SQL Aliases when referencing any instance of SQL server from a SharePoint farm. Doing so makes all future database moves a great deal easier.


4

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: ...


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 ...


3

you can use command "net start sptimerv4" in command window when the wizard is starting phase 9/10, then you can see it's work fine!


3

I had the same errors. Detaching databases didn't help, it was for some reason, the langue packs that were bugging me. After deinstalling the language packs, and running PSconfig again, my upgrade finished! correct upgrade order (In my opinion ;). some people think different about the subject): install SP1 - foundation install SP1 - Server psconfig ...


3

That error can be caused by a lot of things, e.g.: service accounts with invalid passwords missing feature dependencies missing content databases lack of permissions of your account the user account control (UAC) on the server (eventhough you should see a "access denied" error) a previous unfinished upgrade process any many more... I recommend rebooting ...


3

why dont you backup your current system and then try re-run Configuration wizard, this way you will experience it and might learn some bits as well :) however If you didn’t modify the default files of the SharePoint server, you can run the Configuration Wizard. The Default files including the content below: The default files locate in 12 ...


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 ...


2

I had this same issue when running the SharePoint 2010 PSConfigUI.exe and was not too keen to go adjusting the web.config files right away. I went into INETMGR.exe (IIS manager) and changed the .NET framework for all the SharePoint related app pools from 4.0 to 2.0. You may also want to restart IIS (IISRESET from an administration command prompt (right ...


2

I had this error message when I tried to run a Silverlight application as a sub directory of my SharePoint application in IIS with the Silverlight application running under .NET 4.0. Try checking that all the sub directories of your SharePoint application are still running on .NET 2.0.


2

If you haven't already done so, you may also need to add the dbcreator and securityadmin server roles to your user in SQL Server. Have you looked at the SharePoint logs (in the "12 hive") and the Windows Event Viewer on both servers already? They are helpful in diagnosing configuration issues.


2

I had the same problem. It turns out I just needed to remember to run the SP2010 Products Configuration Wizard by right clicking and using "Run As Administrator". (as my system is deployed on a Windows 2008 R2 server). Even though I was logged in with privileged accounts (including the admin account used to install SharePoint in the first place), it would ...


2

Even this could seems useless in your situation, please do a SQL Backup of your corrupted DBs, I can't promise you'll solved your problems usign this. I did it once for a Content Database (in powershell): $db = Get-SPDatabase "Your DB"; $db.Repair($true); $db.Update(); In stsadm there is also the line stsadm -o Databaserepair


2

Sounds like you have an orphaned database, try running this SQL statement on your content database. select name, CAST(properties as XML) from objects where Properties like '%SPIisSettings%' If you find an entry like <sFld type="Guid">2FD90694-8C16-4582-AEFB-75F0915BA745</sFld> <fld type="null"/> then you can remove it by doing $wa = ...


2

It might get you connected to the Config database on the new server, but all the other databases would still be wrong. The technet article Move all databases (SharePoint Server 2010) suggests that you create an SQL alias pointing to the new database server after making sure you got permissions set up correctly


2

When you say "can't access this page" do you mean they get prompted for credentials and can't get in when providing them? Is it a .NET error message, a SharePoint error message or a browser error message? Is that error copied and pasted exactly? What rights are the users who can't get in supposed to have? anonymous only? contribute? Can they get into ...


2

Start Central Administration as Administrator (right-click -> Run as Administrator) Not sure why this will help, but it has something to do with how Central Admin trims some links depending on if the IE process is running as local admin or not


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

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

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

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

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 ...


1

I had the same issue, the solution to solve it is very simple.Just make sure you start Microsoft SharePoint Foundation Web Application on the server which will run the configuration wizard before starting. Best regards


1

It could be basically some patch update issue. Are you running the configuration wizard for the first time? There is a technet blog for some better understanding, where it says KB2560890 could be the issue. No guarantees though. Do you have SharePoint SP1 installed? Have you updated to the latest cumulative update for SharePoint. Better apply all the ...


1

In my experience it is easiest to rebuild the farm than to try and fix/troubleshoot/validate the environment. The wizard was created for testing/demo purposes and not meant for production deployments.



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