This is the code I have been using to connect to my default instance for 18 months. A recent upgrade to Windows Live onecare now prevents me connecting to the server from the same machine. The following error message is generated:-
Unhandled Exception: System.Data.SqlClient.SqlException: SQL Server does not exist or access denied.
at System.Data.SqlClient.ConnectionPool.GetConnection(Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnectionPoolManager.GetPooledConnection(SqlConnectionString options, Boolean& isInTransaction)
at System.Data.SqlClient.SqlConnection.Open()
at TrainerReport001.Form1.Form1_Load(Object sender, EventArgs e) in F:#ProjectsStatsOwnerReport001Form1.vb:line 84
at System.Windows.Forms.Form.OnLoad(EventArgs e)
at System.Windows.Forms.Form.OnCreateControl()
at System.Windows.Forms.Control.CreateControl(Boolean fIgnoreVisible)
at System.Windows.Forms.Control.CreateControl()
at System.Windows.Forms.Control.WmShowWindow(Message& m)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ScrollableControl.WndProc(Message& m)
at System.Windows.Forms.ContainerControl.WndProc(Message& m)
at System.Windows.Forms.Form.WmShowWindow(Message& m)The program '[3336] TrainerReport001.exe' has exited with code 0 (0x0).
at System.Windows.Forms.Form.WndProc(Message& m)
at System.Windows.Forms.ControlNativeWindow.OnMessage(Message& m)
at System.Windows.Forms.ControlNativeWindow.WndProc(Message& m)
at System.Windows.Forms.NativeWindow.DebuggableCallback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)
at System.Windows.Forms.SafeNativeMethods.ShowWindow(HandleRef hWnd, Int32 nCmdShow)
at System.Windows.Forms.Control.SetVisibleCore(Boolean value)
at System.Windows.Forms.Form.SetVisibleCore(Boolean value)
at System.Windows.Forms.Control.set_Visible(Boolean value)
at System.Windows.Forms.ThreadContext.RunMessageLoopInner(Int32 reason, ApplicationContext context)
at System.Windows.Forms.ThreadContext.RunMessageLoop(Int32 reason, ApplicationContext context)
at System.Windows.Forms.Application.Run(Form mainForm)
at TrainerReport001.Form1.Main() in F:#ProjectsStatsOwnerReport001Form1.vb:line 2
If I turn off the onecare firewall I can connect as normal, but this is not a desired option. I have tried enabling port 1433 on the firewall, this does not work either. Any help greatly appreciated, onecare support seems reluctant to help.
When I try to connect to a default Express instance in Management Studio at the machine (Windows XP SP2) where the instance is installed, I'm getting 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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server)
What does provider: SQL Network Interfaces mean? Does it mean the Shared Memory, Named Pipes and TCP/IP?
Additional information: 1. The following Network Protocols are enabled: Shared Memory, Named Pipes, TCP/IP thru Configuration Manager 2. SQL Server Express default instance is running using NT AUTHORITYNetworkService. 3. SQL Server Browser service is not running. I believe this is not needed unless I want to connect to the instance from another machine. 4. Has tried to disable Windows Firewall but I believe it should not be matter in this particular case since this is within the same machine. 5. Can connect to the instance in ODBC Administrator using System DSN thru Named Pipes or TCP/IP.
Can such error caused by not having sufficient memory so the system is running kind of slow?
I have trying to access a 2nd SQL Server instances running on my WHS 2011 server from my Windows 8.1 Pro client.
The first SQL Server instance I installed is SQL Server 2014 Developer. This has been in place for many months and access from my client pc is not a problem. The Developer instance was installed using standard settings so uses TCP port 1433 and I have verified this by checking the firewall rules. This instance name is <SERVERNAME>
As I want to host a personal website on my server I installed SQL Server 2014 Express as a 2nd instance on my WHS 2011 box for website database purposes. After this installation both instances are accessible via Management Console on the WHS 2011 box.Â
The second instance is named as <SERVERNAME>SQLEXPRESS.
However, I am unable to access the SQLEXPRESS instance using Management Console on my client pc. I know it is a firewall issue as when I turn off the firewall on the WHS 2011 box I can connect successfully. The errors reported have resulted in my trying many things to resolve the problem but none have worked, e.g.
Use the default SQLEXPRESS instance to listen on all TCP ports (default installation option). I checked the necessary firewall rules were set up correctly and they were, i.e. UDP ANY and TCP ANY for the SQLEXPRESS sqlservr.exe file.
Change the default SQLEXPRESS instance to list on a specific TCP port, e.g. 19344
Create an ALIAS for the SQLEXPRESS installation
The instance is definitely set up for Remote Access and is not Hidden.
Are there any other firewall rules I need to apply?
I have a server with 3 SQL Server named instances on it - servername, servername/TST and servername/GOLDSTD. I have several databases on the default instance (servername) but users cannot access the databases unless they are given system admin privileges to their login. This occurs using both SQL Server Logins and Windows authentication logins. If I move the database to a different named instance (servername/TST), the problem no longer exists and users can connect with dbo privileges. Any suggestions or is this typical for default instances? Thanks in advance for any help
I am unable to access the default port 1433 on my SQL 2003 server. There is no firewall. I run telnet <ip> <port> and get "Connection failed" which explains my inability to connect to the server for weeks. I have being unable to connect to the server after I uninstalled sql 2000 and reinstalled it on my 2003 server. Some of the things I have checked is Network Configuration in EM. Named Pipes and TCP/IP is installed with port set to 1433. HKLMSoftwareMicrosoftMSSQLServerClientSuperSocketNetLibTcpDefaultPort port is set to 1433. Is there anything I need to configure on the server side to have the default sql server port enabled.
The box I am trying to connect to is running two instances of SQL Server. There is a SQL Server 2005 instance which is the default. There is a SQL Server 2000 instance which is named 'SQLSERVER'. I can connect to the SQL Server 2000 instance no problem:<add key="ConnectionString" value="server=MYPCSQLSERVER;database=mydatabase;user id=****;password=****" /> However, I am having trouble connecting to the Default SQL Server 2005 instance. I have tried: <add key="ConnectionString" value="server=MYPC;database=mydatabase;user id=****;password=****" /> but it doesn't work. I have tried explicitly setting SQL Server 2005 to use port 1434 (as SQL Server 2000 is running on port 1433), and then used: <add key="ConnectionString" value="server=MYPC,1434;database=mydatabase;user id=****;password=****" /> but this doesn't work either.
Am I mssing something here? Any help much appreciated Thanks...
I've two instances(Default, Named[dynamicsFINANCE]) running on SQL server 2014. However, when I try to connect to named instance say (dynamicsFINANCE) using SQL authentication from local SSMS, I get below error message:
A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
I assigned a static port number to the named instance [dynamicsFINANCE] 1450. I also setup the firewall rule to allow access to Port 1450.
I have a 3 node cluster on which I have installed SSAS as it's own insntance. I have created this as a named instance and can connect to it by serverinstance if I'm on the server itself. However from my desktop I get the error saying instance was not found on server name.
I have defined an alternate port and setup firewall rules and can connect via server:port but not serverinstance. Prior to making this change SSAS was running on default port of 2383 and I could connect just by servername.
I have read many articles for previous versions saying that clustered SSAS will always use 2383 and that you must connect just using servername. However and this is were it gets strange. I have a 2 node UAT cluster with SSAS setup exactly the same way I've described above and I can connect from my desktop as serverinstance.
Should I be able to connect as serverinstances for a named clustered instance in 2012 ?
I am connecting to several SQL 2000 servers on another LAN from my workstation and I have to go through a firewall.
I got the firewall people to open port 1433 and was then able to connect any server with a default instance using Query Anlyzer and the IP address of the Server.
When I try to connect from my workstation to a server with a named instance I am being blocked by the firewall before it gets to the server.
I went into Client Network Utility on my workstation and removed named pipes which only left Tcpip using port 1433.
Fire wall is now blocking “nbname UDP 137”.
Is there a setting somewhere on my workstation that I can force the traffic to the named instance to use Tcpip through port 1433.
We have an internal sql 2000 server that acts as the database backend for our Internet presence. I believe that the sql server can be accessed because of a firewall "exception" (?) that allows the external web server to talk to the sql server using a specific IP address and port (namely that of the sql server.)
Now we need to install a sql 2005 instance on the same box which needs to act as an Internet backend. The sql browser service will resolve all client requests to the default or named instance. But I read that the sql browser service assigns a "dynamic" port to the Instance! If that is the case, it's unlikely that, unless the firewall has all ports open for outgoing traffic, that the sql instance will be able to communicate with the web server.
My conclusion:
Leave the default instance (sql 2000) port at its current value; assign the named instance an unused port; Make sure the sql browser is running on the box! Tell the firewall guys to make an exception for the new port.
We have an external webserver(server1 on domain1) is a DMZ, and sql server7(server2 on domain2) inside the firewall.
Domain1 trusts domain2 but domain2 does not trust domain1.
Our firewall hosting by outside vendor and they told me they already opened up the port 1433 for server2.
I put a small asp.net application on server1(this application works fine in intranet. 2000 server,iis5,virtue directory, and .net frameword were well installed and configured), and I got S'QL server does not exist or login fail error'.
Any idea about that? And how to test the port was opened?
We install SQL Express 2005 with a custom named instance. Since a named instance uses dynamic ports, how can I add this named instance to the Windows Firewall exception list? Previously with MSDE 2000 we installed as default, then I added port 1433 to the Firewall exception list.
Is there a way to install SQL Express to a static port (programmatically)? Or, is there a better method, like adding the SQL custom named instance service to the firewall exception list?
Hi, I have a task in hand to migrate (upgrade) from SQL2K named instance to SQL2K5 default instance. There are many intranet applications touching current SQL2K. I would like to perform this upgrade such that I don't have to touch any application code - meaning I don't have to change the connectionstring to point to new Default instance. How can I achieve this?
So, in otherwords, here is what I want to achieve:
Current Server: SQL2K: SERVER_AINSTANCE_A (named instance)
If I have both default, I could achive this by setting up DNS alias after migration done so that any call for SERVER_A would point to SERVER_B. But in my case, I don't have SERVER_A, I have named instance. Is there any solution?
Currently I have a server that has two instances of SQL Server that areboth heavily used. We are moving the databases that are on the defaultinstance of this server to a new server. Since the old server willonly need one instance (the current named instance) of SQL Server isthere a good way to remove the default instance and make the namedinstance the default? If this change is possible will the name of thecurrent named instance need to be changed? Will all of the programscurrently accessing the named instance need to change their connectionstring?
Can I Install a default instance on Virtual SQL Server on a 2 node Cluster. If I already have a default instance on a different Virtual SQL Server on the same clustered Server.
What i am trying to do..
if i create 2 virtual sql Server (say sqlVi1 and sqlVi2).. i want o connect using sqlVi1 and sqlVi2..not Sqlvi1 and SQlvi2Namedinstance.
If yes..How can I do it?
Thanks in advance I Hope someone from Microsoft or MVPs will help me.
if this is not the corrcet forum...please point me the correct one
I am trying to set up a Named Instance of SQL 2000 on the same machine that has a default instance of SQL 7.0. The setup always completes and I am able to register the Named Instance of the SQL Server with which it was installed on. However, when I try to connect the users to the database, with both windows and SQL authentication, I receive a SQL server not found error. I have tried an alias setup as well as physically specifying the port number in settup up an ODBC connection. Has anyone ran into similar problems? Also, has anyone been able to successfully complete the process as mentioned above?
I have a server with sql server 2005 installed as the default instance -- I have a piece of software that needs SQL2000 to be the default instance. Is there a way other than install new sql2005 named instance and move databases to rename my SQL2005 instance from <machinename> to <machinename>sql05 for example?
I have question about install both default instance and name instance on to one server. Do I need follow a specific order such as default instance first then name instance?
If my server already has two or more name instances, can I install one more default instance?
Most of our reports need to be rendered directly to PDF. And since we have multi paged reports, we have implemented document map to have navigation. while exporting to the PDF, Users want the Bookmarks to be visible by default. However, this is not the case. The bookmarks tab in the Navigation tools of Acrobat is not expanded rather we need to manually click on it to see the bookmarks. This behavior is different from Crystal Reports XIr2 where the bookmarks are defaulted to be visible when opening a PDF exported by crystal.Is there any way to replicate this behavior in SSRS too?
I installed SQL Server 2005 recently on a cluster. I didn't go for the default instance and instead I named the instance option. Now I would like to migrate everything from the named instance to the default instance, which I haven't yet installed.
Is this an easy process? What about the logins and the maintenance plans and jobs? Is there anything else I need to be aware of?
I've never had to do this, but when I downloaded the Web Workflow Approvals Starter Kit, it requested that I install the database into a User Instance of .SQLEXPRESS.
Now the problem is, I've installed it onto a default instance, so I was wondering whether you can create a named instance on top of a default instance... and if so, how would you do that?
I have just installed SQL Server 2005. I was not given a choice during installation (that I remember seeing anyway) about which drive I wanted to place the default SQL instance on.
It ended up on C: and I needed it on D:.
So my questions are:
Is there a way to move it to D: that is easier than the way you had to go about it in SQL 2000? Is there a way to do it during setup so I can avoid this in the future?
Tried to uninstall SQL Server 64-bit on Windows 2003 remotely. All components uninsntalled properly except Reporting Services.
The log file lists the following error -
/***** ReportingServicesService!library:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> System.Data.SqlClient.SqlException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
*******/
Now I cannot see Reporting Services under Add/Remove programs (ARPWrapper.exe /remove). It is also not displayed when using Windows Installer Cleanup Utility (msicuu2.exe). I can start the default instance of RS via Reporting Services Configuration manager and it can also be also started under Windows Services. BTW, the IIS folder structure is under the default website for Reports and ReportServer is present.
So, now how do I go about uninstalling SQL Reporting Services when I cannot see it (as an installed program) without rebuilding the machine ?
Tried to uninstall SQL Server 64-bit on Windows 2003 remotely. All components uninsntalled properly except Reporting Services.
The log file lists the following error -
/*****
ReportingServicesService!library:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing., ; Info: Microsoft.ReportingServices.Diagnostics.Utilities.ReportServerDatabaseUnavailableException: The report server cannot open a connection to the report server database. A connection to the database is required for all requests and processing. ---> System.Data.SqlClient.SqlException: 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: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)
*******/
Now I cannot see Reporting Services under Add/Remove programs (ARPWrapper.exe /remove). It is also not displayed when using Windows Installer Cleanup Utility (msicuu2.exe). I can start the default instance of RS via Reporting Services Configuration manager and it can also be also started under Windows Services. BTW, the IIS folder structure is under the default website for Reports and ReportServer is present.
So, now how do I go about uninstalling SQL Reporting Services when I cannot see it (as an installed program) without rebuilding the machine ?
I installed SQL Server 2005 flawlessly yesterday. When login as "sa" through SQL Server Management Studio, I get an error message saying it cannot connect to my PC.
I checked the MSSQL Server Service. It is not started and cannot be started because it's looking for a path that does not exist!.
The folder in question is missing. C:Program FilesMicrosoft SQL ServerMSSQL
The following folders do exist: C:Program FilesMicrosoft SQL ServerMSSQL.1 C:Program FilesMicrosoft SQL ServerMSSQL.2
I initially suspected this problem was cause by a previous MSDE 2000 installation.
I uninstalled SQL Server 2005 & MSDE 2000. I re-installed SQL Server 2005. Same problem. I executed http://support.microsoft.com/default.aspx/kb/320873 to make sure all registries are removed and manually deleted C:Program FilesMicrosoft SQL Server€™s content
Re-installed SQL Server 2005. Same problem.
I do not know what do in order to get SQL Server 2005 up & running.
OS: Windows 2003 Server Enterprise Edition SQL Server: SQL Server 2005 Enterprise Edition (2 instances) SQL Server : SQL Server 2000 Enterprise Edition ( 1 instance)
Problem: 2nd instance of sql server 2005 installed and service pack 2 applied when using SS Mangement Studio I get the error:
Cannot connect to <ServerName>MSSQL2K5_2. =================================== 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) ------------------------------ For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=10060&LinkId=20476 ------------------------------ Error Number: 10060 Severity: 20 State: 0
------------------------------ Program Location: at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection) at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj) at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, Int64 timerExpire, SqlConnection owningObject) at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(String host, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, Int64 timerStart) at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance) at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionFactory.CreateNonPooledConnection(DbConnection owningConnection, DbConnectionPoolGroup poolGroup) at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection) at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory) at System.Data.SqlClient.SqlConnection.Open() at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server) at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()
Open MyComputer Services & Applicaitons | Services SQL SERVER (<SERVER NAME> MSSQL2K5) STARTED SQL SERVER (<SERVER NAME> MSSQL2K5_2) STARTED SQL AGENT (<SERVER NAME> MSSQL2K5) STARTED SQL AGENT (<SERVER NAME> MSSQL2K5_2) NOT STARTED
Application Event Log
SQLServerAgent could not be started (reason: Unable to connect to server 'BLUESTONEMSSQL2K5_2'; SQLServerAgent cannot start).
SOURCE: MSSQL%MSSQL2K5_2
Server is listening on [ 'any' <ipv4> 2777].
DAC is listening on [ 'any' <ipv4> 2778]
<SQL ERROR LOG> AND <APPLICATION EVENT LOG ENTRY>
The SQL Network Interface library could not register the Service Principal Name (SPN) for the SQL Server service.
Error: 0x54b, state: 3.
Failure to register an SPN may cause integrated authentication to fall back to NTLM instead of Kerberos.
This is an informational message.
Further action is only required if Kerberos authentication is required by authentication policies.
CONFIGUATION MANGER Alias is configured with correct port. (2777) Protocol TCP/IP
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: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified) (Microsoft SQL Server, Error: -1)
For help, click: http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=-1&LinkId=20476
