Are you sure you updated to 16.x ? Or you updated from 16.x to v17/v100/majorversionless ?

My apologies, you're correct. I upgraded from 16.x to the latest version(less) build. Was going through a bunch of tech docs trying to find a solution and had 15 and 16 on my brain. Thanks for helping me clarify.

Hello, When you go to  http://<yourhostname>/interface/convert-status  this page should tell you, why the domain is failing to load. If you could copy and paste the errors here, we can try to diagnose it. Otherwise your best bet may be to submit a support ticket.

That's very odd, since we don't technically have a version "0" for that file. Not sure how it would've been set like that. Glad to hear you fixed it. You can use that same page at anytime to verify that your domains are at least being loaded correctly by visiting that page. If there are no other domains showing Errors or Warnings you should be fine.

Also side note, tickets are now free as long as you have an active license. If you had unused support tickets, contact sales and they can work with you on getting reimbursed for those. You can read more about that and all our other changes on our Blog post, https://www.smartertools.com/blog/2018/11/1-new-smartertools

This same think just happened to me on 8 of my 38 domains. Same resolution worked as above: changed settings:json , file_version from 0 to 1

Was affected by the same, this helped, thanks!

This resolved the issue of the domains failing to load.  But now I none of my domains are receiving email..

Ted, look in your proc folder to see if you have a bunch of received emails sitting in there. If so, then you probably were using Declude, which isnt supported in this version yet. You will need to disable Declude manually in the smartertools/smartermail/service/settings/settings.json file. search for "declude_enabled": true and just set that to "declude_enabled": false then restart the smartermail service. You will need to move any email in the proc folder to a spooler folder to get them delivered.

Thanks David,  I was running declude.  Looking at the settings.json file declude was set to false.  Although I do have a bunch of emails sitting in the proc folder.

Do I just simply move them to the SubSpool folder?  I also have 9 different SubSpool folders. 

Thanks!

Yes, I simply moved all my files in the proc folder to my SubSpool0 folder and watched the count go down on the admin panel.

Just chiming in because I had this issue today when I upgraded a server from 15x to 17x. The problem for me was that the customer had some old, leftover domain folders in his Domains directory that never were deleted when he removed the domains from the SM admin interface a while back. Also, for some strange reason, the old, invalid domains were added to the settings.json file during the migration. I had to manually remove the old folders from the Domains directory and manually remove the domain entries from the domains.json file. Once I did that and restarted the SM service, all was well.