Test-cmdlets failed

Discussion:

Test-cmdlets failed

(too old to reply)

Prabhulingam

2009-04-02 10:41:12 UTC

Hi,

SCOM frequently reports errors when running test-cmdlets on Exchange Mailbox
server which is in a cluster node: "An error occurred when running the
Test-IMAPConnectivity diagnostic cmdlet." Also, this error is shown for other
diagnostic cmdlets like Test-OWAConnectivity (both External and Internal),
Test-Mailflow.

I have also checked the mailbox nodes by opening to Operations Manager
Console, and going to the monitoring pane and open discovered inventory. Also
Set the Target Type as "Microsoft Exchange 2007 Mailbox Servers
Installation".
What i could see here is my Physical virtual cluster node showing as
"NotMonitored"

Also under Administration pane - "Agent Managed" i could see by both
physical Mailbox servers node as monitored and healthy.
But my virtual mailbox node is showing under "Agentless Managed" as healthy.
Is this is right ?

Can anyone help?

Regards
Prabhulingam

Steven Halsey [MSFT]

2009-04-02 17:36:50 UTC

Permalink

SCOM shouldn't be running commandlets like test-imapconnectivity and
test-owaConnectivity on the Mailbox Server, as these workflows should target
the Client Access Server.
If you go into Discovered Inventory in the Console and change the Target
Type to "Microsoft Exchange 2007 Client Access Servers Installation" does
you mailbox server appear in this list or only your Exchange Client Access
servers?
If your mailbox is appearing please let me know as this shouldn't be
happening and implies something in your environment is causing an error in
the discovery, and I would like to understand what it is.

Are you getting alerts about a problem connecting to the Mailbox Server
instead? Have you run the commandlet to create the Test Accounts on the
Mailbox server? Run the following commands in Exchange Management Shell to
create the test mailbox "get-mailboxserver [Your Virtual Mailbox Server
Name] | new-TestCasConnectivityUser.ps1".

Your agent management of the physical nodes (passive, active) and the
Exchange Mailbox Virtual Server seems to be correct.
--
Steven Halsey [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi,
SCOM frequently reports errors when running test-cmdlets on Exchange Mailbox
server which is in a cluster node: "An error occurred when running the
Test-IMAPConnectivity diagnostic cmdlet." Also, this error is shown for other
diagnostic cmdlets like Test-OWAConnectivity (both External and Internal),
Test-Mailflow.
I have also checked the mailbox nodes by opening to Operations Manager
Console, and going to the monitoring pane and open discovered inventory. Also
Set the Target Type as "Microsoft Exchange 2007 Mailbox Servers
Installation".
What i could see here is my Physical virtual cluster node showing as
"NotMonitored"
Also under Administration pane - "Agent Managed" i could see by both
physical Mailbox servers node as monitored and healthy.
But my virtual mailbox node is showing under "Agentless Managed" as healthy.
Is this is right ?
Can anyone help?
Regards
Prabhulingam

Prabhulingam

2009-04-06 06:15:01 UTC

Permalink

Hi Steven,

Thank you for the reply.
As you guided i looked into the discovered inventory wherein i could able to
see only the Exchange Client Access servers with the STATE as Not Monitored.

I have already run the Exchange command for creating the test mailbox.
I am typing the exact error with Event id which i am facing so that you can
have some idea.

Event Id: 500
Description: Could not find any available Domain Controller.

Event Id: 400
Description: Exchange diagnostic cmdlet invocation succeeded.

Let me know if require more details...

Post by Steven Halsey [MSFT]
SCOM shouldn't be running commandlets like test-imapconnectivity and
test-owaConnectivity on the Mailbox Server, as these workflows should target
the Client Access Server.
If you go into Discovered Inventory in the Console and change the Target
Type to "Microsoft Exchange 2007 Client Access Servers Installation" does
you mailbox server appear in this list or only your Exchange Client Access
servers?
If your mailbox is appearing please let me know as this shouldn't be
happening and implies something in your environment is causing an error in
the discovery, and I would like to understand what it is.
Are you getting alerts about a problem connecting to the Mailbox Server
instead? Have you run the commandlet to create the Test Accounts on the
Mailbox server? Run the following commands in Exchange Management Shell to
create the test mailbox "get-mailboxserver [Your Virtual Mailbox Server
Name] | new-TestCasConnectivityUser.ps1".
Your agent management of the physical nodes (passive, active) and the
Exchange Mailbox Virtual Server seems to be correct.
--
Steven Halsey [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Steven Halsey [MSFT]

2009-04-06 18:01:21 UTC

Permalink

The 400 event just indicates the commandlet ran successfully, not that the
synthetic transaction was successful.
The 500 event inidcates a definite problem. If on the Client Access Server
you open Exchange Management Shell and run the command manually
"Test-ImapConnectivity -ConnectionType:2 -TrustAnySSLCertificate:$true -LightMode:$true"
what results are returned?

Make sure the agent on the Client Access Server has Local System as the
Default Action Account, if it is using a different account that might be the
source of the error.
Check the Application Event log on the Client Access Server, and make sure
there are no errors or warnings indicating a problem with the Client Access
Server itself.
--
Steven Halsey [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi Steven,
Thank you for the reply.
As you guided i looked into the discovered inventory wherein i could able to
see only the Exchange Client Access servers with the STATE as Not Monitored.
I have already run the Exchange command for creating the test mailbox.
I am typing the exact error with Event id which i am facing so that you can
have some idea.
Event Id: 500
Description: Could not find any available Domain Controller.
Event Id: 400
Description: Exchange diagnostic cmdlet invocation succeeded.
Let me know if require more details...

Post by Prabhulingam
Hi,
SCOM frequently reports errors when running test-cmdlets on Exchange Mailbox
server which is in a cluster node: "An error occurred when running the
Test-IMAPConnectivity diagnostic cmdlet." Also, this error is shown for other
diagnostic cmdlets like Test-OWAConnectivity (both External and Internal),
Test-Mailflow.
I have also checked the mailbox nodes by opening to Operations Manager
Console, and going to the monitoring pane and open discovered
inventory.
Also
Set the Target Type as "Microsoft Exchange 2007 Mailbox Servers
Installation".
What i could see here is my Physical virtual cluster node showing as
"NotMonitored"
Also under Administration pane - "Agent Managed" i could see by both
physical Mailbox servers node as monitored and healthy.
But my virtual mailbox node is showing under "Agentless Managed" as healthy.
Is this is right ?
Can anyone help?
Regards
Prabhulingam

Prabhulingam

2009-04-07 06:21:01 UTC

Permalink

Hi Steven,

I had run the command on the Client Access server and i got the following
result.
CasServer MailboxServer Scenario Result
Latency(MS) Error
--------- ------------- --------
------ ----------- -----
XXXXXX Test IMAP4 Connectivity Success
49.88
(My webmail server)

May i know how to check the agent local system account ?
I have checked the Application event log, there are errors related to MS
forefront security only.

Post by Steven Halsey [MSFT]
The 400 event just indicates the commandlet ran successfully, not that the
synthetic transaction was successful.
The 500 event inidcates a definite problem. If on the Client Access Server
you open Exchange Management Shell and run the command manually
"Test-ImapConnectivity -ConnectionType:2 -TrustAnySSLCertificate:$true -LightMode:$true"
what results are returned?
Make sure the agent on the Client Access Server has Local System as the
Default Action Account, if it is using a different account that might be the
source of the error.
Check the Application Event log on the Client Access Server, and make sure
there are no errors or warnings indicating a problem with the Client Access
Server itself.
--
Steven Halsey [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi,
SCOM frequently reports errors when running test-cmdlets on Exchange Mailbox
server which is in a cluster node: "An error occurred when running the
Test-IMAPConnectivity diagnostic cmdlet." Also, this error is shown for other
diagnostic cmdlets like Test-OWAConnectivity (both External and Internal),
Test-Mailflow.
I have also checked the mailbox nodes by opening to Operations Manager
Console, and going to the monitoring pane and open discovered
inventory.
Also
Set the Target Type as "Microsoft Exchange 2007 Mailbox Servers
Installation".
What i could see here is my Physical virtual cluster node showing as
"NotMonitored"
Also under Administration pane - "Agent Managed" i could see by both
physical Mailbox servers node as monitored and healthy.
But my virtual mailbox node is showing under "Agentless Managed" as healthy.
Is this is right ?
Can anyone help?
Regards
Prabhulingam

Steven Halsey [MSFT]

2009-04-07 16:29:43 UTC

Permalink

In Operations Manager Console, go to Administration Pane, and find the Run
As Configuration Profiles.
Look for the Default Action Account in the profiles, and right click and
select properties. Go to the Run As Accounts Page, find the Client Access
Server in the list and check the account is listed as Local System Action
Account.
--
Steven Halsey [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi Steven,
I had run the command on the Client Access server and i got the following
result.
CasServer MailboxServer Scenario Result
Latency(MS) Error
--------- ------------- --------
------ ----------- -----
XXXXXX Test IMAP4 Connectivity Success
49.88
(My webmail server)
May i know how to check the agent local system account ?
I have checked the Application event log, there are errors related to MS
forefront security only.

Post by Prabhulingam
Hi Steven,
Thank you for the reply.
As you guided i looked into the discovered inventory wherein i could
able
to
see only the Exchange Client Access servers with the STATE as Not Monitored.
I have already run the Exchange command for creating the test mailbox.
I am typing the exact error with Event id which i am facing so that you can
have some idea.
Event Id: 500
Description: Could not find any available Domain Controller.
Event Id: 400
Description: Exchange diagnostic cmdlet invocation succeeded.
Let me know if require more details...

Post by Steven Halsey [MSFT]
SCOM shouldn't be running commandlets like test-imapconnectivity and
test-owaConnectivity on the Mailbox Server, as these workflows should target
the Client Access Server.
If you go into Discovered Inventory in the Console and change the Target
Type to "Microsoft Exchange 2007 Client Access Servers Installation" does
you mailbox server appear in this list or only your Exchange Client Access
servers?
If your mailbox is appearing please let me know as this shouldn't be
happening and implies something in your environment is causing an
error
in
the discovery, and I would like to understand what it is.
Are you getting alerts about a problem connecting to the Mailbox Server
instead? Have you run the commandlet to create the Test Accounts on the
Mailbox server? Run the following commands in Exchange Management
Shell
to
create the test mailbox "get-mailboxserver [Your Virtual Mailbox Server
Name] | new-TestCasConnectivityUser.ps1".
Your agent management of the physical nodes (passive, active) and the
Exchange Mailbox Virtual Server seems to be correct.
--
Steven Halsey [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi,
SCOM frequently reports errors when running test-cmdlets on Exchange Mailbox
server which is in a cluster node: "An error occurred when running the
Test-IMAPConnectivity diagnostic cmdlet." Also, this error is shown
for
other
diagnostic cmdlets like Test-OWAConnectivity (both External and Internal),
Test-Mailflow.
I have also checked the mailbox nodes by opening to Operations Manager
Console, and going to the monitoring pane and open discovered
inventory.
Also
Set the Target Type as "Microsoft Exchange 2007 Mailbox Servers
Installation".
What i could see here is my Physical virtual cluster node showing as
"NotMonitored"
Also under Administration pane - "Agent Managed" i could see by both
physical Mailbox servers node as monitored and healthy.
But my virtual mailbox node is showing under "Agentless Managed" as healthy.
Is this is right ?
Can anyone help?
Regards
Prabhulingam

Prabhulingam

2009-05-12 07:31:01 UTC

Permalink

Hi Steve,

I had checked the Action Account for CAS server. It is in Local System
Action account only.

But still then i could not able to see the graph for "Test-OWAconnectivity
External" or "Test-OWAConnectivity Internal". Also i coulnot able to view the
Exchange reports based on it.
Need your guidance.

Post by Steven Halsey [MSFT]
In Operations Manager Console, go to Administration Pane, and find the Run
As Configuration Profiles.
Look for the Default Action Account in the profiles, and right click and
select properties. Go to the Run As Accounts Page, find the Client Access
Server in the list and check the account is listed as Local System Action
Account.
--
Steven Halsey [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi Steven,
Thank you for the reply.
As you guided i looked into the discovered inventory wherein i could
able
to
see only the Exchange Client Access servers with the STATE as Not Monitored.
I have already run the Exchange command for creating the test mailbox.
I am typing the exact error with Event id which i am facing so that you can
have some idea.
Event Id: 500
Description: Could not find any available Domain Controller.
Event Id: 400
Description: Exchange diagnostic cmdlet invocation succeeded.
Let me know if require more details...

Post by Steven Halsey [MSFT]
SCOM shouldn't be running commandlets like test-imapconnectivity and
test-owaConnectivity on the Mailbox Server, as these workflows should target
the Client Access Server.
If you go into Discovered Inventory in the Console and change the Target
Type to "Microsoft Exchange 2007 Client Access Servers Installation" does
you mailbox server appear in this list or only your Exchange Client Access
servers?
If your mailbox is appearing please let me know as this shouldn't be
happening and implies something in your environment is causing an
error
in
the discovery, and I would like to understand what it is.
Are you getting alerts about a problem connecting to the Mailbox Server
instead? Have you run the commandlet to create the Test Accounts on the
Mailbox server? Run the following commands in Exchange Management
Shell
to
create the test mailbox "get-mailboxserver [Your Virtual Mailbox Server
Name] | new-TestCasConnectivityUser.ps1".
Your agent management of the physical nodes (passive, active) and the
Exchange Mailbox Virtual Server seems to be correct.
--
Steven Halsey [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi,
SCOM frequently reports errors when running test-cmdlets on Exchange
Mailbox
server which is in a cluster node: "An error occurred when running the
Test-IMAPConnectivity diagnostic cmdlet." Also, this error is shown
for
other
diagnostic cmdlets like Test-OWAConnectivity (both External and Internal),
Test-Mailflow.
I have also checked the mailbox nodes by opening to Operations Manager
Console, and going to the monitoring pane and open discovered
inventory.
Also
Set the Target Type as "Microsoft Exchange 2007 Mailbox Servers
Installation".
What i could see here is my Physical virtual cluster node showing as
"NotMonitored"
Also under Administration pane - "Agent Managed" i could see by both
physical Mailbox servers node as monitored and healthy.
But my virtual mailbox node is showing under "Agentless Managed" as
healthy.
Is this is right ?
Can anyone help?
Regards
Prabhulingam

Steven Halsey [MSFT]

2009-05-12 16:36:33 UTC

Permalink

Are you still getting errors when the Operations Manager Agent attempts to
run the Client Access Synthetic Transactions like test-OwaConnectivity?
--
Steven Halsey [MSFT]

This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi Steve,
I had checked the Action Account for CAS server. It is in Local System
Action account only.
But still then i could not able to see the graph for "Test-OWAconnectivity
External" or "Test-OWAConnectivity Internal". Also i coulnot able to view the
Exchange reports based on it.
Need your guidance.

Post by Prabhulingam
Hi Steven,
I had run the command on the Client Access server and i got the following
result.
CasServer MailboxServer Scenario
Result
Latency(MS) Error
--------- ------------- --------
------ ----------- -----
XXXXXX Test IMAP4 Connectivity Success
49.88
(My webmail server)
May i know how to check the agent local system account ?
I have checked the Application event log, there are errors related to MS
forefront security only.

Post by Steven Halsey [MSFT]
The 400 event just indicates the commandlet ran successfully, not that the
synthetic transaction was successful.
The 500 event inidcates a definite problem. If on the Client Access Server
you open Exchange Management Shell and run the command manually
"Test-ImapConnectivity -ConnectionType:2 -TrustAnySSLCertificate:$true
-LightMode:$true"
what results are returned?
Make sure the agent on the Client Access Server has Local System as the
Default Action Account, if it is using a different account that might
be
the
source of the error.
Check the Application Event log on the Client Access Server, and make sure
there are no errors or warnings indicating a problem with the Client Access
Server itself.
--
Steven Halsey [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi Steven,
Thank you for the reply.
As you guided i looked into the discovered inventory wherein i could
able
to
see only the Exchange Client Access servers with the STATE as Not Monitored.
I have already run the Exchange command for creating the test mailbox.
I am typing the exact error with Event id which i am facing so that
you
can
have some idea.
Event Id: 500
Description: Could not find any available Domain Controller.
Event Id: 400
Description: Exchange diagnostic cmdlet invocation succeeded.
Let me know if require more details...

Post by Steven Halsey [MSFT]
SCOM shouldn't be running commandlets like test-imapconnectivity and
test-owaConnectivity on the Mailbox Server, as these workflows
should
target
the Client Access Server.
If you go into Discovered Inventory in the Console and change the Target
Type to "Microsoft Exchange 2007 Client Access Servers
Installation"
does
you mailbox server appear in this list or only your Exchange Client Access
servers?
If your mailbox is appearing please let me know as this shouldn't be
happening and implies something in your environment is causing an
error
in
the discovery, and I would like to understand what it is.
Are you getting alerts about a problem connecting to the Mailbox Server
instead? Have you run the commandlet to create the Test Accounts
on
the
Mailbox server? Run the following commands in Exchange Management
Shell
to
create the test mailbox "get-mailboxserver [Your Virtual Mailbox Server
Name] | new-TestCasConnectivityUser.ps1".
Your agent management of the physical nodes (passive, active) and the
Exchange Mailbox Virtual Server seems to be correct.
--
Steven Halsey [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi,
SCOM frequently reports errors when running test-cmdlets on Exchange
Mailbox
server which is in a cluster node: "An error occurred when
running
the
Test-IMAPConnectivity diagnostic cmdlet." Also, this error is shown
for
other
diagnostic cmdlets like Test-OWAConnectivity (both External and
Internal),
Test-Mailflow.
I have also checked the mailbox nodes by opening to Operations Manager
Console, and going to the monitoring pane and open discovered
inventory.
Also
Set the Target Type as "Microsoft Exchange 2007 Mailbox Servers
Installation".
What i could see here is my Physical virtual cluster node showing as
"NotMonitored"
Also under Administration pane - "Agent Managed" i could see by both
physical Mailbox servers node as monitored and healthy.
But my virtual mailbox node is showing under "Agentless Managed" as
healthy.
Is this is right ?
Can anyone help?
Regards
Prabhulingam

Prabhulingam

2009-05-14 07:12:06 UTC

Permalink

Yeah Steven, i am still facing the problem.
I also looked into Test-OWAConnectivity events occuring, by which also i
couldnt understand whats happening.
In the events i could see the Success and Error log alternatively ( 1
success and 1 error).

Success:
Event number - 400
Description - Exchange diagnostic cmdlet invocation succeeded

Error:
Event number - 500
Description: Could not find any available domain controller

Post by Steven Halsey [MSFT]
Are you still getting errors when the Operations Manager Agent attempts to
run the Client Access Synthetic Transactions like test-OwaConnectivity?
--
Steven Halsey [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi Steven,
I had run the command on the Client Access server and i got the following
result.
CasServer MailboxServer Scenario
Result
Latency(MS) Error
--------- ------------- --------
------ ----------- -----
XXXXXX Test IMAP4 Connectivity Success
49.88
(My webmail server)
May i know how to check the agent local system account ?
I have checked the Application event log, there are errors related to MS
forefront security only.

Post by Steven Halsey [MSFT]
The 400 event just indicates the commandlet ran successfully, not that the
synthetic transaction was successful.
The 500 event inidcates a definite problem. If on the Client Access Server
you open Exchange Management Shell and run the command manually
"Test-ImapConnectivity -ConnectionType:2 -TrustAnySSLCertificate:$true
-LightMode:$true"
what results are returned?
Make sure the agent on the Client Access Server has Local System as the
Default Action Account, if it is using a different account that might
be
the
source of the error.
Check the Application Event log on the Client Access Server, and make sure
there are no errors or warnings indicating a problem with the Client Access
Server itself.
--
Steven Halsey [MSFT]
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi Steven,
Thank you for the reply.
As you guided i looked into the discovered inventory wherein i could
able
to
see only the Exchange Client Access servers with the STATE as Not
Monitored.
I have already run the Exchange command for creating the test mailbox.
I am typing the exact error with Event id which i am facing so that
you
can
have some idea.
Event Id: 500
Description: Could not find any available Domain Controller.
Event Id: 400
Description: Exchange diagnostic cmdlet invocation succeeded.
Let me know if require more details...

Post by Steven Halsey [MSFT]
SCOM shouldn't be running commandlets like test-imapconnectivity and
test-owaConnectivity on the Mailbox Server, as these workflows
should
target
the Client Access Server.
If you go into Discovered Inventory in the Console and change the Target
Type to "Microsoft Exchange 2007 Client Access Servers
Installation"
does
you mailbox server appear in this list or only your Exchange Client
Access
servers?
If your mailbox is appearing please let me know as this shouldn't be
happening and implies something in your environment is causing an
error
in
the discovery, and I would like to understand what it is.
Are you getting alerts about a problem connecting to the Mailbox Server
instead? Have you run the commandlet to create the Test Accounts
on
the
Mailbox server? Run the following commands in Exchange Management
Shell
to
create the test mailbox "get-mailboxserver [Your Virtual Mailbox Server
Name] | new-TestCasConnectivityUser.ps1".
Your agent management of the physical nodes (passive, active) and the
Exchange Mailbox Virtual Server seems to be correct.
--
Steven Halsey [MSFT]
This posting is provided "AS IS" with no warranties, and confers no
rights.
Use of included samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm

Post by Prabhulingam
Hi,
SCOM frequently reports errors when running test-cmdlets on Exchange
Mailbox
server which is in a cluster node: "An error occurred when
running
the
Test-IMAPConnectivity diagnostic cmdlet." Also, this error is shown
for
other
diagnostic cmdlets like Test-OWAConnectivity (both External and
Internal),
Test-Mailflow.
I have also checked the mailbox nodes by opening to Operations
Manager
Console, and going to the monitoring pane and open discovered
inventory.
Also
Set the Target Type as "Microsoft Exchange 2007 Mailbox Servers
Installation".
What i could see here is my Physical virtual cluster node showing as
"NotMonitored"
Also under Administration pane - "Agent Managed" i could see by both
physical Mailbox servers node as monitored and healthy.
But my virtual mailbox node is showing under "Agentless Managed" as
healthy.
Is this is right ?
Can anyone help?
Regards
Prabhulingam