While using the Citrix SCOM Management Pack for StoreFront (MPSF), you might come across an error, StoreFront Store Service Probe failed, that triggers an alert in the SCOM Console. Let’s troubleshoot and understand the possible causes and solutions for this error.
Possible reasons for this issue might be that the MPSF Probing User Account domain is not listed as a trusted domain in the requested format, or not configured in the Citrix StoreFront Management Pack Configuration tool. Also, Site Bindings (HTTP/HTTPS) might not be configured properly.
You can identify several reported issues through the Check requirements and configuration for MPSF agent task. An issue detected with the MPSF probing account is not reported on the Check requirements and configuration for MPSF agent task. Hence it requires further troubleshooting.
Let’s go through the probable reasons for this error and see how they can be resolved.
“Could not get credentials”
An alert, StoreFront Store Service Probe Failed, with description, Could not get credentials, might be triggered in the. Because the Check requirements and configuration for MPSF agent task does not report any issue, this issue must be further investigated.
Symptoms or Error
The alert with the following description appears in the SCOM Console:
StoreFront Store Service Probe Failed
Availability probe for ‘Store Service’ store service failed.
Error Description: ‘Could not get credentials’
Initial Response Time (ms): ‘6’
Login Time (ms): ‘-1’
Get Resources Time (ms): ‘-1’
Figure: Alert Screenshot
Simultaneously, on the StoreFront Server where the MPSF agent is installed, an error similar to the following is logged in the MPSF Agent log file at %ProgramData%\Citrix\StoreFront MP Agent\logs\ComTrade.MP.StoreFront.Service.log:
2017-02-06 14:00:30,924 ERROR [server-discovery] ComTrade.MP.StoreFront.Discovery.PerformStoreProbe – Could not get credentials
This error message indicates that the MPSF Probing User Account might not be configured in the Citrix StoreFront Management Pack Configuration tool. Or, the MPSF configuration (mpsf_config.dat) file might not be deployed on the StoreFront server where MPSF is installed. Or, the MPSF agent account might not have access to read the MPSF configuration file (mpsf_config.dat).
To configure the Probing User Account, follow the steps described in the product’s User Guide, section Configure a User Account for StoreFront Availability. After configuring the account, deploy the MPSF configuration on all the related StoreFront servers. Also verify that the MPSF agent service account has access to the configuration (mpsf_config.dat) file.
NOTE: After StoreFront is configured properly, the alert disappears in the next discovery cycle (five minutes).
“Token not returned, check configured credentials”
You might see an alert, StoreFront Store Service Probe Failed, with the description, Token not returned, check configured credentials, in the SCOM Console.
This alert might be triggered if the MPSF Probing User Account domain is not on the list of trusted domains in StoreFront or if Site Bindings is not configured properly with the Default Web Site in IIS.
Because the alert description does not return sufficient information and the Check requirements and Configuration for MPSF task does not return any error in the output, let’s identify the issue with additional troubleshooting.
First, check the MPSF agent log file. When the alert is triggered, an error is logged in the MPSF log file on the StoreFront server at
%ProgramData%\Citrix\StoreFront MP Agent\logs\ComTrade.MP.StoreFront.Service.log.
Search for the text string, “Incorrect domain” in the MPSF log file. If the string is present and logged during the same time period as the alert generation, the MPSF Probing User account is not listed as a trusted domain in StoreFront.
To solve this issue, verify that the configured MPSF Probing User Account domain is listed as a trusted domain in the particular StoreFront server in the StoreFront Console. To check the trusted domain setting, follow the steps below:
- Open the Citrix StoreFront Management
- Click the Authentication
- Click Configure Trusted Domains.
- If the Trusted domains only option is selected, the configured MPSF Probing User Account domain must be listed correctly as a trusted domain for the MPSF Agent to log in using the account configured for probing.
Example: If the MPSF probing account is SFAdmin and the trusted domain is mydomain.com, the Probing account in the MPSF configuration tool must be configured as SFAdmin@mydomain.com or mydomain.com\SFAdmin.
Now, perform additional troubleshooting on the MPSF agent side. Search for the following text string in the MPSF log file:
“System.IO.IOException: Unable to read data from the transport connection: An existing connection was forcibly closed by the remote host.”
If this string is present and logged during the same time period as the alert generation, Site Bindings is not configured properly.
To solve this issue, set Default Web Site > Site Bindings on the particular StoreFront server to All Unassigned. Follow the steps below to set Site Bindings:
- Open IIS Manager on the particular StoreFront server.
- Expand Sites, right-click Default Web Site, and click Edit bindings …
- In the Site Bindings window, set IP Address to All Unassigned.
NOTE: After the StoreFront server is configured properly, the alert disappears in the next discovery cycle (five minutes).