Azure & Office 365

Posts Tagged ‘environment’

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.

Hi All,

Lets try to configure a SharePoint farm in a workgroup environment. Normally if we have to configure a SharePoint on a Workgroup environment only option available for us is Standalone environment. Now lets us try to understand how we can configure a SharePoint farm environment in a Workgroup environment. We need to run below powershell commands. Make sure you update passphase and SQL server name in below powershell. We have SharePoint and SQL installed on same machine. Make sure account used during FarmAccount does have access to SQL server.

$FarmAccount = Get-Credential
$PassPhrase = “FarmPassphrase”
$FarmPassphrase = (ConvertTo-SecureString $PassPhrase -AsPlainText -force)
$FarmConfigDatabase = “Wss_config_2”
$AdminContentDatabase = “SPFarm_Admin_ContentDB_2”
$CentralAdminPort = 8080
New-SPConfigurationDatabase -DatabaseServer (SQLservername) -DatabaseName $FarmConfigDatabase -AdministrationContentDatabaseName $AdminContentDatabase -Passphrase $FarmPassphrase -FarmCredentials $FarmAccount

Now let’s move a steps ahead and try to use different server for SharePoint and SQL server. Here we created a SQL user account and updated credentials in dbcredential.
$dbcredential = New-Object –typename System.Management.Automation.PSCredential –argumentlist “SQLuser”, (ConvertTo-secureString “SQLpassword” –AsPlainText –Force)
$PassPhrase = “FarmPassphrase”
$FarmPassphrase = (ConvertTo-SecureString $PassPhrase -AsPlainText -force)
$FarmConfigDatabase = “Wss_config”
$AdminContentDatabase = “SPFarm_Admin_ContentDB”
$CentralAdminPort = 8080
$FarmAccount = Get-Credential
New-SPConfigurationDatabase -DatabaseServer “SQLservername” -DatabaseName $FarmConfigDatabase -AdministrationContentDatabaseName $AdminContentDatabase -Passphrase $FarmPassphrase -FarmCredentials $FarmAccount -DatabaseCredentials $dbcredential

Note: We still cannot create a Multiple SharePoint server farm in Workgroup environment. Using above script you can connect only 1 SharePoint server with a SQL server.

This script works for both SharePoint 2010 and SharePoint 2013