I have an Access front-end on physical box A linked to a SQL Server instance in physical box A. When I launch the FE, it automatically connects to the SQL Server database with no issue. However, when I launch the same FE from networked physical box B, I get a "login timeout expired" error. I click "OK" which opens the generic SQL Server Login dialog, I click "OK" and I'm immediately connected. Any ideas? Thanks!
Well, first up, are you using sql logons, or windows logons?
I would on that 2nd machine re-link the tables. And you VERY much want to do make the connection with what we call a FILE dsn. If you do this, then if that instance of SQL server is open and allows incoming connections, then it should work.
So re-link the tables - in fact I recommend that you delete the table links. And AS stated you MUST use a FILE dsn - not machine/user. So, you can setup this link on the dev box that has both access + SQL server - but you REALLY need to use SQL server logons - not windows based logons.
I am really tired, it's been 3 days that I can't open my SQL Server Management Studio. I got connection string error with number 87. Below screenshot show my problem:
And I use localhost\MSSQLSERVER with error 87 and Arash-PC (my machine name) with error number 2.
And I tried sqlcmd -U sa -S Arash-PC too
You need to check in your SQL Server Configuration Manager what services and instances you have installed. Go to Start Menu > All Programs > Microsoft SQL Server (version) > Configuration Tools and launch the appropriate Configuration Manager. You should see a screen something like this:
Find the SQL Server (.....) service(s), and make sure the service is started.
If you find a SQL Server (MSSQLSERVER) service started, then you have a (unnamed) default instance to which you can connect using
.
(local)
Arash-PC
You MUST NOT supply the MSSQLSERVER as the instance name!
If you find any other SQL Server (instance name) service started (e.g. SQL Server (SQLEXPRESS) in my screenshot), then the instance name (SQLEXPRESS) needs to be appended to the server name to connect to that instance:
.\SQLEXPRESS
(local)\SQLEXPRESS
Arash-PC\SQLEXPRESS
Make sure you are not running out of space on the drive where SQL is installed. Try rebooting as well.
Verify that the SQL Server (MSSQLSERVER) service is started. Click Start, click Administrative Tools, click Services, and scroll to SQL Server (MSSQLSERVER). If it is not started, right-click the service, select Properties, in Startup Type select Automatic, click Apply, click Start, and then click OK. Make sure service started. If service did not start - you need to analyze event log. Alternatively - try reinstalling/repairing SQL server.
Make sure you have no network problems - try temporary disabling any firewalls(including Windows Firewall) and antiviruses.
If service is started and firewalls disabled but still no luck - time to check SQL Server Configuration Manager settings. In detail it is described here and here. Shortly I would recommend first enable all protocols in both server and client sections. Reboot. Check it works. If that would not help - then try disabling everything apart from TCP/IP (both server and client sections). Reboot again.
If above does not help - try reinstalling SQL Server. Just make sure you have saved your databases 1st. To save them - stop sql server service, and copy your *.mdf and *.ldf (from SQL server Data folder) files to safe location. Later on you can attach them. If you are not sure where your SQL server Data folder located - just search for files with mdf extension.
Edit:
Successful telnet showing SQL server port is up looks this way:
Edit2:
Launch Event Viewer:
Click System, then Filter Current Log:
Setup filter as shown below:
Then look for SQL-related events:
Usually event text provides information why MSSQLSERVER service fails to start. If the text is unclear please google it for more details.
If your problem was the same as mine (or to anyone else whose attempting to connect to their MS SQL Server w/ a similar connection string), MSSQLSERVER is the default instance name when you set it up, if you don't provide an instance name. I omitted the MSSQLSERVER from the connection string and I was successfully able to connect.
With all respect to "Anton Kruglov" and "marc_s" , Unfortunately, my problem is not resolved . I had to change my windows and reinstall softwares . Now it works properly .
I am willing to write a connection string to allow one computer connect to another computer's sql server located in the same work group.
Anyway, searching the Internet only confused me and led me to fail tries.
So, if I am willing to connect to an sql express server to a database called "Analyze", what should my connection string look like?
Create a new text file with the extension UDL in a folder.
Right click on the file and click open with "OLE DB Core Services"
Filll in the appropriate entries and save.
Open the file in notepad - voila, your connection string is in there.
Good luck.
There is a post on MSDN explaining how to connect to SQL Server express over a network.
The main points are; you need to configure SQL Server to listen for requests. This can be done using the SQL Browser. You also need to ensure the firewall will allow requests through.
I am using SSIS within Visual Studio 2012. I am planning to use the Transfer SQL Server Objects Task in SSIS to, well, transfer (nearly) all objects (schema only) between servers. I am unfortunately stuck at the SMO Connection Manager configuration step. While in the Editor for the task, I click on Source Connection and select <New Connection ...>. I then enter the name of the server I wish to use as the source. When clicking on Test Connection, I get a Failed to Server error message. I am able to connect to the server from SSMS, and I can make a successful connection if I create a Connection Manager in SSIS. I simply cannot successfully connect when using the SMO Connection Manager within the Transfer SQL Server Object Task.
It's probably already too late, but I've realized that if you don't click on Test Connection and leave the Server Name, you can click OK, and when you hit the dropdown on SourceDatabase, the list of DBs appear.
In my case the solution was to enable TCP/IP protocol for instance (I was trying to connect to) in Sql Server Configuration Manager and in Properties of protocol on tab IP Addresses for IPAll set TCP Port to 1433.
I have just came across the same issue one hour ago in VS2012. There is a bug related to Visual Studio, which gives you this error message regardless the network connection when you add SMOServer type of connection and press Test Connection button before pressing OK button.
Therefore, what you need to do is to add SMOServer Connection, select your source and press OK without testing the connection. Then you can test the connection after making a right click and edit on the connection manager. The test works when you do in that way.
I have the following error while I connect to SQL Server 2008 Management Studio with Windows authentication.
"The request failed or the service did not respond in a timely fashion.
Consult the event log or other applicable error logs for details."
Is anybody tell me why i am getting this error, whereas my SQL Server is running under network service built in a/c????
I googled it but not getting solution..
Thanks
Had the same problem, I fixed it.
Open SQL Server Configuration manager
Click on the SQL Server Services (on the left)
Double-click on the SQL Server Instance that I wanted to start
Select the Built-in account radio button in the Log On tab and choose Local system from the dropdown menu
Click apply at the bottom, then right click the instance and select Start
Above mentioned issue happened in my local system. Check in sql server configuration manager.
Step 1:
SQL server Network configuration
step 2:
Protocols for local server name
Protocol name VIA Disabled or not..
if not disabled , disable and check
.. after I made changes the sql server browser started working
This really works - i had verified lot of sites and finally got the answer.
This may occurs when the master.mdf or the mastlog.ldf gets corrupt . In order to solve the issue goto the following path.
C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL , there you will find a folder ” Template Data ” , copy the master.mdf and mastlog.ldf and replace it in
C:\Program Files\Microsoft SQL Server\MSSQL10_50.MSSQLSERVER\MSSQL\DATA folder .
That's it. Now start the MS SQL service and you are done.
If you are running SQL Server in a local environment and not over a TCP/IP connection. Go to Protocols under SQL Server Configuration Manager, Properties, and disable TCP/IP. Once this is done then the error message will go away when restarting the service.
If you recently changed the password associated with the service account:
Start SQL Server Configuration Manager.
Select SQL Server Services in the left pane.
Right click the service you are trying to start in the right pane and click Properties.
Enter the new Password and Confirm password.
It was very tedious when I get same problem. When I got this problem, I uninstall my SQL Server 2008 but after installing the SQL Server 2008 again,I got the same problem. I was so tensed plus, I had not gotten any help from any site.
To over come this problem. Simply You Need to go on SQL Server Configuration Manager and then click On Protocols on left panel. If you running Network service just disable 'VIA' Protocol.
And after that try to start your SQL service it will run successfully.
After chasing this issue for some hours, we found an log in the SQL Server Agent logs stating the following:
This installation of SQL Server Agent is disabled. The edition of SQL server that installed this service does not support SQL server agent.
We were using SQL Server Express. After some Googling it appears SQL Server Express does not support SQL Server Agent.
I didn't find a direct piece of Microsoft communications stating that SQL Express doesn't support SQL Server Agent, however this sentiment seems to be echoed across many forums.
In my case, the issue was that I was running two other SQL Server instances which were (or at least one of them was) causing a conflict.
The solution was simply to stop the other SQL Server instance and its accompanying SQL Server Agent.
While I'm at it, I'll also recommend making sure Named Pipes is enabled in your server's protocol settings
I had a similar issue. The next solution is in *case to can't launch the server Locally * and you will see the same error msg.(Image 1)
Imagen 1
Imagen 2
To solve that and have the server working you must have the next steps.
Go to SQL Server Services
Right click to open properties
Go to LogOn tab (By default you will see something like Image 3)
Select the radio button Built-in account (Image 4)
Click on Ok
Go back to SQL Server Services and launch again the server (Image 5)
After that you must be able to see run it.
Image 3
Image 4
Image 5
I hope that works for you or others with similar issues. Follow me for more tips.
Just disable the VIA protocol in sql server configuration manager
I found from event logs that My SQL server evaluation has expired.
I needed to upgrade or needed to use community edition.
For me a simple windows update fixed it, I wish I tried it before.
I think this solution is more appropriate, because it does not prevent you from using TCP/IP access.
To open a port in the Windows firewall for TCP access
On the Start menu, click Run, type WF.msc, and then click OK.
In the Windows Firewall with Advanced Security, in the left pane,
right-click Inbound Rules, and then click New Rule in the action pane.
In the Rule Type dialog box, select Port, and then click Next.
In the Protocol and Ports dialog box, select TCP. Select Specific
local ports, and then type the port number of the instance of the
Database Engine, such as 1433 for the default instance. Click Next.
In the Action dialog box, select Allow the connection, and then click
Next.
In the Profile dialog box, select any profiles that describe the
computer connection environment when you want to connect to the
Database Engine, and then click Next.
In the Name dialog box, type a name and description for this rule, and
then click Finish.
(Source: https://msdn.microsoft.com/en-us/library/ms175043.aspx)
I have SQL 2017 installed and this issue happens when the free trial / evaluation period ends, the solution to the problem is the following:
1 - Go to the windows start button, find the Microsoft SQL Server 20XX folder
2- Then, SQL Server 20XX Installation Center
3- On the left, select the option "Maintenance"
4- Then click on “Edition upgrade”
5- Then in the combox select "developer" option, and then click on “next” button
6- Click on the option "I accept the license terms" and then next
7- Finally, click on "Next" and click on "Upgrade", and wait approximately 15 minutes.
8- After this, restart the SQL Server service in "Services.msc" and open SQL again, it should work.
For more information: watch this video: https://www.youtube.com/watch?v=EVG35ahhjec
If you are still scrolling through the answers, here is one more step you might have missed.
Open SQL server configuration manager with admin access.
Apply the changes first(to local System) and then try to run.
If you are configuring your SQL Server connection using Computer Management under Administrative Tools or SQL Server Configuration Manager in Enterprise or Corporate environment,
make sure you open your Computer Management or SQL Server Configuration Manager as an Administrator or you have
Administrative Privileges
All answers above didn't work for me, but when I run it as Administrative mode, I can now start my SQL Server Agent or SQL Server service.
For me happened similar issue when I did uninstall Microsoft Visual C++ 2015-2020 Redistributable and installed the Microsoft Visual C++ 2017 version
Fixed this issue when re-installed Microsoft Visual C++ 2015-2020 Redistrubutable versions. then services started automatically.
Try changing login from different account:
Open SQL Server Configuration Manager as Admin.
Right click SQL sever and SQL Server Integration Services.
Go to Properties and choose Log on.
Choose Built in account.
Select local service.
Apply and Ok.
Start service again.
This is beacuse your both SQL Servers are using same TCP Port Number i.e. 1433 and only one server could run at this port at a time. You have to change or Remove Port number from below settings;
In SQL Server Configuration Manager Click on SQL Server Network Configration.
Click on required Protocols for SQL...
Double click on TCP/IP then select IP Address tab.
Scroldown to end double click in TCP Port Textbox.
Change Port number from 1433 to other one or remove it.
After save these settings now Start your required server.
Good Luck
https://social.technet.microsoft.com/wiki/contents/articles/52394.sql-server-troubleshooting-logon-failure-the-user-has-not-been-granted-the-requested-logon-type-at-this-computer.aspx
event viewer shows
Logon failure - the user has not been granted the requested logon type at this computer