I get the same error if I send a bad userid/password combo.

Most of the time SQL Server is set up to use your NT logon as your userid/password. Try sending the command with the userid and password values blank. That way SQL Server will default to your NT logon (assuming that SQL Server was set up that way).

Good luck and let us know what happens...

Pat