Tag Info

Hot answers tagged

9

Check out this article on nothingbutsharepoint.com on how to find the versions in SP2010. And Todd Klindt has a nice break down too. Taken from Todd's article, To see which build your farm is, go to Central Administration > System Settings > Manage servers in your farm (/_admin/FarmServers.aspx) Or using Windows PowerShell: ...


7

The guidance and "best practice" up until the August 2011 CU is to install SPF Service Packs and CU's on Server edition. From August 2011 the packaging process has changed and you only need one package to install. So in order to install SP1 + June CU do this: (the Microsoft recommendation is to install June CU directly after SP1, there are a couple of nasty ...


5

Per Microsoft: Although SP2 for the 2007 Office Desktop products can be uninstalled, you cannot uninstall 2007 Office Servers Service Pack 2 for Office server products. The main reason for this is that the installation of 2007 Office Server Service Pack 2 makes changes to back-end databases, and those database changes are currently unable to be ...


4

Foundation SP1 - http://support.microsoft.com/kb/2460058 Joel Oleson has spelled it out very well, http://www.sharepointjoel.com/Lists/Posts/Post.aspx?ID=453


4

Here it is : Service Pack 1 for SharePoint Foundation 2010 (KB2460058) Service Pack 1 for Microsoft SharePoint Server 2010 (KB2460045)


4

Yes, Service Pack 2 contains all Cummulative Updates and Hot fixes before it.. including SP1 Install SharePoint 2010 Service Pack 2 the right way SharePoint Server 2010 Service Pack 2 has been released (Updated July 31st, 2013)


3

Looks like this a common issue. I had same issue after researching why Search wasn't working and only returning an error message. You could fix the issue by following instructions here: http://blogs.msdn.com/b/opal/archive/2010/04/18/track-sharepoint-2010-installations-by-service-connection-point-ad-marker.aspx But, you don't want to leave as is. You can ...


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

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

Here are the links: Windows SharePoint Services 3.0 x86 Windows SharePoint Services 3.0 x64 SP1 for WSS 3.0 (both x64 and x86 versions are included)


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

The workflow issue is a security feature, although in your current situation, you might not agree. It's easier to just fix the recursion issues for the workflows because going forward it has to be done anyway (SP2 required for upgrade where it will be required to be fixed). Add trigger column(s) to your list and create a second workflow that fires on ...


2

Thanks for all the answers so far. I have managed to resolve the issue myself. I was attempting to install WSS3 onto Server 2008. It seems that during the install process SP2 is downloaded and installed. I can only assume SP2 is required for WSS3 to work on 2008. I'm now using a machine running Server 2003 and have managed to install WSS3 SP1. I should ...


2

The stored procedure you are referring to is (proc_DefragmentIndices) and is discussed in this KB article. The stored procedure works within the limitations of the online index build feature, one of which being that you cannot perform an online index on an index that contains a LOB (large object) column. The bad news? SharePoint stores a lot of BLOB data ...


2

From my experience: Hot Fixes are to be applied IF and ONLY if the issue affects you. Hotfixes can go horribly wrong if applied in production without testing out in a staging environment first CUs are usually pre-requisites for SP installs, so you can either do it in one shot before the SP Install or pace them out and do CU and then SP We usually wait ...


2

Are you able to take a backup of the content database that holds the site collection? If you do so you can then restore the SQL Content DB to your dev sql instance and attach it to a development web application, the attach will perform an 'upgrade' on the content db and should take care of your issue.


2

If you want to have your SharePoint Farm up to Dec 2011 CU, following is the path: 1) Install SharePoint Server SP1 - Following the installation Guide 2) http://support.microsoft.com/kb/2597014 - Dec 2011 CU Note that while installing Dec CU for Server version, you do NOT install Foundation Version of CU. After Aug 31 2011, all Server CU will include ...


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

I finally sorted this issue. I ended up ringing MS on it and their only official supported fix was to delete and recreate the User Profile Service Application & it's database. However this was on our production server and I couldn't do that. Luckily based on their information I was able to come up with an unofficial fix. The error happens because ...


2

It'll state that on the installation instructions You'll find installed language packs in "Programs and Features" in Control Panel See 1. Yes. Also see 1. Office Web Apps is a separate Microsoft Product so updates for that are delivered through the OWA portal on TechNet. Here's instructions on installing updates: ...


2

Just install the Server Service Pack. When it comes to SharePoint patches, you really can't "go back" (easily).


2

their is no easy way as far i know unless uninstall the SharePoint. I would simply install the SharePoint server SP1, you will all set. If you know Server Service Pack include both Foundation & server SP1. So if you installed the foundation separately then when you run the Server SP1 it will automatically detect it and install only server related stuff ...


1

After a lot of debugging, I was able to figure out what was causing our issue. For some reason, our app pool was recycling frequently throughout the day. Users who were actively working on the site were losing their cookies if they had checked Remember Me. Some code we had in our custom chunked cookie handler was checking for the HttpContext.User ...


1

I don't think SharePoint (or most other 'server products' for that matter) are deployed by Windows Update. You can download updates here and manually install http://technet.microsoft.com/en-us/office/sharepointserver/bb735839


1

Your AD is configured to track SharePoint installations. All accounts that are used to run PSCONFIG need to have specific permission on a specific AD container in order to be able to add a marker of itself to the container. Probably the tracking was enabled after initial SharePoint installation, or are you perhaps using different account from the original ...


1

The Service Pack 1 (SP1) for SharePoint Foundation 2010 and SharePoint Server 2010 white paper describes the features that are included in Microsoft SharePoint Foundation 2010 Service Pack 1 (SP1). In addition, this paper provides some guidelines you can follow so that your solutions work with current and future versions of SharePoint Foundation 2010. ...


1

Yes it is recommended to apply the foundation packages before the SP 2010 SP1. Please refer to the following link: http://blogs.technet.com/b/office_sustained_engineering/archive/2011/06/29/sharepoint-2010-sp1-and-the-june-cumulative-update-for-sharepoint-2010.aspx


1

Backup all your Config and Content databases, and your servers, before doing the update. If your servers are VMs, snapshot them before the update. You'll need to have a maintenance window to do the update. Depending on the size of your content, you may need a weekend. You then have a restore point you can go back to. Microsoft's Service Pack ...


1

A couple of things to check: Can you access the lists from the browser? Try and open Fiddler on your client machine where you run infopath to see where the requests to the SharePoint lists go check publishurl in manifest (cab) to see that you havent by accident re-published some older version from a test server (happend to me more than i care to admit;-)


1

I had the same issue of actually restoring the Site Collection on a different server that had a patch different than my server. And the DB restore also did not work because my SQL version were different. So, I basically downloaded the SQL Express same version as my other machine and then restored the DB. Then I actually upgraded my test server to the same ...



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