Our test environment was giving me issues today. It’s an error that was reported and supposedly fixed nearly 18 months ago. When typing a query in the text box, the initial search works, but when using a refiner or changing the query the result would return an error Field or Property ‘TimeZoneId’ does not exist. This was first reported after the July 2015 CU as a regression and supposedly fixed in the August 2015 CU. The problem was in the Microsoft.Office.Server.Search.ServerProxy.dll. Now I admit our servers are out of date when it comes to CUs (something I have been trying to get time from my client to do) but we are well beyond August 2015 CU.
Our environment is setup with Search being provided by our App servers in a Shared Services configuration. When checking the WFE I found the dll version to be at 15.0.4815.1000. We have two app servers that are running the search services. App#1 had the same version of the dll, but App#2 was actually sitting at an older version: 15.0.44020.1017. I believed this to be the culprit.
Resolving: “Field or Property ‘TimeZoneId’ does not exist“
- Shut down IIS on the server you need to update.
- From a server with the correct version copy Microsoft.Office.Server.Search.ServerProxy.dll to the _app_bin folder of the SharePoint virtual directory (example: C:\inetpub\wwwroot\wss\VirtualDirectories\AppServer\_app_bin)
- If you don’t have a “good” location, the correct file should also be located in “C:Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\CONFIG\BIN”
- Restart IIS and test. Should be fine now.
The cause is likely this single file not being copied over properly when patched. Hope this helps someone still having this issue.
Thanks for reading!
Comments