Mailbox creation was working before, although I haven't touched the control panel in a while, so I'm not sure if it broke after the CU22 install.
I've gone through the forum and checked the following:
PowerShell Virtual directory (internalUrl): https://ex01.mydomain.lan/PowerShell
Integrated Windows Authentication: Enabled
Basic Authentication: Disabled
SCP Server on Exchange Server: Application Pool set to AD User
AD User Perms Membership: Enterprise Admins
Organization Management
Administrators
SolidCP:
Configuration > Servers > Settings > Active Directory Settings:
Tried both "Use Local Accounts" and "Use Active Directory Accounts"
Authentication Type: None
Root Domain: mydomain.lan
Configuration > Servers > Hosted Exchange
PowerShell Url: Same as PowerShell Virtual directory (internalUrl) above
I've run iisreset and both the Exchange server and the SolidCP server, I've also restarted both of them.
On both the Exchange Server and on the SolidCP server, I can the following PowerShell and successfully connect, I've tried this with the Domain Admin account and also whilst running PowerShell.exe as the Solid CP user account used in the AppPool:
$Session = New-PSSession -ConfigurationName Microsoft.Exchange -ConnectionUri http://ex01.mydomain.lan/PowerShell/ -Authentication Kerberos Import-PSSession $Session -DisableNameChecking
No luck in the SolidCP logs on the Exchange Server either.
Any ideas, because I can't think of anything else to troubleshoot.
Hello,
Do you not have any error at all? It normally means everything is working fine if no errors are logged.
Are you running the SolidCP Server on a different server than the Exchange server? We normally recommend the Server component is ran on the exchange server directly.
Regards,
Trevor
Yes, the error would help wouldn't it, unfortunately is the generic winrm error.
The server component is running on the Exchange server itself and the enterprise and the other component I can't remember the name off is on a dedicated server.
Interestingly if I deliberately change the url on the SolidCP configuration to use HTTP instead of HTTPS, it seems to work, but actually just times out after 10 minutes, I've seen another thread with the exact same issue, including the fact that it creates a user account in AD, but no mailbox. However the fix was to change to HTTPS, which gives the error below.
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'CREATE_MAILBOX' task on 'Joe Bloggs' EXCHANGE ---> System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Connecting to remote server ex01.mydomain.lan failed with the following error message : The SSL connection cannot be established. Verify that the service on the remote host is properly configured to listen for HTTPS requests. Consult the logs and documentation for the WS-Management service running on the destination, most commonly IIS or WinRM. If the destination is the WinRM service, run the following command on the destination to analyze and configure the WinRM service: "winrm quickconfig -transport:https". 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,
Please check the bindings of the default website. Do you have it enabled for all unassigned or a specific ip? We recommend leaving it to unassigned and ensuring IPv6 is enabled.
Kind Regards,
Trevor
Unassigned and IPv6 is enabled.
