Trying to upgrade a 6.5 to a 2K.
Running SQL Agent from an admin account, admin account active as admin on both 6.5 machine and 2K machine, but I can not get the upgrade past the second screen, where I get the error message:
Unable to connect to export server, please verify that you are an NT Administrator on that machine.
Stefanie
I would like to setup the membership and role in web administrator tool, however, under Security section, I got the error message of "Unable to connect to SQL database".
I tried to run aspnet_regsql.exe to edit the config(C:WINDOWSMicrosoft.NETFrameworkv2.0.50727>aspnet_regsql.exe), however, it still shows this error message.
I am using web developer 2008 and SQL Server 2005.
Please advice me how to tackle this problem.
Thank you.
Hi all,
This is weird situation for me as i can access my database server from 32- bit processor and its working fine but when i try to connect through 64 bit processor it throws the following error : Please help. I am using enterprise library january 2006 to access database.
An Error has occured while stablishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow Remote Connections . (provider : Named Pipes provider,error: 40 - Could not open a connection to SQL Server)
Any clue or help will be appreciated.
All,
I was wondering if anyone could tell me why I could not connect to my server with the DAC when the server CPU utilization for all CPU's was greater than 90%.
BACKGROUND: I have successfully established DAC connections to this server in other periods when the CPU utilization was not pinned so high. I have done so by RDP'ing into the server, opening SSMS and cancelling the request to connect Object Explorer. Finally, I start a new query adding the "Admin" prefix to my server.
As I mentioned, when the server has CPU resource available, this works fine. This indicates that all the groundwork to setting up and using the DAC is laid correctly (i.e. DAC is enabled, I am connected locally, I am logged in with a user role with proper permissions, etc.).
This leads to my question. Why can I not connect to SQL Server 2005 Standard Edition using the DAC when all the (8-way) CPU utilization is at 90% or higher?
I need to make this connection to analyze why the server is so busy.
Any help will be greatly appreciated!!
Thanks,
Tom
I have an interesting problem. I am running xp pro and when I try to connect to an instance of SQL2005 running on WIN2003 using SQL Sevrer Management Studio, I get the following error:
An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that under the default settings SQL Server does not allow remote connections. (provider: TCP Provider, error: 0 - A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed because connected host has failed to respond.) (.Net SqlClient Data Provider)
This instance is protected by a vpn and is running on a clustered environment. I can connect to other SQL2000 servers that are running on a clustered environment and SQL2005 that is not clustered.
After adding a host file entry, I was able to connect to the server using OSQL. I was able to telnet into the port the server is listening on.
Others in my group can connect to the server using SQL Server Management Studio with no problems. They are running Win2003 Server. I originally could connect to this server, but I needed to change my password. After that I lost my remote connectivity. I can RDP into the server and map drives to the server. I map to a local administrator of this machine.
I am not sure what else to try?
Help.
I want to connect to company's SQL Server from home and to connect to home's SQL server from company remotely.
The new released SQL Server Web Data Administrator by Microsoft seems solving my issue.
I use it to connect to different SQL servers in different domains company wide successfully, but I failed to connect to home from company( I have static IP on the home server).
Also I want to know how to configure the sever name if I want to connect to company's SQL Server from home. The company SQL server is inside the firewall with a internal IP. How it works?
Any ideas?
Thanks!
I'm trying to installed SQL 2000 on a NT 4.0 Platform locally.
When I followed the wizard and specified the name of the server which is my machine name. I received the following message : "SQL Server does not exist or access denied. Connection open Connect()".
Any Suggestions!
Thanks in advance,
Vic
Hello, I know this has been covered many times but I just can't get an answer that applies to my situation. - SQL Server is on different machine.- I need to connect to SQL Server with SQL authentication. (Not a Windows account)- I CAN connect through Server Explorer as the user specified by the database administrator. - I CAN run stored procedures through the Query Analyzer as the user specified by the database administrator. - I CANNOT connect by the browsing ASP.NET applicationI have tried the connection string in the Web.Config and at the page level but keep getting messages such as Login failed for user 'User' or sometimes "Not associated with a trusted Connection"In Web.Config I have:<authentication mode="None" />
On the page I have:Dim strConn As String = "database=servername;initial catalog=databasename;user id=User;password=password"Dim conn As New SqlConnection(strConn)conn.Open()I always get an error at conn.Open()I have spent too many hours playing around with this - any suggestions?? Please!!By telling it to connect as User the ASPNET account does not have to be created in SQL Server correct?Thanks for any help!!
With SQL Server 7, I could connect to a "local" server
driver={SQL Server};server={Local};uid=sa;pwd=password;
with SQL Server 2K it seems to need the computer name
driver={SQL Server};server=MachineNameInstanceName;uid=sa;pwd =password;
How can I replace "MachineNameInstanceName" by "{Local}"
Hi All,I have been struggling with this problem for quite some time. Basicallyi have an asp page (on the ISP server) that I want to connect to a sqlserver on another machine (on my server) and I have been trying tofigure out how to do this. I tried to connect using an ip address inthe data source and it did not work. The asp.net code looks somethinglike this:Conn.Open ("Provider=SQLOLEDB;Password=xxxx;Persist SecurityInfo=True;User ID=xxxx;Initial Catalog=mssqlxxx;DataSource=xx.xxx.xxx.xxx,1433;Network Library=dbmssocn")That did not work. Gave me an access denied or sql server does notexist error. I tried playing around with or without the 1433 port,still no luck.Is there something I need to set up on sql server in order for me toconnect to this?? Can someone give me some suggestion how i can connectto another computer?My ISP offers sql server support and they give me an ip address toconnect directly to the sql server, code looks something like this:conMyData = New SqlConnection( "Server=xxxxxxxxx.registeredsite.com;UID=userxxxxxx; PWD=xxxxxx;Database=samplecom" )now, my question is, how do I set up my sql server to have an ipaddress so i can connect??so i see 2 possible w ays to do this but i have no clue to make thiswork. Any help is appreciated.
View 1 Replies View RelatedHi Friends
I
have a sql server (2005 standard edition) on Win xp machine. i can
connect to this server from my machine ok but others on the network try
to connect i get following error
"An error has occurred during report processing.
Cannot create a connection to data source 'dataSource1'.
A
connection was successfully established with the server, but then an
error occurred during the pre-login handshake. When connecting to SQL
Server 2005, this failure may be caused by the fact that under the
default settings SQL Server does not allow remote connections.
(provider: Named Pipes Provider, error: 0 - No process is on the other
end of the pipe.) "
but my remote connection allows remote
connects. i also enabled "Named pipes" and "VIA" protocols under sql
configuration manager but no avail.
any ideas on this one.
Thanks for your help.
Cheers
Hi,
I am hoping you will be of assistance to me and provide a little advice on what exactly is possible using SQL Express / SQL Server 2005 with regards to remotely connecting to a server.
I am a final year undergraduate student studying computing sciences in the UK. As a final year project I am attempting to create a client-server database, where the client (a WM5 PDA) can connect to an SQL server hosted on a different machine (a PC). However, I must be able to connect to the server when the PDA is being used on any Wi-Fi connection.
Basically I want the PDA to be able to connect to a database kept on the PC at home when you're out and about using the PDA's wi-fi.
Is this possible? If so, could you explain in 'dummy' terminology how one would go about this?
As my university is part of the MS Academic Alliance I have access to VS 2005 and SQL Server 2005 for this project.
Many thanks for your time and I eagerly await your responses!
Simon
Hi all
I m a new member to this forum. Im a hardware engineer who rectify aome software related issues. Now our employees having problem with connecting their XP prof based clients to 2003 server from SQL query analyzer. I tried refresh sql server manager in server and tried restarting the server machine many times. sometimes it the client machine connects and disconnects immediately. i aslo tried changing the poll interval , but no use.
waiting for a speedy solutin... i know this is as easy query.
Hi,
I am trying to connect to a SQL server on a deferent machine using ASP.Net written in C#. The machine on which the SQL server reside dose not have the ASPNET user and the authentication is falling. Any ideas on how to connect using a different User. I changed the ASP.Net service on my machine to run as a deferent user MyUser, which is a domain user that have access to the server machine?
Note: We can not change the privileges on the server side.
Thanks.RH
I have tried this several times and each time get the same result. I even installed Visual Studio 2008 beta 2 - everything but SQL Server Express installed fine. The error I get when running the SQL Server 2005 Express download is (from the log file):
Doing Action: Do_sqlScript
PerfTime Start: Do_sqlScript : Mon Nov 12 22:31:11 2007
Service MSSQL$SQLEXPRESS with parameters '-m SqlSetup -Q -qSQL_Latin1_General_CP1_CI_AS -T4022 -T3659 -T3610 -T4010' is being started at Mon Nov 12 22:31:11 2007
SQL service MSSQL$SQLEXPRESS started successfully waiting for SQL service to accept client connections
Service MSSQL$SQLEXPRESS started at Mon Nov 12 22:31:18 2007
SQL_ERROR (-1) in OdbcConnection::connect
sqlstate=IM003, level=-1, state=-1, native_error=160, msg=Specified driver could not be loaded due to system error 193 (SQL Native Client).
Error Code: 0x800700a0 (160)
Windows Error Text: One or more arguments are not correct.
Source File Name: libodbc_connection.cpp
Compiler Timestamp: Wed Jun 14 16:28:15 2006
Function Name: OdbcConnection::connect@connect
Source Line Number: 148
Error 29515. SQL Server Setup could not connect to the database service for server configuration. The error was: Specified driver could not be loaded due to system error 193 (SQL Native Client). Refer to server error logs and setup logs for more information. For details on how to view setup logs, see "How to View Setup Log Files" in SQL Server Books Online.
I have no idea what the error is or how to fix it; I've enountered a number of postings related to install errors but none match exactly.
I do have the full log. Thanks in advance for any/all help!
Mary
When you connect to SQL Server using SQLConnection, how to set client machine name(or IP address) so that you can monitor the process on Server side using Enterprise Manager?
View 2 Replies View RelatedI know there have been many posts made on this subject; however, despite the resources available, I have not been able to get this to work! I've spent time working on this here and there over the last couple of months only resulting in frustration. I am finally posting to solicit help for my situation to figure out what is wrong with my SQL Server or firewall configuration.
Two machines connected to a router, one wireless, one wired. Both have SQL Server Express and the Management Studio tools installed. From either machine I can connect to its local SQL Server Express instance.
I have enabled Shared Memory, Named Pipes, TCP/IP, and VIA in the SQL Server Configuration Manager. (BTW what is VIA?)
I have added sqlsrvr.exe and sqlbrowser.exe to my Windows Firewall exceptions. I have tried disabling Windows Firewall. One of the machines is configured as DMZ in the router configuration.
Please, someone offer up some brilliant diagnostic steps I am missing to expose what is wrong in my setup and make this work... Thank you!
The error states:
Additional Information:
An error has occured while establishing a connection to the server. When connecting to SQL Server 2005, this failure may be caused by the fact that unthe default settings SQL Server does not allow remote connections.
How do I correct this issue?
Thanks,
Steve C.
I connected successfully in SQL Server Management studio using the 'sa' login and changed the authentication mode to Windows NT because I could not connect using my windows login but now I can't get any connection at all because 'sa' is no longer trusted.
I changed the loginmode registry setting to 2 and rebooted my PC but this has made no difference.
Can anyone help me get the 'sa' login back?
Hi Y'all,
I'm using SQL Server 2005 Standard edition on Windows 2003 Standard server.
I can connect with no problems as user 'sa' to SQL Server Management Studio.
I can also create users and databases there with no problems and I can connect to them
using SQL Server Management Studio, again, with no problem.
However,. I want to use the Web Data Administrator.
I installed it,. without a problem, and I can access it as Server/Administrator and then using 'sa' and it's corresponding password.
So where is the problem?
The problem is that when I create a different user on the server and want them to have access to the Web Data Administrator, they can pass the WindowsAuth pop up screen, but when prompted to enter the MSSQL username and password, the login doesn't pass.
In fact you only see the clock hangin, but no login process is taking place.
I'm at a lose on this!
Any pointers?
-Alon.
Can someone point me at an article that tells how to allow the
ASP.net worker process to connect, via windows authentication, to a
remote sql server instance ?
Here's the context:
Database server:
- Remote machine running SQL 2005 Standard as a named instance
- Named pipes and TCP are enabled for remote connections
- SQLBrowser service is running
- Listening on default named pipe (\servernamepipeMSSQL$instancenamesqlquery)
Client:
- Vista Business machine
- Not in same domain as server, but on the same network (via Cisco VPN)
- SQL 2005 Express is installed (for use with local databases)
- Windows Firewall enabled
- Running Symantec Antivirus, Corporate Edition
Connectivity:
- I CAN connect to SQL 2005 databases on the remote server using "nperverinstancename"
- I CAN connect to SQL 2005 databases on the remote server using Excel 2007
The problem is that I cannot successfully create an ODBC datasource using the "ODBC Data Source Administrator" application. I'm using the "SQL Server" driver and trying to create a System DSN. I'm also running the tool with elevated permissions.
- When I try to use "servernameinstancename" as the server and TCP as the connection type, I get this error:
Connection failed: SQL Server Error: 18452; "[Microsoft][ODBC SQL Server Driver][SQL Server] Login failed for user ''. The user is not associated with a trusted SQL Server connection.
- When I try to use "npervernameinstancename" as the server and Named Pipes, I get this error:
Connection failed: SQLState: '01000'; SQL Server Error: 1326; [Microsoft][ODBC SQL Server Driver][DBNETLIB]ConnectionOpen(Connect()).
Connection failed: SQLState: '08000'; SQL Server Error: 17; [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or access denied.
Help! I've really been beating my head against the wall on this one. It all works just fine with a Windows XP client machine.
I changed the login password on my computer today, and now I cannot connect to the SQL Server instance I have on that same machine. I am using Windows Authentication. I would think that, if I can log on to my computer, I would be able to connect to the database, since I have been "authenticated" by windows but, that does not appear to be the case. Can anyone offer any advice? Thanks in advance for any help you can provide.
View 4 Replies View RelatedPlease help! I am new in SQL Server 2000 Administration. My manager had ask me to manage a SQL Server, but Windows Adminstrator refuse to give me Local Admin rights. I only have sa account to login to databases. I don't know any excuses or reasons to give to Windows Adminstrator so that he can give me the local admin rights. If any one have this answer, please help. Thank you.
-JC
I upgraded my 6.5 server to 7.0 two days ago running into small problems with the database upgrade wizard. I had some small problems with security which took me some time but was not that difficult once I figured it out. I then proceeded to switch back to 6.5 mode to transfer all the data that had been done that day to my development machine so I could then import it to the SQL 7.0 version. When I was done with the transfer I switched back successfully, started the server successfully, but I was unable to connect. I get the error "Connection could not be established...", so after several attempts to connect and shuting the server down I now am at a loss. The server runs fine in 6.5 mode but it will not connect in 7.0?? Tonight I am going to try to reinstall SP1, if that does not work I am going to try to reinstall SQL 7.0. Any suggestions???
View 2 Replies View RelatedOn a fresh installation of SQL Server 6.5, I have
opened the EM and registered the server but am unable
to connect. I get the error of 'A connection could not
be established to [ServerName]- [DB-Library] Unable
to connect: SQL Server is unavailable or does not exist.
General Network Error. Check your documentation.'
I've tried connecting with all different DB-Lib settings
to no avail. Ultimately, I want to use TCP/IP. I am,
however, able to connect to other SQL Server boxes from
this EM, just not the local server. I am able to stop
and start the services from Control Panel and from SQL
Service Manager.
Since I haven't been able to log into the local SQL Server,
I've registered the server in EM to log in with sa and a
blank password. I've already completely uninstalled SQL
and reinstalled it to see if that would help. It didn't.
Does anyone have any idea what the problem could be?
Thank you!
Toni
Hi,
I am running SQL 2000 on Windows 2000 Server. The clients are running different OS ranging from Win 98/NT/2000. Although i am able to connect to the local host, but whenever i try to connect over the network the following error pops up :
unable to connect to server <server name>
Server : Msg 11, Level 16, State 1
[Microsoft][ODBC SQL Server Driver][TCP/IP Socket]General network error. Check your network documentation.
I checked up the event long on the server and found the following entry:
Event Type: Warning
Event Source: MSSQL$NETSDK
Event Category: (8)
Event ID: 19011
Date: 1/20/2003
Time: 2:12:32 PM
User: N/A
Computer: <computer name>
Description:
The description for Event ID ( 19011 ) in Source ( MSSQL$NETSDK ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. The following information is part of the event:
(SpnRegister) : Error 1355.
May i further clarify that this error started today n till last week end (saturday, i am
stationed in India) there was no problem and the users were able to connect to the server
without any problem. My network engineer feels that its an sql problem and has nothing to do with network related issues.
i would appreciate if anybody could help me out. thanking in advance
- Paramesh
recently i made my PC dual boot by installing windows 2000 advanced server. It already had win2000 profesional installed on it. since then i have been unable to connect to sql server running on some other server(called CONTROLS) on the LAN. I am able to access the CONTROLS server thru 'my networkplaces' and able to see all its hsared directories and access htem. but when i open Enterprise manager i cannot connect to CONTROLS.
Please help me . i have already wasted 2 days over it.
I am unable to connect to SQL Server using isql_w or enterprise manager. The ODBC settings register successfull and the services show as started. I have tried starting SQL server in single-user mode with minimum config to see if memory is a problem but still cannot connect. The error logs show SQL as having started successfully with no errors. Has anyone got any ideas?
View 5 Replies View RelatedFrom my Win98SE box with MDAC 2.6sp1, I can't connect to SQL (win2k, sql2k).
I've tried everything I know but nothing works.
I always get the following error:
Unable to connect to server 192.168.1.2
ODBC: Msg 0, Level 16, State 1
[Microsoft][ODBC Sql Server Driver] Timeout Expired
some additional info...
- both computers are in a workgroup, not in a domain.
- this is a home network and they're connected via a Linksys cable modem router
- another box on this same lan can connect to sql just fine, although it's
running win2k.
- all boxes have identical DSN, Subnet...settings
- I also installed Jet4.0sp1 just in case, but that didn't help either
- I'm primarily trying to connect via TCP, although I have tried Named Pipes
as well
- i can ping both boxes from each other just fine
- odbc ping fails
MDAC has worked beautifully for me for the last several years. Did MS
change something recently...or is there another problem?
Thanks, Andre
Hi,
I encounter (suddenly) the following error:
[ODBC SQL-Server Driver][Shared Memory] Unknown connection
by connecting either with the query analyzer or enterprise manager.
No connection possible anymore.
My configuration is:
Windows 2003 Server with
SQL Server 2000 SP3a Enterprise Edition with standard network configuration
One MSDE is still running on same machine and can connect.
I have checked with Compchecker, but no mismatches.
Any ideas ? It all sounds weired !
dajm
:(
Hello. I am very new to SQL Server. I've tried to look through other posts on the forum but did not find the solution I needed. Please help.
I have SQL Server running on Machine1 which I am able to connect to. What I want to do is connect to this server through a Machine2 that is on my network.
Both Machines run on WindowXP Professional
On the server of Machine1, I have:
1. Under the security tab, I have created a New Login using SQL Server Authentication (general tab), checked all server roles (server roles tab) and checked to permit all databases (in the database access tab)
2. On the server, went to properties -> security tab and allowed for SQL Server and Windows authentication
On Machine2 when I try to register the server of Machine1 through the Register SQL Server Wizard, I am able to see the server. However, when I use the newly created Login Name and password (from step 1 of above). I get a Login Failed for user message. When I try to connect to the server through Query Analyzer I also get an unable to connect to server message (Server: Msg 18456, Level 16, State1)
What else do I need to configure to make it work?
Thank you!
If you place an image of your server on a rebuilt server, rename it andchange the SID. You get an error message “UNABLE TO CONNECT” when youuse the SQL Query analyzer on a desktop computer to connect to theserver (hosting the image). If you add the server (hosting the image)to the Windows2000 server domain/active server and restart the server(hosting the image), you get the following error message: "YOUR SQLSERVER INSTALLATION IS EITHER CORRUPT OR HAS BEEN TAMPERED WITH (UNKNOWNPACKAGE ID). PLEASE RERUN SETUP."Wouldn't you think changing the name, the sid and adding it to a domainwould be enough to access it. I even created a new ODBC connection.*** Sent via Developersdex http://www.developersdex.com ***Don't just participate in USENET...get rewarded for it!
View 1 Replies View Related