locked
Set CAS Connectivity Test Credentials Alert for Exchange 2007 MOM Pack RRS feed

  • Question

  • Hi,

    I am getting following alert from Exchange Server where i have installed the Mailbox Role. I could see that this is coming because there is no cmdlet such as Set-CasConnectivityTestCredentials on the node.

    Date and Time: 9/11/2009 5:35:04 PM
    Log Name: ScriptGenerated.Data
    Source: MSExchange CasConnectivityTestCredentials
    Event Number: 500
    Level: 1
    Logging Computer: E12RAVS.emerald.com
    User: 
     Description:
    Object reference not set to an instance of an object.
     

    Event Data:

    Date and Time: 9/11/2009 5:35:04 PM
    Property Name Property Value
    Message Object reference not set to an instance of an object.
    EventNumber 500
    EventType 1
    EventSource MSExchange CasConnectivityTestCredentials
    LoggingComputer E12RAVS.emerald.com



    Please let me know what am i missing . I am running Exchange 2007 SP1.
    Friday, September 11, 2009 12:22 PM

Answers

  • This is a hidden cmdlet. You could try running the New-TestCasConnectivityUser.ps1 again on the mailbox server.
    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    • Marked as answer by S. Halsey Saturday, September 12, 2009 3:03 AM
    Friday, September 11, 2009 11:18 PM

All replies

  • This is a hidden cmdlet. You could try running the New-TestCasConnectivityUser.ps1 again on the mailbox server.
    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    • Marked as answer by S. Halsey Saturday, September 12, 2009 3:03 AM
    Friday, September 11, 2009 11:18 PM
  • Yes, if you re-run the new-testCasConnectivityUser.ps1 it should fix up any problems with the mailbox account that exists for your mailbox server.  The next time the set-casconnectivity credential runs it should pick up the update and start to function.
    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    Saturday, September 12, 2009 3:04 AM
  • What's the new-testCasConnectivityUser.ps1,

    How could i run it on exchange server, running exchange 2007 !!!!
    Tuesday, December 29, 2009 10:23 AM
  • You need to run it on mailbox servers that are monitored using cas synthetic transactions (they will use the user context created by thisc script). The script is included with Exchange 2007. You can read more here http://technet.microsoft.com/en-us/library/dd772554.aspx 


    This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at http://www.microsoft.com/info/cpyright.htm
    Tuesday, December 29, 2009 8:59 PM
  • I´ved imported the MP for Exchange 2010 (which still is using the account for syn tran. In our environment the account is named like: extest_123456789). This account gets locked out in a short period of time.

    Is it possible to set credential on this account and use pw never expires? though in the cmdlet new-cas.... it says this account will handle pw reset (but I don´t think SCOM likes it?) automatically


    !
    Wednesday, February 10, 2010 12:21 PM
  • I'm having the same problem with the Exchange 2010 pack.   The extest_xxxxx account keeps getting locked out.   I've tried running the new-test account script multiple times and have restarted the correlation service, but it keeps getting locked out. 

    Microsoft - No help on this one?   

    Tuesday, April 13, 2010 3:23 PM
  • I'm experiencing exactly the same issue.
    Thursday, April 15, 2010 10:17 PM
  • I found the solution but now RPC over HTTP not working.

    Its so stupid. I found a Microsoft Article http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b2022687&sd=rss&spid=13965

    and there was remarkt that you need to change in IIS RPC / Authentication you must enable ASP.NET Impersination. With this change the Exchange Test Account wil no moor lockout.

     

    But now RPC will not work?

    What we need to do?

     

     

     

     


    Roendi
    Tuesday, May 4, 2010 11:44 AM