To attempt a resolution I decided to patch all the servers again. I corrected this (or so I thought) by reinstalling the patch on SP04. For some reason, even though it showed up fine in the services list (no errors listed) it was indicated that the server was missing files while trying to patch the WFEs. However, when my colleague patched the servers something when wrong with our second app server (call it SP04). This wasn’t caught before because the farm isn’t currently in active use.
And by recent I mean within the last few months. So as I stated before, we had recently had a patch run on this farm. So to ensure it wasn’t the issue, I gave the service account full ownership access. To make life easier, I simply compared the mappings and access between the farm that wasn’t working and a farm that was.
Since the DB didn’t seem to be the culprit I moved on to security.When I compared the latest IDs I found the DB were each at the same version.Once against the config DB and once against the content DB. So I finally confirmed the versions were the same running the following SQL command. Upgrade-SPContentDatabase WSS_Content_Database This didn’t work, so the next step was to attempt to upgrade the content database manually:.PSConfig.exe -cmd upgrade -inplace b2b -force The wizard was run during the patch, but wanted to ensure nothing was missed. Ran the command-line version of the SharePont Config Wizard.I tried the following fixes to resolve that possible issue: I initially thought the issue was the version mismatch as we recently updated the servers to Oct 2015 CU and this farm wasn’t used much.This post discusses the steps I took and the end result. First the farm did indeed have a misconfiguration (I am writing about that one separately) and it was found one of our servers in the farm wasn’t functioning properly due to a recent patch not applying properly.
We were receiving version mismatch errors when running code within our farm. The other day I was attempting to fix what appeared to be a configuration issue with our farm.
0 kommentar(er)
