Cannot enlist with MSX server

We have a server with the default instance and 2 additional named instances running SQL 2000 SP4. Recently I installed another instance for SQL Server 2005. We also use MSX/TSX approach to manage the servers so I tried to enlist the SQL 2005 instance with the master server using the

msdb..sp_msx_enlist @.msx_server_name = N'SQLMON', @.location = N'Datacentre. Margin Lending overnight copy'

and got this error,

Msg 22026, Level 16, State 1, Line 0

The enlist operation failed (reason: SQLServerAgent Error: Unable to connect to MSX 'SQLMON'.)

Looking at the text for this procedure it looks like it reads the wrong registry keys. The procedure it hardcoded to read,

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\SQLServerAgent

This key doesn't exist, but this one does,

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL.1\SQLServerAgent

Is this causing the connection error? I know that the MSX server is available as I can connect and query it in Management Studio.

http://msdn2.microsoft.com/en-us/library/ms365379.aspx

Please take a look at the above link on what has changed in MSX/TSX on security lines.

Also, note that in a mixed(SQL 2K and 2005) multi-server environment MSX can be only SQL 2000. TSXs can be both SQL 2K and 2005

|||

Thanks for your reply. I set the Encryption option to zero.and was able to make the SQL 2005 server a TSX.

When will the encryption option be selecteable in the TSX setup wizard?

|||Unfortunately no. We have a tracking bug for the next release to expose it at SMO and UI level

Cannot edit RS reports...!

You need the Manage reports task. You can get this on a default report server installation by having the Content Manager role.
-Lukasz
This posting is provided "AS IS" with no warranties, and confers no rights.
--Original Message--
From: Kerc
Posted At: Wednesday, October 05, 2005 10:32 AM
Posted To: microsoft.public.sqlserver.reportingsvcs
Conversation: Cannot edit RS reports...!!!
Subject: Cannot edit RS reports...!!!
I'm new at using RS, so please bear with me...
I need to make small changes to existing reports. I'm able to execute
the reports and view the report list through the Report Manager, but I
don't ge the "Edit" options for the reports.
What security options must I have to be able to edit the reports?
Also, are the RDLs stored in the Catalog table? I ask because I can't
find an RDL on the report server to save my life...
Thanks!I just verified and I do have the "Content Manager" role. So far my
experience with RS has been pretty frustrating...

Cannot determine default collation

when i tried to install the lastest MSDE release A, it has this error. How should I solve it?
See the following KB article for more info on this problem:
http://support.microsoft.com/?id=838302
You can avoid the problem by (temporarily) changing your default system
locale to a locale that isn't in the list in that article, reboot, then
retry the installation. You can also avoid the problem by passing the
COLLATION command line parameter to setup (e.g.
"COLLATION=SQL_Latin1_General_CP1_CI_AS".
Bart
Bart Duncan
Microsoft SQL Server Support
Please reply to the newsgroup only - thanks.
This posting is provided "AS IS" with no warranties, and confers no
rights.
Thread-Topic: Cannot determine default collation
thread-index: AcRS8jxBIFmv0lEuTbeceZiciXUOYg==
X-WBNR-Posting-Host: 61.10.7.203
From: =?Utf-8?B?U2Fu?= <San@.discussions.microsoft.com>
Subject: Cannot determine default collation
Date: Tue, 15 Jun 2004 09:03:01 -0700
Lines: 1
Message-ID: <9101766C-F170-4F20-A300-554889E2A0C2@.microsoft.com>
MIME-Version: 1.0
Content-Type: text/plain;
charset="Utf-8"
Content-Transfer-Encoding: 7bit
X-Newsreader: Microsoft CDO for Windows 2000
Content-Class: urn:content-classes:message
Importance: normal
Priority: normal
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
Newsgroups: microsoft.public.sqlserver.msde
NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 127.0.0.1
Path:
cpmsftngxa10.phx.gbl!TK2MSFTFEED01.phx.gbl!TK2MSFT NGXA01.phx.gbl!TK2MSFTNG
XA03.phx.gbl
Xref: cpmsftngxa10.phx.gbl microsoft.public.sqlserver.msde:15056
X-Tomcat-NG: microsoft.public.sqlserver.msde
when i tried to install the lastest MSDE release A, it has this error.
How should I solve it?

Cannot create a new instance in sqlserver 2005

I have installed sqlserver 2005 and by mistake i have made a default instance. I previously had sqlserver 2000 installed on my machine. Now I want to create a new instance of sqlserver 2005 but dont know how to do it .... Please help me on thisInsert the setup media and simply install another instance. Make sure that you applay the service pack afterwards, because the service pack level is maitained per instance.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

Cannot connect to the SQL 2005 Express

I created test project and want to use SQL 2005 database inside.

1. I created Test database with DEFAULT rights

2. I go into server explorer, press Add Connection. Shows message box for connecting to the server: <PCNAME> using windows authntification.

But NO database allowed to view :(.

Which setting should be set for SQL server database to i could connect and work with it?

P.S I use LOCAL connection. The Application and Server should be on the same PC.|||

sqlexpress is a named instance with instance name as "sqlexpress". For local connection, your connection string can be ".\sqlexpress", "(local)\sqlexpress", "<machinename>\sqlexpress", and e.t.c..

some other useful info: http://blogs.msdn.com/sql_protocols/archive/2006/03/23/558651.aspx

|||

I do not use connection string - I use Visual Studio User Interface for connecting. I could try to connect as blind but I want to get list of the databases and connect on click.

Could you please give me advice how I could to do that?

|||In Visual Studio, click Connect to Database in Server Explorer. Under Choose Data Source, select Microsoft SQL Server. Under Data Provider drop-down list, select .NET Framework Data Provider for SQL Server and click Continue. On the Add Connection window, in the Server Name drop-down list, either you type .\SQLEXPRESS or select it in your list. Select the database in the drop-down list and click Test Connection. Once you're done, you now have this connection in your SQL Server 2005 Express database from Visual Studio 2005|||

bass_player wrote:

On the Add Connection window, in the Server Name drop-down list, either you type .\SQLEXPRESS or select it in your list. Select the database in the drop-down list and click Test Connection.

I CANNOT SEE ANY databases, so I CANNOT SELECT invisible (for me) database and because I ask - WHICH RIGHTS I should to set in MS SQL Express to Databases could be visible.

Server list - exist (one server: <PCNAME>)

Databases list is EMPTY!!!!!!

|||

The list is for server, a server can host multiple databases. In order to see your local server in the drop down list, you need to have your SQL Browser running. Did you try to type ".\sqlexpress"?

|||

Aaaaaaa!!!....

I've understood. You all were right. .\sqlexpress is required - and all works.

Thanx bass_player and Xinwei Hong - MSFT

Cannot connect to the Report Mgr.

Hi All,
I'm experiencing the error referenced in the following link to MS
Support
http://support.microsoft.com/Default.aspx?kbid=922656
I implemented the workaround but I'm still getting the error. Actually
when I started I was receiving "error message 1" and then when I
updated my RSWebApplication.config file to use the fully qualified URL
using the IP Address that is assigned to the Default Web Site's "IP
Address" property.
My config file now looks like this...
<ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
<ReportServerVirtualDirectory></ReportServerVirtualDirectory>
The server is a Windows 2003 server and the Reporting Services was
installed with SQL2005 but not configured. I was able to configure the
Reports server (from what I can tell) using the "Reporting Services
Configuration" tool).
Any idea as to what may still be causing the problem?
Thanks in advance for any help you can offer.
Mike Gorgone
Senior Software Engineer
PictureU PromotionsOn Aug 21, 2:06 pm, Mike <m_gorg...@.hotmail.com> wrote:
> Hi All,
> I'm experiencing the error referenced in the following link to MS
> Support
> http://support.microsoft.com/Default.aspx?kbid=922656
> I implemented the workaround but I'm still getting the error. Actually
> when I started I was receiving "error message 1" and then when I
> updated my RSWebApplication.config file to use the fully qualified URL
> using the IP Address that is assigned to the Default Web Site's "IP
> Address" property.
> My config file now looks like this...
> <ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
> <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> The server is a Windows 2003 server and the Reporting Services was
> installed with SQL2005 but not configured. I was able to configure the
> Reports server (from what I can tell) using the "Reporting Services
> Configuration" tool).
> Any idea as to what may still be causing the problem?
> Thanks in advance for any help you can offer.
> Mike Gorgone
> Senior Software Engineer
> PictureU Promotions
The last response in this link might be helpful.
http://www.sqlreportingservices.net/Ask/1730.aspx
Regards,
Enrique Martinez
Sr. Software Consultant|||On Aug 21, 9:55 pm, EMartinez <emartinez...@.gmail.com> wrote:
> On Aug 21, 2:06 pm, Mike <m_gorg...@.hotmail.com> wrote:
>
> > Hi All,
> > I'm experiencing the error referenced in the following link to MS
> > Support
> >http://support.microsoft.com/Default.aspx?kbid=922656
> > I implemented the workaround but I'm still getting the error. Actually
> > when I started I was receiving "error message 1" and then when I
> > updated my RSWebApplication.config file to use the fully qualified URL
> > using the IP Address that is assigned to the Default Web Site's "IP
> > Address" property.
> > My config file now looks like this...
> > <ReportServerUrl>http://10.0.0.102:80/Reports</ReportServerUrl>
> > <ReportServerVirtualDirectory></ReportServerVirtualDirectory>
> > The server is a Windows 2003 server and the Reporting Services was
> > installed with SQL2005 but not configured. I was able to configure the
> > Reports server (from what I can tell) using the "Reporting Services
> > Configuration" tool).
> > Any idea as to what may still be causing the problem?
> > Thanks in advance for any help you can offer.
> > Mike Gorgone
> > Senior Software Engineer
> > PictureU Promotions
> The last response in this link might be helpful.http://www.sqlreportingservices.net/Ask/1730.aspx
> Regards,
> Enrique Martinez
> Sr. Software Consultant
Hi Enrique,
Thanks for the link. I've seen some information along those same lines
but I can't set the IP Address property to "All Addresses" the IP
needs to be set to the specific address we have in there.
Is there any war around that?
Mike

Cannot connect to SQL server with NT groups

Hi.
Have problems connecting to SQL server with NT group authentication.
Get error 4064: Error connecting to user default database.

There's no problems connecting with NT users og SQL users.

SQL2000 + Windows2000 both running latest service packs. All SP have been reinstalled.

The server suddenly stopped accepting NT group logins. It have been running for 1 year with no problems - 4 days ago it started generating this error.

Any ideas anyone?Talk to the network guys...something changed...

Cannot Connect to SQL Server Analysis Services - 2005

Help please!!! I tried everything I can think of - several re-installs, but I still can't connect to Analysis Services (named or default).

My SQL is installed on XP Pro. I get the following error message:

TITLE: Connect to Server

Cannot connect to RBM.

ADDITIONAL INFORMATION:

A connection cannot be made. Ensure that the server is running. (Microsoft.AnalysisServices.AdomdClient)

No connection could be made because the target machine actively refused it (System)

BUTTONS:

OK

===================================

Cannot connect to RBM.

===================================

A connection cannot be made. Ensure that the server is running. (Microsoft.AnalysisServices.AdomdClient)

Program Location:

at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.OpenTcpConnection(ConnectionInfo connectionInfo)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.Connect(ConnectionInfo connectionInfo, Boolean beginSession)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.XmlaClientProvider.Microsoft.AnalysisServices.AdomdClient.AdomdConnection.IXmlaClientProviderEx.ConnectXmla()
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.ConnectToXMLA(Boolean createSession, Boolean isHTTP)
at Microsoft.AnalysisServices.AdomdClient.AdomdConnection.Open()
at Microsoft.SqlServer.Management.UI.VSIntegration.ObjectExplorer.ObjectExplorer.ValidateConnection(UIConnectionInfo ci, IServerType server)
at Microsoft.SqlServer.Management.UI.ConnectionDlg.Connector.ConnectionThreadUser()

===================================

No connection could be made because the target machine actively refused it (System)

Program Location:

at System.Net.Sockets.Socket.DoConnect(EndPoint endPointSnapshot, SocketAddress socketAddress)
at System.Net.Sockets.Socket.Connect(EndPoint remoteEP)
at System.Net.Sockets.TcpClient.Connect(IPEndPoint remoteEP)
at System.Net.Sockets.TcpClient.Connect(IPAddress address, Int32 port)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClientByAddress(String hostName, Int32 port)
at Microsoft.AnalysisServices.AdomdClient.XmlaClient.GetTcpClient(ConnectionInfo connectionInfo)

What am I doing wrong? Does anyone have the answer? Microsoft? What is wrong? Help please!! - Hope your listenning to all the frustrations. I never had these issues with SQL 2000 - Analysis Services worked just terrific.

I need to get this working soon. Any help will be greatly appreciated.

Thanks in advance to everyone.

Start by disabling the XP firewall. I have seen this message before when talking to the wrong port, or hitting SSAS 2000.

If this works you can configure the XP fiewwall to only have the relevant port open.

Cannot connect to second cluster node w/instance name

I have an active/active SQL2005 cluster. Node1 has a default instance of
SQL 2005 installed (i.e. no named instance). Node2 has a named instance of
SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005
without problem. When I attempt to connect to node2 remotely I get an error
basically stating "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)".
When I connect I am using node2\sqlb as the connection name--this should
give me access to the named instance. I can however access node2\sqlb from
node2 directly (locally on the server). Yes, I have made sure named pipes
and tcp/ip are enabled. Made sure no firewalls, etc. The weird thing is
that I was able to make a remote connection for a short time (like two
hours) and then I couldn't anymore.
I am using a Windows Vista Ultimate RTM machine with SQL 2005 management
console installed locally. Any information would be greatly appreciated.
Is the SQL Server Browser Service running to provide the tcp port number for
the named instance?
If not, what port is the named instance listening on? Can you connect to
node2,<port number> ?
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"JPerkins" <joshp@.CUIAB.LOCAL> wrote in message
news:DBDEDBC3-AEF7-48E0-91D7-25977A8AEBB9@.microsoft.com...
>I have an active/active SQL2005 cluster. Node1 has a default instance of
>SQL 2005 installed (i.e. no named instance). Node2 has a named instance of
>SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005
>without problem. When I attempt to connect to node2 remotely I get an
>error basically stating "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)".
> When I connect I am using node2\sqlb as the connection name--this should
> give me access to the named instance. I can however access node2\sqlb
> from node2 directly (locally on the server). Yes, I have made sure named
> pipes and tcp/ip are enabled. Made sure no firewalls, etc. The weird
> thing is that I was able to make a remote connection for a short time
> (like two hours) and then I couldn't anymore.
> I am using a Windows Vista Ultimate RTM machine with SQL 2005 management
> console installed locally. Any information would be greatly appreciated.

Cannot connect to second cluster node w/instance name

I have an active/active SQL2005 cluster. Node1 has a default instance of
SQL 2005 installed (i.e. no named instance). Node2 has a named instance of
SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005
without problem. When I attempt to connect to node2 remotely I get an error
basically stating "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)".
When I connect I am using node2\sqlb as the connection name--this should
give me access to the named instance. I can however access node2\sqlb from
node2 directly (locally on the server). Yes, I have made sure named pipes
and tcp/ip are enabled. Made sure no firewalls, etc. The weird thing is
that I was able to make a remote connection for a short time (like two
hours) and then I couldn't anymore.
I am using a Windows Vista Ultimate RTM machine with SQL 2005 management
console installed locally. Any information would be greatly appreciated.Is the SQL Server Browser Service running to provide the tcp port number for
the named instance?
If not, what port is the named instance listening on? Can you connect to
node2,<port number> ?
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.
"JPerkins" <joshp@.CUIAB.LOCAL> wrote in message
news:DBDEDBC3-AEF7-48E0-91D7-25977A8AEBB9@.microsoft.com...
>I have an active/active SQL2005 cluster. Node1 has a default instance of
>SQL 2005 installed (i.e. no named instance). Node2 has a named instance of
>SQL 2005 (i.e. node2\sqlb). I can connect remotely to node1 SQL 2005
>without problem. When I attempt to connect to node2 remotely I get an
>error basically stating "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)".
> When I connect I am using node2\sqlb as the connection name--this should
> give me access to the named instance. I can however access node2\sqlb
> from node2 directly (locally on the server). Yes, I have made sure named
> pipes and tcp/ip are enabled. Made sure no firewalls, etc. The weird
> thing is that I was able to make a remote connection for a short time
> (like two hours) and then I couldn't anymore.
> I am using a Windows Vista Ultimate RTM machine with SQL 2005 management
> console installed locally. Any information would be greatly appreciated.

Cannot connect to Remote SQL Server Named Instance

Hi...
On a remote server, I have SQL 2005 installed as the default instance as
well as a new named instance.
From SQLCMD, I can connect to both instances. However, from Management
Studio, I can only connect to the default instance. Is there something
special I have to do to connect to the named instance? I try connecting
using:
[My-Server-Name]/InstanceName
Any ideas? I get the "error locating server/instance specified" generic
error.
Thanks![/] is also not allowed for a servername -the instance is part of the na
me.
So put the square brackets around the entire [server/instance] name.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
"Forch" <Forch@.discussions.microsoft.com> wrote in message
news:DE18DCC1-CA47-4066-8E34-2ED8250A9DD5@.microsoft.com...
> Hi...
> On a remote server, I have SQL 2005 installed as the default instance as
> well as a new named instance.
> From SQLCMD, I can connect to both instances. However, from Management
> Studio, I can only connect to the default instance. Is there something
> special I have to do to connect to the named instance? I try connecting
> using:
> [My-Server-Name]/InstanceName
> Any ideas? I get the "error locating server/instance specified" generic
> error.
> Thanks!|||Use SQL Server Configuration Manager and for the Services,
make sure the SQL Browser Service is running.
-Sue
On Thu, 10 Aug 2006 09:06:01 -0700, Forch
<Forch@.discussions.microsoft.com> wrote:

>Hi...
>On a remote server, I have SQL 2005 installed as the default instance as
>well as a new named instance.
>From SQLCMD, I can connect to both instances. However, from Management
>Studio, I can only connect to the default instance. Is there something
>special I have to do to connect to the named instance? I try connecting
>using:
>[My-Server-Name]/InstanceName
>Any ideas? I get the "error locating server/instance specified" generic
>error.
>Thanks!|||Thanks for the suggestion. Unfortunately it didn't work...
The name without the square brackets works with Management Studio locally.
Do you have any other ideas?
Thanks,
Mark
"Arnie Rowland" wrote:

> [/] is also not allowed for a servername -the instance is part of the
name.
> So put the square brackets around the entire [server/instance] name.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
>
> "Forch" <Forch@.discussions.microsoft.com> wrote in message
> news:DE18DCC1-CA47-4066-8E34-2ED8250A9DD5@.microsoft.com...
>
>

Cannot connect to MSDE database from Enterprise Manager

Hello,
I try to access a MSDE 2000 3.0a Database installed on Windows Server 2003 a
s the default instance.
MSDE has been installed with the following options:
[Options]
TARGETDIR="C:\Program Files\MSDE 2000\"
SAPWD="<My Password>"
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
I try to connect to this MSDE database from another machine where SQL Server
2000 3.0a is running, using the Enterprise Manager.
In Enterprise Manager I enter the IP-address of the server where the MSDE-da
tabase is running and choose the option "Connect using the SQl server login
information..." where I enter "sa" and "<My Password>", the same assigned to
MSDE during setup.
As result I always get the message: "SQL Server does not exist or access is
denied. ConnectionOpen (Connect())".
I don't have any more ideas about what might be wrong...
Can anybody help me please?Are you sure MSDE isn't a named instance (so you would enter <ip
address>\<instance name> )?
"Roberto Rocco" <roberto@.rocco.de> wrote in message
news:eHYPhUZ0DHA.3196@.TK2MSFTNGP11.phx.gbl...
Hello,
I try to access a MSDE 2000 3.0a Database installed on Windows Server 2003
as the default instance.
MSDE has been installed with the following options:
[Options]
TARGETDIR="C:\Program Files\MSDE 2000\"
SAPWD="<My Password>"
DISABLENETWORKPROTOCOLS=0
SECURITYMODE=SQL
I try to connect to this MSDE database from another machine where SQL Server
2000 3.0a is running, using the Enterprise Manager.
In Enterprise Manager I enter the IP-address of the server where the
MSDE-database is running and choose the option "Connect using the SQl server
login information..." where I enter "sa" and "<My Password>", the same
assigned to MSDE during setup.
As result I always get the message: "SQL Server does not exist or access is
denied. ConnectionOpen (Connect())".
I don't have any more ideas about what might be wrong...
Can anybody help me please?|||Hello Foo,
thank you for your fast reply. Yes, I am sure that it is the default
instance.
Meanwhile I made some other tests: Running the same MSDE installation on
another machine (Windows XP) with the same Options.ini file (same settings,
same password, etc.) works pretty well!!
So I guess it must be "something" on the Windows 2003 Server.
I checked if it has a firewall configured, but it has not.
Can some ports be disabled on the Windows 2003 Server?
Are there other places to check?
Roberto.
"Foo Man Chew" <foo@.man.chew> schrieb im Newsbeitrag
news:OHbGqBa0DHA.2580@.TK2MSFTNGP09.phx.gbl...

quote:

---

> Are you sure MSDE isn't a named instance (so you would enter <ip
> address>\<instance name> )?
>
>
> "Roberto Rocco" <roberto@.rocco.de> wrote in message
> news:eHYPhUZ0DHA.3196@.TK2MSFTNGP11.phx.gbl...
> Hello,
> I try to access a MSDE 2000 3.0a Database installed on Windows Server 2003
> as the default instance.
> MSDE has been installed with the following options:
> [Options]
> TARGETDIR="C:\Program Files\MSDE 2000\"
> SAPWD="<My Password>"
> DISABLENETWORKPROTOCOLS=0
> SECURITYMODE=SQL
> I try to connect to this MSDE database from another machine where SQL

---

Server

quote:

---

> 2000 3.0a is running, using the Enterprise Manager.
> In Enterprise Manager I enter the IP-address of the server where the
> MSDE-database is running and choose the option "Connect using the SQl

---

server

quote:

---

> login information..." where I enter "sa" and "<My Password>", the same
> assigned to MSDE during setup.
> As result I always get the message: "SQL Server does not exist or access

---

is

quote:

---

> denied. ConnectionOpen (Connect())".
> I don't have any more ideas about what might be wrong...
> Can anybody help me please?
>

---

|||Problem solved!
Port 1433 was blocked on the Windows 2003 Server. After adjusting the Packet
Filter Policies to permit Port 1433 access I was able to connect to the MSDE
database.
Thanks all for your support.
Roberto.
"Roberto Rocco" <roberto@.rocco.de> schrieb im Newsbeitrag
news:OTXwf%23f0DHA.1532@.TK2MSFTNGP10.phx.gbl...

quote:

---

> Hello Foo,
> thank you for your fast reply. Yes, I am sure that it is the default
> instance.
> Meanwhile I made some other tests: Running the same MSDE installation on
> another machine (Windows XP) with the same Options.ini file (same

---

settings,

quote:

---

> same password, etc.) works pretty well!!
> So I guess it must be "something" on the Windows 2003 Server.
> I checked if it has a firewall configured, but it has not.
> Can some ports be disabled on the Windows 2003 Server?
> Are there other places to check?
> Roberto.
> "Foo Man Chew" <foo@.man.chew> schrieb im Newsbeitrag
> news:OHbGqBa0DHA.2580@.TK2MSFTNGP09.phx.gbl...
2003[QUOTE]
> Server
> server
> is
>

---

|||Hi.
I have the same problem, I have changed the TCP/IP filtering under the
TCP/IP setting on the network adapter to 'Enable TCP/IP Filtering' and
set to 'Permit All' on all types, but it still doesn't work. Are you
talking about something else? If so can you post a short guide of what
to change and where it is found in the Windows 2003 maze.
Thanks
Best Regards
Andrew.
da644
---
Posted via http://www.mcse.ms
---
View this thread: http://www.mcse.ms/message238297.html

Cannot connect to an instance of SQL 2000

I have a server running SQL 2005 as the default instance, and sql server 2000 running as a named instance called SQL2000. When I try to connect to my SQL instance Servername\SQL2000, i am actually connected to my SQL 2005 instance. When I connect using SQL 2000's Entreprise manager, i get the error saying you need to use SQL 2005 connectivity tools. Any Ideas?

You can connect to SQL2K using 2K5 tools. Follow the directions at this link:

http://msdn2.microsoft.com/en-us/library/ms345332.aspx

|||

Sorry, but when i connect to the sql2000 instance using 2005 tools, i connect to the defuaalt SQL instance on this machine which is sql2005.

When I use Entreprise manager from the local system, i can connect to the sql 2000 instance just fine.

|||

Can you post the exact steps your doing including exactly what you're typing in and where?

Cheers,

Dan

Cannot connect to an instance of SQL 2000

I have a server running SQL 2005 as the default instance, and sql server 2000 running as a named instance called SQL2000. When I try to connect to my SQL instance Servername\SQL2000, i am actually connected to my SQL 2005 instance. When I connect using SQL 2000's Entreprise manager, i get the error saying you need to use SQL 2005 connectivity tools. Any Ideas?

You can connect to SQL2K using 2K5 tools. Follow the directions at this link:

http://msdn2.microsoft.com/en-us/library/ms345332.aspx

|||

Sorry, but when i connect to the sql2000 instance using 2005 tools, i connect to the defuaalt SQL instance on this machine which is sql2005.

When I use Entreprise manager from the local system, i can connect to the sql 2000 instance just fine.

|||

Can you post the exact steps your doing including exactly what you're typing in and where?

Cheers,

Dan

Cannot connect to an express instance in Management Studio

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 th
e
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.
(provide: SQL Network Interfaces, error: 26 - Error Locating Server/Instance
Specified) (Microsoft SQL Server)
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
AUTHORITY\NetworkService.
3. SQL Server Browser service is not running.
4. Has tried to disable Windows Firewall
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?Peter (Peter@.discussions.microsoft.com) writes:
> 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:
Just a check: did you explicitly install SQL Server Express as a
default instance? (Since by default Express is installed as a named
instance.)
How do you specify the instance when you try to connect?

> Can such error caused by not having sufficient memory so the system is
> running kind of slow?
I would not really think this is an issue? How much memory is there in the
box althogether? How much is used by other applications?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Hi Erland,
I actually want to say the default named instance (SQLEXPRESS).
Peter
"Erland Sommarskog" wrote:

> Peter (Peter@.discussions.microsoft.com) writes:
> Just a check: did you explicitly install SQL Server Express as a
> default instance? (Since by default Express is installed as a named
> instance.)
> How do you specify the instance when you try to connect?
>
> I would not really think this is an issue? How much memory is there in the
> box althogether? How much is used by other applications?
>
> --
> Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
> Books Online for SQL Server 2005 at
> http://www.microsoft.com/technet/pr...oads/books.mspx
> Books Online for SQL Server 2000 at
> http://www.microsoft.com/sql/prodin...ions/books.mspx
>|||Peter (Peter@.discussions.microsoft.com) writes:
> I actually want to say the default named instance (SQLEXPRESS).
And you specify it as .\SQLEXPRESS in MgmtStudio?
Can you connect to it through SQLCMD?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx

Cannot connect to a default Express instance

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
AUTHORITY\NetworkService.
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?

KBA http://support.microsoft.com/kb/914277 should take you through.|||

Hi Satya,

Since I'm using Management Studio Express to connect to a local instance (computername\SQLEXPRESS), I don't think that it is a remote connection issue.

Peter