Misunderstanding when upgrade Sharepoint Server 2010 SP1 with Language Service Packs KB2460059 vs KB2460056

As you know we have installation setup for language pack 2010 Service Pack 1

1) Service Pack 1 for Microsoft SharePoint Foundation (MSF) 2010 Language Pack (KB2460059)
http://www.microsoft.com/download/en/details.aspx?id=26629

2) Service Pack 1 for Microsoft SharePoint  Server (SPS) Language Pack 2010 (KB2460056)
http://www.microsoft.com/download/en/details.aspx?id=26621

Some of the articles in internet tell us install MSF Language service pack1 first KB2460059 and than install KB2460056 after.
THAT IS NOT CORRECT !!!
If you fallow this order  ,you can easily detect that you can not able install KB2460056  after KB2460059 .

First of all the KB2460056 contains all packs for KB2460059.

That’s why if you have Sharepoint Server 2010 you should install only  Service Pack 1 for Service Pack 1 for Server Language Pack 2010 (KB2460056) or
if you have Sharepoint Foundation 2010 you should install only  Service Pack 1 for Microsoft SharePoint Foundation 2010 Language Pack (KB2460059)

For prove this i have download Turkish SPS and MSF Language Service Pack1 and extract the packages and compre them.

Service Pack 1 for Microsoft SharePoint Foundation (MSF) 2010 Language Pack (KB2460059)
spflanguagepack2010sp1-kb2460059-x64-fullfile-tr-tr.exe

Service Pack 1 for Microsoft SharePoint  Server (SPS) Language Pack 2010 (KB2460056)
serverlanguagepack2010sp1-kb2460056-x64-fullfile-tr-tr.exe

 

 

 

 

Advertisements

Move Sharepoint 2010 server to another domain

If once you need to move your sharepoint server to another farm you have to know this is not an easy process. In this article i am telling you a way of doing migration via using domain trusts.

  1. Upgrade Current farm lastest SP (Service Pack 1) and lasted CU
    Sharepoint SP1 and June CU information
    http://blogs.msdn.com/b/joerg_sinemus/archive/2011/06/29/sharepoint-2010-sp1-and-post-sp1-june-2011-cu.aspx
    http://blog.bugrapostaci.com/2011/06/29/sharepoint-2010-service-pack-1-sp1-and-june-2011-cu-released/
  2. Estabilish two way domain trust between Domain A (old) and Domain B
    http://technet.microsoft.com/en-us/library/cc773178(WS.10).aspx
    http://technet.microsoft.com/en-us/library/cc816837(WS.10).aspx
    http://technet.microsoft.com/en-us/library/cc816590(WS.10).aspx
  3. Setup and Install new Sharepoint Server on Domain B and Upgrade this server lastest SP and Lastest CU
    Prepare to deploy software updates (SharePoint Server 2010)
    http://technet.microsoft.com/hi-in/library/ff806331(en-us).aspx
  4. Join new server to farm using configuration wizard.
  5. Migrate all roles and service applications to new server and stop the domain A server services.
    Server and Site Architecture
    http://msdn.microsoft.com/en-us/library/ms473633.aspx
    Service Applications and Topologies in SharePoint Server 2010
    http://technet.microsoft.com/en-us/sharepoint/ff686757
  6. Update all service accounts and farm admin account with new Domain users.
    Initial deployment administrative and service accounts
    http://technet.microsoft.com/en-us/library/ee662513.aspx
    http://blogs.msdn.com/b/russmax/archive/2010/01/08/changing-sharepoint-2010-service-accounts.aspx
  7. Migrate all other needed users and groups using stsadm.
    http://technet.microsoft.com/en-us/sharepoint/ee517214
    Verify that you meet the following minimum requirements: See Add-SPShellAdmin.
    On the Start menu, click All Programs.
    Click Microsoft SharePoint 2010 Products.
    Click SharePoint 2010 Management Shell.
    From the Windows PowerShell command prompt, type the following:
    $w = Get-SPWebApplication “http://<server>/&#8221;
    $w.MigrateUsers($True)
  8. Check if needed Equalize all custom solutions, and web.config files and make a complete test of your custom solutions
    http://technet.microsoft.com/en-us/library/cc262995.aspx
  9. Stop all services on Domain A sharepoint servers and test your all application for any problem .(broken links , content redirections, posible errors)
  10. If Everything is ok at step 9 .Disconnect old servers (domian A servers) from farm
  11. Stop All Sharepoint servers on Domian B
  12. Stop SQL Server and change domain of SQL Server .
  13. Start SQL server services.
  14. Start Sharepoint Servers.
  15. Remove Domain Trusts.

I hope this helps 🙂

Think twice for installing September Security Bulletin (MS11-074) KB2560890 on Sharepoint 2010

We have getting more problem after installing September Security Bulletin (MS11-074) if you not have sp1 .So i decided to write an article for that.

we have two known issue:

Issue #1- Users unable to browse Publishing sites
Actually i didnt face this problem yet but for this in Tehnoon Raza blog says:
This issue affects the ability of users to browse to and use SharePoint Publishing sites. When browsing to the site, users may experience the following error:
“An Unexpected error has occurred”
Following error is reported in the ULS logs or on the SharePoint page if the “CallStack” attribute of set to “true” in the web.config file:

Method not found: ‘Void Microsoft.Office.Server.WebControls.AudienceLoader.GetAudiencesFetchedDuringPageRequest(System.Collections.Generic.Dictionary`2<System.Guid,Boolean> ByRef, System.Collections.Generic.Dictionary`2<System.String,Boolean> ByRef, System.Collections.Generic.Dictionary`2<System.String,Boolean> ByRef)’.

Issue #2- Unable to Manage User Profile Service Application
the main problem is when you try to open User Profile Service Application , you are getting a “File Not Found” error :

System.IO.FileNotFoundException: Could not load file or assembly ‘Microsoft.ResourceManagement, Version=4.0.2450.34, Culture=neutral, PublicKeyToken=65bf2559ag374f77’ or one of its dependencies. The system cannot find the file specified.    at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager.InitializeIlmClient(String ILMMachineName, Int32 FIMWebClientTimeOut)     at Microsoft.Office.Server.UserProfiles.UserProfileConfigManager..ctor(UserProfileApplicationProxy userProfileApplicationProxy, Guid partitionID)     at Microsoft.SharePoint.Portal.UserProfiles.AdminUI.ProfileAdminPage.IsProfileSynchronizationRunning() 

For resolving this problem you can apply the KB article action plan (but this is not solve the problem) :
To do this, follow these steps:

  1. Open Central Administration.
  2. In the System Settings section, click Manage Services
  3. Find User Profile Synchronization Service in the list of services. If its status is Started, click Stop. Click Start, and then provide the credentials to start the User Profile Synchronization service.

After do that may be you need a full reset for Sharepoint Machine. i could say this not resolve your problem even if the problem “file not found” has gone. If you try full syncronization you will notice that FIM service gonna hang on MOSS_EXPORT step with an error of “ma-extention-error” and your users not synced at all.
And you can see the error on your Event Viewer Application Log:

System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. —> System.MissingMethodException: Method not found: ‘Void Microsoft.Office.Server.UserProfiles.ProfileManagerBase.UpdateProfileWithBulkProperties(Int64, System.String, System.String, System.Collections.Hashtable)’. at Microsoft.Office.Server.UserProfiles.ProfileImportExportService.UpdateWithProfileChangeData(Int64 importExportId, ProfileChangeData[] profileChangeData) — End of inner exception stack trace — at System.RuntimeMethodHandle._InvokeMethodFast(Object target, Object[] arguments, SignatureStruct& sig, MethodAttributes methodAttributes, RuntimeTypeHandle typeOwner) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean skipVisibilityChecks) at System.Reflection.RuntimeMethodInfo.Invoke(Object obj, BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture) at Microsoft.Office.Server.WebServiceDirectProxy.WebMethodInfo.Invoke(Object webServiceInstance, Object[] args) at Microsoft.Office.Server.WebServiceDirectProxy.Invoke(String methodName, Object[] args) at Microsoft.Office.Server.UserProfiles.ManagementAgent.ProfileImportExportDirect.UpdateWithProfileChangeData(Int64 importExportId, ProfileChangeData[] profileChangeData) at Microsoft.Office.Server.UserProfiles.ManagementAgent.ProfileImportExportExtension.Microsoft.MetadirectoryServices.IMAExtensibleCallExport.ExportEntry(ModificationType modificationType, String[] changedAttributes, CSEntry csentry) Forefront Identity Manager 4.0.2450.34

Root Cause:
The problem has been caused due to inconsistent assembly versions on the SharePoint servers after the installation of the package KB2560890. Multiple packages were released as part of the security bulletin that affect SharePoint 2010 and all applicable packages must be installed on SharePoint servers to ensure that version inconsistencies are not created in the environment.  However, it has been observed that only KB2560890 was pushed to servers via WSUS, resulting in the SharePoint assemblies being in an inconsistent state and creating dependency issues

Resolution:
Only known resolution yet:
Install SP1 and Lasted CU.
iSP1 + June Cu there are lots of fixes over all included in it, and also from June Cu we have new bits for the FIM agent and some performance improvements.
Anyway, after applying the udpates and patches, you should recreate the UPA as well to gain full functionality of all added fixes.
But don’t forget that the SP1 and Lasted CU has also some known issues . For preventing problems please check the microsoft release documents and blogs in Technet.

Prepare to deploy software updates (SharePoint Server 2010)
http://technet.microsoft.com/hi-in/library/ff806331(en-us).aspx

Sharepoint SP1 and June CU information
http://blogs.msdn.com/b/joerg_sinemus/archive/2011/06/29/sharepoint-2010-sp1-and-post-sp1-june-2011-cu.aspx
http://blog.bugrapostaci.com/2011/06/29/sharepoint-2010-service-pack-1-sp1-and-june-2011-cu-released/

Resources:
http://blogs.msdn.com/b/tehnoonr/archive/2011/09/19/september-security-bulletin-ms11-074-and-sharepoint-2010-issues.aspx
http://support.microsoft.com/kb/2560890
http://social.msdn.microsoft.com/Forums/en-AU/sharepoint2010general/thread/8b4d64ed-5f7b-473b-8121-d7f5b0bb5902

Have a nice patching.

Sharepoint 2010 Misconception with RBS

After Sharepoint 2010 sp1 is released , some new features and improvements has been spreading in several blogs.And one of the most interested the new content database limits. In SP1 , by defining specific requirements for large data storage in SharePoint, Microsoft is able to increase the supported limits for data storage in SharePoint.
Sotware boundaries and limits and the primary changes are:

  1. For a SharePoint content database up to 200 GB there are no special requirements and this limit is included for consistency.
  2. For a SharePoint content database up to 4 TB you need to additionally plan for the following two requirements:
    • Requires disk sub-system performance of 0.25 IOPS per GB, 2 IOPS per GB is recommended for optimal performance.
    • Requires the customer to have plans for high availability, disaster recovery, future capacity, and performance testing.
    • And you need to review additional considerations in the TechNet Boundaries and Limits article.
  3. For a SharePoint content database over 4TB specifically for a Document Archive scenario you are required to additionally plan for the following:
    • SharePoint sites must be based on Document Center or Records Center site templates and must be an archive scenario where less than 5% of content is actively read from each month and less than 1% of content is actively written to.
    • Do not use alerts, workflows, link fix-ups, or item level security on any SharePoint objects in the content database. Note: document archive content databases can be the recipient of documents as a result of Content Routing workflow.
  4. Other specific limits changes being made at the same time:
    • A new limit of 60million items in any one SharePoint content database
    • The specific 5 TB limit per SQL Server instance has been removed.  Instead you should work with a SQL Server professional to plan for database storage.

 Also these new extended limitation is not our artile issue if you need more info see:
http://technet.microsoft.com/en-us/library/cc262787.aspx

And also RBS has some improvements:
The Microsoft SQL Server FILESTREAM RBS provider is now supported allowing for iSCSI connections to lower cost NAS storage. The SQL Server RBS provider is one option for RBS use with SharePoint and there are a number of ISV’s who also have RBS providers.

What about RBS misconception: Misconception is that RBS can provide extra database size limit ? Answer is “No”:

First of all Microsoft Says :
“We are clarifying that Remote Blob Storage (RBS) does not offer a way to increase the SharePoint content database size limits. The content database supported size limits apply to the sum of data stored in SQL Server plus data stored outside of SQL Server using an RBS provider”

Even if you use RBS or not , Sharepoint boundries is strict and you should not able to change it. And this is not only just Content DB size limit. it is also valid for all Sharepoint Limitation,  including Maximum document size limit of 2 GB for one file.

See you in next article…

 

Sharepoint 2010 Service Pack 1 (SP1) and June 2011 CU released

Here is the download links.

Service Pack 1 for Microsoft Sharepoint Server 2010 (KB2460045)
http://www.microsoft.com/download/en/confirmation.aspx?id=26623

Service Pack 1 for SharePoint Foundation 2010 (KB2460058)
http://www.microsoft.com/download/en/details.aspx?displaylang=en&id=26640

SharePoint Foundation 2010 Language Pack SP1
http://support.microsoft.com/kb/2460059

Sharepoint Designer 2010 SP1
http://support.microsoft.com/kb/2460057

List of all SharePoint 2010 and Office Server 2010 SP1 packages
http://support.microsoft.com/kb/2510766

For SharePoint customers planning to deploy Service Pack 1, it is also recommended to install the June 2011 Cumulative Update for SharePoint.

SharePoint Server 2010 cumulative update package (SharePoint server-package): June 28, 2011
http://support.microsoft.com/kb/2536599

SharePoint Foundation 2010 cumulative update package (SharePoint Foundation server-package): June 28, 2011
http://support.microsoft.com/default.aspx?scid=kb;EN-US;2536601

Service Pack 1 does not contain June 2011 CU fixes means if you would like to install last CU you should better first install SP1 than patched with June 2011 CU  . And also sp1 is not mandatory thats mean you can able to install only June 2011 CU but Microsoft recommend to install sp1 . Sp1 contains new feature packs if you dont install it you could not able to use new features.

!!! UPDATE 12.07.2011
June 2011 CU for SharePoint 2010 has been re-released
Because of some side effects of June 2011 has been re-released.

Issue 1
If you install the earlier build of this hotfix package on a SharePoint server that has .NET 4.0 installed, you cannot synchronize user profiles from AD and LDAP into the SharePoint User Profile Service application database. The user profile synchronization export process fails. Additionally, the System.PlatformNotSupportedException exception shows in Event Viewer.

Issue 2
After you install the earlier build of this hotfix package, the following services may fail at either runtime or the provision process if you run these services by using a user account other than the farm administrator account:

  • Session State Service
  • Secure Store Service
  • Business Data Connectivity (BDC) Service

The rereleased CU has build 14.0.6106.5002. The KB articles have been updated and the binaries on our hotfix server have been replaced with the updated version.

Source article:
http://blogs.technet.com/b/stefan_gossner/archive/2011/07/12/june-2011-cu-for-sharepoint-2010-has-been-re-released.aspx

!!!

Important for all Server Applications listed above:
After applying the preceding updates, run the SharePoint Products and Technologies Configuration Wizard or “psconfig –cmd upgrade –inplace b2b -wait” in command line. This needs to be done on all servers in the farm with SharePoint installed. You can run psconfig in parallel on all SharePoint machines.

The recommended order of installation is as follows:

Update Foundation first:
SharePoint Foundation 2010 Service Pack 1
Service Pack 1 for SharePoint Foundation 2010 Language Pack
June 2011 CU for SharePoint Foundation 2010

Then SharePoint Server:
SharePoint Server 2010 Service Pack 1
Service Pack 1 for Server Language Pack 2010
June 2011 CU for SharePoint Server 2010

Frequently Asked
Questions

Q: Can I install Service Pack 1 on RTM builds of
SharePoint 2010 Products?

A: Yes,
Service Pack 1 can be installed directly on RTM builds; however, we suggest you
install Service Pack 1 then apply the June 2011 Cumulative Update.

Q: Do I need to run psconfig after the install
of every package?

A: No, apply all of the available packages then
run psconfig – the database will only be updated once, to the newest version.

Q: Do I need to run psconfig on every machine in
the farm?

A: Yes. Although database is already updated,
the binaries on each server need to be set and permissioned using psconfig.

Q: Will there be a slipstream build including
Service Pack 1 available for download?

A: At this time a slipstream build including
Service Pack 1 is not available.

Have a nice patching…