Link to home
Start Free TrialLog in
Avatar of Snowmizer01
Snowmizer01

asked on

Exchange 2010 SP3 Update Rollup 7

After applying the Exchange 2010 SP3 Update Rollup 7 in October we have had issues with Outlook clients not being able to download the OAB.  For the mobile users this is inconvenient since they cannot see new users.  We are also seeing an error in the eventlogs
SourceName=MSExchange MailTips
EventCode=14039
The most recent group metrics file was generated at 10/18/2014 12:57:51 PM, which is older than 3/7/2015 8:27:26 PM.

These all appear to be centered around the Exchange  update which was installed with the MS Updates.  

Any thoughts are much appreciated.
Avatar of Simon Butler (Sembee)
Simon Butler (Sembee)
Flag of United Kingdom of Great Britain and Northern Ireland image

Mailtips comes off availability.
OAB is something else.
Could be two different issues, could be the same.

When you try to download the OAB, what happens? Do you get a sync error log in Outlook?
Does free/busy information work?
Are you using web publishing for OAB or public folders?

Single server I presume?

Simon.
Avatar of Snowmizer01
Snowmizer01

ASKER

Both of these issues started after the update.  The folders in which they reside have the same dates so that is why I say they are the same issue  This is a single Exchange server.  When we try to download the OAB we get an error, Task reported error 0x80190194 The operation failed.

I created a new OAB over the weekend and set it up for web publishing.  Everything else appears to be working.

Thanks for the quick response.
Run this command:

get-MailboxServer | select identity, ForceGroupMetricsGeneration

If it comes back with false, then run this command:

 Set-MailboxServer -ForceGroupMetricsGeneration $true

Then wait a couple of hours and see if the mail tips error clears.

Simon.
This was already set to true.

Also, on the OAB I did enable the public folder distribution.

One thing that I did notice regarding the OAB is that the under V14\ClientAccess\OAB the folder name is still set to the old Address book quid and is dated 10/18/14 the date when the patch was applied.  So when I created the new OAB this weekend this did not get updated.  The V14\ExchangeOAB folder has the current OAB files.

Also, if I look at the V14\ClientAccess\GroupMetrics folder the files here are dated 10/18/14.  If I look at V14\GroupMetrics the files are current.

It appears the ClientAccess folder is not getting updated with the current information.  What updates these folders?  From what I have read the update that was applied did update the CAS.  I also read that previous updates were suppose to be uninstalled, this was not done and now we have update rollup 8-v2 installed as well.
Also, in looking at IIS The OAB site is pointing to the V14\ClientAccess\OAB folder with the old files.
" I also read that previous updates were suppose to be uninstalled.."

That is not the case. The only thing you have to remove is any interim update that was received directly from Microsoft support. If you have just been installing rollups, then you have nothing to worry about.

Try running the updatecas.ps1 script from EMS. You will find it in C:\Program Files\Microsoft\Exchange Server\V14\Bin

Simon.
I ran the command, the results are the same.  No change to the files/folders that I mentioned.
Can you tell me what permissions are suppose to be on the C:\Program Files\Microsoft\Exchange Server\V14\ClientAccess folder?  I set the permissions for the OAB folder but since groupmetrics is not working I figure the permissions at the ClientAccess level are not correct and were filtered down through the sub-folders.
https://www.experts-exchange.com/questions/26842235/Exchange-2010-errors.html

This link is very similar to what I am seeing.  This all started after applying the exchange update roll up.  All the services are starting/started and we get the  errors during normal operations throughout the day.  Any other ideas would be much appreciated.
ASKER CERTIFIED SOLUTION
Avatar of Snowmizer01
Snowmizer01

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
This completely resolved the issue.  Since Exchange requires UNC paths to function, once I made the change the errors have stopped.