Cannot invoke this funcion....

Question

I wrote a small script to get Mail Queue stats on all my Exch 2010 Hub Tansport servers. It works in EMS but when I configure as a Custom Command it returns an error; "Cannot invoke this function because the current host does not implement it. " Can you assist in getting this fixed?

add-pssnapin Microsoft.Exchange.Management.PowerShell.E2010
$HubServer = Get-TransportServer |sort-object -property Name
foreach ($server in $HubServer) {
get-Queue -server $server -EA inquire -SortOrder -messagecount
write-output ""
}

Answer 1

Michael,

The Get-Queue cmdlet prompts for user confirmation. Unfortunately, this is not supported by Adaxes. You will not be able to use the Get-Queue cmdlet in Custom Commands.

Comments

Do you have any recommendation for how I might achieve a similar outcome?

---

In the context of the script I posted the variable $HubServer is passed through so there is no prompt. It is not possible to replicate this or something similar with a Custom Command?

---

Hello Michael,

Sorry, we got the prompt in our environment because of the issues with our testing Exchange Servers that prevented the cmdlet from getting the necessary data. If your Exchange Servers are OK, there should be no prompt. Try the following script for your task:

add-pssnapin Microsoft.Exchange.Management.PowerShell.E2010
$HubServer = Get-TransportServer | sort-object -property Name
foreach ($server in $HubServer) 
{ 
   $queueInfos = Get-Queue -server $server -EA inquire -SortOrder -messagecount 
   foreach ($queueInfo in  $queueInfos)
   {
       $message = "Identity: " + $queueInfo.Identity + "; DeliveryType: " + $queueInfo.DeliveryType 
       $Context.LogMessage($message, "Information")
   }
}

For more information on the ExtensibleQueueInfo class object, a collection of which the Get-Queue cmdlet returns, see the description of the ExtensibleQueueInfo Class on MSDN.

---

This returns the following error"

Cannot invoke this function because the current host does not implement it. Cannot find an overload for "LogMessage" and the argument count: "0". Cannot find an overload for "LogMessage" and the argument count: "0". Cannot find an overload for "LogMessage" and the argument count: "0". Cannot find an overload for "LogMessage" and the argument count: "0". Cannot find an overload for "LogMessage" and the argument count: "0".

---

Michael,

Sorry, my fault. Didn't copy the entire thing. I've updated the script in the post above.

---

Still returning this message

Run PowerShell script 'Check Mail Delivery Queue Status' for the user

Identity: ; DeliveryType:
Identity: S1CAS1\Submission; DeliveryType: Undefined
Identity: S1CAS2\Submission; DeliveryType: Undefined
Identity: S2CAS1\Submission; DeliveryType: Undefined
Identity: S2CAS2\Submission; DeliveryType: Undefined
Cannot invoke this function because the current host does not implement it.

HEre is a copy of the script im putting in to the Poweshell Command for my Custom Command, which i copied from your post

add-pssnapin Microsoft.Exchange.Management.PowerShell.E2010
$HubServer = Get-TransportServer | sort-object -property Name
foreach ($server in $HubServer)
{
$queueInfos = Get-Queue -server $server -EA inquire -SortOrder -messagecount
foreach ($queueInfo in $queueInfos)
{
$message = "Identity: " + $queueInfo.Identity + "; DeliveryType: " + $queueInfo.DeliveryType
$Context.LogMessage($message, "Information")
}
}

---

Hello Michael,

The 'Cannot invoke this function because the current host does not implement it' error message means that the Get-Queue cmdlet nevertheless tries to write some warnings/prompts to the PowerShell console. Try to run your initial script from the PowerShell console and take look if it writes any warnings messages to the console or prompts for user imput.

Unfortunately, currently Adaxes does not support functions similar to Write-Host and prompting for user input, so, probably, it will be impossible to use the Get-Queue cmdlet with the Run a Program or PowerShell script action if you do not eliminate all warning messages and prompts.

---

I do not receive any warning/error messages or prompts when running my original script from EMS located on the Adaxes Server.
This is exactly what the output from the original scripts looks like.

[PS] C:\scripts>.\Get-MailQueue.ps1

Identity DeliveryType Status MessageCount NextHopDomain
-------- ---------------- -------- ---- -------------
S1CAS1\Submission Undefined Ready 0 Submission
S1CAS2\Submission Undefined Ready 0 Submission
S2CAS1\Submission Undefined Ready 0 Submission
S2CAS2\Submission Undefined Ready 0 Submission

---

This is the message received when attempting to run the script you provided directly from the Adaxes Powershell

PS C:\scripts> .\Get-MailQueueAD.ps1

Confirm
The queue viewer client can't process the results received from the server. The
data may be corrupted.
[Y] Yes [A] Yes to All [H] Halt Command Suspend [?] Help
(default is "Y"):

---

Hello Michael,

Try this version of the script, it works successfully in our testing environment:

$exchangeServer = "exchangeserver.domain.com" # TODO: Modify me

$session = new-pssession -connectionURI "http://$exchangeServer/powershell?serializationLevel=Full" -ConfigurationName Microsoft.Exchange
Import-PSSession -session $session

$HubServer = Get-TransportServer | sort-object -property Name
foreach ($server in $HubServer)
{
    $queueInfos = Get-Queue -server $server -EA inquire -SortOrder -messagecount
    foreach ($queueInfo in $queueInfos)
    {
       $message = "Identity: " + $queueInfo.Identity + "; DeliveryType: " + $queueInfo.DeliveryType
       $Context.LogMessage($message, "Information")
    }
}
Remove-PSSession -Session $session

---

Now recieving this error:

Run PowerShell script 'Check Mail Delivery Queue Status' for the user

Identity: ; DeliveryType:
Connecting to remote server failed with the following error message : WinRM cannot process the request. The following error occured while using Kerberos authentication: The network path was not found. Possible causes are: -The user name or password specified are invalid. -Kerberos is used when no authentication method and no user name are specified. -Kerberos accepts domain user names, but not local user names. -The Service Principal Name (SPN) for the remote computer name and port does not exist. -The client and remote computers are in different domains and there is no trust between the two domains. After checking for the above issues, try the following: -Check the Event Viewer for events related to authentication. -Change the authentication method; add the destination computer to the WinRM TrustedHosts configuration setting or use HTTPS transport. Note that computers in the TrustedHosts list might not be authenticated. -For more information about WinRM configuration, run the following command: winrm help config. For more information, see the about_Remote_Troubleshooting Help topic. <output truncated>

---

Michael,

This error means that Adaxes cannot establish a remote PowerShell session with the computer where your Exchange Server is installed. The possible errors are specified in the error message that you posted.

The most probable reason is that you specified a DNS alias for this computer in $exchangeServer. Try specifying the Fully Qualified Domain Name (FQDN) or the Flat Name of the computer where your Exchange Server is installed.

---

Inserting the FQDN seems to have worked. Thank you for your assistance!