Hi.
If I setup SolidCP in an AD where the Exchange AD Schema has not been extended, disabling a user will fail with a long web exception. We've traced it back to the AD Schema not being extended with the Exchange AD Schema and it's trying to set hideAddressBook to true as part of the disable process.
Since the Exchange module is not enabled for the Hosted Organization, this should not happen. I assume this is a bug in the 1.4 implementation of SolidCP.
Hello,
Would you be able to share your results for the how it was traced and to what command inside of SolidCP Server?
Kind Regards,
Trevor Robinson
Here is the error I get when I try to disable a user:
System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> System.Exception: Error executing 'UPDATE_USER_GENERAL' task on 'Test User' ORGANIZATION ---> System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> The specified directory service attribute or value does not exist. 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.EnterpriseServer.OrganizationController.SetUserGeneralSettings(Int32 itemId, Int32 accountId, String displayName, String password, Boolean hideAddressBook, Boolean disabled, Boolean locked, String firstName, String initials, String lastName, String address, String city, String state, String zip, String country, String jobTitle, String company, String department, String office, String managerAccountName, String businessPhone, String fax, String homePhone, String mobilePhone, String pager, String webPage, String notes, String externalEmail, String subscriberNumber, Int32 levelId, Boolean isVIP, Boolean userMustChangePassword) --- End of inner exception stack trace --- at SolidCP.EnterpriseServer.OrganizationController.SetUserGeneralSettings(Int32 itemId, Int32 accountId, String displayName, String password, Boolean hideAddressBook, Boolean disabled, Boolean locked, String firstName, String initials, String lastName, String address, String city, String state, String zip, String country, String jobTitle, String company, String department, String office, String managerAccountName, String businessPhone, String fax, String homePhone, String mobilePhone, String pager, String webPage, String notes, String externalEmail, String subscriberNumber, Int32 levelId, Boolean isVIP, Boolean userMustChangePassword) --- End of inner exception stack trace ---
Hi,
I also face with the same issue.
I wonder if there is any workaround?
Do you have 1.4.0 or 1.4.1 installed?
As i do believe there has been a fix in this regard since 1.4.1
