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
:)
No comments:
Post a Comment