Resolution is quite simple - use different account name, if you must use the same name for both machine and account use different account for installation and then change account name under which SQL is supposed to run later after installation.
As for me reason seems to be simple - however it is just a wild guess: Most probably if your logon name is the same computer name most probably internal code trying to login recognises account name as a computer name followed by empty name.
So CompAndAccountName is translated to CompAndAccountName\"", instead of CompAndAccountName\CompAndAccountName
Any other name entered as AccountName without domain or computer name would be interpreted as ComputerName\AccountName
Bear in mind that using the same name for both computer and account on the computer might be misleading as by default the computer name (with $ character added) is used for NETWORK SERVICE account.
Comments
As for me reason seems to be simple - however it is just a wild guess: Most probably if your logon name is the same computer name most probably internal code trying to login recognises account name as a computer name followed by empty name.
So CompAndAccountName is translated to CompAndAccountName\"", instead of
CompAndAccountName\CompAndAccountName
Any other name entered as AccountName without domain or computer name would be interpreted as ComputerName\AccountName
Bear in mind that using the same name for both computer and account on the computer might be misleading as by default the computer name (with $ character added) is used for NETWORK SERVICE account.
Regards,
Slawek
Dynamics NAV, MS SQL Server, Wherescape RED;
PRINCE2 Practitioner - License GR657010572SG
GDPR Certified Data Protection Officer - PECB License DPCDPO1025070-2018-03