Renaming domain name
Problem reported by Emil Babayev - November 22 at 3:21 AM
Resolved
Greetings,

We have several domains up and running on SM15, and we have trouble renaming one of them (largest one, around 2000 users) it says "Failed to rename domain"
We can rename smaller domains (around 30 users)  no problem

Here is error log:

[2018.11.22] [CurrentUser: admin@]
[2018.11.22] [22.11.2018 13:49:41]
[2018.11.22] https://domain1/UserControls/Popups/frmRenameDomain.aspx?domain=domain1
[2018.11.22]
[2018.11.22] System.Exception: Failed to move the files from 'd:\SmarterMail\Domains\domain1' to 'd:\SmarterMail\Domains\domain2\
[2018.11.22]
[2018.11.22] Server stack trace:
[2018.11.22]    at MailService.Remoting.Mail.RenameDomain(String sessionStr, String oldName, String newName)
[2018.11.22]    at System.Runtime.Remoting.Messaging.StackBuilderSink._PrivateProcessMessage(IntPtr md, Object[] args, Object server, Object[]& outArgs)
[2018.11.22]    at System.Runtime.Remoting.Messaging.StackBuilderSink.SyncProcessMessage(IMessage msg)
[2018.11.22]
[2018.11.22] Exception rethrown at [0]:
[2018.11.22]    at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
[2018.11.22]    at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
[2018.11.22]    at SmarterMail.RemoteInterface.IMail.RenameDomain(String sessionStr, String oldName, String newName)
[2018.11.22]    at SMWeb.HelperClasses.RemoteWrapper.SessionCallWithConnection(UserData usr, Action`1 f)
[2018.11.22]    at SMWeb.UserControls.Popups.frmRenameDomain.btnOK_Click(Object sender, EventArgs e)
[2018.11.22] Failed to rename the domain 'domain1' to 'domain2'

Any help will be appreciated 

And another question: is it possible to rename domain name manually just like in SM14 - renaming folder and making changes to domainlist.xml?

2 Replies

Reply to Thread
0
Paul Blank Replied
My guess is that you can still do just that with v15; stop the Windows SM service, rename the domain's folder, edit domainlist.xml, and then restart the SM service.

You can easily test this by setting up a temporary domain, populating it with a few emails (you can perhaps send from other domains on the same server to avoid also setting up Internet access) and then renaming as suggested.

You might want to check your bindings after renaming the production domain, to make sure they are all as needed; and of course check/edit your domain entries in IIS to be sure they are consistent with the SM domains.
1
Kyle Kerst Replied
Employee Post Marked As Resolution
Hello Emil, thank you for reporting this. I've tested this with a larger domain (250+ users) and did not have issues renaming the domain under the latest release of SmarterMail v15/16, so I'd like to suggest updating to the latest available minor release. Next, as Paul already noted you can certainly perform the rename process via edits to the XML files, but please make sure the SM service is stopped when you make these changes. 
Kyle Kerst
Technical Support Specialist
SmarterTools Inc.
(877) 357-6278
www.smartertools.com

Reply to Thread