Comments
Sort by recent activity
Hi @James R
You got me thinking there about the connection parameters. I usually connect using Windows auth, but I just changed it over to using a SQL login to see if that helps, and I'm now not getting the error dialog.
My AD account is [DOMAIN\firstname surname], so is it possible that having a space in my Windows login is the cause?
Although saying that, the database(s) I got that error on was on a development server. But when I connect to my local SQL instance also by Windows auth (same login), I have no issues. Just a thought.
Thanks,
Mike. / comments
Hi @James R
You got me thinking there about the connection parameters. I usually connect using Windows auth, but I just changed it over to using a SQL login to see if that helps, and I'm now not ge...
Just to add to that, I didn't change any other connection parameters - I literally changed the authentication type over from Windows to SQL and left everything else as it was. Both login types are sysadmin on the server. / comments
Just to add to that, I didn't change any other connection parameters - I literally changed the authentication type over from Windows to SQL and left everything else as it was. Both login types are ...
SQL Prompt version I'm using is 8.0.0.1241, connecting to SQL Server 2016 / comments
SQL Prompt version I'm using is 8.0.0.1241, connecting to SQL Server 2016
I'm having the exact same issue, but my error states the invalid character is in the network library. / comments
I'm having the exact same issue, but my error states the invalid character is in the network library.