Last seen: Mar 25, 2026
Hello, Input string was not in a correct format is an odd error, it almost gives the idea that one or more components do not match the same version...
Hello, I'm afraid there's not yet a time frame on that (mainly due to many internal changes within management etc, we currently do not provide time...
Hello, I don't think there's currently a way to work around this just yet. We are currently working on reducing the massive bug list (and had lo...
Hello, I must say i haven't tried it, but it seems odd how SolidCP can affect that, or is there a new webdeployment version released which has diff...
Hello, Unfortunatly SolidCP doesn't have any feature for this yet. I do remember Mailenable has a global feature for it too on the smtp settings...
You can update directly to 1.2.0
Hello, 2008 and 2012 R2 with Exchange 2010 means you most likely ran into the asp.net 4.5 bug with Exchange 2010. The only 2 workarounds for tha...
Hello, Unfortunately SolidCP doesn't really help much with this issue as it's mostly Remote Domain configurations. A bit of information in regar...
-1 error is generally ad related (which also means creating a new mailbox won't work). Soap errors shown indicate the SolidCP Server is either not up...
Just to be sure: Update to wsp 2.0 using (just the database) Update to scp 1.2.0 (latest) For the actual files you will need to: Delete all WSP ...
Hello, the error indicates there's still some spaces under the reseller. Due to that it can't be converted into a normal user. All spaces / existin...
Hello, Do you get any error or something when you want to update? Or it just doesn't do anything when you try to save it? Regards, Marco
Hello, The first bit: Backup MX is still OK if your mail server isn't redundant, aslong as it's not an open relay etc. Backup DNS (Secondary DNS) is...
Hello, If your coming from 1.2.1 you will first need to update your database to wsp 2.0 I have uploaded the WSP Manual update package here: Once t...
The issue above indicates you most likely aren't using a HTTPS url, or Windows Integrated auth isn't enabled properly on your powershell url. (in the ...