Cannot connect to SQL Server

Recently, I installed a fresh copy of Windows Vista Business.

Then, I installed SQL Server 2005 Developer Edition.

Upon completion I get a message saying that I should update my SQL Server with SQL

Server SP1.

Good. Go to Microsoft.com, download and installed it. Update succesful.

Then I get another message telling me that I need to update to SQL Server 2005 SP2

because that one is also need it for compatibility with Windows Vista.

Good. Go again to Microsoft.com and install SP2.

Trying to connect to the server is imposible. When I try I get the folowing message:

Cannot connect to Val-PC ( the server name )

Login failed for for user 'Val-Pc\Val' (Microsoft SQL Server, Error 18456 )

Can anyone help? It would be very much appriciated.

Thanks.

What is the state of the error message ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de|||It seems that you are using windows authentication. check whether this user has enough permission to the server|||

For some reason, as soon as Service Pack 2 was installed successfully, the problem

was gone. I could connect to the server right away.

I understand by looking at the documentation that previous versions of SQL Server 2005 have

compatibility problems with Windows Vista and Service Pack 2 is supposed to address them.

Thanks for the help, anyway!

Cannot connect to SQL express database ??

Dear all,
I have setup a database under SQLexpress 2005 which is install on a Vista OS
.
I can manage without any problem my database from the VIsta workstation.
Then on an other PC, I am trying to create a connection to that databse with
.NET 1.1, but no luck
I ma using similar conenction string as for an SQL server databse excpet
that Server="MyWorkStationName\SQLEXPRESS".
I have place the conenctionstring in a config file as follow :
" Database=Line_Config;Server=MyWorkStatio
nName\SQLEXPRESS;uid=rptuser;Pwd=re
porting"
What is wrong that prebvent me from connection to database ?
Is it possible to connect to an SQLExpress database located on an other PC ?
thnaks for help
regards
sergeProbably either the SQL Server Express instance has not enabled remote
connections, or a firewall is blocking the connection.
Run through the short tutorial in Books Online and see if that solves the
problem. The tutorial is also online at
http://msdn2.microsoft.com/en-us/library/ms345318.aspx Note that lesson 2 is
Connecting from Another Computer.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:067F10D8-72B1-4858-AE9F-E5EEF213BEF1@.microsoft.com...
> Dear all,
> I have setup a database under SQLexpress 2005 which is install on a Vista
> OS.
> I can manage without any problem my database from the VIsta workstation.
> Then on an other PC, I am trying to create a connection to that databse
> with
> .NET 1.1, but no luck
> I ma using similar conenction string as for an SQL server databse excpet
> that Server="MyWorkStationName\SQLEXPRESS".
> I have place the conenctionstring in a config file as follow :
>
> " Database=Line_Config;Server=MyWorkStatio
nName\SQLEXPRESS;uid=rptuser;Pwd=
reporting"
> What is wrong that prebvent me from connection to database ?
> Is it possible to connect to an SQLExpress database located on an other PC
> ?
> thnaks for help
> regards
> serge|||Thnaks for your reply...
I have check seetings as describe in this link.
What happen is that I have SQL express install on a Vista machine
Then I set use of tcp port from the surface configuration tool and set port
to 1500
From a simple remote machine running w2000, I try to establish an ODBC
connection to my VIsta machine where SQL express is installed.
For that I have install on my 2000 machine the SQL native client for 2005
and try to define a DSN name but when trying to connect...no way...
Any ideas ?
regards
serge
"Rick Byham, (MSFT)" wrote:

> Probably either the SQL Server Express instance has not enabled remote
> connections, or a firewall is blocking the connection.
> Run through the short tutorial in Books Online and see if that solves the
> problem. The tutorial is also online at
> http://msdn2.microsoft.com/en-us/library/ms345318.aspx Note that lesson 2
is
> Connecting from Another Computer.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:067F10D8-72B1-4858-AE9F-E5EEF213BEF1@.microsoft.com...
>|||Did you stop and restart SQL Server 2005 Express Edition after setting 1500
as the fixed port?
Are you attempting to connect to the Express Edition by name in the format
computer_name\SQLExpress ?
Is the SQL Server Browser service running?
Can you connect to the Express Edition by the port number using
computer_name,1500 or by IP address in the format 127.025.144.315,1500 ?
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:F1AB79D1-899E-40C6-BE14-21D0305C36CA@.microsoft.com...[vbcol=seagreen]
> Thnaks for your reply...
> I have check seetings as describe in this link.
> What happen is that I have SQL express install on a Vista machine
> Then I set use of tcp port from the surface configuration tool and set
> port
> to 1500
> From a simple remote machine running w2000, I try to establish an ODBC
> connection to my VIsta machine where SQL express is installed.
> For that I have install on my 2000 machine the SQL native client for 2005
> and try to define a DSN name but when trying to connect...no way...
> Any ideas ?
> regards
> serge
> "Rick Byham, (MSFT)" wrote:
>|||OK it works now rick...
I have made 2 mistakes...
Frist of all I forgot to open the port 1500 in my windows firewall.
Then I was accessing my server by using <myPCname>\SQLEXPRESS as I use to do
normally with SQL server.
SO in order to work I have to connect using tcp:<myPCname>\SQLEXPRESS,1500
But I like whem I undersatnd things. This connection string using sytax
above is use like that only for this express edition ? I guess not, I mean I
have made many connection like that with SQL server ( On a real server sure)
and I was juist using the instance and Pc name.
Or may be it would work also if I add left the default setting when you use
TCP as port 1443 and let SQL as dynamic mode and then just open the port 144
3
on my firewall. Then use as connection string :<myPCname>\SQLEXPRESS.
But of course dynamic means dynamic.
Does it means that this dynamic TP port seting should never be use with SQL
server ?
regards
serge
"Rick Byham, (MSFT)" wrote:

> Did you stop and restart SQL Server 2005 Express Edition after setting 150
0
> as the fixed port?
> Are you attempting to connect to the Express Edition by name in the format
> computer_name\SQLExpress ?
> Is the SQL Server Browser service running?
> Can you connect to the Express Edition by the port number using
> computer_name,1500 or by IP address in the format 127.025.144.315,1500 ?
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights
.
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:F1AB79D1-899E-40C6-BE14-21D0305C36CA@.microsoft.com...
>|||Connecting to the server name (<myPCname>\SQLEXPRESS) should work, if the
SQL Server Browser service is running. However, yes, you are correct that if
SQL Server Express Edition is using dynamic ports, then the port could
change to one that is blocked by the firewall. So you will need to switch
SQL Server Express Edition to a fixed port.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:B778178D-FF1E-4827-981E-369B3C5C9AFE@.microsoft.com...[vbcol=seagreen]
> OK it works now rick...
> I have made 2 mistakes...
> Frist of all I forgot to open the port 1500 in my windows firewall.
> Then I was accessing my server by using <myPCname>\SQLEXPRESS as I use to
> do
> normally with SQL server.
> SO in order to work I have to connect using tcp:<myPCname>\SQLEXPRESS,1500
> But I like whem I undersatnd things. This connection string using sytax
> above is use like that only for this express edition ? I guess not, I mean
> I
> have made many connection like that with SQL server ( On a real server
> sure)
> and I was juist using the instance and Pc name.
> Or may be it would work also if I add left the default setting when you
> use
> TCP as port 1443 and let SQL as dynamic mode and then just open the port
> 1443
> on my firewall. Then use as connection string :<myPCname>\SQLEXPRESS.
> But of course dynamic means dynamic.
> Does it means that this dynamic TP port seting should never be use with
> SQL
> server ?
> regards
> serge
> "Rick Byham, (MSFT)" wrote:
>

Cannot connect to SQL express database ??

Dear all,
I have setup a database under SQLexpress 2005 which is install on a Vista OS.
I can manage without any problem my database from the VIsta workstation.
Then on an other PC, I am trying to create a connection to that databse with
..NET 1.1, but no luck
I ma using similar conenction string as for an SQL server databse excpet
that Server="MyWorkStationName\SQLEXPRESS".
I have place the conenctionstring in a config file as follow :
"Database=Line_Config;Server=MyWorkStationName\SQL EXPRESS;uid=rptuser;Pwd=reporting"
What is wrong that prebvent me from connection to database ?
Is it possible to connect to an SQLExpress database located on an other PC ?
thnaks for help
regards
serge
Probably either the SQL Server Express instance has not enabled remote
connections, or a firewall is blocking the connection.
Run through the short tutorial in Books Online and see if that solves the
problem. The tutorial is also online at
http://msdn2.microsoft.com/en-us/library/ms345318.aspx Note that lesson 2 is
Connecting from Another Computer.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:067F10D8-72B1-4858-AE9F-E5EEF213BEF1@.microsoft.com...
> Dear all,
> I have setup a database under SQLexpress 2005 which is install on a Vista
> OS.
> I can manage without any problem my database from the VIsta workstation.
> Then on an other PC, I am trying to create a connection to that databse
> with
> .NET 1.1, but no luck
> I ma using similar conenction string as for an SQL server databse excpet
> that Server="MyWorkStationName\SQLEXPRESS".
> I have place the conenctionstring in a config file as follow :
>
> "Database=Line_Config;Server=MyWorkStationName\SQL EXPRESS;uid=rptuser;Pwd=reporting"
> What is wrong that prebvent me from connection to database ?
> Is it possible to connect to an SQLExpress database located on an other PC
> ?
> thnaks for help
> regards
> serge
|||Thnaks for your reply...
I have check seetings as describe in this link.
What happen is that I have SQL express install on a Vista machine
Then I set use of tcp port from the surface configuration tool and set port
to 1500
From a simple remote machine running w2000, I try to establish an ODBC
connection to my VIsta machine where SQL express is installed.
For that I have install on my 2000 machine the SQL native client for 2005
and try to define a DSN name but when trying to connect...no way...
Any ideas ?
regards
serge
"Rick Byham, (MSFT)" wrote:

> Probably either the SQL Server Express instance has not enabled remote
> connections, or a firewall is blocking the connection.
> Run through the short tutorial in Books Online and see if that solves the
> problem. The tutorial is also online at
> http://msdn2.microsoft.com/en-us/library/ms345318.aspx Note that lesson 2 is
> Connecting from Another Computer.
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:067F10D8-72B1-4858-AE9F-E5EEF213BEF1@.microsoft.com...
>
|||Did you stop and restart SQL Server 2005 Express Edition after setting 1500
as the fixed port?
Are you attempting to connect to the Express Edition by name in the format
computer_name\SQLExpress ?
Is the SQL Server Browser service running?
Can you connect to the Express Edition by the port number using
computer_name,1500 or by IP address in the format 127.025.144.315,1500 ?
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:F1AB79D1-899E-40C6-BE14-21D0305C36CA@.microsoft.com...[vbcol=seagreen]
> Thnaks for your reply...
> I have check seetings as describe in this link.
> What happen is that I have SQL express install on a Vista machine
> Then I set use of tcp port from the surface configuration tool and set
> port
> to 1500
> From a simple remote machine running w2000, I try to establish an ODBC
> connection to my VIsta machine where SQL express is installed.
> For that I have install on my 2000 machine the SQL native client for 2005
> and try to define a DSN name but when trying to connect...no way...
> Any ideas ?
> regards
> serge
> "Rick Byham, (MSFT)" wrote:
|||OK it works now rick...
I have made 2 mistakes...
Frist of all I forgot to open the port 1500 in my windows firewall.
Then I was accessing my server by using <myPCname>\SQLEXPRESS as I use to do
normally with SQL server.
SO in order to work I have to connect using tcp:<myPCname>\SQLEXPRESS,1500
But I like whem I undersatnd things. This connection string using sytax
above is use like that only for this express edition ? I guess not, I mean I
have made many connection like that with SQL server ( On a real server sure)
and I was juist using the instance and Pc name.
Or may be it would work also if I add left the default setting when you use
TCP as port 1443 and let SQL as dynamic mode and then just open the port 1443
on my firewall. Then use as connection string :<myPCname>\SQLEXPRESS.
But of course dynamic means dynamic.
Does it means that this dynamic TP port seting should never be use with SQL
server ?
regards
serge
"Rick Byham, (MSFT)" wrote:

> Did you stop and restart SQL Server 2005 Express Edition after setting 1500
> as the fixed port?
> Are you attempting to connect to the Express Edition by name in the format
> computer_name\SQLExpress ?
> Is the SQL Server Browser service running?
> Can you connect to the Express Edition by the port number using
> computer_name,1500 or by IP address in the format 127.025.144.315,1500 ?
> --
> Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no rights.
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:F1AB79D1-899E-40C6-BE14-21D0305C36CA@.microsoft.com...
>
|||Connecting to the server name (<myPCname>\SQLEXPRESS) should work, if the
SQL Server Browser service is running. However, yes, you are correct that if
SQL Server Express Edition is using dynamic ports, then the port could
change to one that is blocked by the firewall. So you will need to switch
SQL Server Express Edition to a fixed port.
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:B778178D-FF1E-4827-981E-369B3C5C9AFE@.microsoft.com...[vbcol=seagreen]
> OK it works now rick...
> I have made 2 mistakes...
> Frist of all I forgot to open the port 1500 in my windows firewall.
> Then I was accessing my server by using <myPCname>\SQLEXPRESS as I use to
> do
> normally with SQL server.
> SO in order to work I have to connect using tcp:<myPCname>\SQLEXPRESS,1500
> But I like whem I undersatnd things. This connection string using sytax
> above is use like that only for this express edition ? I guess not, I mean
> I
> have made many connection like that with SQL server ( On a real server
> sure)
> and I was juist using the instance and Pc name.
> Or may be it would work also if I add left the default setting when you
> use
> TCP as port 1443 and let SQL as dynamic mode and then just open the port
> 1443
> on my firewall. Then use as connection string :<myPCname>\SQLEXPRESS.
> But of course dynamic means dynamic.
> Does it means that this dynamic TP port seting should never be use with
> SQL
> server ?
> regards
> serge
> "Rick Byham, (MSFT)" wrote:

Cannot connect to SQL 2005 remotely from Vista

TITLE: Connect to Server

Cannot connect to iiii\dddbbb.

ADDITIONAL INFORMATION:

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)

What's blocking my remote connection to SQL 2005 on Windows 2003? I am using Vista Ulttima and the above message comes up after I clicked connect. However I have no problem to connect to same database from same location using XP. Can someone help?

Do you block port 1433 on your machine ?

Jens K. Suessmeyer.

http://www.sqlserver2005.de

|||I'm new to Vista. How can I tell if it's been blocked?|||

Anonymous wrote:

TITLE: Connect to Server

Cannot connect to iiii\dddbbb.

ADDITIONAL INFORMATION:

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)

What's blocking my remote connection to SQL 2005 on Windows 2003? I am using Vista Ulttima and the above message comes up after I clicked connect. However I have no problem to connect to same database from same location using XP. Can someone help?

In addition, I can't run/debug my .net web app from VS2005 on Vista where I have no problem using XP Pro to do the same thing. The message I got is same as above.

|||

Can moderator look into this issue... I can't see my original thread nor see any of my postings under my threads since I was prompted to change my display name. Forturnately I still keep copy of alert emails which allow me trace my threads.

Hi Jens,

The machine I'm using is a new one, do you mean the 1433 on server or on my local machine?

Cannot connect to shared database

Using Vista, when I start Outlook 2007 I get the following message:

Business Contact Manager for Outlook could not connect to the shared database.//looking for msslbiz Do you want to work offline?

I click Continue and get the messagebox:

Business Contact Managerdatabase cannot be loaded

This action cannot be completed because Business Contact Manager cannot access the database. The database is currently stopped.

Do you want to change the database configuration?

i say Yes and the messagebox says

Microsoft Windows Search Protocol Host has stopped working.
A problem cause the program to stop working correctly. Windows will close the program and notify you if a solution is available.

I close program (no choice) and message says:

Cannot find the selected database. Verify that the network and the computer on which the databases are located are available, and that you have permission to access the database, and then retry.

Connect to computer name prompt does not work

Create new database does not work

Database creation was unsuccesful

Using MS SQL Server Management Studio Express) to connect to msslbiz

SQLServer does not allow remote connections (when trying to conect to

Note that SqlServer Express is started and running on the Vista machine, and the databases I create are available to other machines on my lan. I cannot find a way to enable remote connections on msslbiz. Any help would be greatly appreciated.

I found the answer, atthough I may have other questions about SQL Express. For some reason Windows Firewall was not allowing inbound TCP traffic. I allowed it on one port and that allowed msslibiz to start up.|||

If I understand what you're trying to do, consider that SQL Express' default behavior is to disable the ability to view the server instance from another system on the LAN. You'll need to follow the instructions in http://betav.com/blog/billva/2006/06/getting_and_staying_connected.html. Basically, this means enabling the SQLBrowser service, enabling the ports and protocols needed to share the SQLEXPRESS instance. This is generally done using the SQL Server Surface Area Configuration Tool.

hth