Please also have a look at the article that discusses how to properly patch a SharePoint 2013 farm which has Search enabled (see below).

Previous releases of the SharePoint Server 2013 cumulative update included both the executable and the .CAB file in the same self-extracting executable download. Because of the file size, the SharePoint Server 2013 package has been divided into several separate downloads. One contains the executable file, while the others contain the CAB file. All are necessary and must be placed in the same folder to successfully install the update. All are available by clicking the same Hotfix Download Available link in the KB article for the release.

Important: If your farm has been on a patch level lower than July 2015 CU: Unlike other CUs - after installing the August 2015 CU you need to run the SharePoint 2013 Products Configuration Wizard on each machine in the farm. If you don't run PSCONFIG after installing August 2015 CU (on a farm which had a lower patch level than July 2015 CU) crawl might no longer work - so ensure to schedule a maintenance window when installing this CU which includes PSCONFIG runs.

Hi Stephen,
I tried applying August 2015 CU to see if it fixes Time ZoneId error (as mentioned in JUly 2015 CU) . I applied August 2015 CU on machine running July2015Cu . Run Psconfig , run crawl , however I am still getting exact same issue as before "Field or property
"TimeZoneId" does not exist " when performing search.
I am able to reproduce by doing following
Search for a file
When results are presented , retype or change the query and this time you get an error "Field or property "TimeZoneId" does not exist "in sp2013 " in search center .

I have also verified that we do have Rerelease SP1 for all SharePoint components i.e version 15.0.4571.1502

I’m not sure which problem you refer to – but did you see a KB article stating that this issue should be fixed in August?
Did you raise a support case with Microsoft to report the issue or has someone else reported that issue to Microsoft through official channels?

I'm experiencing the same issue as a lot of people with the July 2015 CU. When running search it returns with an error "Field or property "TimeZoneId" does not exist." Looks like some people are fixing this by replacing the Microsoft.Office.Server.Search.ServerProxy.dll
file with one that was not affected. Unfortunately I don't have one of those. =[

Am I the only one getting "failed identification" before even extracting the files this update? On 2 of my 3 DEV servers it installs fine but on the third one I'm getting that error (but in my local language so translation may be off) when i try to install
it. I get as far as the "do you want to run as admin" dialogue and the next one where I tick the checkbox and then it's supposed to extract files. Only mine doesn't. But only on one server? This is weird behavior…
// Kris

Hello Stefan,
I have rebooted, ran Windows Update, no luck.
I have re-downloaded the entire packs directly on the server just to eliminate corrupt files, no luck.
I have retried it as every user I can think of, even the domain administrator, no luck.
The install goes through fine on my CA/Search/Index server and my web front end server. The server that it isn't working on is our BI server, which has a local SQL2014 install with Powerpivot, Reporting Services etc.

The error I'm getting is the one triggered by "OPatchInstall: Property 'PACKAGE.PROMPT.DETECTIONERROR' value 'Det gick inte att köra identifieringen.'. Screenshot is located herehttp://imgur.com/a9V55vF

From the error message the problem is not the patch you downloaded – it might be that the installation database on your machine which holds the information about previously installed products and patches is corrupt or that files in the installer folders (C:windowsinstaller
or c:windowssoftwaredistribution) got corrupted.

Without further analysis it is not possible to identify if the issue can be resolved without reinstalling the whole box. I would recommend to open a support case with Microsoft to get this analyzed in more details.

Ran into the same issue with the 'Field or Property TimezoneId Does not exist' and the proposed fix mentioned above sorted the issue out.

Copied the Microsoft.Office.Server.Search.ServerProxy.dll (Version 15.0.4687.1000) from C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15CONFIGBIN and replaced the same file in the _app_bin folder of the SharePoint sites (in all web
front ends) after stopping the Sites in IIS first.
Thanks for the information pointing to the issue.
William

We installed the new patch over this weekend and now are having users complaining they can't attach a file to a list item. It produces a "File names can't contain the following characters: & " ? < > # { } % ~ / ." even though the filename is simple and
doesn't have any of those characters. Anyone else experiencing this issue?

We also have problem with the TimeZoneID property introduced by CU July 2015. There is an incident opened and Microsoft has confirmed the problem was indeed introduced by CU JUly 2015. There is no solution yet and they are looking into it.

A little feedback on the issue I saw in our DEV environment: (@dsingh1980)
The problem originated from a corrupt c:windowsinstaller folder. Without it ubersvr just couldn't tell what was installed and what wasn't.

– With the help of Microsoft support engineer, restore most of it with a tool known as OPUtil.vbs (but that might be internal MS stuff) I was able to rebuil most of the c:windowsinstaller files from the Test / Production server.
– When running ubersvr it would go on to the installation phase but still fail.
– Checking the log showed exactly which MSP file couldn't install it.
– I extracted the ubersvr package and ran the MSP file manually which went fine.
– I then ran the ubersvr exe again and it failed on another MSP.
– I repeated the above steps to manually install the failing MSP file and after about 4 failed attempts it succesfully installed.
– Ran psconfig wizzard on all server.
– Done!

Although I really, REALLY wouldn't recommend this in a production environment. But it will be interesting to see what happens next time!

On one of the farms, I restarted the server – ran the install – ran ps config and did the steps many times and one time it succeeded. It looks like we need to run the same installer many times to get past all the errors. Not sure if this is the right way to
do it though.

@Kris: once I saw the problem you described. It was caused by a "system cleaner" application that removed files from C:WindowsInstaller. As described here –https://support.microsoft.com/en-us/kb/2667628 – you should never remove them, so make sure to steer clear from any "magical" system cleaners that promise to free up gigabytes of space. Those programs
are just useless.

@dsingh1980
I don't see why they should based on this issue. It was a very localized issue on one server, and it was more of a Windows issue than SharePoint issue. I had to perform the same steps to get SQL updated on the same server so this is a corrupted Windows, nothing
bad with the CU itself as far as I know, except this TimeZoneID issue people are having.

I also got your error message. What I did was extract the entire ubersvr package (just add "/extract" to it in a windows command prompt) and I ran the "x-none" MSP files manually and then I ran the CU update again. Hope it works for you and I hope it's not
a production server because then it might be best to reinstall it.

After august CU is installed i see this error in ULS "Original error: System.MissingMethodException: Method not found: 'System.String Microsoft.Office.Server.UserProfiles.UserProfile.get_FollowPersonalSiteUrl()'.

please compare the version of the Microsoft.Office.Server.UserProfiles.ServerStub.dll in the c:inetpubwwwrootwss\_app_bin directory with the one in C:Program FilesCommon FilesMicrosoft SharedWeb Server Extensions15CONFIGBIN directory.
It might be that the dll did not get updated when running PSCONFIG.
If that is the case, please backup the version in the _app_bin directory and copy the version from 15CONFIGBIN to the _app_bin directory to fix the issue.

Install-SPApplicationContent is the same as psconfig -cmd applicationcontent -install. So probably some updates require more than just psconfig -cmd upgrade -inplace b2b -wait. It could be that psconfigui does just that, so that's why not everyone has
experienced this issue.

Hi Piotr,
the UI version of PSConfig will run all tasks that it identifies necessary.
In the commandline version the user has to choose the tasks.
So indeed the UI version would be the recommended method to prevent such problems.
Cheers,
Stefan

I compared both DLL versions as you suggested they were same and updated at same time , just to validate i copied Microsoft.Office.Server.UserProfiles.ServerStub.dll from other server where CU was not installed to the one where CU was installed and i don't
see the error any more happening .

Actually I noticed this error when i was trying to execute the below code in CSOM

Hi Bjørn,
A fix to correct the issue is in the works and should be included in a future CU.
The workaround right now is to create the list item without attachment and then to attach the document using the ribbon.

I had the same "The installation of this package failed." issue as did Dheepa 18 Aug 2015 12:29 AM (and similar failed install reports for the July CU). I re-downloaded the files this morning and found increased file sizes for ubersrv2013-kb3055009-fullfile-x64-glb.EXE
(1,498,220,048 vs. 1,355,013,088 bytes) and Ubersrv_1.CAB (1,498,170,808 vs. 1,421,251,640 bytes). With the new binaries, the CU progresses farther, but ultimately, still fails. [Just curious … not sure how the .EXE even worked if it was truncated … did
MS re-post these files?]

Thanks Stefan. Actually, it ran clean overnight from the C: volume. As with anything, it could have failed for any number of non-reproducible reasons, but that's the one difference between my failure and success, D-volume versus C-volume.

I had a new installation of Win 2012 R2 with all the updates up to date. Then i've downloaded SharePoint 2013 with SP1 included, and installed it on the server. All was fine. Now i needed to install latest CU, and i tried to use August 2015, but i receive the
error: The installation of this package failed.
Then i tried with July 2015 CU and result is the same.
PS: i didn't run any kind of configuration wizard to create the farm, as i need to install all the binaries, and then to configure the farm.
Can you tell me what i'm doing wrong here? From my point of view i have no problem to open a case with Microsoft, but if they will ask to pay for this, then this is wrong, as what's the point?

Hi Cripian,
the issue you describe can happen with August CU – but it should not with July CU.
If it continues with July CU I would recommend to open a support case with Microsoft as this is not a known issue.
Cheers,
Stefan

Well i discovered it was my mistake. In the download link (http://www.microsoft.com/en-us/download/details.aspx?id=48560) there are 3 files: ubersrv2013-kb3055009-fullfile-x64-glb ,
ubersrv_1, ubersrv_2. Me i was downloading only exe file. After i tried several times, and installation still failed, i've downloaded the other two cab files, and started the installation again. After third time with all the files in the same folder, installation
was completed, so indeed i can confirm that the workaround with installation of August CU 3 times is working.

Awesome blog, this is always my go-to resources to CU updates. I’m hoping you can point me in the right direction. The August CU claims to provide fixes for Chrome deprecating NPAPI which enables a multitude of functionality in SharePoint, none the least of
which is ability to click links to Office documents and launch the corresponding Office application in the context of SharePoint so that check in/out, save, document information panel, etc. work.

The CU doesn’t have any fix for this, it just forwards Chrome over to Office Web Apps now. Can you recommend a good place to surface this as an issue? Collectively we have known Chrome is disabling NPAPI for almost a year and my clients/users expect to have
an ETA for a fix.

Hi Marcus,
where did you read that August CU fixes these issues?
Regarding your question: always open a support case if you see a need for a fix. Using a support case allows you to raise such concerns.
Cheers,
Stefan

Has anyone else ran into this issue on the August 2015 CU for SharePoint 2013? We are using promoted links that have several links that point to a file share. For example – file://servername/filename.docx. When the launch behavior is set to "In Page Navigation"
and you use the Promoted Links view, we get INVALID PAGE URL: message.