Hi Techguy,
You will not upgrade SM from de 100? We are working only in the last version, but since the API is the same since SM100 it should work.
ST is a little bit messy with the API and is always changing methods, but should work with the last (8629+). We stop change the 100 DLL to not affect the v. 100 users and create a new one.
Maybe we not resolve all the problems of the 100 DLL. In our environment the DLL do well all account operations but had problems with the alias/groups.
Did you try my last upload?
Regards,
SR
This will work with Build 8747 and newer. As of today it works with Build 8839. You can try it with older versions 86xx, it might work.
the costs of upgrading the 2 servers for what they are being used for, does not warrant the cost they are enterprise servers and as they are they are doing fine as far as services to customers goes. we would never recover the costs back. Its sad, but our exchange rate is 1:20 so its costly to upgrade all the time..
ok i been through all of these dlls and the issue remains the same,
1) If I use the original one from smartermail it creates mail accounts, changes passwords etc, just fine. However it cant import in detached domains and accounts and it bitches about the groups issue.
2) If i goto the patches that were made (I cant even give version names as they all have the same 1.4.9.0 145 in the file description.) But the first one in the original chat. I can then import in domains accounts, etc fine, but if you create an account it doesn't create the account. and if i try to edit the account i get this error.
Stack Trace: | System.Web.Services.Protocols.SoapException: System.Web.Services.Protocols.SoapException: Server was unable to process request. ---> Could not get mailbox ---> One or more errors occurred. ---> Unexpected character encountered while parsing value: <. Path '', line 0, position 0. at System.Web.Services.Protocols.SoapHttpClientProtocol.ReadResponse(SoapClientMessage message, WebResponse response, Stream responseStream, Boolean asyncCall) |
I tried the one after that one and it gave the same issues. I am just a bit worried of changing all these dlls etc and patching the sql db and then to try revert back if it doesnt work is going to be a mission.
I just don't understand what is the difference between the original file and the second on as to why some stuff works and others don't on both the dlls. The provider for version 12 server is running 100% fine no issues, its just this dam 100 version ones that are having the problems.
for now, I created a batch file to switch between the 2 versions, its not that we import in a lot of detached domains, its just a PITA that it doesnt work anymore as it did work fine before moving to 1.4.9