Fix: Exchange 2010 Message tracking is currently unavailable & RBAC

[ZeroHour]

Hi

We had a problem where we couldnt launch message tracking (or rbac) in the Exchange 2010 management console. If we did we got an error about "Message tracking is currently unavailable" (also "Role Based Access Control (RBAC) User Editor is currently unavailable") when ever it was double clicked. Initially we found no solution and knowing exchange 2010 sp1 was coming out soon we hoped it would be resolved then but after installing sp1 it was still broken. We left the issue unfixed until now due to lack of use/time but we recently needed it and I found a fix that worked for us.

 

Our fix:

Firstly lets double check message tracking is on and working. Bring your exchange shell up and run

get-transportserver | fl *track*

This should show you something like:

MessageTrackingLogEnabled               : True
MessageTrackingLogMaxAge                : 30.00:00:00
MessageTrackingLogMaxDirectorySize      : 1000 MB (1,048,576,000 byt
MessageTrackingLogMaxFileSize           : 10 MB (10,485,760 bytes)
MessageTrackingLogPath                  : {a path to a dir}
MessageTrackingLogSubjectLoggingEnabled : [b]True[/b]

MessageTrackingLogEnabled               : True
MessageTrackingLogMaxAge                : 30.00:00:00
MessageTrackingLogMaxDirectorySize      : unlimited
MessageTrackingLogMaxFileSize           : 4 GB (4,294,967,296 bytes)
MessageTrackingLogPath                  :
MessageTrackingLogSubjectLoggingEnabled : [b]True[/b]

So hopefully MessageTrackingLogSubjectLoggingEnabled is true which means its enabled.

Now check that files are at least being made at the path specified in MessageTrackingLogPath above.

 

Now assuming files are made etc just sanity check the "Microsoft Exchange Transport Log Search" service is running.

 

Next run:

get-ecpvirtualdirectory | fl

Now pay attention to "InternalUrl" as thats the address its trying to access the ecp (which handles message tracking)

Ours was blank but the same fix would apply if its not the internal servername for example.

 

To fix run:

set-ecpvirtualdirectory ecp* -InternalURL https://{your internal fqdn of the exchange server}/ecp

Now try launching the tracker again, you may get prompted to login when using a fqdn as internet explorer wont auto authenticate usually but an admin account should work.

If this does not work try changing that path to see if set for another url such as without https or using a non fqdn as the address.

 

Hope this helps as it fixed our issue.

 

NOTE: this fix should also fix the "Role Based Access Control (RBAC) User Editor is currently unavailable" parts as well as both use the ecp path to manage these sections.

Edited December 7, 2010 by ZeroHour

[bodminman]

Just what I was coming on here to look for!

[ZeroHour]

Just what I was coming on here to look for!

 

I presume it worked? I just found this fix 10 mins ago, wow coincidence.

[bodminman]

Just finished remoting and yep it worked, cheers!

[Jawloms]

Worked for me too. Thanks @ZeroHour.