Sqlcmd With Trusted Connection And IP Address Or Fully Qualified Hostname
Nov 9, 2006
The command sqlcmd seems to fail when using trusted connection and an IP address or a fully qualified hostname. For example:
sqlcmd -E -S nnn.nnn.nnn.nnn
where nnn.nnn.nnn.nnn is the real IP address of the machine, or
sqlcmd -E -S hostname.domain.com
where hostname.domain.com is the fully qualified hostname of the machine, gives the error:
Msg 18452, Level 14, State 1, Server 380GX280B05, Line 1
Login failed for user ''. The user is not associated with a trusted SQL Server c
onnection.
On the other hand, sqlcmd -E -S 127.0.0.1 works, and so does sqlcmd -E -S hostname, or sqlcmd -E -S tcp:hostname,1433.
This is on a clean machine, with SQL Server 2005 freshly installed
as Administrator with mixed authentication, and the test runned also by
Administrator.
The command sqlcmd seems to fail when using trusted connection and an IP address or a fully qualified hostname. For example:
sqlcmd -E -S nnn.nnn.nnn.nnn
where nnn.nnn.nnn.nnn is the real IP address of the machine, or
sqlcmd -E -S hostname.domain.com
where hostname.domain.com is the fully qualified hostname of the machine, gives the error:
Msg 18452, Level 14, State 1, Server 380GX280B05, Line 1 Login failed for user ''. The user is not associated with a trusted SQL Server c onnection.
On the other hand, sqlcmd -E -S 127.0.0.1 works, and so does sqlcmd -E -S hostname, or sqlcmd -E -S tcp:hostname,1433.
This is on a clean machine, with SQL Server 2005 freshly installed as Administrator with mixed authentication, and the test runned also by Administrator.
I need to create flat file connection managers. The connection Manager editor forces me to use fully qualified file names. Is there a possibility to use unqualified file names, because I need to reference to files in different directories with the identical file strcture.
I have a database that has been upgraded from SQL 200 to 2005. The database was owned by 'Joe' and all objects were also owned by 'Joe'. In SQL 2000 when Joe logged in he could simply issue 'select * from table' and would get results.
The upgraded db now has a user Joe and a schema Joe. All objects now belong to the schema Joe. Joe the user has his default schema set to Joe and he is the owner of the schema. When Joe logs in and tries to 'select * from table' he gets an invalid object. He can 'select * from joe.table'.
How can I set it up so that the objects are still owned by the schema Joe and a simple 'select * from table' works when user Joe logs in? I was convinced that is he owned the schema and this was his default schema it should work.
Why am im i getting this error I am trying to join four table from different databases.select INBTable.InBound_Calls, OUTTable.OutBound_Calls, INBTable.Line_Number as INLine_Number, OUTTable.Line_Number as OUTLine_Number, INBTable.Hold_Time as INHold_Time,OUTTable.Hold_Time as OUTHold_Time, INBAbandonInfo.INAbandon_Calls as INBAbandon_Calls, OUTAbandonInfo.OutAbandon_Calls as OUTAbandon_Callsfrom sql2.XMWin_Test.dbo.temp_Report20070807IN as INBTable JOIN sql2.Juniper_I.dbo.temp_Report20070807OUT as OUTTableon INBTable.Line_Number = OUTTable.Line_Number sql2.XMWin_Test.dbo.temp_GraphIN_INAbandon as INBAbandonInfoJOIN sql2.Juniper_I.dbo.temp_GraphIN_OutAbandon.Line_Number as OUTAbandonInfo on INBAbandonInfo.Line_Number = OUTAbandonInfo.Line_Number My Error Message: Msg 170, Level 15, State 1, Line 8 Line 8: Incorrect syntax near 'sql2'.
Are there any perfmonace or query optimization limitations or issues that arise when issueing a fully qualified query across multiple databases on the same Instance of SQL Server. In other words are all features of query optimization fully supported in queries that span databases on the same Instance.
I wihsh to discuss whether to use fully qualified names:[database].[schema].objectof objects to operate (create, query..) on is good or not?If someone change order of sql code blocks in my script - this may causelose of it's context (like: use master / use <mydb>..). I wish to have mysript independed on changes like this and always produce correct result.Does using full name make use of 'use <db>' statement unnecessary?
Our team has a DBA governing body that refuses to accept any T-SQL script that our dev group writes where fully qualified names of the objects aren't used. These non fully named objects in scripts just aren't accepted in their world.
So, all the scripts the developers now have to write must have fully qualified names in them. Of course, the Query analyser in Managment Studio could care less about object names as long as ambiguity is not found. So, I need some sort of Static Code analysis of these scripts that my team creates in order to hand them over to our DBA's to run.
The DBA's intend to make this inspection a manual process (they have time to kill I guess)... but my team doesn't have that luxury. It is not easy to ensure all scripts have this qualification in them with some many of them being written.
Does anyone know of any algorithim, tool, or options that could help me detect the presence of non-fully qualified names in T-SQL scripts?
I had been trying to solve this error with no success :
One or more of the server network addresses lacks a fully qualified domain name (FQDN). Specify the FQDN for each server, and click Start Mirroring again.
The syntax for a fully-qualified TCP address is: TCP://<computer_name>.<domain_segment>[.<domain_segment>]:<port>
I had installed three instances on my local machine to test Data base mirroring :
Principal : running SQL Developer Instance
Mirror : running SQL Developer Instance .
Witness : Running SQL Express.
Database mirroring already enabled using startup flag : -T1400
i even tried to configure it with out a witness but still have the same error .
I used the follwoing server name in the mirroring wizard(not localhost) :
Hello all - this has now happened to me on a few occasions (different installs, different sites, etc.), but my client PCs cannot access Report Manager by the server's hostname (even though I can ping by hostname from the client).
For instance, if I try:
http://ovenserver/reports
I get the infamous "Internet Explorer cannot display the webpage" message.
If I try:
http://10.0.0.20/reports
The Report Manager loads properly without a hitch.
I know I am missing something simple here - can anyone help?
When using the MS SQL 2005 JDBC driver, I now need to have the DNS nameresolution to the client correctly set up. If not I get the followingerror:SQLState: 08S01SQLError: 0Message: hostname : hostnameWhere "hostname" is the client host name. It doesn't seem to matter ifIuse an IP address or hostname in my connection URL. When searching thenet,I have seen a similar error, but not exactly the same, where themessage is"Hostname: hostname not found" (once again, here "hostname" is theclientmachine) where they suggested the issue was the DNS name conflict.I found the error goes away if the client machine's hostname match theDNSname used for the same IP addess that the DB server is using. Onework-around is to set hostname on the client to the IP address beingused.I know the right thing to do is set the hostname and the DNS namelookup thesame, but I have a customer who doesn't want to do this. They didn'thave tofor 2003, and they don't want to for 2005. Sigh. Is there a way todisablethis feature?
I currently have the following connection string set up in Excel to connect to my SQL db:
Provider=SQLOLEDB.1;Persist Security Info=True;User ID=XXXXXX;Initial Catalog=YYYYY;Data Source=SQL;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=PROJMNT1;Use Encryption for Data=False;Tag with column collation when possible=False
What I would like to do is replace the Workstation ID (which apparently is hard coded?) so that the user's workstation name pulls (%COMPUTERNAME%) so that I can see who is connecting, using what, for how long etc etc.
All -- Please help. I have some questions about connection strings.
BACKGROUND...
Note that I am using the "SQL Native Client OLE DB Provider", SQL Sever 2005 Express, ASP.NET, C#.NET, and VS.NET 2005. Note that I do not want to use the "Attach a database file" type of connection string. Note that I am using the site http://www.ConnectionStrings.com as a reference. Note that this "Standard security" connection string...<add name="LocalSqlServer" connectionString="Server=MYTESTOFFICESERVERS;Database=MyDatabase;Uid=MyDatabaseUser;Pwd=MyDatabasePassword;" />...does not work and causes the following run-time error...A connection was successfully established with the server, but then an error occurred during the login process. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.) Note that this "Trusted connection" connection string...<add name="LocalSqlServer" connectionString="Server=MYTESTOFFICESERVERS;Database=MyDatabase;Trusted_Connection=yes;" />...works but is less-than ideal because it uses a Trusted Connection rather than a Username/Password combination.
QUESTIONS... (A) What exactly does the error in Item 4 mean? (B) Do 4 and 5 imply that one must use a Trusted_Connection for all SQL Server 2005 Express connection strings when the database does not reside in the web application's App_Data folder or use a "Attach a database file" type of connection string? (C) Are there any alternatives? (D) What do you suggest?
We are using the Windows Task Scheduler as a substitute for the SQL Server Agent, which isn't available in the Express edition. The scheduled task just calls a batch file, which in turn, runs a stored procedure using osql with the -E option for a Trusted Connection.
SQL Server Express has been installed using the defaults, which means the service is running in the "NT AUTHORITYNETWORK SERVICE" account. The scheduled task we create is set to run using the "NT AUTHORITYSYSTEM" account.
Now we find that on Windows Vista (tested using Ultimate Edition) that the scheduled task fails to run the stored procedure until the machine is rebooted the first time after installing SQL Server Express. When I say "fail", I mean that the stored procedure isn't executed. The scheduled task however completes and reports no errors. On Windows XP, we do not run into this problem so I suspect it has something to do with the UAC in Vista?
We further found that after installing SQL Server Express and creating the scheduled task in the "NT AUTHORITYNETWORK SERVICE" account, the scheduled task (and stored procedure) runs fine WITHOUT requiring a reboot.
Can anyone explain why a reboot is needed to get SQL Server Express to run the scheduled task correctly under Windows Vista and the SYSTEM account?
When using jdbc with IntegratedSecurity, I run into this problem when the machine is not part of a domain & gets its IP address via dhcp. Is this expected behavior or a bug in the jdbc driver.
The SQLServer and client application are installed on the same machine and a local admin is logged in, running the client app.
If I change one of the two parameters mentioned above, the connection can be established leading me to believe this may be intentional for security issues. Am I correct?
I have a Web application in asp.net 1.1Iam using windows authentication. The application is on IIS on MachineA. When i try to access this from MachineB as http://MachineA/test/test.aspx, it gives me the error "login failed for user 'null' : not associated with a trusted sql connection"Both MachineA and MachineB are on the same domain & iam not using any sql authentication. Could someone suggest me where i might have gone wrong. Web.config has authentication as 'windows', allow users = "*" and Identity impersonation = trueOn IIS, the vitual directory of 'test' application has Directory secuirty set to 'Integrated Security'Please let me know if someone had dealt with similar scenario. Thanks.
I have just installed MSSQL 2000 on Windows 2000. what I am finding is that I cannot open an isql (or query analyzer) session using the sql login (i am successful when i use NT authentication). The error message I get is as follows
Msg 18452, Level 14, State 1: Login failed for user 'xxx'. Reason: Not associated with a trusted SQL Server connection. DB-Library: Login incorrect.
MSDN talks about setting the registry entries differently, but that seems to be only for SQL 7.
Can anyone please tell me how to create a trusted connection?. I am from Unix world and NT is still kind of new to me. Let say my SQL server is located in this machine residing in domain X and I want a NT user, ABC, who is in domain Y to have acess to my server. What do I need to do?. Many thanks.
What does it mean when a users is connected but it is a "non-trusted connection". This is showing up in the log file after my users connect. How does this effect the system/user? We have been experiencing speed issues and I was wondering if this might be a possible source of the problem.
Hi-Is it possible to do a trusted connection for a web server not onthe same physical machine. By this I mean can I make a remoteconnection from a web server to a sql server using a trusted connection.If so, how?Thanks,Dave
I'm trying to get a utility to run, and it's insisting on a user or trusted connection. I'm using SQL Server 2000 running locally. I've tried every login name, default, user I can think of but it rejects all of them.
I have an application we use here at work that I wanted to bring home to work from my house. At work I can get the application to connect to the SQL Server without problems. At home I get:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
I am connected to the office using a VPN connection. I have permissions to access the database (I am the server admin). It only happens when I connect thru VPN. I have tried it on 2 other systems here in the house to insure its not just my computer.
At the moment the application will only work with a trusted connection or Windows Authentication. It will not work with SQL authentication.
Hello, I appologize if this is in the wrong spot, but it seemed like the appropriate place. We have IIS installed on one box and SQL on another. We use a trusted connection to connect. When we try an connect to our DB, we don't get an error, the page just refreshes. From what i have gathered, it looks like we are not being authenticated. We have the ASPNET domain user on both boxes and its configured with the correct permissions, but we still can't connect. Do i need to set up or give permissions to another account i dont know about, or is there some file that needs access?
Hi folks, when i try to connect to my sql express sever through Sql sever authentication I keep getting an error that says "Login failed for user 'username'. The user is not associated with a trusted SQL Server connection. " I know the password is right.. how do i overcome this??
Hello All, I know this issue has been dealt with every where in the universe. but none seem to solve my problem. I need help desperatelyThe Web Application is a Classic ASP/Sql Server 2000 using two computers in the same physical network:Computer-A is the Sql Server2000 running Windows XP Professional.Inside Sql Server2000 i created a login, AA, as a dbowner of a database called XXX. Inside XXX, AA is right there as a user. i configured the SqlServer to accept mixed (Windows and Sql) logins.I restarted the computer and i logged into sqlserver successfully as AA. Everything is fine here.
Computer-B is the Web Server running IIS in Windows XP Professional.Here, I successfully created a System ODBC i named EEEE to connect to XXX using the AA login. Everything is fine up to this point.But, to my greatest surprise when i use - conn.Open("DSN=EEEE;UID=AA;PWD=AApassword;") in a classic ASP page, it returns this very famous error.
Hi All, My Webserver and SQL Server are of different machines.I have connected my website with sql server database. I published that website in IIS. I can able to browse that in local machine. But, if I try to browse from some other machine its giving me error saying "NOT ASSOCIATED WITH TRUSTED SQL SERVER CONNECTION". MY Connection string is this: connectionString="Data Source=BOOKSQL;Initial Catalog=CustomerDb;Trusted_Connection=True;" I also tried with connectionString="Data Source=BOOKSQL;Initial Catalog=HeCustomerDb;Integrated Security=SSPI;" How can I overcome this problem. Please help me! I need ur immediate response.
I am trying to use a trusted connect to connect to a DB. Currently I use this code:
WindowsPrincipal wp = (WindowsPrincipal)HttpContext.Current.User; WindowsIdentity id = (WindowsIdentity)wp.Identity;
// impersonate user to connect to DB WindowsImpersonationContext impersonatedUser = id.Impersonate(); try { connection = new SqlConnection("Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=DBname;Data Source=server;Packet Size=4096;"); dataAdapter = new SqlDataAdapter("select query"); data = new DataSet(); connection.Open(); dataAdapter.Fill(data); connection.Close(); } finally { // restore our old security context impersonatedUser.Undo(); }
I am testing the app with my user which has full access to the server and database I am trying to connect to. But I always get this error:
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.
Now I'm new to this and not sure if I am going about it correctly, so any help would be appreciated. I just want it to use the ID of the person viewing the page to login to the server.
Login failed for user 'ASPNET'. Reason: Not associated with a trusted SQL Server connection. -~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~-~
Hi, Iam getting the following error when trying to connect to a database on the remote server using asp.net web form "Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection." can anybody tell me what could be the exact reason for this. Regards Adonis
