I have a problem in my SQL SERVER 2000 ,
the server is so slow when i made any query
and recently i couldn't link with other SQL servers.
The message is "the server doesn't exists or access is denied".
In spite of that the linked servers were working well and i can access them remotely & the service pack is SP4...
Well, based on the meagre information... check the network status if everything is slow full duplex, cable OK etc
Or another random guess, old server or very old install or buy new stuff (based on running SQL Server 2000)
Related
I have a virtual desktop which is hosting a SQL Server 2014 32 bit intance named "MyRemoteServer". The server has been set up with a linked server named "mscribe" using VFPOLEDB which is the OLEDB for FOXPro.
When I am logged directly into the virtual desktop I am able to query the linked server in SSMS by connecting with either Windows Authentication or a SQL Account. However when I access the server using SSMS from my laptop, the SQL Account is able to query the linked server without a problem, but when using Windows Authentication the same query returns an error. I have also tried formatting this as an openquery however I get the same error. What confuses me further about this is that I have another linked server (this one is a remote SQL Server) setup on MyRemoteServer and when I connect from my laptop using Windows Authentication I have no problems querying it.
Query:
Select o.ordernr from mscribe...[order] o where o.ordernr = 'O12345'
Error:
Msg 7303, Level 16, State 1, Line 1 Cannot initialize the data source object of OLE DB provider "VFPOLEDB" for linked server "mscribe".
With this error and the fact that I can query the other linked server my first assumption would be that the issue is with the setup of the linked server, however since the same query works when executed using the SQL Account I must assume that this is not the issue. My next assumption would be a permissions issue, however the Windows Authentication works when I am logged directly into the Server so I am not sure that this is the issue either.
Any help or suggestions are very much appreciated.
Thank You
Scenario: ISS 8.5 is on our work machines, our Microsoft SQL Server is currently down for an indeterminate amount of time, and we don't have a back-up. We can continue to develop code on localhost. Because SQL Server is down, we can't execute any data transactions. Are there any reliable resources online to, at least, test if the developed SQL syntax is correct?
Edit: I will go ahead and eat my words. I had presumed that we were not allowed to install SQL Server Express locally. That was a bad guess. After I had sent our boss the suggestion from marc_s, he gave us the go-ahead. Now we have a back-up plan. For the record, the SQL Server is now online.
You must have access to another SQL server in order to test code against a SQL server. Your only options are to install SQL server on local machines, install SQL server on a local networked computer, or use a SQL server installed at a third party host.
SQL Server 2008 R2 runs on Windows Server 2008 R2 in a domain and using the same
domain accounts (Windows authentication) to allow the connection between the client PCs and the SQL Server, created and ODBC source(System DSN named Renta_Equipos) which connects to the database and and the solution. Example: BD <---- DSN <---- WinForm Solution.
The Connection String is an Application.Settings:
Name: ConnectionString_RentaEquipos
Type: (Connection string)
Scope: Application
Value: DSN=Renta_Equipos
Now this is, normally the users log in without problems, but sometimes the connections gets closed for them (not all at the same time, 1-2 of 6 users experiment this) and the only way they can connect again is restarting the client's PC, it happens randomly.
Error it gaves me:
ERROR [08001] [Microsoft][ODBC SQL Server Driver][DBNETLIB] the SQL
server does not exist or access has been denied. ERROR
[01000][Microsoft][ODBC SQL Server Driver][DBNETLIB]Connection Open
(Connect())
I cannot find the problem, I know nothing about configuring an SQL server nor a professional programmer (all I know is from the Internet, books and some little help from other people), so I'm guessing it might be the server, but I can't get it, everything seems to be perfect (for me)
Here is a link for the Github source code: https://github.com/DarkLS/RentaEquipos.git
The error: http://i.stack.imgur.com/O20ls.jpg
Are all 6 of your client PCs desktops? If so, do the 1-2 users whom are having issues use a wired and/or wireless connection (some of the newer desktop towers have wireless capabilities)?
If it's going as far as denying access, you might be hitting your SQL user license cap (hard to say for sure)... Might want to review your SQL Server 2008 R2 environment with your IT guys.
EDIT: Check this site
I use a Microsoft Access 2010 front end with linked tables on an SQL Server 2012 installation. Local network.
When Access Starts, a VBA script runs which connects to the SQL server and performs some checks.
I recently upgraded from SQL Server 2008 to 2012, that's when the connection between client and Server started to fail intermittently.
When the connection between my client and the server fails, I see a generic message "SQL Server does not exist or access denied". This is covered in a Microsoft support article http://support.microsoft.com/kb/328306. The potential causes detailed in that article do not match the trouble I am encountering.
This connection issue is intermittent. The trouble arises about 3 times a week and lasts for about 30 minutes at a time. Between these 30 minute failures, the the system works perfectly.
My Current VBA Connection String: (have tried several, trouble persists with all of them):
Dim conn As ADODB.Connection
Set conn = New ADODB.Connection
conn.Open "Provider=SQLOLEDB;Server=Server3.companydomain.local;Database=My_Database;Trusted_Connection=Yes"
I hope that I can find something in the SQL Server Logs (which I do have access to) but I do not know which Log file to investigate.
I do not have a direct answer to your question, but I believe you could start by exploring the IP and ports on which the SQL server is listening to...Is is possible that the machine using DHCP to assign IP for the DB server as well? In this case I guess it could happen when the IPs are refreshed.
We had a similar issue where multiple IPs were getting assigned on the same machine (having multiple NIC connected) which created such intermittent disruptions.
Well it's been 7 months. Here is the solution for this problem (in my case):
My secondary DNS Server was an external Server. It could not look up my database (192.168.x.x) because this is an internal address.
When My application called the Primary DNS Server to look up the SQL Server address, it worked fine. When my primary DNS was busy, and the application failed over to secondary DNS- the request would time out. There are many reasons someone may see this error. That is the reason I was seeing it.
It's a little strange, but I've found I get this error when I don't have proper "CLOSE DB CONNECTION" type code on my site. And then when too many users hit the site, I start getting this error.
Solution: Do a hard Close of DB connections, after every db call. Yes, most DB Connectors have cleanup routines, but it's not enough under heavy load.
Also, implement a high DB connection limit in the web.config
I installed Microsoft SQL Server 2005 Express edition on my Vista Ultimate computer. However, when it opens I enter my computer name / SQLEXPRESS. When I click the Connect button, it gives me an error message.
Under the configuration tools I cannot find the SQL Server Surface Area Configuration. It only has SQL Server Error and Usage Reporting.
The error message I receive when I click the Connect button is:
A network related or instance specific error occurred while establsihing a connection to SQL server. The server was not found or was not accessible. Verify that the instance name is correct and that the SQL server is confugured to allow remote connection (provider: Named Pipes Provider, error 40- Could not open a connection to SQL Server) (Microsoft SQL Server : error 67)
From your question, as you'd written, it appears the slash is incorrect. Try:
.\SQLEXPRESS
Also ensure that your SQL Server services are started. Run services.msc and find SQL Server(SQLExpress).
Another thing to check for is the account that the SQL Express service is running under. I think it defaults to network service, but I typically run it under Local System (or if you're feeling ambitious, make a service account for it). This has taken care of a handful of permission issues I've had with SQL Express in the past.