SQL Server Service Pack 3a  
Author Message
Maktub





PostPosted: Thu May 20 11:33:39 CDT 2004 Top

SQL Server >> SQL Server Service Pack 3a

Has anyone encountered a problem after they apply SQL
Server Service Pack 3a when they run an OSQL statement?
Basically I have a PERL Script that runs and checks if a
file is sent up to another system. If it has not been
sent for some reason it's moved into another directory
and the script uses an OSQL statement to call a Stored
Procedure to send out a notification e-mail saying this
process failed. Has anyone ever encountered a problem
with their OSQL statement returning an "Error Conflicting
Switches: -U and -E", Where -U = Username and -E =
Trusted Connection. This comes up when you go to a
command prompt and type in OSQL /?. Any help is greatly
appreciated. Thanks.

-Craig

SQL Server278  
 
 
Narayana





PostPosted: Thu May 20 11:33:39 CDT 2004 Top

SQL Server >> SQL Server Service Pack 3a You mean, you are specifying both -U and -E as parameters to OSQL.exe? If
so, there's nothing wrong with that. If you want trusted connection (-E)
then there's no need to specify a user name.
--
HTH,
Vyas, MVP (SQL Server)
http://vyaskn.tripod.com/
Is .NET important for a database professional?
http://vyaskn.tripod.com/poll.htm




Has anyone encountered a problem after they apply SQL
Server Service Pack 3a when they run an OSQL statement?
Basically I have a PERL Script that runs and checks if a
file is sent up to another system. If it has not been
sent for some reason it's moved into another directory
and the script uses an OSQL statement to call a Stored
Procedure to send out a notification e-mail saying this
process failed. Has anyone ever encountered a problem
with their OSQL statement returning an "Error Conflicting
Switches: -U and -E", Where -U = Username and -E =
Trusted Connection. This comes up when you go to a
command prompt and type in OSQL /?. Any help is greatly
appreciated. Thanks.

-Craig