MSExchangeRPC issues

Question

MSExchangeRPC issues

intel233 (MIS)

(OP)

1 Jul 13 09:27

I am having an issues with Public folders. Users can't access them and I look on my Exchange server and the MSExchangeRPC services memory seems to be ballooning. I have to kill it and restart for users to be able to access the public folders. This is Exchange 2010 Version: 14.02.0342.003. It's a VM with 32gig Ram.
Any help is appreciated.

ShackDaddy (MIS) · Answer 1 · 2013-07-01 11:09:32

Sounds like it probably is the iPhone iOS bug:

http://support.microsoft.com/kb/2814847

http://support.apple.com/kb/TS4532

Dave Shackelford
ThirdTier.net
TrainSignal.com

intel233 (MIS) · Answer 2 · 2013-07-01 16:58:34

Thanks will have to look at that. I entered anther post cause but how can I get a list of all IOS devices and the users that are associated with them? I see there are a bunch of scripts but they do not work. I think its the way this environment is setup. For me to get info from power shell I have to set-adserversettings -viewentireforest $true.

I have tried Export-iOSDeviceStatistics and ActiveSyncReport.ps1

My exchange servers sit in the root domain.

intel233 (MIS) · Answer 3 · 2013-07-12 10:39:59

I blocked the old IOS and the issue is still happening. You have any other ideas on what might be causing this?

TIA

Zelandakh (MIS) · Answer 4 · 2013-07-14 17:04:24

Yup. Almost certainly http://support.microsoft.com/kb/2497453 will fix your issue.

Zelandakh (MIS) · Answer 5 · 2013-07-14 17:13:28

See also http://support.microsoft.com/kb/2535105

intel233 (MIS) · Answer 6 · 2013-07-14 17:22:08

http://support.microsoft.com/kb/2497453 w
Wasn't that part of the latest rollup?
http://support.microsoft.com/kb/2535105 points back to 2497453

Could the throttling policy have anything to do with this?

The .NET has no download. I would have to call Microsoft to get this?

Zelandakh (MIS) · Answer 7 · 2013-07-17 04:10:58

It isn't part of a rollup. Try the registry method in 2535105 first and by all means try the throttling policy but I don't think it will make any difference as you are hitting an RPC limit. If all else fails, yes you'd need to call MS to get the fix.

intel233 (MIS) · Answer 8 · 2013-07-17 06:55:04

OK thanks. Just one more question. For the .NET, do I apply that to my MB servers or CAS servers?

Zelandakh (MIS) · Answer 9 · 2013-07-28 02:26:19

Technically only the MBX but for completeness I always do all Exchange boxes in the org.

intel233 (MIS) · Answer 10 · 2013-08-19 08:25:17

I did a dump file when the public folders stopped working and this is what I get:
Loading Dump File [C:\EXCHANGE\Microsoft.Exchange.RpcClientAccess.Service.DMP]
User Mini Dump File with Full Memory: Only application data is available

Symbol search path is: *** Invalid ***
****************************************************************************
* Symbol loading may be unreliable without a symbol search path. *
* Use .symfix to have the debugger choose a symbol path. *
* After setting your symbol path, use .reload to refresh symbol locations. *
****************************************************************************
Executable search path is:
Windows 7 Version 7601 (Service Pack 1) MP (8 procs) Free x64
Product: Server, suite: Enterprise TerminalServer SingleUserTS
Machine Name:
Debug session time: Mon Aug 19 08:15:07.000 2013 (UTC - 4:00)
System Uptime: 36 days 3:31:30.492
Process Uptime: 10 days 0:34:22.000
................................................................
...............................................................
Loading unloaded module list
.
*** ERROR: Symbol file could not be found. Defaulted to export symbols for ntdll.dll -
*** ERROR: Symbol file could not be found. Defaulted to export symbols for KERNELBASE.dll -
ntdll!NtWaitForSingleObject+0xa:
00000000`7779135a c3 ret

Come Join Us!

Posting Guidelines

MSExchangeRPC issues