Azure & Office 365

Posts Tagged ‘install’

Hi Friends,

Today we will discuss on how to configure Multi Server Office Web Apps farm with a SharePoint farm. Also the specialty of this OWA configuration is that it can work inside and outside of firewall. Normally OWA farms are setup HTTP inside the firewall network(Internal network) and HTTPS outside the network(External world) but using this configuration we will configure HTTPS for both inside and outside network. This will not only decrease additional overhead and configuration but also is recommended by Microsoft to use HTTPS for production environment.

We need to meet below pre-requisites before we proceed further:
1. SharePoint farm configured and ready to use
2. Two or more Office Web Apps servers with setup files
3. One certificate for Office Web App
4. If you are using Windows server 2012 R2 then you would need to install latest update for Office Web Apps
5. FQDN name for your Office web app farm e.g.(owa.domain.com) and its DNS entry with Round Robin(You can also configure Windows NLB or a Load Balancer entry for same)

Installation of Office Web App is very simple, You just need to download the installable and execute it on all OWA servers.

Install Office Web apps on all Office Web Apps servers. If you are using Office Web App on Windows Server 2012 R2, you should install latest update for Office Web Apps. You would need an Office Web app certificate imported to IIS
Now Let’s configure Office Web App, Open Windows PowerShell and execute below command

Once the Office Web App farm is configured, open IIS and make sure SSL binding for site HTTP80 has proper certificate attached.

From IIS binding select the certificate and export the .cer file.
You need to import it to central admin manage trust.

To Attach this Office web app farm to SharePoint farm, you need to create a WOPI connection. Open SharePoint PowerShell on SharePoint server and execute below command:

New-SPWOPIBinding -ServerName “officewebapp.domain.com”

Set Wopi zone

Now if you want to add other Office Web App Server to OWA farm, you need to execute below command on existing OWA server
new-officewebappsmachine -machinetojoin “owa2server.domain.com”

Hope this will help you

Hi Friends,

Recently I faced issue while updating SharePoint 2010 sp1 on servers. Installation of SharePoint 2013 SP1 didn’t caused any issue but when I try to run PSconfig wizard to update SharePoint databases, site features, etc, it stopped with below errors.

Environment : SharePoint 2010 standalone environment

ULS Logs:
UpdatedConcurrencyException: The object SPAdministrationWebApplication was updated by another user. Determine if these changes will conflict, resolve any differences, and reapply the second change. This error may also indicate a programming error caused by obtaining two copies of the same object in a single thread. Previous update information: User: Machinname\username Process:PSCONFIG (2624) Machine:machinename Time:April 22, 2015 10:54:48.0000 Current update information: User: machinename\username Process:PSCONFIG (2624) Machine:machinename Time:April 22, 2015 10:54:48.2154

Exception: System.NullReferenceException: Object reference not set to an instance of an object.
at Microsoft.SharePoint.Upgrade.SPContentDatabaseIntegrity.CheckAppOrphans()
at Microsoft.SharePoint.Upgrade.SPContentDatabaseIntegrity.Check(SPContentDatabaseIntegrityCheckOptions options)
at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.ContentDatabaseDataIntegrityCheck()
at Microsoft.SharePoint.Upgrade.SPContentDatabaseSequence.PreUpgrade()

Upgrade.log:
This upgrade session has been stopped. Possible causes include the process being terminated abruptly or the OS has rebooted. Please restart the upgrade again.

PSCDiagnostics logs:
An exception of type Microsoft.SharePoint.Upgrade.SPUpgradeException was thrown. Additional exception information: Upgrade completed with errors. Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20150422-104856-16.log. The number of errors and warnings is listed at the end of the upgrade log file.

Microsoft.SharePoint.Upgrade.SPUpgradeException: Upgrade completed with errors. Review the upgrade log file located in C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\14\LOGS\Upgrade-20150422-104856-16.log. The number of errors and warnings is listed at the end of the upgrade log file.
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.CheckPoint()
at Microsoft.SharePoint.Upgrade.SPUpgradeSession.LogEnd()
at Microsoft.SharePoint.PostSetupConfiguration.UpgradeTask.Run()
at Microsoft.SharePoint.PostSetupConfiguration.TaskThread.ExecuteTask()

Troubleshooting steps tried:
To resolve the issue I tried to run below command, but it did not help:
PSCONFIG -cmd upgrade -inplace b2b -wait -force

Confirmed that there was no password change in SharePoint farm, No issues related to content databases. Checked permission for the farm account on SQL server and SharePoint server.

User Account Control (UAC) was enabled on server to disabled it so disabled it. Tried to reboot SharePoint machine and disabled Firewall.

Resolution:
After some research I found that configuration database was locked which caused this issue. To resolve the issue I executed below command in powershell:

stsadm -o setproperty -pn “command-line-upgrade-running” -pv No

Then tired to refresh sharePoint by running below command:
IISreset
net stop sptimerv4
net start sptimerv4

Now when I try to run PSconfig wizard from PowerShell, it completed without any issue:
PSCONFIG -cmd upgrade -inplace b2b -wait -force

Hope this will help you in case you face any similar issue.

Microsoft has released another SharePoint 2013 Cumulative Update in February 2015. Let me help you know how we can install  February 2015 on SharePoint 2013 server.

Its per-requisites is either SharePoint 2013 SP1 or SharePoint 2013 March PU.

Now the most important part is how to install SharePoint server February 2014 Cumulative Update.

Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hotfix Download Available link in the KB article for the release.

Here is link for all the updates:

Sharepoint Foundation 2013 has only 1 setup file ubersts2013-kb2920801-fullfile-x64-glb.exe
Download SharePoint Foundation 2013 February 2015 CU

Now here the twist starts, SharePoint 2013 update has 3 setup files ubersrv_1.cab, ubersrv_2.cab, ubersrv2013-kb2920804-fullfile-x64-glb.exe. You can download this from:
Download SharePoint Server 2013 February 2015 CU

Project Server 2013 update has 3 setup files ubersrvprj_1.cab, ubersrvprj_2.cab, ubersrvprj2013-kb2920796-fullfile-x64-glb.exe. You can download this from below
Download Project Server 2013 February 2015 CU

Office Web App server 2013 has only 1 setup filewacserver2013-kb2956101-fullfile-x64-glb.exe.
Download Office Web App 2013 February 2015 CU

The KB articles for September CU are available at the following locations:

• KB 2920801 – SharePoint Foundation 2013 February 2015 CU
• KB 2920804 – SharePoint Server 2013 February 2015 CU
• KB 2920796 – SharePoint Server 2013 with Project Server February 2015 CU
• KB 2956101 – Office Web App Server 2013 February 2015 CU

Once the updated the downloaded you need to extract all the updates in 1 folder as shown below:

• Now when you run the main setup file exe file, you will be able to extract and install the update.Do not try to extract cab file it will be extracted by exe.
• Once you install these updates, you need to reboot the server
• Now system needs to be restarted.
• Follow the same steps on all SharePoint servers in farm.
• SharePoint PSconfig wizard on all servers.
• Finally it is installed

Note : SharePoint Server 2013 update contains the SharePoint Foundation update.Where as SharePoint Server 2013 with Project Server update contains Project Server update, SharePoint Server update and SharePoint Foundation update.

For more information:
http://blogs.technet.com/b/stefan_gossner/archive/2015/02/10/february-2015-cu-for-sharepoint-2013-has-been-released.aspx

One of my friend recently installed SharePoint 2013 SP1 and run PSCONFIG wizard on all SharePoint server. The wizard completed without any issue except 1 server which has Workflow server installed on it.

Issue: 

In SharePoint UI, user was getting below error:
———–Site error————
Sorry, something went wrong
Method ‘StartWorkflowOnListItem’ in type ‘Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider’ from assembly ‘Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ does not have an implementation.
———–Site error————
In ULS logs we could see error message:
———–ULS log error————
12/21/2014 10:09:14.44 w3wp.exe (0x06D6) 0x1F3C SharePoint Foundation General 8nca Medium Application error when access /_layouts/15/Workflow.aspx, Error=Method ‘StartWorkflowOnListItem’ in type ‘Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider’ from assembly ‘Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ does not have an implementation. at Microsoft.SharePoint.WorkflowServices.FabricSolutionProviderFactory….

12/21/2014 10:09:14.46 w3wp.exe (0x06D6) 0x1F3C SharePoint Foundation Runtime tkau Unexpected System.TypeLoadException: Method ‘StartWorkflowOnListItem’ in type ‘Microsoft.SharePoint.WorkflowServices.FabricWorkflowInstanceProvider’ from assembly ‘Microsoft.SharePoint.WorkflowServices, Version=15.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c’ does not have an implementation. at Microsoft.SharePoint.WorkflowServices.FabricSolutionProviderFactory.<.cctor>b__3(WorkflowServicesContext context) at Microsoft.SharePoint.WorkflowServices.FabricSolutionProviderFactory.GetProvider[T]…

———–ULS log error————

Cause for the issue: 
Found that when we upgrade SharePoint server, STS service does not updated properly and require a separate update. There is a mismatch of STS and SharePoint which cause this issue.

Resolution to the issue:
To install this update:
1. Browse to site http://www.microsoft.com/en-us/download/details.aspx?id=42898
2. Now click on “Download”
3. Once update is downloaded, Install it on SharePoint server.

For More information about update check http://support.microsoft.com/kb/2880963