Hey there Tom! I'm sorry to hear you're seeing errors on this. Typically this error means one of the JSON configuration files for the domain has become corrupted in transit. You can check the validity of those files by copying the JSONs out of that domain's root to a temporary location, then you can open each one and copy/paste it into something like jsonlint.com to make it human-readable. This will also validate the format, so you should find out pretty quick if one of these is problematic. If you need any help with this please don't hesitate to submit a ticket with us. Have a good one!

Kyle,

Thank you for the answer. I saw this answer before, that's why I did a clean install with an empty Domain folder and made a test domain. Even then I receive the error.

If you have any other suggestion, it would be welcome,

Tom

In this case I think we might need to take a look at the Domain Defaults potentially, as that should be all that is present in a newly created domain. One of your configuration files somewhere is problematic I'm betting. Aside from that, there could be permissions issues on the disk as well, is that possible? Lastly, what do you see in the error logs under Manage>Troubleshooting>View Logs?

Kyle,

I completely uninstalled Smartermail and removed all folders and the old backup from the server according to https://portal.smartertools.com/kb/a2651/completely-uninstall-smartermail.aspx

Then I did a reboot and a clean install. After I added mytestdomain.com and tried to open it, I again receive the object object error.

Since it's a clean install, it can't be a corrupted json. What else could it be then?

I had on this server Smartermail successfully running (although it was version 14) before I upgraded to version 16 and moved the domains folder. So don't think it's permissions. Can it be the asp.net version?

Sincerely,

Tom

Unfortunately it could still be a corrupt JSON, even on a brand new installation, depending on the environment. The most common cause of chronically corrupted JSON files is an antivirus that hasn't been excluded from our directories per this KB here:

So I do recommend checking this out and if possible, validating your JSONs against something like jsonlint.com. That being said, since you've uninstalled and purged the files, this would lend weight to the theory that it is not JSON related. In that case I'll need to take a closer look at the environment to get to the bottom of it for you. Can you submit a ticket on this one please?

Kyle,

I've added the 2 folders as exception in Avast.

I validated the 4 json files standing in C:\SmarterMail\Domains\mytestdomain.com and they are all fine.

In the folder C:\Program Files (x86)\SmarterTools are 133 json files. So that's allot to scan, but I found that allot of json files in the reports folder are containing errors like below:

What's the best way to correct them, I already manually corrected 10, but this seems an endless work.

Sincerely,

Tom

The JSONs found in the reports folder may not be true JSON formats, as we use a lot of these internally. So, I wouldn't worry about those too much. I would validate the JSON files contained in the domain itself, but if this is a newly created domain I would be less inclined to believe its a corruption issue. What build version is this install out of curiosity?

Thanks for your follow-up on this Tom, and sorry for the delay in getting back to you. I think you're spot on, there is definitely something amiss on that environment. Good call! Let us know if you need anything else. Have a good one!