|
|
Posted by Ted on 08/22/06 20:50
Erland Sommarskog wrote:
> Ted (r.ted.byers@rogers.com) writes:
> > Specifying my UID/pwd along with the workstation's name (parameters -U,
> > -P, and -H) as arguments for SQLCMD, I get the following error message:
> >
> > Msg 18452, Level 14, State 1, Server TEDSNEWACER, Line 1
> > Login failed for user 'TByers'. The user is not associated with a
> > trusted SQL Server connection.
>
> That means that the server is not configured for SQL authentication.
>
Thanks. I finally found the part of SQL Server Management Studio where
I can change this. It wasn't where I'd expected it to be, but I found
it and changed it, and now all problems on my LAN have been resolved.
AND all my scripts (both SQL and Perl) run on my client's server as
they do on mine.
There are two, probably related, differences between my notebook
computer and my colleagues' notebooks. 1) They are using SQL Server
Express 2005 and I am using the developer's edition of SQL Server 2005.
2) I can connect to my server using SQLCMD without specifying any
command line arguments while they must specify the server machine and
instance (i.e. SQLCMD -S my_machine\an_instance). Probably related to
this, if I edit my perl script to provide the additional parameters
they have to submit, connection fails while the very same commandline
submitted on the commandline instead of through Perl works. i.e.
Submitting SQLCMD -S my_machine\an_instance on the commandline works
but connection fails if it is submitted from within a perl script.
Thanks again
Ted
Navigation:
[Reply to this message]
|