Hi All,

I'm sort of stuck on the Exchange 2013 Probe Monitors, Monitors such as Imap, ActiveSync, Pop3 and FrontEndTransport keep failing. To fix/check the issue I'm following the below links:

http://technet.microsoft.com/en-us/library/ms.exch.scom.activesync(v=exchg.150).aspx

http://technet.microsoft.com/en-us/library/ms.exch.scom.imap(v=exchg.150).aspx

For example typing in Invoke-MonitoringProbe ActiveSync\ActiveSyncCTPProbe -Server server1.contoso.com | Format-List

I will get the following error:

WARNING: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

Not sure why I'm getting this error.

For Imap testing i.e. typing in Invoke-MonitoringProbe IMAP\ImapCTPProbe -Server server1.contoso.com | Format-List

I will get the following error:

WARNING: No mailboxes were found to use in the CTP probe.

I'm absolutely stumped on why I'm getting these errors.

I'm running my Exchange servers on Hyper-V 2012 (My Hyper-V 2012 is clustered and managed by VMM 2012 SP1)

I have 8 Exchange 2013 Enterprise CU6 nodes, with 2 DAGS

Each Exchange server is running 4 cores of Processor and 24Gig of Ram (Not using Dynamic Memory)

If someon can shed some light on this issue it would be most appreciated.

Regards

Mike

Hi Mike

Try  opening the EMS in elevated mode (Run as Administrator) and then run the command

Hi Mike,

Please make sure the user who run the command is a member of following groups:

1. Organization Management

2. Server Management

3. Recipient Management

4. Local Server Administrator

 

Thanks

If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com

Hi,

This is still not working giving me the same errors.

Hi,

Thanks for your update.

Based on my research, I notice that most of this issue occur on the code level.

Some threads that I've refered:

1. https://social.msdn.microsoft.com/Forums/en-US/b4d46d2b-ed00-45ce-82ce-1a23790e52d5/index-was-out-of-range-must-be-nonnegative-and-less-than-the-size-of-the-collection-parameter?forum=csharplanguage

2. http://stackoverflow.com/questions/19162248/index-was-out-of-range-must-be-non-negative-and-less-than-the-size-of-the-colle

Disclaimer: Microsoft is providing this information as a convenience to you. The sites are not controlled by Microsoft. Microsoft cannot make any representations regarding the quality, safety, or suitability of any software or information found there. Please make sure that you completely understand the risk before retrieving any suggestions from the above link.

 

I suggest ask Exchange Development Forum to double confirm this issue. For your convenience:

https://social.technet.microsoft.com/Forums/office/en-US/home?forum=exchangesvrdevelopment

 

Thanks

Hi All,

I'm sort of stuck on the Exchange 2013 Probe Monitors, Monitors such as Imap, ActiveSync, Pop3 and FrontEndTransport keep failing. To fix/check the issue I'm following the below links:

http://technet.microsoft.com/en-us/library/ms.exch.scom.activesync(v=exchg.150).aspx

http://technet.microsoft.com/en-us/library/ms.exch.scom.imap(v=exchg.150).aspx

For example typing in Invoke-MonitoringProbe ActiveSync\ActiveSyncCTPProbe -Server server1.contoso.com | Format-List

I will get the following error:

WARNING: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

Not sure why I'm getting this error.

For Imap testing i.e. typing in Invoke-MonitoringProbe IMAP\ImapCTPProbe -Server server1.contoso.com | Format-List

I will get the following error:

WARNING: No mailboxes were found to use in the CTP probe.

I'm absolutely stumped on why I'm getting these errors.

I'm running my Exchange servers on Hyper-V 2012 (My Hyper-V 2012 is clustered and managed by VMM 2012 SP1)

I have 8 Exchange 2013 Enterprise CU6 nodes, with 2 DAGS

Each Exchange server is running 4 cores of Processor and 24Gig of Ram (Not using Dynamic Memory)

If someon can shed some light on this issue it would be most appreciated.

Regards

Mike

I've been receiving these same exact error messages since upgrading to Exchange 2013 CU 6. Has anyone confirmed that these are a bug? 

Hi there,

I have SCOM 2012 and Exchange 2013 with the latest CU.  In SCOM I see multiple "- Activesync" alerts with the following diagnostic command: Invoke-MonitoringProbe -Identity:"ActiveSync\ActiveSyncCTPProbe" -Server:SERVER01| fl

When I try to run this command on my Exchange server, I get the following warning:

WARNING: Index was out of range. Must be non-negative and less than the size of the collection.
Parameter name: index

Is there something I can do about this? At least filter this error in SCOM or Exchange or something?

@Mavis Huang, your answer really doesn't help us at all...

Well I'm receiving the same problem with two Exchange 2013 Servers updated to CU7, so i think is configuration issue.Maybe something with Test Email account.

It will be good if someone enlighten us with more information.

edit: I did more deep investigation so the test probe is using one of the HealthMailbox accounts. It can login trough IMAP so I guess that the monitoring probe is the problem. I recreated the Health Mailboxes but this didn't resolve anything.

• Edited by Martin Dutsov 17 hours 16 minutes ago

Well I'm receiving the same problem with two Exchange 2013 Servers updated to CU7, so i think is configuration issue.Maybe something with Test Email account.

It will be good if someone enlighten us with more information.

edit: I did more deep investigation so the test probe is using one of the HealthMailbox accounts. It can login trough IMAP so I guess that the monitoring probe is the problem. I recreated the Health Mailboxes but this didn't resolve anything.

• Edited by Martin Dutsov Wednesday, April 22, 2015 2:11 PM

Well I'm receiving the same problem with two Exchange 2013 Servers updated to CU7, so i think is configuration issue.Maybe something with Test Email account.

It will be good if someone enlighten us with more information.

edit: I did more deep investigation so the test probe is using one of the HealthMailbox accounts. It can login trough IMAP so I guess that the monitoring probe is the problem. I recreated the Health Mailboxes but this didn't resolve anything.

• Edited by Martin Dutsov Wednesday, April 22, 2015 2:11 PM

I have the same issues, for the ActveiSyncProbe, I get the index is out of range

for the CTPProbe I get No mailboxes were found to use in the CTP Probe the StateAttribute3 say: Unable to retrieve server name.

I have these issues since I can remember from CU2 to CU7 (I didnt install CU8 yet). I have yet to find any kind of solution.

Well I found the solution for this after months and full of forum with the same issues. In my case:

I noticed on my AD the Monitoring Mailboxes folder was non existant (Under Microsoft Exchange System Objects). I couldnt recreate it even using the web solution. I ran a setup /prepareAD (which worked fine before). and got a LDAP server not found issue.

It's a bug in the Exchange 2013 setup (not fixed in CU8). You have to move/make the server listed Global Catalog. Once I made that DC a GC (and rebooted it and waited for the replication).

Just run the setup /prepareAD and you should see the folder create. (Its pretty quick to run and I did it live)

After this, go under your Health Monitoring service, change the log on for an Administrator logon, restart the service and you should see the mailboxes there. (rechange it to System logon once they are created). 

Mailboxes are recreated and It finally fixed my issues.

Some ref:

https://ril3y.wordpress.com/2014/06/27/possible-bug-in-exchange-2013-cu5-setup-exe-preparead/

• Edited by Carl Olsen V 15 hours 35 minutes ago

Well I found the solution for this after months and full of forum with the same issues. In my case:

I noticed on my AD the Monitoring Mailboxes folder was non existant (Under Microsoft Exchange System Objects). I couldnt recreate it even using the web solution. I ran a setup /prepareAD (which worked fine before). and got a LDAP server not found issue.

It's a bug in the Exchange 2013 setup (not fixed in CU8). You have to move/make the server listed Global Catalog. Once I made that DC a GC (and rebooted it and waited for the replication).

Just run the setup /prepareAD and you should see the folder create. (Its pretty quick to run and I did it live)

After this, go under your Health Monitoring service, change the log on for an Administrator logon, restart the service and you should see the mailboxes there. (rechange it to System logon once they are created). 

Mailboxes are recreated and It finally fixed my issues.

Some ref:

https://ril3y.wordpress.com/2014/06/27/possible-bug-in-exchange-2013-cu5-setup-exe-preparead/

http://theucguy.net/recreate-exchange-2013-health-mailboxes/

• Edited by Carl Olsen V Monday, June 08, 2015 3:51 PM

Well I found the solution for this after months and full of forum with the same issues. In my case:

I noticed on my AD the Monitoring Mailboxes folder was non existant (Under Microsoft Exchange System Objects). I couldnt recreate it even using the web solution. I ran a setup /prepareAD (which worked fine before). and got a LDAP server not found issue.

It's a bug in the Exchange 2013 setup (not fixed in CU8). You have to move/make the server listed Global Catalog. Once I made that DC a GC (and rebooted it and waited for the replication).

Just run the setup /prepareAD and you should see the folder create. (Its pretty quick to run and I did it live)

After this, go under your Health Monitoring service, change the log on for an Administrator logon, restart the service and you should see the mailboxes there. (rechange it to System logon once they are created). 

Mailboxes are recreated and It finally fixed my issues.

Some ref:

https://ril3y.wordpress.com/2014/06/27/possible-bug-in-exchange-2013-cu5-setup-exe-preparead/

http://theucguy.net/recreate-exchange-2013-health-mailboxes/

• Edited by Carl Olsen V Monday, June 08, 2015 3:51 PM

Well the problem still persist in CU9 .

@Carl - I have the object on my DC so this is not the case.

I have this problem on two completely different environments ,so i'm starting to think that it is a BUG.

Well the problem still persist in CU9 .

@Carl - I have the object on my DC so this is not the case.

I have this problem on two completely different environments ,so i'm starting to think that it is a BUG.

• Proposed as answer by Hoosie2 17 hours 9 minutes ago