While trying to create mailbox this error appears.
Exchange management tools powershell connects without a problem.
Exchange 2013 with solidCPServer has access to internet for revocation checks.
solidCPPortal + SolidCPEnterpise server also has access to internet.
at ECP panel I've changed internal url from http to https://mail.internal.fqdn/powershell and checked Integrated Windows Authentication
Error creating mailbox. See audit log for more details.
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'CREATE_MAILBOX' task on 'test user' EXCHANGE ---> System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Connecting to remote server mail.internal.fqdn.local failed with the following error message : The server certificate on the destination computer (mail.internal.fqdn.local:443) has the following errors: The SSL certificate could not be checked for revocation. The server used to check for revocation might be unreachable. For more information, see the about_Remote_Troubleshooting Help topic. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) at System.Web.Services.Protocols.SoapHttpClientProtocol.Invoke(String methodName, Object[] parameters) at SolidCP.Providers.Exchange.ExchangeServer.CreateMailEnableUser(String upn, String organizationId, String organizationDistinguishedName, String securityGroup, String organizationDomain, ExchangeAccountType accountType, String mailboxDatabase, String offlineAddressBook, String addressBookPolicy, String accountName, Boolean enablePOP, Boolean enableIMAP, Boolean enableOWA, Boolean enableMAPI, Boolean enableActiveSync, Int64 issueWarningKB, Int64 prohibitSendKB, Int64 prohibitSendReceiveKB, Int32 keepDeletedItemsDays, Int32 maxRecipients, Int32 maxSendMessageSizeKB, Int32 maxReceiveMessageSizeKB, Boolean hideFromAddressBook, Boolean isConsumer, Boolean enabledLitigationHold, Int64 recoverabelItemsSpace, Int64 recoverabelItemsWarning) at SolidCP.EnterpriseServer.ExchangeServerController.CreateMailbox(Int32 itemId, Int32 accountId, ExchangeAccountType accountType, String accountName, String displayName, String name, String domain, String password, Boolean sendSetupInstructions, String setupInstructionMailAddress, Int32 mailboxPlanId, Int32 archivedPlanId, String subscriberNumber, Boolean EnableArchiving) --- End of inner exception stack trace --- at SolidCP.EnterpriseServer.ExchangeServerController.CreateMailbox(Int32 itemId, Int32 accountId, ExchangeAccountType accountType, String accountName, String displayName, String name, String domain, String password, Boolean sendSetupInstructions, String setupInstructionMailAddress, Int32 mailboxPlanId, Int32 archivedPlanId, String subscriberNumber, Boolean EnableArchiving) at SolidCP.EnterpriseServer.esExchangeServer.CreateMailbox(Int32 itemId, Int32 accountId, ExchangeAccountType accountType, String accountName, String displayName, String name, String domain, String password, Boolean sendSetupInstructions, String setupInstructionMailAddress, Int32 mailboxPlanId, Int32 archivedPlanId, String subscriberNumber, Boolean EnableArchiving) --- End of inner exception stack trace ---
Hello,
Revocation check failed is the Certificates section in Exchange.
Can you verify that if you go to Servers --> Certificates you see the certificates with a Valid status? (following the error one should have some other status).
If all are valid now, and you verified the correct valid certificate has the services enabled (iis etc) --> it might be worth to try an iisreset or a reboot (sometimes it caches the failed check which only resolves it self by a reboot or iisreset).
Regards,
Marco
Thanks Marco,
Yes it was the case.
In EMC -> Servers -> Certificates -> I had "Revocation check failure" status.
With this status everything works pretty well, even Exchange Management Tools also works without a problem cause it skips "revocation checks".
I fixed status to "Valid" with winhttp proxy settings -> now SolidCP works without this problem.
