SocketNameLookupError caused by quotation marks
Status: Alpha
Brought to you by:
gcc
Menu
▾
▴
#66 SocketNameLookupError caused by quotation marks
---------------------------
Boxi Error
---------------------------
Error connecting to server: Connection SocketNameLookupError (Check hostname specified.)
---------------------------
OK
---------------------------
The real error is "The Notify Script does not exist ("d:\NotifySysAdmin.cmd")". In fact, the script exists, but the quotation makes confuse boxi. This is related to bug 2869646 [1], because quotation marks are required in Box Backup for the script that have spaces in their path.
In short words: Box Backup needs quotes, Boxi does not.
Removing the quotation marks around "d:\NotifySysAdmin.cmd" eliminates the error, and Boxi can connect to the server without problems.
Clearly the error message "Error connecting to server: Connection SocketNameLookupError (Check hostname specified.)" is either wrong, or the lookup error is caused by a side-effect of the quotation marks error.
[1] <https://sourceforge.net/tracker/?func=detail&aid=2869646&group_id=135105&atid=731482>
The same is true if any of the settings (NotifyScript, DataDirectory, ...) contain an invalid value. Should this really prevent Boxi from doing for instance a restore?
In any case, the error message is very confusing and wrong, because "Error connecting to server: Connection SocketNameLookupError (Check hostname specified.)" is clearly not the problem, it is one of the other settings. Perhaps this is a copy/paste issue for the message in the error handling routine, where all errors return the same message?