I have installed SQL Server 2005 on my Domain Controller successfully
and installed the SQL Server tools from the DVD including workstation components on my XP client computer (which is actually hosting the Domain controller as virtual VMWare machine).
The authentication is set to mixed mode and I have created a login with all possible rights on SQL Server, but which is at the same time my Domain Admin (So the user is setup in SQL Server in the format Domainuser)
Now when I open any client program (SQL Srvr2005 Management console, or Toad for SQLSrvr) and try to connect, the client does find the server correctly, but I cannot login.
The error status is actually 1, which means "unexpected internal error" as far as I have read.
I have turned off Windows firwalls by default and also turned off my custom firewall to see if it makes a difference, but it doesn't.
My activated connection protocol on both the server and the client is TCP/IP and I have then changed the port on both the server and the client to a common 4665, which I then granted full passage through my firewall.
Now the error has changed and says "the target machine has actively refused the connection", with status code 0... ???
So that's my current situation... Please, can anyone help me? What am I doing wrong?
I want to give a client access to a SQL Server 7 database sitting on a different NT domain without setting up a trust relationship between the two domains. Has anyone tried doing this?
On Windows XP systems I get the following issue when trying to browse the MSDB folder in SSIS
Client unable to establish connection Encryption not supported on SQL Server. (Microsoft SQL Native Client)
I have noticed another post where several others have noticed the same issue. It appears to only occur on Windows XP installations. Is there a workaround or fix for this?
I have a quick question regarding domains and workgroups.
Currently I am working on an issue in the office of a small business. Right now there are 3 client computers that connect to a dell server running windows std. server 2003. The server has sql running on it that takes care of the invoicing system. Two out of the three work stations are able to use the database fine, but there is one that is unable to connect to the database. The only different that I could find is that the two workstations that DO work are currently set to use a workgroup, whereas the one workstation that does NOT work is set to use a domain...... I tried switching that computer to workgroup, but then I was unable to login as the normal user that I had always logged in as before.....
What can I do to solve this dilemma?
Any help would be greatly appreciated!
I apologize if this is the wrong forum for this, and if it is, if someone would point me to the correct one I would appreciate it.
Hi all,it happen to me a strange problem:i have a mdb file (in Access 2K) with SQL Server 2K linked tables whoruns on a workstation which is on a different domain that the SQLServer. It works.If i create a mdb file from a workstation which is a the domain of theSQL Server and then i run it a my non-domain workstation i have errormessage:Login failed for user '(null)'. Reason: Not associated with a trustedSQL Server connectionBut if i reattached my tables it works.If someone have an idea....PS: same ODBC on both machines
I have tried this on several different operating systems (VISTA and XP ) and several versions of SQL NATIVE CLIENT including 2005.90.3042.0
I have a 64 bit "SQL NATIVE CLIENT" connection that fails. The exact same connection and code succeeds on 32 bit. My customer and I prepend "oledb:" to the connection string and it starts working.
FAILS on 64 bit: Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Wrigley_Test;Data Source=MONGO;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RIPTIDE;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False
WORKS oledb:Provider=SQLNCLI.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=Wrigley_Test;Data Source=MONGO;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=RIPTIDE;Use Encryption for Data=False;Tag with column collation when possible=False;MARS Connection=False;DataTypeCompatibility=0;Trust Server Certificate=False
I debugged my code to the point that I know it is happening when I call CreateAccessor for my SQL statement.
i like to use my Excel pivot from other domain, but I always get the error message "Cannot find repository". I tried a ping on IP of analysis server, no problem. The connection string includes the IP adress as well. Anybody knows the clue ?
SQL Server 2005 SP2, installed as a default instance at the domain controller. SSIS connection failed with the message Failed to retrieve data for this request. (Microsoft.SqlServer.SmoEnum) The RPC server is unavailable. No firewalls, client and server in the same subnet, ping is ok. I suspect the issue is similar to described here: http://support.microsoft.com/kb/940232 I've given the user all the rights to DCOM MsDTSServer, but I cannot include him to the local "Distributed COM users" group because the domain controller doesn't have local group at all. I have included the user into the "domain admins" group, after that user got a connection. But this is not good, you know what I mean. Does any other solution exists, without reinstallation SQL Server to another server or giving the administrator's rights to the user? Thank you.
Sorry I didn't know the best forum for this question.
I have 3 SQL 2005 x64 servers on my remote domain. 10.1.10.65 is the primary 10.1.10.66 is the mirror 10.1.10.67 is the whitness.
All 3 machines run the MSSQLSERVER service as a domain admin user acount, and all of the other servies use LocalSystem. All machines are configured to use the default instance name of MSSQLSERVER.
I have another seperate server ON THAT DOMAIN which runs IIS and ASP Classic. I installed the SQL Native client on that machine.
Here is the ASP code: ----------- <% dim strConnString, objConn, rs, sql
sql = "SELECT * FROM DFW" Set objConn = CreateObject("ADODB.Connection") objConn.ConnectionString = strConnString objConn.CommandTimeout = 300 objConn.Open
SET rs = Server.CreateObject("ADODB.Recordset") rs.CursorLocation = 3 rs.Open sql, objConn
Do While Not rs.EOF Response.Write rs(0) & " " rs.MoveNext Loop
rs.close objConn.close set objConn = nothing set rs = nothing %> --------------------------------
If I run this code on the server on the SAME domain and shutdown MSSQL services on the primary machine the Failover server starts working an serving data requests.
It I then take that code and run it from another REOMTE domain, I can connect to the primary server and get data, but when I force a failover for testing it refuses to connect the the MIRROR server.
In the error log on the primary server I see 12 errors. There are 4 sets of the following 3 errors, as SQL will try to connect 4 times before failing.
1) Date 4/7/2008 12:00:39 PM Log SQL Server (Current - 4/7/2008 12:00:00 PM) Source Logon Message Login succeeded for user 'sa'. Connection: non-trusted. [CLIENT: 10.1.3.79]
Does anybody know if it is possible to establish a connection to an sql express instance only with integrated security when this express instance is running on XP which is NOT part of a domain?
I used 3 seperate web.config files - one for Development seerver, one for Certification server, and one for Production server. The only difference between these three is the within the <connectionStrings> tags. For Example: <connectionStrings><add name="strConn" connectionString="server=xxx;uid=xxxx;pwd=xxxxx;database=yyy;"/></connectionStrings> Within Development the connectionString points to the Development SQL server, Cert to cert SQL, and Prod to Prod SQL. I do not have permissions to copy new Web.Config files into Cert or Prod, so when I have a change within my web.config I have to have another group manually add these files. Is there a way to identify the domain I am curernt within and use a specific set of connections string within the web.config based off this information. If so, can anyone post an example of how to do this...
(Cross post from newsgroup) Attempting to implement Windows authentication between trusted domains. . . I have a domain trust set up between two domains connected via persistent vpn:
Hi all. I am a bit new to SQL but I have studied much info, BOL, various best practices and so on. The problem is - I cannot find any tutorial which could tell me step by step how to set SQL server on a PC and connect to it from another computer (they all are on a domain). So I decided that I am doing something wrong...
I have done the following (all is done on virtual PCs): 1.I have installed a virtual PC with windows 2003, which acts as a domain controller.
2.I installed Win2003 on a second PC and added it to the domain. Installed MS SQL Server 2005 and SP2 on it. Server uses Windows auth. and all the services are running from a dedicated domain account which I added on the first PC.
I added a domain account (let's call it USER_X) to the SQL server Security/Logins
Everything is OK locally, I can connect to the server using USER_X from the same PC.
3.I installed Win2003 on a second PC and added it to the domain. Installed MS SQL Server 2005 client componenst, SSMS and SP2 on it. Logged on as USER_X. And tried to connect to the PC number 2. And failed. SSMS gives an error (1396) Named pipes error "Could not open a connection to SQL server". But the server appears on the list if I click Server name->Browse for more->Network servers. Why I cannot connect to it if I see it? Tried to enable Windows and SQL auth, created a pure SQL user USER_Y, checked locally - ok, can connect. But cannot connect as USER_Y from the third PC.
Finally 4.I installed Win2003 on a fourth PC (did not add it to the domain). Installed MS SQL Server 2005 and SP2 on it. Server uses Windows and SQL auth. Enabled Windows and SQL auth, again created a pure SQL user USER_Y, checked locally - ok, can connect. And checked connection from the third PC - I can connect fine as SQL USER_Y to the SQL server on a PC which is not on the domain but cannot connect as SQL USER_Y to the SQL server on a PC which is on the domain!
What am I doing wrong? How to connect from a PC on a domain to another SQL server on the same domain? It is just a basic config which (I think) SQL admins have gone through many times but I am stuck.
Help, please! I hope to hear from someone who has installed SQL server on a domain and successfully created remote connections.
Hi, I have been creating a web store, which we will be hosting on our Windows Server 2003 system. I am also writing a windows application that will be running on our client systems on the same network/domain. I have no need to allow internet access to the database, just within our domain. Pretty much the windows application will be running and whenever a customer places an order, the program will automatically pop-up the needed information for our credit card processing, and shipping department. So far I have been able to establish a connection to our server by creating a data connection under the server explorer. However, it does not list any databases whatsoever, the web site has been published using Visual Studio 2005 Professional on the server, and is in 100% working order. I have searched and haven't found anything concrete on this, i'm sure its just something simple that im missing. It appears that the server is definetely connected to the database (since the website is fully functional), but it is not listing the information for other systems to access it. If anyone has any ideas, please let me know. Thank you
We recently upgraded to SQL 2005 from SQL 2000. We have most of our issues ironed out however about every 1 minute there is a message in the Application Event log and the SQL log that states:
EVENT ID 18456 Login Failed for the users DOMAIN/ACCOUNT [CLIENT: <local machine>]
This is a state 16 message which I thought meant that the account does not have access to the default database. The account is actually the account that the SQL services run under.
Any ideas? We can't seem to figure this one out. We actually upgraded to 2005 from 2000 and had an error appear after every reboot that prevented the SQL Agent from running(This application has failed to start because GAPI32.dll was not found. Re-installing the application may fix this problem.) We did a full uninstall of SQL and reinstalled fresh and restored the databases from .bak files and that is when the EVENT ID 18546 started occuring every minute.
We don't have any SQL heavy hitters here so please be detailed with any possible solutions. That you very much for any help you can provide!
Attempting ODBC connection to SQL Server by MachineNameSqlServerName doesn't work. Can only connect by using IP address of server machine with name of SQL Server instance. Any help would be appreciated. thanks
Hi ;I m trying to create Merge Replication. I was able to create thereplication on the same machine, however my aim is to use clientmachine and do all the neessary work on the client machine and thensynchronize to the server. Thus, I have installed client version of SQL2000, I connected to the database server, the thing is when I go offline I lose connection. Is there any way to create the subscription into the client machine as an off line user then synchronize it ?Or DO Ihave create my shopshot on the client machine?If someone can help me I would really appreciateRegardsAs
I have a SQL server with mixed authentication, the user 'sa' is the password zitiz configured. And attach the database server. Locally connection not informing me about errors connection, but when I try to access from the client informs me that there is no server or SQL server has been denied access to the same.
Parameters connection are in a file. Ini contains: DriverName=MSSQL HostName=ST-02SQLEXPRESS Database=MANEXKA USER_NAME=sa Password=zitiz BlobSize=-1 ErrorResourceFile= LocaleCode=0000 MSSQL TransIsolation=ReadCommited OS Authentication=True
It has windows xp sp2, framework. Net 2.0 on the server and the client and the firewall is disabled.
How to verify the client or the need to configure the server?
yo ce folks... Anyone had any trouble using a dataset for return values in a datagridview for the client app?
trying to make this work...
' Open the Connection For SQL Compact Edition
Dim cn As New SqlServerCe.SqlCeConnection("Data Source = " & Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData) & "ffgsCRM.sdf")
Dim cmdProduct As SqlServerCe.SqlCeCommand
' create dataset with table
cn.Open()
cmdProduct = cn.CreateCommand
cmdProduct.CommandText = "SELECT ProductDesc AS Description, ProductCost AS Cost, ProductListPrice AS [List Price] FROM Product"
Dim daProduct As New SqlServerCe.SqlCeDataAdapter(cmdProduct)
Dim dtProduct As New Data.DataTable("Product")
daProduct.Fill(dtProduct)
Dim ds As New DataSet
ds.Tables.Add(dtProduct)
'' FILL DATAGRIDVIEW
Me.dbGridProducts.DataSource = ds
I have this working:
' search product description
Dim reqProductSearch As String
reqProductSearch = tstxtSearchDescription.Text
' Open the Connection For SQL Compact Edition
Dim _conn = New SqlCeConnection("Data Source = " & Environment.GetFolderPath(Environment.SpecialFolder.LocalApplicationData) & "ffgsCRM.sdf")
Dim cmd As New SqlCeCommand()
cmd.Connection = _conn
cmd.CommandText = "select ProductDesc as Description, ProductCost as Cost, ProductListPrice as [List Price] from Product where ProductDesc like '%" & reqProductSearch & "%' ORDER BY ProductDesc"
_conn.Open()
Dim resultSet As SqlCeResultSet
resultSet = cmd.ExecuteResultSet(ResultSetOptions.Scrollable Or ResultSetOptions.Updatable)
Here are the error messages: Enterprise Manager: A connection could not be established to SERVERNAME - Client unable to establish connection ConnectionOpen (CreateFile())
Query Analyzer: Unable to connect to server ServerName Server Msg 67, Level 16, State 1 [Microsoft][ODBC SQL Server Driver]Client unable to establish connection
I can't register any other new servers, even ones in my workgroup. I'm connecting using named pipes, but have also tried using TCP/IP setting it up using Client Network Utility.
When i log on to another machine using my network login - I can connect.
There have been no problems connecting in the past and I haven't changed anything on my machine - any ideas???
We have a clustered server. When i create DTS packages in the secondary server I can get all the connection. But when i create DTS package that has connection to other servers. I am getting the follwing error. So my jobs that runs the DTS packages are failing.
Error Source: Microsoft OLE DB Provider for sql server
Error Description: Client Unable to establish connection. Connectionopen(createfile())
I deleted all the entries in the Client network utility and recreated with ip addresses and TCP/IP protocol.
Added all the ip addresses to Lmhosts and host files.
I cannot connect to my SQL2005 server using the old SQL ODBC drivers, I have to use the Native client drivers. The database I am trying to connect to is a SQL 2000 db I just attached. Its owner is a SQL user login, which works fine and can connect remotely.
I have a VB 2005 synchronization application that successfully pulls (through RDA) data to a SQL 2005 Mobile DB at my place of business, but when I try it at home on my SSL VPN Client connection, I get Hresult -2147012889 ("A request to send data to the computer running IIS has failed."). Typically, a -2147012889 error is a connection issue that relates to resolving the server name.
Here's a snippet:
Dim RemoteConn As String = "Provider=sqloledb; Data Source={company server};" _
& "Initial Catalog={companyDB}; User ID={username}; password={pass}"
Dim SourceURL As String = "http://{Company server name}/MobileConnection/sqlcesa30.dll"
Dim SqlRA As New System.Data.SqlServerCe.SqlCeRemoteDataAccess
SqlRA.LocalConnectionString = strConn
SqlRA.InternetUrl = SourceURL
SqlRA.InternetLogin = ""
SqlRA.InternetPassword = ""
SqlRA.CompressionLevel = 3
Try
(Perform Pulls...etc..)
When I pull the sourceURL string and plug it into IE, it works fine. I get the "SQL Server Mobile Server Agent 3.0" message indicating that I have a solid connection over to IIS. That works fine.
But I can't figure out anything in the program. I've rotated the IP address with the name resolution and neither works for me in the program. The difference though when I use the IP address for the server is that I get a slightly different Hresult of -2147012867 (which means you can't connect to the server).
Also, I have IIS configured for anonymous access, the SQL DB I'm trying to pull from isn't restricting access, and my company doesn't have a proxy I need to go through.
We have SQLSERVER 7.0 in one of the production. The clients r connected thru ODBC. The clients doesn't gets disconnected after a task result in increase in sqlserver log.
I used the selfssl.exe tool to generate a certificate on my db server, successfully added to Personal Certificates in MMC, added R/W permissions for the service account to the cert, selected the new certificate in the protocols for mssql and restarted the service. So far so good, however when trying to connect from SSMS with encryption check box checked I get the following error:
A connection was successfully established with the server, but then an error occurred during the login process. (provider: SSL Provider, error: 0 - The certificate chain was issued by an authority that is not trusted.) (Microsoft SQL Server, Error: -2146893019)
The certificate chain was issued by an authority that is not trusted.
When I look in MMC, the only intended purpose for the certificate is "Server authentication" and I'm not able to add "Client authentication". Does selfssl.exe not support client authentication?
Hi, I am not sure if I select right Froum:) It might be a basic question but could you please help me on that?
Working Environment:
I have developed application on SQL Server 2005 and now wants to Run on Client Site, I am using access as a front end and SQL server 2005 back end through ODBC (System Dsn) which is working good. (user has been added on SQL Server and on Database)
Question:
1) Do I need to create new System Dsn Or other DSN (Keep in mind I have already create System DSN in Server) at each client site to access application from Server?
(If yes then I am trying to do that, it allow me to create (with required database which is on Server) and verify but doesn’t save on ODBC list so I can’t use that name to run appliation on client site)
I'd like to do this:Have a SQL Server database hosted on a public facing web server.I want it to be held at an ISP/Web hosting company. Though I have ADSL hereI don't want to manage a server.I want some ASP pages accessing the database.I would also like for a very small number (probably 2) of users to accessthe database from a richer client. Perhaps Access/VB.I've tried using www.shanje.com, as a test. It seems to work, though thereare worries about security.I want to keep cost down!On 'normal' shared MS hosting, would it be possible to connect to the dbfrom a client like Access. The way most web hosts talk it doesn't look likeit.Is there any way of providing a richer client interface than plain webpages? I want things like autocomplete (beyond the first character) for dropdowns, keyboard shortcuts etc.This would be low volume. Essentially a private database held on theinternet.Yours, Jo
i'm experiencing an extremely slow connection from a WXPP Sp2 client to a MSSQL2000 running on a W2k server. The client is running a VB6 application that connect with Windows authentication: every form requesting data opens with a long delay at the first launch; next attempts run normally fast.
In the same LAN there are some others identical clients, all running fine.
Every other network activity from that client is ok.
The following error message was displayed in the SQL server event log when the client application attempted to connect to sql server "The Tabular Data Stream (TDS) version 0x72020002 of the client library used to open the connection is unsupported or unknown. The connection has been closed. [CLIENT: XX.XX.XX.XX]"
I can retrieve "host" name of the current connection from "sysprocesses" system table(select host from sysprocesses). But is it possible to get the IP address of the client connection instead of host?
I could not find any stored procedures or extended procedures that would let me retrieve such information.
Our 32-bit applications connect to SQL Server 32-bit through OLEDB with Shared memory as preferred protocol. Our client applications and SQL Server generally reside on same machine. We are evaluating possible impact when SQL Server 2008 64-bit is accessed with our 32-bit client applications running on 64bit WindowsServer 2008. Can shared memory protocol will be still used by underlying SQL server OLEDB dll considering the client application is 32-bit where as SQL Server is 64-bit ? Or it will switch to Named pipes or TCP/IP automatically ?
