Hi!I haven’t have any error while developing CMG, certificates, features linked, etc. But when I try to test with Connection Analyzer, I allways get this errors: 1. Configuration edition of the CMG provider can be 3. Failed to get CMG service metadata.
For more information, see SmsAdminUI. log. In SMSAdminUI. log I see thiis entry: :System. Net. WebExceptionrnThe remote server lower back an error: 403 Forbidden.
rn at System. Net. HttpWebRequest. GetResponse 2. Failed to refresh MP area.
Selected client certificates is not depended on by the CMG service. Check if certificate chain for the customer certificates is unique to upload to the CMG provider and check revocation check surroundings. We are running into a controversy on our environment 90k+ buyers over 5 primary sites where after 4 8 days the MPs we now have put in the CMG connectors on are getting in a “disconnected” state. Sometimes we are looking to restart them as the RDC connection dies and we can no longer login. This appears to be as the TCP/IP ports are exhausted indicators are observed by TCP/IP 4231/4227 errors in the system event log. I’ve logged this with MS who have recommended updating to 1810.
Just reporting here in case anyone else has identical issues. Am also seeing an inconsistency with the the max variety of concurrent connections and number of actual consumers. One of our sites has about 25k shoppers, even though the console is reporting 120k+ concurrent connections!ERROR: Failed to construct Http connection 8adcf040 5723 4055 8597 0e17d43e21fd with server CMG. CLOUDAPP. NET:443. Exception: System.
Net. WebException: The remote server again an error: 990 BGB Session Ended. at System. Net. HttpWebRequest.
GetResponse at Microsoft. ConfigurationManager. CloudConnection. ProxyConnector. HttpConnection. SendBoolean isProxyData, Byteand payload at Microsoft.
ConfigurationManager. CloudConnection. ProxyConnector. ConnectionBase. Start at Microsoft.
ConfigurationManager. CloudConnection. ProxyConnector. ConnectionManager. MaintainConnectionsIn any event, I think I’ve got it working. I had set the relationship point up on a new mp and after digging via more logs I found that bgbisapi.
msi couldn’t get installed as a result of BITS was not installed when the mp was put in I thought that was computerized but I guess it isn’t. I enabled BITS then restarted the location element manger and after that the lacking components were installed. From there the bad responses in CMG CLOUD PROXYCONNECTOR. log cleared up and were replaced with “ResponseHeader: HTTP/1. 1 200 OK” and “ResponseHeader: HTTP/1. 1 280 BGB Session Continued”.
The connection analyzer also reviews fulfillment so I think I’m good.