Upgrade farm :- SP2010Exception: Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException

We have 2 app server and 3 frontend server with clustered SQl server (2 nodes). Now we are find that except App server our all front end server require upgrade , it seems some one install patches (e.g. service pack or cumulative update applied, or language packs installed) without running PSConfing or command line equal to PSConfing.

Now normal process to upgrade farm by PSconfig UI and it showing upgrade is required.but when we try to upgrade it by UI after 9 tasks it getting failed with SharePoint’s Admin content DB error.

Because our app server is saying that no update is required to so we plan to run up command on front end server. but we have not luck we got below is the error message

Exception: Microsoft.SharePoint.Administration.SPUpdatedConcurrencyException: An update conflict has occurred, and you must re-try this action. The object SPUpgradeSession Name=Upgrade-20121029-090244-405 was updated by DOMAINNAME\USERNAME, in the PSCONFIG (7112) process, on machine MACHINENAME.  View the tracing log for more information about the conflict.

 

So we did so Google/Bing but no one giving us assurence that this is the root cause but in this blog can help us.

first we ran

stsadm -o setproperty -pn command-line-upgrade-running -pv Yes

than we ran

psconfig.exe -cmd upgrade -inplace b2b –wait –force

after these command we successfully upgrade the first FE server

But when we tried on second server we get same error this approach not worked for us Also, the command-line-upgrade-running STSADM property was already set to “Yes.”  So we decided to fist set the property No and than again set the property Yes by above command and run upgrade command, this time we successfully upgrade.

Now all servers and DBs are upgrade properly.

Other post that help us to understand more http://technet.microsoft.com/en-us/library/ff806338.aspx

Regards

Could not get the current time from the SNTP (RFC1769) server <52.102.13.2>

Last day i got a call that user is not able to access Sandbox solution. So as an administrator i think this could be a reason that sandbox service stop working but it hard from me to accept that without any reason service stop working . That was Prod environment so things were more critical.

Here is the scenario we have 2 app serve ,3 WEF and cluster based SQL server with two nodes . from App server i am getting multiple “Cannot generate SSPI context” error messages. yes there could be several reasons behind this error one is described in Microsoft support site here.

But before this we also check SQL server and we find Could not get the current time from the SNTP (RFC1769) server <52.102.13.2>. warning message.

now we checked from SP app and We were able to access Central admin.

now where is issue With SP or SQL or Some service account is missing form local user group(like WSS_*) or some where else ?

Step to dig it more

1. Hit iisreset on app server . now try to access Central Admin . That will not come properly and will show service related error.

2. we hit command prompt and type Time and checked current time.

3. we went to SQL server node and follow above step 2

4. we compare time and find, time difference is more than hrs. so this could be reason because if time difference is more than the Maximum tolerance for computer clock synchronization there could be sysn problem between SQL and SP.

We adjusted time nearly same.

Now we hit the iisreset again and try to access central admin ohhhhh that come fine . Now we can start Sandbox service from windows service console from all three WFEs .

Now we tried to access site collection and they are working fine even sandbox solution.

So we find there could be several reason behind these issues but when above issue came together ,time difference between servers(VM) in farm  could be a reason and we need to check that also.

Now we are not getting and SSPI context error anymore.

Hope this help you.

Kindest Regards

:)