Can't get connected to MSDE Remotely

I have a problem getting connected to an instance of MSDE remotely. I can
register the instance in Enterprise Manager, and work with it locally on the
machine it is installed on but cannot get connected remotely. I get the
famous SQL Server does not exist or access is denied.
It is a named instance.
The security mode is set to SQL.
Network Protocols are enabled.
netstat tells me that it is listening on the correct port.
I'm logging in remotely as sa with the correct password.
Any help here would be appreciated.
Also for some reason the name of the server doesn't show up in the list in
Enterprise manager on the remote machine when trying to register the server.
I typed in the name of the server, the sa login and password, but still the
same error. Server doesn't exist or access is denied.
"jdehne" wrote:

> I have a problem getting connected to an instance of MSDE remotely. I can
> register the instance in Enterprise Manager, and work with it locally on the
> machine it is installed on but cannot get connected remotely. I get the
> famous SQL Server does not exist or access is denied.
> It is a named instance.
> The security mode is set to SQL.
> Network Protocols are enabled.
> netstat tells me that it is listening on the correct port.
> I'm logging in remotely as sa with the correct password.
> Any help here would be appreciated.
|||I have also tried adding the alias with the same port as MSDE is configured.
"jdehne" wrote:
[vbcol=seagreen]
> Also for some reason the name of the server doesn't show up in the list in
> Enterprise manager on the remote machine when trying to register the server.
> I typed in the name of the server, the sa login and password, but still the
> same error. Server doesn't exist or access is denied.
> "jdehne" wrote:
|||i have also noticed that when running osql -L on the remote machine the MSDE
instance does not show up.
"jdehne" wrote:
[vbcol=seagreen]
> I have also tried adding the alias with the same port as MSDE is configured.
> "jdehne" wrote:
|||Am Mon, 17 Oct 2005 15:06:03 -0700 schrieb jdehne:
[vbcol=seagreen]
> i have also noticed that when running osql -L on the remote machine the MSDE
> instance does not show up.
> "jdehne" wrote:
I can only guess:
a) TCP is enabled on the server but not on the client
b) connect doesn't work with servername but with server-IP
c) MDAC's are different versions
bye,
Helmut
|||hi,
jdehne wrote:
> i have also noticed that when running osql -L on the remote machine
> the MSDE instance does not show up.
try having a look at http://support.microsoft.com/kb/841251/en-us ,
http://support.microsoft.com/kb/841249/en-us
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||I managed to figure it out. SP2 Secruity center was blocking the port and I
had add the sqlserver.exe to the list of programs that can get through the
firewall.
"Andrea Montanari" wrote:

> hi,
> jdehne wrote:
> try having a look at http://support.microsoft.com/kb/841251/en-us ,
> http://support.microsoft.com/kb/841249/en-us
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>

Can't find sql 2000 CD for named instance

Any way to install a named instance without a sql server 2000 CD! I need to install a named instance TODAY but can not find the CD. Or any where I can download the install so I can create a named instance
Thanks for any help.Ashley,
No, the CD is required unless you are okay with the 120-day limit evaluation
copy or MSDE.
--
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"AshleyT" <anonymous@.discussions.microsoft.com> wrote in message
news:A56A7DCB-B09D-44E3-AEE8-83037FD8CA8F@.microsoft.com...
> Any way to install a named instance without a sql server 2000 CD! I need
to install a named instance TODAY but can not find the CD. Or any where I
can download the install so I can create a named instance.
> Thanks for any help.

Can't find sql 2000 CD for named instance

Any way to install a named instance without a sql server 2000 CD! I need to install a named instance TODAY but can not find the CD. Or any where I can download the install so I can create a named instance.
Thanks for any help.
Ashley,
No, the CD is required unless you are okay with the 120-day limit evaluation
copy or MSDE.
Dinesh
SQL Server MVP
--
SQL Server FAQ at
http://www.tkdinesh.com
"AshleyT" <anonymous@.discussions.microsoft.com> wrote in message
news:A56A7DCB-B09D-44E3-AEE8-83037FD8CA8F@.microsoft.com...
> Any way to install a named instance without a sql server 2000 CD! I need
to install a named instance TODAY but can not find the CD. Or any where I
can download the install so I can create a named instance.
> Thanks for any help.

Can't find sql 2000 CD for named instance

Any way to install a named instance without a sql server 2000 CD! I need to
install a named instance TODAY but can not find the CD. Or any where I can
download the install so I can create a named instance.
Thanks for any help.Ashley,
No, the CD is required unless you are okay with the 120-day limit evaluation
copy or MSDE.
Dinesh
SQL Server MVP
--
--
SQL Server FAQ at
http://www.tkdinesh.com
"AshleyT" <anonymous@.discussions.microsoft.com> wrote in message
news:A56A7DCB-B09D-44E3-AEE8-83037FD8CA8F@.microsoft.com...
> Any way to install a named instance without a sql server 2000 CD! I need
to install a named instance TODAY but can not find the CD. Or any where I
can download the install so I can create a named instance.
> Thanks for any help.sql

Can't find odbcping.exe

I am trying to troubleshoot a SQL Server connection from my home machine
to an instance of SQL server running on my client's network using
Enterprise Manger and I am going through the steps in the MS KB article
How to troubleshoot connectivity issues in SQL Server 2000,
http://support.microsoft.com/default...;en-us;827422, which
suggests using odbcping.exe.
However, I cannot find this in my local SQL Server directories or in the
server Sql Server directories.
Doe anyone know where it is?
It's not installed by default with SQL 2000. The utility can
be found in the \x86\Binn directory on the SQL Server 2000
CD.
-Sue
On Sun, 12 Dec 2004 00:05:34 -0500, Douglas Forrest
<dforrest@.optonline.net> wrote:

>I am trying to troubleshoot a SQL Server connection from my home machine
>to an instance of SQL server running on my client's network using
>Enterprise Manger and I am going through the steps in the MS KB article
>How to troubleshoot connectivity issues in SQL Server 2000,
>http://support.microsoft.com/default...;en-us;827422, which
>suggests using odbcping.exe.
>However, I cannot find this in my local SQL Server directories or in the
>server Sql Server directories.
>Doe anyone know where it is?
|||Sue Hoegemeier wrote:
> It's not installed by default with SQL 2000. The utility can
> be found in the \x86\Binn directory on the SQL Server 2000
> CD.
> -Sue
> On Sun, 12 Dec 2004 00:05:34 -0500, Douglas Forrest
> <dforrest@.optonline.net> wrote:
>
>
Thanks

Can't Deploy AdventureWorks Database

Hi All,

I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.

For some reason, I encountered the following error (after deployment during processing):

Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; 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.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0

Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.

Nothing seems to work. Any help would be greatly appreciated!

Thanks,

Raj

Hi,

We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:

Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0

This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.

Brad

|||

We are having the exact same error. Did you all find a solution?

|||

I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.

G'luck.

|||Hi everyone!
I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||

Try:

Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.

Can't Deploy AdventureWorks Database

Hi All,

I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.

For some reason, I encountered the following error (after deployment during processing):

Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; 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.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0

Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.

Nothing seems to work. Any help would be greatly appreciated!

Thanks,

Raj

Hi,

We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:

Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0

This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.

Brad

|||

We are having the exact same error. Did you all find a solution?

|||

I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.

G'luck.

|||Hi everyone!
I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||

Try:

Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.

Can't Deploy AdventureWorks Database

Hi All,

I created a named instance of SQL SERVER 2005 (Evaluation version) on Windows XP pro, attached the AdventureWorks and AdventureWorks DW databases to the database engine, and tried to deploy the AdventureWorks DW (Enterprise and Standard) database in Analysis Services using SQL SERVER Business Intelligence Development Studio.

For some reason, I encountered the following error (after deployment during processing):

Error 1 OLE DB error: OLE DB or ODBC error: Login timeout expired; HYT00; 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.; 08001; Named Pipes Provider: Could not open a connection to SQL Server [2]. ; 08001. 0 0

Please note that I used the configuration manager to enable named pipes and allow remote connections. I also, renamed the target server (to the named server instance instead of the localhost), disabled my Windows and Norton firewalls, and changed the deployment server edition to the Evaluation version in the Adventure Works DW Property page.

Nothing seems to work. Any help would be greatly appreciated!

Thanks,

Raj

Hi,

We also experienced a similar problem deploying the AdventureWorks DW using the Business Intelligence Development Studio. Our error is as follows:

Error 1 OLE DB error: OLE DB or ODBC error: Communication link failure; 08S01; Shared Memory Provider: The system cannot open the file. ; 08S01; Login failed for user 'NT AUTHORITY\SYSTEM'.; 28000; Cannot open database requested in login 'AdventureWorksDW'. Login fails.; 42000. 0 0

This error occurred after we had dropped and uninstalled the sample databases from a previous install. Please note we downloaded the samples from Microsoft and used the AdventureWorks Data Warehouse Database and Analysis Services Project to install the databases.

Brad

|||

We are having the exact same error. Did you all find a solution?

|||

I'm moving this post to the Tools forum since this isn't a setup or upgrade issue.

G'luck.

|||Hi everyone!
I just had the same problem and solved it. What you have to do is:
1) Right-click the project name, and choose properties
2) In the deployment tab change the server name from localhost to your instance name
3) Double-click the data source in solution explorer
4) In General tab click Edit to change the connection string
5) Choose Native OLE DB\Microsoft OLE DB Provider for SQL Server
6) Type in your server name
7) Select the AdventureWorksDW as database name and click OK
Now the deployment should be successfull...|||

Try:

Double click on AdvantureWork.ds from DataSource (From Solution Explorer). and in Impersonation Information Select the Use the Service Account.

Can't created a linked server on a named instance to default insta

I have been trying to create a linked server on a named instance to a defaul
t
instance using intergrated security. It seems to work fine from a default
instance to any other SQL instance, including a named instance, but any time
I create the linked server on the named instance a call to the linked server
fails with the error:
Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
All servers are running SQL Server 2000 and the only difference in the
installation besides the fact one is named, is that the named instance is SP
4
and all others are SP3.
From a default instance the following works fine:
sp_addlinkedserver 'ORDEV01'
ORDEV01.Master.dbo.sp_helpdb
and the following to a named instance works as well:
sp_addlinkedserver 'LOU\Master'
[LOU\Master].Master.dbo.sp_helpdb
But if I try to created a linked server on the name dinstance LOU\Master I
get the error:
Msg 18452, Level 14, State 1, Line 1
Login failed for user '(null)'. Reason: Not associated with a trusted SQL
Server connection.
Thanks in advance for any help.Byron
Does the instance have Windows Authentication?
"Byron" <Byron@.discussions.microsoft.com> wrote in message
news:CB90A676-83FF-41CC-9C04-221920F998FF@.microsoft.com...
>I have been trying to create a linked server on a named instance to a
>default
> instance using intergrated security. It seems to work fine from a default
> instance to any other SQL instance, including a named instance, but any
> time
> I create the linked server on the named instance a call to the linked
> server
> fails with the error:
> Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> All servers are running SQL Server 2000 and the only difference in the
> installation besides the fact one is named, is that the named instance is
> SP4
> and all others are SP3.
> From a default instance the following works fine:
> sp_addlinkedserver 'ORDEV01'
> ORDEV01.Master.dbo.sp_helpdb
> and the following to a named instance works as well:
> sp_addlinkedserver 'LOU\Master'
> [LOU\Master].Master.dbo.sp_helpdb
> But if I try to created a linked server on the name dinstance LOU\Master I
> get the error:
> Msg 18452, Level 14, State 1, Line 1
> Login failed for user '(null)'. Reason: Not associated with a trusted SQL
> Server connection.
> Thanks in advance for any help.

Can't create a ODBC DSN to a remote MSDE instance

Hello,
I need to create an ODBC DNS that points to a remote MSDE instance, but I
can only get it to work if I turn Windows Firewall off. Both the local and
remote machines are WinXP SP2 and have SQL2000 and MSDE, same domain and I
can login as the same person on each machine.
On the remote machine I've enabled TCP/IP and the default port, and I've
added that port to the firewall, but when I try to add a DSN (on the local
machine) in the ODBC control panel it says
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
I've looked at the instance via Enterprise Manager and my domain login has
admin privs, and can connect a DSN to the SQL2000 server on that machine.
Stumped.
Suggestions?
Keith
hi Keith,
Keith wrote:
> Hello,
> I need to create an ODBC DNS that points to a remote MSDE instance,
> but I can only get it to work if I turn Windows Firewall off. Both
> the local and remote machines are WinXP SP2 and have SQL2000 and
> MSDE, same domain and I can login as the same person on each machine.
> On the remote machine I've enabled TCP/IP and the default port, and
> I've added that port to the firewall, but when I try to add a DSN (on
> the local machine) in the ODBC control panel it says
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not
> exist or access denied.
> I've looked at the instance via Enterprise Manager and my domain
> login has admin privs, and can connect a DSN to the SQL2000 server on
> that machine.
did you define an exception on the server's firewall on the MSDE used TCP/IP
port or on the service itself?
http://support.microsoft.com/default.aspx?kbid=841249
http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
http://support.microsoft.com/default.aspx?scid=kb;[LN];884012 (Win2003)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||>
> did you define an exception on the server's firewall on the MSDE used
> TCP/IP port or on the service itself?
> http://support.microsoft.com/default.aspx?kbid=841249
> http://support.microsoft.com/default.aspx?scid=kb;[LN];841251
> http://support.microsoft.com/default.aspx?scid=kb;[LN];884012 (Win2003)
Well, after some reboots and a walk around the block it works now.
I finally got it to work either with firewall port exception, or a service
exception, but neither way seemed very consistent. Making changes to the
firewall while it is running just doesn't seem to work that well; perhaps I
wasn't waiting long enough for the changes to propagate or I just need to
stop/start the firewall after changing something.
And I suspect that some of the changes that don't "require" rebooting really
do.
Anyway, thanks for the quick response and support links.
Keith

Cant copy database, strange error

I'm trying to copy a database from my web host to local Sql Server 2005 instance using the Copy Database wizard. I get this error:

An exception occurred while executing a Transact-SQL statement or batch.

Server user 'celestine' is not a valid user id database 'db2'.

However, 'db2' isn't the database I was trying to copy! I am trying to copy db1, but this error is complaining about db2, which is in fact somebody else's database that I don't have a login for. Why am I getting an error about db2 when I'm not trying to do anything with db2?

I can however export the tables from db1 just fine using Export. But then I have to go back and generate script to re-create the stored procs, views, etc., so it is rather tedious to do it that way.

This may be possible. For example if there is a view in db1 which references a table in db2, and the celestine login does not have access to db2, you may encounter this error.

So to avoid such issue, you can move/copy database by taking a full backup of the source database and then restore it on the destination server.

|||

Good idea but -- No, this is not the case. This is a shared hosting situation, the 2nd database is owned by someone else, I have absolutely no access to it at all. There is no relationship whatsoever between the databases.

I can't do a backup/restore either because I don't have access to the remote filesystem.

|||

Urgh...that's really a trouble. Then check whether your login has sufficient permissions to perform copy database task:

Required permissions

For the Copy Database Wizard to work, you must have the correct permissions, depending on how you are copying the database, as follows:

For the Detach and Attach Method, you must be a member of thesysadmin fixed server role on the both source and destination servers.

|||Right. But a) I do have correct permissions for both source/destination for the database I'm trying to copy, and b) The error is not pertaining to the database I want to copy. The error mentions a different database, that I have zero permissions for, that I will never have permissions for, that I don't want permissions for. I am trying to copy db1 and the error says "you don't have permissions for db2". Why is it even checking anything for db2?

Cant connect to SQL server 2000 instance from domain machines

Hi
We currently have installed sql2005 (installed first as default
instance) and sql 2000 with a named instance. When developing sites
and using connection strings, we can access the sql2000 db fine by
using SERVERNAME\INSTANCENAME.
However, if we try to connect via enterprise manager from any other
machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
and the instance name alone wont work either.
How do we get round this as at present, we are having to log into the
database server to make any changes etc!!!
Novice here so excuse me if I have missed anything obvious!
Cheers
RajThe easiest workaround would be to connect to the instance using its IP
address followed by a comma and then the port number. You should not use just
hte instance name alone. The SQL Server instance name is not a newtwork name
and won't get resolved to an IP/port number.
Can you connect to the default instance (SQL2005) from a machine where you
can't connect to the SQL2000 instance using ServerName\Instance?
Linchi
"karwalr@.hotmail.com" wrote:
> Hi
> We currently have installed sql2005 (installed first as default
> instance) and sql 2000 with a named instance. When developing sites
> and using connection strings, we can access the sql2000 db fine by
> using SERVERNAME\INSTANCENAME.
> However, if we try to connect via enterprise manager from any other
> machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
> and the instance name alone wont work either.
> How do we get round this as at present, we are having to log into the
> database server to make any changes etc!!!
> Novice here so excuse me if I have missed anything obvious!
> Cheers
> Raj
>|||Managed to sort it. I set it up on my client machine Client Network
Alias to map to the server and the port as suggested. Found the
documentation at Microsoft..
http://support.microsoft.com/kb/265808/en-us
Many thanks!

Cant connect to SQL server 2000 instance from domain machines

Hi
We currently have installed sql2005 (installed first as default
instance) and sql 2000 with a named instance. When developing sites
and using connection strings, we can access the sql2000 db fine by
using SERVERNAME\INSTANCENAME.
However, if we try to connect via enterprise manager from any other
machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
and the instance name alone wont work either.
How do we get round this as at present, we are having to log into the
database server to make any changes etc!!!
Novice here so excuse me if I have missed anything obvious!
Cheers
RajThe easiest workaround would be to connect to the instance using its IP
address followed by a comma and then the port number. You should not use jus
t
hte instance name alone. The SQL Server instance name is not a newtwork name
and won't get resolved to an IP/port number.
Can you connect to the default instance (SQL2005) from a machine where you
can't connect to the SQL2000 instance using ServerName\Instance?
Linchi
"karwalr@.hotmail.com" wrote:

> Hi
> We currently have installed sql2005 (installed first as default
> instance) and sql 2000 with a named instance. When developing sites
> and using connection strings, we can access the sql2000 db fine by
> using SERVERNAME\INSTANCENAME.
> However, if we try to connect via enterprise manager from any other
> machine on the domain, we cannot seem to use SERVERNAME\INSTANCENAME
> and the instance name alone wont work either.
> How do we get round this as at present, we are having to log into the
> database server to make any changes etc!!!
> Novice here so excuse me if I have missed anything obvious!
> Cheers
> Raj
>|||Managed to sort it. I set it up on my client machine Client Network
Alias to map to the server and the port as suggested. Found the
documentation at Microsoft..
http://support.microsoft.com/kb/265808/en-us
Many thanks!

Can't connect to new sql server instance

I installed sql server 2000 on a box that already has sql server 2005
installed. I used an instance name of "{machine name}/mssql2k" and I'm
trying to connect using {machine name}/mssql2k. When I open SQL Server
Management Studio and try to connect to the new instance, I get the message
shown below. Please let me know what I need to do to connect.
Thanks,
Keith
TITLE: Connect to Server
Cannot connect to LT-E48643/mssql2k.
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
For help, click:
http://go.microsoft.com/fwlink?ProdN...3&LinkId=20476
BUTTONS:
OK
Change the forward slash to a backward slash, and try again.
Linchi
"Keithb" wrote:

> I installed sql server 2000 on a box that already has sql server 2005
> installed. I used an instance name of "{machine name}/mssql2k" and I'm
> trying to connect using {machine name}/mssql2k. When I open SQL Server
> Management Studio and try to connect to the new instance, I get the message
> shown below. Please let me know what I need to do to connect.
> Thanks,
> Keith
> TITLE: Connect to Server
> --
> Cannot connect to LT-E48643/mssql2k.
> --
> 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: Named Pipes Provider, error: 40 - Could not open a connection to
> SQL Server) (Microsoft SQL Server, Error: 53)
> For help, click:
> http://go.microsoft.com/fwlink?ProdN...3&LinkId=20476
> --
> BUTTONS:
> OK
> --
>
>
|||That did it.
Thanks,
Keith
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:9321139D-EDCF-4D8B-9C06-D67A8A1005E1@.microsoft.com...[vbcol=seagreen]
> Change the forward slash to a backward slash, and try again.
> Linchi
> "Keithb" wrote:

Can't connect to new sql server instance

I installed sql server 2000 on a box that already has sql server 2005
installed. I used an instance name of "{machine name}/mssql2k" and I'm
trying to connect using {machine name}/mssql2k. When I open SQL Server
Management Studio and try to connect to the new instance, I get the message
shown below. Please let me know what I need to do to connect.
Thanks,
Keith
TITLE: Connect to Server
--
Cannot connect to LT-E48643/mssql2k.
--
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
For help, click:
http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
--
BUTTONS:
OK
--Change the forward slash to a backward slash, and try again.
Linchi
"Keithb" wrote:
> I installed sql server 2000 on a box that already has sql server 2005
> installed. I used an instance name of "{machine name}/mssql2k" and I'm
> trying to connect using {machine name}/mssql2k. When I open SQL Server
> Management Studio and try to connect to the new instance, I get the message
> shown below. Please let me know what I need to do to connect.
> Thanks,
> Keith
> TITLE: Connect to Server
> --
> Cannot connect to LT-E48643/mssql2k.
> --
> 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: Named Pipes Provider, error: 40 - Could not open a connection to
> SQL Server) (Microsoft SQL Server, Error: 53)
> For help, click:
> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
> --
> BUTTONS:
> OK
> --
>
>|||That did it.
Thanks,
Keith
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:9321139D-EDCF-4D8B-9C06-D67A8A1005E1@.microsoft.com...
> Change the forward slash to a backward slash, and try again.
> Linchi
> "Keithb" wrote:
>> I installed sql server 2000 on a box that already has sql server 2005
>> installed. I used an instance name of "{machine name}/mssql2k" and I'm
>> trying to connect using {machine name}/mssql2k. When I open SQL Server
>> Management Studio and try to connect to the new instance, I get the
>> message
>> shown below. Please let me know what I need to do to connect.
>> Thanks,
>> Keith
>> TITLE: Connect to Server
>> --
>> Cannot connect to LT-E48643/mssql2k.
>> --
>> 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: Named Pipes Provider, error: 40 - Could not open a connection
>> to
>> SQL Server) (Microsoft SQL Server, Error: 53)
>> For help, click:
>> http://go.microsoft.com/fwlink?ProdName=Microsoft+SQL+Server&EvtSrc=MSSQLServer&EvtID=53&LinkId=20476
>> --
>> BUTTONS:
>> OK
>> --
>>

Can't connect to new sql server instance

I installed sql server 2000 on a box that already has sql server 2005
installed. I used an instance name of "{machine name}/mssql2k" and I'm
trying to connect using {machine name}/mssql2k. When I open SQL Server
Management Studio and try to connect to the new instance, I get the message
shown below. Please let me know what I need to do to connect.
Thanks,
Keith
TITLE: Connect to Server
--
Cannot connect to LT-E48643/mssql2k.
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: Named Pipes Provider, error: 40 - Could not open a connection to
SQL Server) (Microsoft SQL Server, Error: 53)
For help, click:
http://go.microsoft.com/fwlink?Prod...53&LinkId=20476
BUTTONS:
OK
--Change the forward slash to a backward slash, and try again.
Linchi
"Keithb" wrote:

> I installed sql server 2000 on a box that already has sql server 2005
> installed. I used an instance name of "{machine name}/mssql2k" and I'
m
> trying to connect using {machine name}/mssql2k. When I open SQL Serve
r
> Management Studio and try to connect to the new instance, I get the messag
e
> shown below. Please let me know what I need to do to connect.
> Thanks,
> Keith
> TITLE: Connect to Server
> --
> Cannot connect to LT-E48643/mssql2k.
> --
> 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: Named Pipes Provider, error: 40 - Could not open a connection t
o
> SQL Server) (Microsoft SQL Server, Error: 53)
> For help, click:
> http://go.microsoft.com/fwlink?Prod...53&LinkId=20476
> --
> BUTTONS:
> OK
> --
>
>|||That did it.
Thanks,
Keith
"Linchi Shea" <LinchiShea@.discussions.microsoft.com> wrote in message
news:9321139D-EDCF-4D8B-9C06-D67A8A1005E1@.microsoft.com...[vbcol=seagreen]
> Change the forward slash to a backward slash, and try again.
> Linchi
> "Keithb" wrote:
>

Can't connect to named instance from clients

I created a second SQL Server 2000 instance in my computer. I started the
service using the service manager and registered it successfully to the
local Enterprise Manager.
When I try to register the instance to a remote Enterprise Manager or when I
try to create a dsn from another machine to the new instance I get a "SQL
Server is unavailable or does not exist" error.
Sergio Florez M.
Miembro activo www.AlianzaDev.net
El que persevera insiste
Medelln, Colombia
DCE 4
How are you connecting to the instance?
Servername\InstanceName?
"Sergio Florez M." wrote:

> I created a second SQL Server 2000 instance in my computer. I started the
> service using the service manager and registered it successfully to the
> local Enterprise Manager.
> When I try to register the instance to a remote Enterprise Manager or when I
> try to create a dsn from another machine to the new instance I get a "SQL
> Server is unavailable or does not exist" error.
> --
> Sergio Florez M.
> Miembro activo www.AlianzaDev.net
> El que persevera insiste
> MedellXn, Colombia
> DCE 4
>
>

Can't connect to named instance from clients

I created a second SQL Server 2000 instance in my computer. I started the
service using the service manager and registered it successfully to the
local Enterprise Manager.
When I try to register the instance to a remote Enterprise Manager or when I
try to create a dsn from another machine to the new instance I get a "SQL
Server is unavailable or does not exist" error.
Sergio Florez M.
Miembro activo www.AlianzaDev.net
El que persevera insiste
Medelln, Colombia
DCE 4How are you connecting to the instance?
Servername\InstanceName?
"Sergio Florez M." wrote:

> I created a second SQL Server 2000 instance in my computer. I started the
> service using the service manager and registered it successfully to the
> local Enterprise Manager.
> When I try to register the instance to a remote Enterprise Manager or when
I
> try to create a dsn from another machine to the new instance I get a "SQL
> Server is unavailable or does not exist" error.
> --
> Sergio Florez M.
> Miembro activo www.AlianzaDev.net
> El que persevera insiste
> Medell_n, Colombia
> DCE 4
>
>

Cant connect to my SQLExpress Instance

Hello guys,

I've got some troubles , by attempting to connect the SQL Server database to my server.

I've got this error message on the SQL Configuration Manager (when i tried to start SQL Server which was stopped) " The request failed or the service did not respond in a timely fashion.Consult the event log or the other applicable error logs for details "

I found that error log :

2007-12-18 19:36:12.20 Server Server process ID is 5080.
2007-12-18 19:36:12.20 Server Logging SQL Server messages in file'c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG'.
2007-12-18 19:36:12.20 Server This instance of SQL Server last reportedusing a process ID of 1180 at 18/12/2007 19:12:20 (local) 18/12/200719:12:20 (UTC). This is an informational message only; no user actionis required.
2007-12-18 19:36:12.20 Server Registry startup parameters:
2007-12-18 19:36:12.20 Server -d c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\master.mdf
2007-12-18 19:36:12.20 Server -e c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\ERRORLOG
2007-12-18 19:36:12.20 Server -l c:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\DATA\mastlog.ldf
2007-12-18 19:36:12.20 Server SQL Server is starting at normal prioritybase (=7). This is an informational message only. No user action isrequired.
2007-12-18 19:36:12.20 Server Detected 2 CPUs. This is an informational message; no user action is required.
2007-12-18 19:36:12.40 Server Using dynamic lock allocation. Initialallocation of 2500 Lock blocks and 5000 Lock Owner blocks per node.This is an informational message only. No user action is required.
2007-12-18 19:36:12.42 Server Database Mirroring Transport is disabled in the endpoint configuration.
2007-12-18 19:36:12.43 spid4s Starting up database 'master'.
2007-12-18 19:36:12.50 spid4s Error: 9003, Severity: 20, State: 1.
2007-12-18 19:36:12.50 spid4s The log scan number (228:88:1) passed tolog scan in database 'master' is not valid. This error may indicatedata corruption or that the log file (.ldf) does not match the datafile (.mdf). If this error occurred during replication, re-create thepublication. Otherwise, restore from backup if the problem results in afailure during startup.
2007-12-18 19:36:12.50 spid4s Cannot recover the master database. SQLServer is unable to run. Restore master from a full backup, repair it,or rebuild it. For more information about how to rebuild the masterdatabase, see SQL Server Books Online.

I'm on it since this morning and i haven't been able to fix it , none of the web ressources helped me you're my last chance of sleeping tightly :'(

Thank you so much.

Amokrane CHENTIR

welcome to the forums,

after reading the logfile, i think the Master database is damaged , note that SQL server can't work wothout this database .

you need to re-install the Sqlserver , or repair the installation , go to add/remove programs from control panel ,

and repair the SQl server Express Installation.

|||

Thank you very much , i've just tried it and it worked :)

Can't Connect to Multiple SQL Instances over the Internet with SQL Browser Service

I recently setup mutliple instances of SQL Server Express at my office. I have 1 default instance, and two named instances. I can connect to the named instance of the default port of 1433 with Microsoft SQL Management Studio Express, however the other instances on dynamic TCP ports can not be accessed by the instance name over the internet. I have to specify the dynamic TCP port in this form: xxx.uconn.edu/SQLTEST, Port number. My current thinking is that the SQL Browser service should tell Management Studio Express what dynamic port number each SQL instance is listening to. Any ideas?

hi,

CTJohn23 wrote:

I recently setup mutliple instances of SQL Server Express at my office. I have 1 default instance, and two named instances. I can connect to the named instance of the default port of 1433 with Microsoft SQL Management Studio Express,

TCP/IP 1433 is usually reserved for the default instance...

however the other instances on dynamic TCP ports can not be accessed by the instance name over the internet. I have to specify the dynamic TCP port in this form: xxx.uconn.edu/SQLTEST, Port number. My current thinking is that the SQL Browser service should tell Management Studio Express what dynamic port number each SQL instance is listening to. Any ideas?

the SQLBrowser can not "work" over the internet in that way... all enlistment for instance presence are available via an UDP broadcast call on the local area, when no firewall action is involved...

don't know if the "tool" still relies on SQLBrowseConnect ODBC function, like SQL Server 7.0 and 2000 ListAvailableServer used it, an ODBC function (SQLBrowseConnect()) provided by ODBC libraries installed by Mdac;
this is a mechanism working in broadcast calls, which result never are conclusive and consistent, becouse results are influenced of various servers's answer states, answer time, etc.

Until Mdac 2.5, SQLBrowseConnect function works based on a NetBIOS broadcast, on which SQL Servers respond (Default protocol for SQL Server 7.0), while in SQL Server 2000 the rules changed, because the default client protocol changed to TCP/IP and now a UDP broadcast is used, beside a NetBIOS broadcast, listening on port 1434:
which is using a UDP broadcast on port 1434, if instance do not listen or not respond on time they will not be part of the enumeration.

Some basic rules for 7.0 are:
- SQL Servers have to be running on Windows NT or Windows 2000 and have to listen on Named Pipes, that is why in 7.0 Windows 9x SQL Servers will never show up, because they do not listen on Named Pipes.
- The SQL Server has to be running in order to respond on the broadcast. There is a gray window of 15 minutes after shutdown, where a browse master in the domain may respond on the broadcast and answer.
- If you have routers in your network, that do not pass on NetBIOS broadcasts, this might limit your scope of the broadcast.
- Only servers within the same NT domain (or trust) will get enumerated.

In SQL Server 2000 using MDAC 2.6 this changes a little, because now the default protocol has been changed to be TCP/IP sockets and instead of a NetBIOS broadcast, they use a TCP UDP to detect the servers. The same logic still applies roughly.
- SQL Server that are running
- SQL Server that listening on TCP/IP
- Running on Windows NT or Windows 2000 or Windows 9x
- If you use routers and these are configured not to pass UDP broadcasts, only machines within the same subnet show up.

Upgrading to Service Pack 2 of SQL Server 2000 is required in order to have .ListAvailableServer method to work properly, becouse precding release of Sql-DMO Components of Sql Server 2000 present a bug in this area.

Courtesy of Mr. Gert E.R. Drapers
further Information at
http://sqldev.net/misc.htm

The Service Pack 3a introduced some new amenity in order to prevent MSDE 2000 to be hit by Internet worms like Slammer and Saphire virus and to increase security, so that Microsoft decided to default for disabling SuperSockets Network Protocols on new MSDE 2000 installation.
Instances of SQL Server 2000 SP3a or MSDE 2000 SP3a will stop listening on UDP port 1434 when they are configured to not listen on any network protocols. This will stop enlisting these servers.