I do think you took the wrong approach there unless you didn't tell us of further steps that would normally be required.
But by your list of steps I...

the .net version of SQL Server has nothing to do with what your code does. Unless its a CLR, and even that I think it will still allow it.

by the error you posted it seems you tried to use a format that is not possible
Create failed for Login '.\TestAccount'.
drop that .\ and it will work

in my shop I try to implement and force the use of synonyms. pitty I can't force them to do it (not being a production DBA), but do try my...

good to see possibilities 😀 and I didn't knew about it either!!!

powershell definitely an option - and possibly plenty of examples on net to do it.

this may also be an option https://blogs.msdn.microsoft.com/markm/2015/06/30/easily-backup-sql-databases-to-azure/

see if this applies https://support.microsoft.com/en-ie/help/3041857/code-0x80070057-the-parameter-is-incorrect-error-when-you-try-to-displ

use the try catch block.
after the try catch do another bulk insert this time of the error file - if any record is loaded you had errors on the...

load the file onto a table with a single column (varchar(max) - or whatever size is enough to hold a single record)
and then do parsing and validation in t-sql...

first I wonder if the syntax is correct
EXECUTE AS LOGIN='[domain]\';
possibly should be
EXECUTE AS LOGIN='[domain\user]'; -- brackets around all of the domain\user, not around both domain and user

you need to go and read the manuals in more detail - and google as there are plenty of good examples.

This is a beginners question.

... a...

gee. why did they install a 32 bit SQL version?

and you should really forget that those 2 options exist - pure evil.

If you have locking issues look into the possibility of enabling READ_COMMITTED_SNAPSHOT your database.
Depending on your...

I fail to see where the SQL Job belongs on your VBA process.
From VBA you can call the proc directly passing whatever parameters you wish.

from what you...

unless you are using a evaluation version then you won't have it.

otherwise the SQL Server license does not expire.

If you have SA this does expire if...