sql report manager: instance

Showing posts with label instance. Show all posts

Tuesday, March 27, 2012

Can't start sql agent

Hi there,
I install SQL server 2000 in Win 2000 server with SQL SP3
and Win 2000 SP4.
The SQL is default instance and use local system as
service startup account.
Currently I change the startup services account from local
system to domain user account.
SQL Server success start but the sql agant no! I don't
know why? I check the error message - it say cannot
connect local server.
Now I change back the sql agent startup agent to local
system but it still can't start!!
Please help cause I need SQL agent!!
ThanksMay be that the BUILTIN\Administrators group was dropped from SQL Server. If
so, recreate it.
--
Sérgio Monteiro - Brasil
www.sqlpass.org
"Chai" <wingschai@.hotmail.com> escreveu na mensagem
news:082a01c38a25$78aa36f0$a401280a@.phx.gbl...
> Hi there,
> I install SQL server 2000 in Win 2000 server with SQL SP3
> and Win 2000 SP4.
> The SQL is default instance and use local system as
> service startup account.
> Currently I change the startup services account from local
> system to domain user account.
> SQL Server success start but the sql agant no! I don't
> know why? I check the error message - it say cannot
> connect local server.
> Now I change back the sql agent startup agent to local
> system but it still can't start!!
> Please help cause I need SQL agent!!
> Thanks|||I'd check what the SQL Server instance is listening on. In the errorlog, you
should find entries similar to the following:
2003-10-03 20:45:28.95 server SQL server listening on 67.83.16.85: 1058.
2003-10-03 20:45:28.95 server SQL server listening on 127.0.0.1: 1058.
2003-10-03 20:45:32.49 server SQL server listening on TCP, Shared Memory,
Named Pipes.
Also, you may want to log into the SQL Server box with the SQL Agent account
and try osql -S<ServerName> -E from the command line.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Chai" <wingschai@.hotmail.com> wrote in message
news:082a01c38a25$78aa36f0$a401280a@.phx.gbl...
> Hi there,
> I install SQL server 2000 in Win 2000 server with SQL SP3
> and Win 2000 SP4.
> The SQL is default instance and use local system as
> service startup account.
> Currently I change the startup services account from local
> system to domain user account.
> SQL Server success start but the sql agant no! I don't
> know why? I check the error message - it say cannot
> connect local server.
> Now I change back the sql agent startup agent to local
> system but it still can't start!!
> Please help cause I need SQL agent!!
> Thanks|||If I'm not mistaken, a different error (other than cannot connect to local
server) would be issued if you drop BUILTIN\Administrators from SQL Server
and then try to start SQLServerAgent.
By the way, SQL Server Agent log file SQLAgent.out may contain useful info.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Sérgio Monteiro" <shsmonteiro@.horizon.com.br> wrote in message
news:ucRO6piiDHA.3204@.TK2MSFTNGP11.phx.gbl...
> May be that the BUILTIN\Administrators group was dropped from SQL Server.
If
> so, recreate it.
> --
> Sérgio Monteiro - Brasil
> www.sqlpass.org
> "Chai" <wingschai@.hotmail.com> escreveu na mensagem
> news:082a01c38a25$78aa36f0$a401280a@.phx.gbl...
> > Hi there,
> >
> > I install SQL server 2000 in Win 2000 server with SQL SP3
> > and Win 2000 SP4.
> >
> > The SQL is default instance and use local system as
> > service startup account.
> >
> > Currently I change the startup services account from local
> > system to domain user account.
> >
> > SQL Server success start but the sql agant no! I don't
> > know why? I check the error message - it say cannot
> > connect local server.
> >
> > Now I change back the sql agent startup agent to local
> > system but it still can't start!!
> >
> > Please help cause I need SQL agent!!
> >
> > Thanks
>|||You're right. The exact message is "SQLServerAgent could not be started
(reason: SQLServerAgent must be able to
connect to SQLServer as SysAdmin, but '(Unknown)' is not a member of the
SysAdmin role). "
But I remember one situation in which I faced this issue and somebody had
dropped the BUILTIN\Administrators. May be I'm confusing the situations.
Sérgio Monteiro - Brasil
www.sqlpass.org
"Linchi Shea" <linchi_shea@.NOSPAMml.com> escreveu na mensagem
news:#kncH4iiDHA.1692@.TK2MSFTNGP10.phx.gbl...
> If I'm not mistaken, a different error (other than cannot connect to local
> server) would be issued if you drop BUILTIN\Administrators from SQL Server
> and then try to start SQLServerAgent.
> By the way, SQL Server Agent log file SQLAgent.out may contain useful
info.
> --
> Linchi Shea
> linchi_shea@.NOSPAMml.com
>
> "Sérgio Monteiro" <shsmonteiro@.horizon.com.br> wrote in message
> news:ucRO6piiDHA.3204@.TK2MSFTNGP11.phx.gbl...
> > May be that the BUILTIN\Administrators group was dropped from SQL
Server.
> If
> > so, recreate it.
> >
> > --
> > Sérgio Monteiro - Brasil
> > www.sqlpass.org
> > "Chai" <wingschai@.hotmail.com> escreveu na mensagem
> > news:082a01c38a25$78aa36f0$a401280a@.phx.gbl...
> > > Hi there,
> > >
> > > I install SQL server 2000 in Win 2000 server with SQL SP3
> > > and Win 2000 SP4.
> > >
> > > The SQL is default instance and use local system as
> > > service startup account.
> > >
> > > Currently I change the startup services account from local
> > > system to domain user account.
> > >
> > > SQL Server success start but the sql agant no! I don't
> > > know why? I check the error message - it say cannot
> > > connect local server.
> > >
> > > Now I change back the sql agent startup agent to local
> > > system but it still can't start!!
> > >
> > > Please help cause I need SQL agent!!
> > >
> > > Thanks
> >
> >
>

Tuesday, March 20, 2012

Can't see the SQL Server Express Instance on SQL Browser

Hi All,

I am using SQL Server Express to connect to the network using VPN on a local machine. I have done the following..

a.) Enabled the remote connections for the Express Instance and rebooted the machine.

b.) Connected to the machine with Express Edition locally and can also connect other SQL Server instances from it to verify connectivity.

c.) Yes, SQL Browser Service is running.

d.) Firewall is not turned on, so I do not have to configure any exceptions.

Now here is the big problem: When I browse for SQL Servers on the network the machine does not show up on the list, i.e "macinename\SQLExpress". I had uninstalled and reinstalled the Express edition and rebooted the machine several times with no luck on the SQL Express Instance showing up on the browser list. I even changed the default instance name to "machinename\MACHINE1" on one of the reinstalls. However, I can connect to other SQL Instances from it. But, I cannot connect to it from other machines since its not registered on the network. I have been working on this for the past few days by looking for a solution via this and other forumns. Is there some setting somewhere that I am missing that prevents this instance from not showing up on the browser list. This issue with SQL Express Edition is baffling as well as frustrating and any ideas that can resolve this issue is very much appreciated.

when you say you cant see it on the list, do you mean in the ODBC dialog list? or some other list? if its involves the ODBC dialog, ive had to actually type in the whole machinename \SQLExpress since it didnt show up initially for it to work.|||I am talking about the SQL Server Browser list, that one can see all of the live SQL Server database Instances. Not the dialog list...|||I have several of them that refuse to show up in any browser list. But, I can connect to just about all of them even though they don't show up in the browser list by just typing in the instance name. Is there a particular error that you are getting? Can you give us more detail on your configuration and exactly what steps you are doing?|||

After installing SQL Server Express Edition on a new HP laptop with WIN 2K sp2, I went to see if it was registered on the Network as "machinename/SQLEXPRESS", and what I can see on the Network is just the "machinename", with the instance name missing. So I reinstalled it with a new instance name "machinename/Machine1", and again it was missing the instance name "Machine1", but I can see the machinename. I tried to connect with the instance name only "Machine1" and believe me I have tried it every which way but I always get the infamous 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)"

Now here is the odd part, I had installed SQL Server Express Edition on a older (1 year) IBM laptop with WIN 2K sp2, about 1 month back and was able to see the complete instance name on the network and can connect just fine. The only difference in these two machines is the age, but they both have the same OS Software installed. I have been pulling my hair in trying to figure out what is going on with SQL Server Express Edition on this new HP laptop with WIN 2K sp2 installed. It just refuses to register itself correctly on the network.

|||I have several that the browser only sees the machine name. That still doesn't mean that is what you use for the connection string. If you are using a default instance of Express Edition, then you still need to connect to machinename\SQLExpress even if browsing only shows you just the machine name. Now, that doesn't mean that you aren't having issues similar to mine on one of my clients which refuses to allow me to connect, we just need to make sure there isn't something else wrong first.|||As I have mentioned before, I tried using "machinename\MACHINE1" as the complete instance name and it throws out the error as I posted before. I can connect other instances from this HP Laptop but cannot connect to it from other machines. Perhaps we are having the same issue. I have been asking our Network Admin, System Admin and Security Admin and they are all puzzled by this SQL Express behavior on this HP laptop. I am wondering if it has anything to do with particular PC machines as the IBM pc works fine, but not the HP, this is just a guess. But I am running out of ideas and my users are running out of patience as I try to find a solution to this big problem....|||

Not sure if this has anything to do with your issue, but you mentioned that you were using Win2000 SP2, that is not a supported platform for SQL 2005, you need to be running SP4. I'm surprised that install didn't block.

Mike

|||

Yes, it looks like you are having exactly the same issue as I'm having on one of my machines. I have everything configured correctly with all of the access configured the way it needs to be. I can quite literally do anything I want to on the client when I'm RDPed into the server including remotely launching applications, remotely stopping start services, etc. The only that that it refuses to do is recognize and connect to the SQL Server Express Edition instance. I'm having problem doing further troubleshooting and opening a support case is rather difficult since the problem machine is in CA and I'm in TX without any direct ability to get hands on with the machine. I thought I had another one exhibiting this behavior, but when I plugged the laptop into my network, it magically started working and it hasn't thrown the error since. Yes, I'm rather baffled. My only saving grace is that I don't have any more hair to pull out at this point. :)

I have several more machines to work through and I'm hoping that I can get at least one of them to exhibit this behavior.

|||

I'm getting a bit closer on my side and now have 2 machines that are having issues. So, I want to try something and see if your results duplicate mine.

Log on to the machine that is having problems using your accouunt. Once it is up and running, go over to another instance and login to the Express instance from the other machine using your Windows credentials. Let me know if that magically makes it work.

|||

Hi Michael,

Nope, I tried as you suggested and I keep getting that same error, from the other machine when I try to connect to the problem machine. However, I can connect from the problem machine to any other SQL Server 2005 instance...Do not know what to do at this point. Perhaps Microsoft needs to help out...I hope they are reading this Message.

|||I am wondering if this issue has anything to do with having 2 NIC cards in a Laptop machine, one for the Local Network and the other for the Wireless Network...That is the only difference I see with the 2 different Laptops I am working with. The IBM machine does not have a Wireless Network NIC and it works...The other newer HP has a Wireless NIC and it does not work..Is Microsoft listening.....|||I can rule that one out. I have machines that connect just fine with multiple NICs and a couple that don't that also have multiple NICs.|||Have you tried opening a support case with Microsoft. I am not sure how this particular Software is supported since it is freely distributed..|||

SQL Server Express Edition is fully supported. Just like you can call in and get support on Internet Explorer.

I found a couple of other things when I was doing additional configuration. Verify that your WINS scopes are set properly. Also verify that the machine is actually getting its IP address correctly registered into DNS. These two items fixed 100% of the connectivity issues that I was having within SQL Server.

Cant See SQL instance from one machine

Hello,
What would cause the inability to see a SQL instance from one machine. I
may not be asking correctly, so I will try to explian.
On 3 out of 4 network workstations (XP SP2), I can see the instance (
servername\instancename ) of the SQL db on the Win2003 server. On the
fourth identical workstation I see the ( servername ) but no actual
DBinstance name. What could be the issue here? Any help really
appreciated!
Thank you
Chris Knapp
Hi,
Looks like for the 4th instance you have installed a Default instance of sql
server. In that case you will have only Server name.
Thanks
Hari
SQL Server MVP
"Chris Knapp" <sboldman_at_gmail_dot_com> wrote in message
news:Oda352bUFHA.3952@.TK2MSFTNGP15.phx.gbl...
> Hello,
> What would cause the inability to see a SQL instance from one machine. I
> may not be asking correctly, so I will try to explian.
> On 3 out of 4 network workstations (XP SP2), I can see the instance (
> servername\instancename ) of the SQL db on the Win2003 server. On the
> fourth identical workstation I see the ( servername ) but no actual
> DBinstance name. What could be the issue here? Any help really
> appreciated!
> Thank you
> Chris Knapp
>
|||Hello, and thank you for the reply.
I'm not sure I understand correctly.
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed. Then
there are four XP workstations that connect to the databases on
(server1\manufacturing). Three of the workstations see the (
server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
Thank you so much for any other help you can provide.
Chris Knapp
"Hari Prasad" <hari_prasad_k@.hotmail.com> wrote in message
news:%23wUlRMiUFHA.2892@.TK2MSFTNGP14.phx.gbl...
> Hi,
> Looks like for the 4th instance you have installed a Default instance of
> sql
> server. In that case you will have only Server name.
> Thanks
> Hari
> SQL Server MVP
> "Chris Knapp" <sboldman_at_gmail_dot_com> wrote in message
> news:Oda352bUFHA.3952@.TK2MSFTNGP15.phx.gbl...
>

Can't see named instance

I have a client running NT 4.0 on one of his workstations. For some reason f
rom that machine he can't see the named Instance on the Server (MyServer\MyI
nstance) and therefore can't connect to the database. If I pull up a list of
available servers, the Ser
ver comes up on the list, just not the named instance. ANy ideas on what mig
ht be causing this?Old version of MDAC. Apply the latest supported MDAC for NT 4.0 and the
client can connect. Alternatively, you can create an alias on the client
that includes the port number and connect via it.
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Sean" <anonymous@.discussions.microsoft.com> wrote in message
news:2E49EBDD-9A7E-4772-9241-FA5A3EFA50C1@.microsoft.com...
> I have a client running NT 4.0 on one of his workstations. For some reason
from that machine he can't see the named Instance on the Server
(MyServer\MyInstance) and therefore can't connect to the database. If I pull
up a list of available servers, the Server comes up on the list, just not
the named instance. ANy ideas on what might be causing this?|||Yeah, thanks, that was it. Was getting burned by the user rights. The instal
l is supposed to load version 2.7 but I don't think the user had enough righ
ts on the box to do it.

Can't see named instance

I have a client running NT 4.0 on one of his workstations. For some reason from that machine he can't see the named Instance on the Server (MyServer\MyInstance) and therefore can't connect to the database. If I pull up a list of available servers, the Server comes up on the list, just not the named instance. ANy ideas on what might be causing this?Old version of MDAC. Apply the latest supported MDAC for NT 4.0 and the
client can connect. Alternatively, you can create an alias on the client
that includes the port number and connect via it.
--
Geoff N. Hiten
Microsoft SQL Server MVP
Senior Database Administrator
Careerbuilder.com
I support the Professional Association for SQL Server
www.sqlpass.org
"Sean" <anonymous@.discussions.microsoft.com> wrote in message
news:2E49EBDD-9A7E-4772-9241-FA5A3EFA50C1@.microsoft.com...
> I have a client running NT 4.0 on one of his workstations. For some reason
from that machine he can't see the named Instance on the Server
(MyServer\MyInstance) and therefore can't connect to the database. If I pull
up a list of available servers, the Server comes up on the list, just not
the named instance. ANy ideas on what might be causing this?

Sunday, March 11, 2012

Can't Route to another LOCAL Broker Instance

Hi Remus,

I am experiencing the same problem, and I can't get the easy fix to work. I drop and create the DB's in between tests, so it is not related to having an old certificate in the DB, as in the case of Tilfried.

The situation is as follows:

DB1 owned by login1, has a user for login2; this DB is for the initiator

DB2 owned by login2, has a user for login1; this DB hosts the target

Both DB's have TRUSTWORTHY flag set to ON

Error in sys.transmission_queue: 'Error 916, State 3: The server principal "Login1" is not able to access the database "DB2" under the current security context.

Going on a limp, I decide to add a remote service binding in DB1, binding the user for Login2 to the target service, even though BOL explicitly states that this is only required for cross-server communications. This does change the situation - I still get an error, but a new message is sys.transmission_queue: "Dialog security is unavailable for this covnersation because there is no certificate bound to the database principal (Id: 5). Either create a certificate for the principal, or specify ENCRYPTION = OFF when beginning the conversation." I already know that the first option works, but I wanted to get the simple solution running. As for the second option, I doublechecked and the initiating procedure DOES already specify ENCRYPTION = OFF in the BEGIN DIALOG CONVERSATION command. My theory is that the remote service binding somehow forces SB to use encryption, but (a) that is not stated in the error message, and (b) if so, then how to get the messages sent over to the target service without using the binding?

==> EDIT: Just saw that you confirmed this theory in your last reply to Tlifried. So I am indeed back to having to find out how to get this to work without remote service binding - it should be possible, but how?

BTW, SELECT @.@.VERSION shows that I'm on build 3054, in case it matters.

Between all the errors in BOL and less than helpfull error messages produced by SB, I feel like I'm slowly losing my sanity. Please help!

Best regards,

Hugo Kornelis

Hi Remus (or whoever is listening),

Just to make sure that I'm not looking in the wrong corner, I decided to make sure that the absence of certificates is the ONLY reason that the services won't talk to each other. So I made certificates for the dbo owner in each of the DBs, dumped them to file and used those files to create certificates for the corresponding users in the other DBs.

After setting up certificates like that, I still got the same error (Error 916, State 3) - but once I added a remote service binding, my dialog ran without further problems.

I still don't understand why a remote service binding is required even though BOL says (quote from the CREATE REMOTE SERVICE BINDING page): "A remote service binding is only necessary for initiating services that communicate with target services outside of the SQL Server instance." - but at least I am now certain that my problems with the version without certificates and with the trustworthy option set on are not related to any other errors in my setup.

Best, Hugo

|||

On the interaction between ENCRYPTION = ON/OFF and the presence/absence of a remote service binding see http://blogs.msdn.com/remusrusanu/archive/2006/07/07/659319.aspx. When a RSB is present, the login mapping between databases is discarded in favour of certificates. This is intentional, as a way to circumvent the problem of no wanting to enable TRUSTWORTHY bit (with all the instance level implications).

To map users trough logins, having TRUSTWORTHY ON is a required condition, but not suficcient. The complete story is detailed at http://msdn2.microsoft.com/en-us/library/ms188304.aspx. What you need is for DB2 to grant AUTHENTICATE permision to login1. TRUSTWORTHY bit is required only on DB1. This is nothing specific to Service Broker, using EXECUTE AS user = 'foo' in DB1 and then issue a USE DB2 statement would run into the same error.

I understand the errors are somehow cryptic and misterious, now the cat is out of the bag we hope to get better at next iteration. Tools would shorley help, give a shot to www.codeplex.com/slm

|||

Hugo Kornelis wrote:

I still don't understand why a remote service binding is required even though BOL says (quote from the CREATE REMOTE SERVICE BINDING page): "A remote service binding is only necessary for initiating services that communicate with target services outside of the SQL Server instance."

Remote service bindings are required for remote dialog security. However, altough not required, if present, they are honored for local dialogs.

|||

without reading the whole thread in detail, I found that the SQL Profiler lets you find problems within minutes, for which you would normally take hours or days of checking everything!

Trace shows messages and errors, you will never receive through SSB directly!

Thursday, March 8, 2012

Can't remotely access SQL 2005 named instance

I read a blurb somewhere that enabling the Browser service opens security
holes in SQL Server. Is this true, and if it is how does it indeed open
security holes?
- Anthony
"Tibor Karaszi" wrote:

> Is the SQL Server Browser service started on the server?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
> news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
>
|||You're welcome Anthony. :-)

> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
Every surface you open opens increases the threat area. I don't know of any particular issues with
the SQL Browser. The same functionality existed in 2000, but it was built-in to the database engine.
To be more specific I guess we would have to see that comment.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:B18F79B4-C704-4903-A98C-FC3D5F25323D@.microsoft.com...[vbcol=seagreen]
> Thanks! That fixed the issue. You have helped me before, Tibor, and I thank
> you again for your expertise. I may be a MCDBA, but I'm still a 2005 novice
>

> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
> - Anthony
> "Tibor Karaszi" wrote:
|||"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> SuHi,
> I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> server. I installed a default instance, and then a named instance called
> "DEV".
> Initially, I could not access either instance from a remote machine. I
> went
> into SQL Server Surface Area Configuration and enabled TCP/IP and Named
> Pipes
> under the Remote Access portion of the dialog for BOTH instances.
> I can access the default instance from a remote machine. I still cannot
> access the named instance from a remote machine. I have triple checked
> all
> my settings. They are exactly the same for both instances.
Have you tried the SQL Server Configuration Manager on the W2K machine.
This iw wher you open up the IP/Named pipes.

Can't remotely access SQL 2005 named instance

I read a blurb somewhere that enabling the Browser service opens security
holes in SQL Server. Is this true, and if it is how does it indeed open
security holes?
- Anthony
"Tibor Karaszi" wrote:

> Is the SQL Server Browser service started on the server?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
> news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
>|||You're welcome Anthony. :-)

> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
Every surface you open opens increases the threat area. I don't know of any
particular issues with
the SQL Browser. The same functionality existed in 2000, but it was built-in
to the database engine.
To be more specific I guess we would have to see that comment.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:B18F79B4-C704-4903-A98C-FC3D5F25323D@.microsoft.com...[vbcol=seagreen]
> Thanks! That fixed the issue. You have helped me before, Tibor, and I th
ank
> you again for your expertise. I may be a MCDBA, but I'm still a 2005 novi
ce
>

> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
> - Anthony
> "Tibor Karaszi" wrote:
>|||"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> SuHi,
> I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> server. I installed a default instance, and then a named instance called
> "DEV".
> Initially, I could not access either instance from a remote machine. I
> went
> into SQL Server Surface Area Configuration and enabled TCP/IP and Named
> Pipes
> under the Remote Access portion of the dialog for BOTH instances.
> I can access the default instance from a remote machine. I still cannot
> access the named instance from a remote machine. I have triple checked
> all
> my settings. They are exactly the same for both instances.
Have you tried the SQL Server Configuration Manager on the W2K machine.
This iw wher you open up the IP/Named pipes.

Can't remotely access SQL 2005 named instance

SuHi,
I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
server. I installed a default instance, and then a named instance called
"DEV".
Initially, I could not access either instance from a remote machine. I went
into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipes
under the Remote Access portion of the dialog for BOTH instances.
I can access the default instance from a remote machine. I still cannot
access the named instance from a remote machine. I have triple checked all
my settings. They are exactly the same for both instances.
The error message I receive is:
26 - Error locating server/instance specified
I can't see the DEV instance in the SQL Server browse list either.
Can anyone help?Is the SQL Server Browser service started on the server?
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> SuHi,
> I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> server. I installed a default instance, and then a named instance called
> "DEV".
> Initially, I could not access either instance from a remote machine. I went
> into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipes
> under the Remote Access portion of the dialog for BOTH instances.
> I can access the default instance from a remote machine. I still cannot
> access the named instance from a remote machine. I have triple checked all
> my settings. They are exactly the same for both instances.
> The error message I receive is:
> 26 - Error locating server/instance specified
> I can't see the DEV instance in the SQL Server browse list either.
> Can anyone help?|||Thanks! That fixed the issue. You have helped me before, Tibor, and I thank
you again for your expertise. I may be a MCDBA, but I'm still a 2005 novice
:)
I read a blurb somewhere that enabling the Browser service opens security
holes in SQL Server. Is this true, and if it is how does it indeed open
security holes?
- Anthony
"Tibor Karaszi" wrote:
> Is the SQL Server Browser service started on the server?
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
> news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> > SuHi,
> >
> > I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> > server. I installed a default instance, and then a named instance called
> > "DEV".
> >
> > Initially, I could not access either instance from a remote machine. I went
> > into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipes
> > under the Remote Access portion of the dialog for BOTH instances.
> >
> > I can access the default instance from a remote machine. I still cannot
> > access the named instance from a remote machine. I have triple checked all
> > my settings. They are exactly the same for both instances.
> >
> > The error message I receive is:
> >
> > 26 - Error locating server/instance specified
> >
> > I can't see the DEV instance in the SQL Server browse list either.
> >
> > Can anyone help?
>|||You're welcome Anthony. :-)
> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
Every surface you open opens increases the threat area. I don't know of any particular issues with
the SQL Browser. The same functionality existed in 2000, but it was built-in to the database engine.
To be more specific I guess we would have to see that comment.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:B18F79B4-C704-4903-A98C-FC3D5F25323D@.microsoft.com...
> Thanks! That fixed the issue. You have helped me before, Tibor, and I thank
> you again for your expertise. I may be a MCDBA, but I'm still a 2005 novice
> :)
> I read a blurb somewhere that enabling the Browser service opens security
> holes in SQL Server. Is this true, and if it is how does it indeed open
> security holes?
> - Anthony
> "Tibor Karaszi" wrote:
>> Is the SQL Server Browser service started on the server?
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
>> news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
>> > SuHi,
>> >
>> > I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
>> > server. I installed a default instance, and then a named instance called
>> > "DEV".
>> >
>> > Initially, I could not access either instance from a remote machine. I went
>> > into SQL Server Surface Area Configuration and enabled TCP/IP and Named Pipes
>> > under the Remote Access portion of the dialog for BOTH instances.
>> >
>> > I can access the default instance from a remote machine. I still cannot
>> > access the named instance from a remote machine. I have triple checked all
>> > my settings. They are exactly the same for both instances.
>> >
>> > The error message I receive is:
>> >
>> > 26 - Error locating server/instance specified
>> >
>> > I can't see the DEV instance in the SQL Server browse list either.
>> >
>> > Can anyone help?
>>|||"Ant-nee" <Antnee@.discussions.microsoft.com> wrote in message
news:2B8ED4DB-E631-4C73-9C06-072557EC7FAA@.microsoft.com...
> SuHi,
> I just installed SQL 2005 Developer Edition on a brand new W2K3 w/ SP1
> server. I installed a default instance, and then a named instance called
> "DEV".
> Initially, I could not access either instance from a remote machine. I
> went
> into SQL Server Surface Area Configuration and enabled TCP/IP and Named
> Pipes
> under the Remote Access portion of the dialog for BOTH instances.
> I can access the default instance from a remote machine. I still cannot
> access the named instance from a remote machine. I have triple checked
> all
> my settings. They are exactly the same for both instances.
Have you tried the SQL Server Configuration Manager on the W2K machine.
This iw wher you open up the IP/Named pipes.

Cant register to a named instance

2nd instance of sql was sucessfully installed on the 2nd node of the
cluster. However if i try to register on this 2nd instance it failes with
msg as sql server does not exists or access denied. I tried with the Ip
address too but it fails with same error. I havent installed sp3a on this
instance was trying to get the instance up and running but the initial step
only fails. Has anyone seen this before. any help will be greatly
appreciated. TIA
Message posted via http://www.sqlmonster.com
Hive you seen
http://msdn.microsoft.com/library/de...eInstances.asp ?
Peter
"I favor the Civil Rights Act of 1964 and it must be enforced at gunpoint if
necessary."
Ronald Reagan
"ishaan99 via SQLMonster.com" wrote:

> 2nd instance of sql was sucessfully installed on the 2nd node of the
> cluster. However if i try to register on this 2nd instance it failes with
> msg as sql server does not exists or access denied. I tried with the Ip
> address too but it fails with same error. I havent installed sp3a on this
> instance was trying to get the instance up and running but the initial step
> only fails. Has anyone seen this before. any help will be greatly
> appreciated. TIA
> --
> Message posted via http://www.sqlmonster.com
>
|||Hi
You might need to add an alias using the SQL Server client network utility.
You can find it in your SQL Server programs group.
What you need to put in depends on your network protocols. We use either
TCP/IP or named pipes. For TCP/IP you need to supply 'server name\instance
name' and the port that SQL Server is running on. For named pipes supply the
server name\instance name.
You then should be able to access the named instance.
Hope this helps
John
"ishaan99 via SQLMonster.com" wrote:

> 2nd instance of sql was sucessfully installed on the 2nd node of the
> cluster. However if i try to register on this 2nd instance it failes with
> msg as sql server does not exists or access denied. I tried with the Ip
> address too but it fails with same error. I havent installed sp3a on this
> instance was trying to get the instance up and running but the initial step
> only fails. Has anyone seen this before. any help will be greatly
> appreciated. TIA
> --
> Message posted via http://www.sqlmonster.com
>
|||Thanks but I did try adding an alias from client n/w . also tried using
osql with servername\instancename but i get the same error. However I could
see 2nd instance of sql server and sql agent running from 2nd node services
though. My 2nd node accesses 4 drives and i have all system files on one of
these 4 drives but MSSQL$2INSTANCE is under c:\ProgramFiles.... Has it got
anyting to do with installation? Since i am not able to isql to this server
I feel is sql itself is failing.. any thoughts on this?
Message posted via http://www.sqlmonster.com
|||This what i see after trying from osql
Unable to connect: SQL Server is unavailable or does not exists. Net-
library error 2: ConnectionOpen (Connect())
Message posted via http://www.sqlmonster.com
|||Have you looked at the SQL Server logs.
It should tell what types of client connections can be made (if you are
using TCP/IP what ports are being used etc).
e.g. my log has the following lines in it
SQL server listening on 127.0.0.1: 2433
SQL server listening on 169.254.151.241: 2433
...
SQL server listening on TCP, Shared Memory, Named Pipes
"ishaan99 via SQLMonster.com" wrote:

> 2nd instance of sql was sucessfully installed on the 2nd node of the
> cluster. However if i try to register on this 2nd instance it failes with
> msg as sql server does not exists or access denied. I tried with the Ip
> address too but it fails with same error. I havent installed sp3a on this
> instance was trying to get the instance up and running but the initial step
> only fails. Has anyone seen this before. any help will be greatly
> appreciated. TIA
> --
> Message posted via http://www.sqlmonster.com
>

Cant register to a named instance

2nd instance of sql was sucessfully installed on the 2nd node of the
cluster. However if i try to register on this 2nd instance it failes with
msg as sql server does not exists or access denied. I tried with the Ip
address too but it fails with same error. I havent installed sp3a on this
instance was trying to get the instance up and running but the initial step
only fails. Has anyone seen this before. any help will be greatly
appreciated. TIA
--
Message posted via http://www.sqlmonster.comHive you seen
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/dnsqlmag2k/html/MultipleInstances.asp ?
Peter
"I favor the Civil Rights Act of 1964 and it must be enforced at gunpoint if
necessary."
Ronald Reagan
"ishaan99 via SQLMonster.com" wrote:
> 2nd instance of sql was sucessfully installed on the 2nd node of the
> cluster. However if i try to register on this 2nd instance it failes with
> msg as sql server does not exists or access denied. I tried with the Ip
> address too but it fails with same error. I havent installed sp3a on this
> instance was trying to get the instance up and running but the initial step
> only fails. Has anyone seen this before. any help will be greatly
> appreciated. TIA
> --
> Message posted via http://www.sqlmonster.com
>|||Hi
You might need to add an alias using the SQL Server client network utility.
You can find it in your SQL Server programs group.
What you need to put in depends on your network protocols. We use either
TCP/IP or named pipes. For TCP/IP you need to supply 'server name\instance
name' and the port that SQL Server is running on. For named pipes supply the
server name\instance name.
You then should be able to access the named instance.
Hope this helps
John
"ishaan99 via SQLMonster.com" wrote:
> 2nd instance of sql was sucessfully installed on the 2nd node of the
> cluster. However if i try to register on this 2nd instance it failes with
> msg as sql server does not exists or access denied. I tried with the Ip
> address too but it fails with same error. I havent installed sp3a on this
> instance was trying to get the instance up and running but the initial step
> only fails. Has anyone seen this before. any help will be greatly
> appreciated. TIA
> --
> Message posted via http://www.sqlmonster.com
>|||Thanks but I did try adding an alias from client n/w . also tried using
osql with servername\instancename but i get the same error. However I could
see 2nd instance of sql server and sql agent running from 2nd node services
though. My 2nd node accesses 4 drives and i have all system files on one of
these 4 drives but MSSQL$2INSTANCE is under c:\ProgramFiles.... Has it got
anyting to do with installation? Since i am not able to isql to this server
I feel is sql itself is failing.. any thoughts on this'
--
Message posted via http://www.sqlmonster.com|||This what i see after trying from osql
Unable to connect: SQL Server is unavailable or does not exists. Net-
library error 2: ConnectionOpen (Connect())
--
Message posted via http://www.sqlmonster.com|||Have you looked at the SQL Server logs.
It should tell what types of client connections can be made (if you are
using TCP/IP what ports are being used etc).
e.g. my log has the following lines in it
SQL server listening on 127.0.0.1: 2433
SQL server listening on 169.254.151.241: 2433
...
SQL server listening on TCP, Shared Memory, Named Pipes
"ishaan99 via SQLMonster.com" wrote:
> 2nd instance of sql was sucessfully installed on the 2nd node of the
> cluster. However if i try to register on this 2nd instance it failes with
> msg as sql server does not exists or access denied. I tried with the Ip
> address too but it fails with same error. I havent installed sp3a on this
> instance was trying to get the instance up and running but the initial step
> only fails. Has anyone seen this before. any help will be greatly
> appreciated. TIA
> --
> Message posted via http://www.sqlmonster.com
>

Wednesday, March 7, 2012

Cant register to a named instance

2nd instance of sql was sucessfully installed on the 2nd node of the
cluster. However if i try to register on this 2nd instance it failes with
msg as sql server does not exists or access denied. I tried with the Ip
address too but it fails with same error. I havent installed sp3a on this
instance was trying to get the instance up and running but the initial step
only fails. Has anyone seen this before. any help will be greatly
appreciated. TIA
Message posted via http://www.droptable.comHive you seen
http://msdn.microsoft.com/library/d...leInstances.asp ?
Peter
"I favor the Civil Rights Act of 1964 and it must be enforced at gunpoint if
necessary."
Ronald Reagan
"ishaan99 via droptable.com" wrote:

> 2nd instance of sql was sucessfully installed on the 2nd node of the
> cluster. However if i try to register on this 2nd instance it failes with
> msg as sql server does not exists or access denied. I tried with the Ip
> address too but it fails with same error. I havent installed sp3a on this
> instance was trying to get the instance up and running but the initial ste
p
> only fails. Has anyone seen this before. any help will be greatly
> appreciated. TIA
> --
> Message posted via http://www.droptable.com
>|||Hi
You might need to add an alias using the SQL Server client network utility.
You can find it in your SQL Server programs group.
What you need to put in depends on your network protocols. We use either
TCP/IP or named pipes. For TCP/IP you need to supply 'server name\instance
name' and the port that SQL Server is running on. For named pipes supply the
server name\instance name.
You then should be able to access the named instance.
Hope this helps
John
"ishaan99 via droptable.com" wrote:

> 2nd instance of sql was sucessfully installed on the 2nd node of the
> cluster. However if i try to register on this 2nd instance it failes with
> msg as sql server does not exists or access denied. I tried with the Ip
> address too but it fails with same error. I havent installed sp3a on this
> instance was trying to get the instance up and running but the initial ste
p
> only fails. Has anyone seen this before. any help will be greatly
> appreciated. TIA
> --
> Message posted via http://www.droptable.com
>|||Thanks but I did try adding an alias from client n/w . also tried using
osql with servername\instancename but i get the same error. However I could
see 2nd instance of sql server and sql agent running from 2nd node services
though. My 2nd node accesses 4 drives and i have all system files on one of
these 4 drives but MSSQL$2INSTANCE is under c:\ProgramFiles.... Has it got
anyting to do with installation? Since i am not able to isql to this server
I feel is sql itself is failing.. any thoughts on this'
Message posted via http://www.droptable.com|||This what i see after trying from osql
Unable to connect: SQL Server is unavailable or does not exists. Net-
library error 2: ConnectionOpen (Connect())
Message posted via http://www.droptable.com|||Have you looked at the SQL Server logs.
It should tell what types of client connections can be made (if you are
using TCP/IP what ports are being used etc).
e.g. my log has the following lines in it
SQL server listening on 127.0.0.1: 2433
SQL server listening on 169.254.151.241: 2433
...
SQL server listening on TCP, Shared Memory, Named Pipes
"ishaan99 via droptable.com" wrote:

> 2nd instance of sql was sucessfully installed on the 2nd node of the
> cluster. However if i try to register on this 2nd instance it failes with
> msg as sql server does not exists or access denied. I tried with the Ip
> address too but it fails with same error. I havent installed sp3a on this
> instance was trying to get the instance up and running but the initial ste
p
> only fails. Has anyone seen this before. any help will be greatly
> appreciated. TIA
> --
> Message posted via http://www.droptable.com
>

cant register sql2k5

I have a local instance of sql2k5, as well as a remote one. From my local
Management Studio, I try to register the remote one, and I get the message...
A connection was successfully established to the server, but then an error
occured during the login process. (provider: TCP Provider, error:0 - An
existing connection was forcibly closed by the remote host. ) (MSSQL, Error:
10054)
Any ideas?
--
TIA,
ChrisRDid you enable TCP/IP connections from remote machines in SQL Surface
Area Configuration Tool? They're not turned on by default in 2005.
ChrisR wrote:
> I have a local instance of sql2k5, as well as a remote one. From my local
> Management Studio, I try to register the remote one, and I get the message...
> A connection was successfully established to the server, but then an error
> occured during the login process. (provider: TCP Provider, error:0 - An
> existing connection was forcibly closed by the remote host. ) (MSSQL, Error:
> 10054)
> Any ideas?
> --
> TIA,
> ChrisR|||I don't have a Configurations tab on the remote box... I just realized its
Beta2. Could this have sometihng to do with it?
--
TIA,
ChrisR
"Corey Bunch" wrote:
> Did you enable TCP/IP connections from remote machines in SQL Surface
> Area Configuration Tool? They're not turned on by default in 2005.
> ChrisR wrote:
> > I have a local instance of sql2k5, as well as a remote one. From my local
> > Management Studio, I try to register the remote one, and I get the message...
> >
> > A connection was successfully established to the server, but then an error
> > occured during the login process. (provider: TCP Provider, error:0 - An
> > existing connection was forcibly closed by the remote host. ) (MSSQL, Error:
> > 10054)
> >
> > Any ideas?
> > --
> > TIA,
> > ChrisR
>|||Are you looking under Programs\SQL 2005\Configuration Tools\Surface Area
Configuration tool?
"ChrisR" wrote:
> I don't have a Configurations tab on the remote box... I just realized its
> Beta2. Could this have sometihng to do with it?
> --
> TIA,
> ChrisR
>
> "Corey Bunch" wrote:
> > Did you enable TCP/IP connections from remote machines in SQL Surface
> > Area Configuration Tool? They're not turned on by default in 2005.
> >
> > ChrisR wrote:
> > > I have a local instance of sql2k5, as well as a remote one. From my local
> > > Management Studio, I try to register the remote one, and I get the message...
> > >
> > > A connection was successfully established to the server, but then an error
> > > occured during the login process. (provider: TCP Provider, error:0 - An
> > > existing connection was forcibly closed by the remote host. ) (MSSQL, Error:
> > > 10054)
> > >
> > > Any ideas?
> > > --
> > > TIA,
> > > ChrisR
> >
> >|||Start\ Programs\ there is no Configuration Tools option.
--
TIA,
ChrisR
"burt_king" wrote:
> Are you looking under Programs\SQL 2005\Configuration Tools\Surface Area
> Configuration tool?
> "ChrisR" wrote:
> > I don't have a Configurations tab on the remote box... I just realized its
> > Beta2. Could this have sometihng to do with it?
> > --
> > TIA,
> > ChrisR
> >
> >
> > "Corey Bunch" wrote:
> >
> > > Did you enable TCP/IP connections from remote machines in SQL Surface
> > > Area Configuration Tool? They're not turned on by default in 2005.
> > >
> > > ChrisR wrote:
> > > > I have a local instance of sql2k5, as well as a remote one. From my local
> > > > Management Studio, I try to register the remote one, and I get the message...
> > > >
> > > > A connection was successfully established to the server, but then an error
> > > > occured during the login process. (provider: TCP Provider, error:0 - An
> > > > existing connection was forcibly closed by the remote host. ) (MSSQL, Error:
> > > > 10054)
> > > >
> > > > Any ideas?
> > > > --
> > > > TIA,
> > > > ChrisR
> > >
> > >|||Sorry... start\programs\sql2k5\ there is no Configuration Tools option.
--
TIA,
ChrisR
"ChrisR" wrote:
> Start\ Programs\ there is no Configuration Tools option.
> --
> TIA,
> ChrisR
>
> "burt_king" wrote:
> > Are you looking under Programs\SQL 2005\Configuration Tools\Surface Area
> > Configuration tool?
> >
> > "ChrisR" wrote:
> >
> > > I don't have a Configurations tab on the remote box... I just realized its
> > > Beta2. Could this have sometihng to do with it?
> > > --
> > > TIA,
> > > ChrisR
> > >
> > >
> > > "Corey Bunch" wrote:
> > >
> > > > Did you enable TCP/IP connections from remote machines in SQL Surface
> > > > Area Configuration Tool? They're not turned on by default in 2005.
> > > >
> > > > ChrisR wrote:
> > > > > I have a local instance of sql2k5, as well as a remote one. From my local
> > > > > Management Studio, I try to register the remote one, and I get the message...
> > > > >
> > > > > A connection was successfully established to the server, but then an error
> > > > > occured during the login process. (provider: TCP Provider, error:0 - An
> > > > > existing connection was forcibly closed by the remote host. ) (MSSQL, Error:
> > > > > 10054)
> > > > >
> > > > > Any ideas?
> > > > > --
> > > > > TIA,
> > > > > ChrisR
> > > >
> > > >|||How about Computer Manager, under Services, you should have some SQL Server Configuration Node. Here
you can enable the netlibs.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:0AA1654F-9449-484F-9CCA-AC7472FEF91B@.microsoft.com...
> Sorry... start\programs\sql2k5\ there is no Configuration Tools option.
> --
> TIA,
> ChrisR
>
> "ChrisR" wrote:
>> Start\ Programs\ there is no Configuration Tools option.
>> --
>> TIA,
>> ChrisR
>>
>> "burt_king" wrote:
>> > Are you looking under Programs\SQL 2005\Configuration Tools\Surface Area
>> > Configuration tool?
>> >
>> > "ChrisR" wrote:
>> >
>> > > I don't have a Configurations tab on the remote box... I just realized its
>> > > Beta2. Could this have sometihng to do with it?
>> > > --
>> > > TIA,
>> > > ChrisR
>> > >
>> > >
>> > > "Corey Bunch" wrote:
>> > >
>> > > > Did you enable TCP/IP connections from remote machines in SQL Surface
>> > > > Area Configuration Tool? They're not turned on by default in 2005.
>> > > >
>> > > > ChrisR wrote:
>> > > > > I have a local instance of sql2k5, as well as a remote one. From my local
>> > > > > Management Studio, I try to register the remote one, and I get the message...
>> > > > >
>> > > > > A connection was successfully established to the server, but then an error
>> > > > > occured during the login process. (provider: TCP Provider, error:0 - An
>> > > > > existing connection was forcibly closed by the remote host. ) (MSSQL, Error:
>> > > > > 10054)
>> > > > >
>> > > > > Any ideas?
>> > > > > --
>> > > > > TIA,
>> > > > > ChrisR
>> > > >
>> > > >|||And do what to the netlibs? I dont see anything like enable remote connections.
--
TIA,
ChrisR
"Tibor Karaszi" wrote:
> How about Computer Manager, under Services, you should have some SQL Server Configuration Node. Here
> you can enable the netlibs.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:0AA1654F-9449-484F-9CCA-AC7472FEF91B@.microsoft.com...
> > Sorry... start\programs\sql2k5\ there is no Configuration Tools option.
> >
> > --
> > TIA,
> > ChrisR
> >
> >
> > "ChrisR" wrote:
> >
> >> Start\ Programs\ there is no Configuration Tools option.
> >> --
> >> TIA,
> >> ChrisR
> >>
> >>
> >> "burt_king" wrote:
> >>
> >> > Are you looking under Programs\SQL 2005\Configuration Tools\Surface Area
> >> > Configuration tool?
> >> >
> >> > "ChrisR" wrote:
> >> >
> >> > > I don't have a Configurations tab on the remote box... I just realized its
> >> > > Beta2. Could this have sometihng to do with it?
> >> > > --
> >> > > TIA,
> >> > > ChrisR
> >> > >
> >> > >
> >> > > "Corey Bunch" wrote:
> >> > >
> >> > > > Did you enable TCP/IP connections from remote machines in SQL Surface
> >> > > > Area Configuration Tool? They're not turned on by default in 2005.
> >> > > >
> >> > > > ChrisR wrote:
> >> > > > > I have a local instance of sql2k5, as well as a remote one. From my local
> >> > > > > Management Studio, I try to register the remote one, and I get the message...
> >> > > > >
> >> > > > > A connection was successfully established to the server, but then an error
> >> > > > > occured during the login process. (provider: TCP Provider, error:0 - An
> >> > > > > existing connection was forcibly closed by the remote host. ) (MSSQL, Error:
> >> > > > > 10054)
> >> > > > >
> >> > > > > Any ideas?
> >> > > > > --
> >> > > > > TIA,
> >> > > > > ChrisR
> >> > > >
> >> > > >
>|||Also, I tried to register in reverse.
1; In my local box, I went into
I logged into the remote box and tried to register my local box. I went into
SQL Server Surface Area Config/ Services and Connections/ Remote Connections/
Local and Remote Connections is checked.
When I try to register it says Unknown ProviderConnection string is invalid.
(MSSQL error: 87)
TIA,
ChrisR
"burt_king" wrote:
> Are you looking under Programs\SQL 2005\Configuration Tools\Surface Area
> Configuration tool?
> "ChrisR" wrote:
> > I don't have a Configurations tab on the remote box... I just realized its
> > Beta2. Could this have sometihng to do with it?
> > --
> > TIA,
> > ChrisR
> >
> >
> > "Corey Bunch" wrote:
> >
> > > Did you enable TCP/IP connections from remote machines in SQL Surface
> > > Area Configuration Tool? They're not turned on by default in 2005.
> > >
> > > ChrisR wrote:
> > > > I have a local instance of sql2k5, as well as a remote one. From my local
> > > > Management Studio, I try to register the remote one, and I get the message...
> > > >
> > > > A connection was successfully established to the server, but then an error
> > > > occured during the login process. (provider: TCP Provider, error:0 - An
> > > > existing connection was forcibly closed by the remote host. ) (MSSQL, Error:
> > > > 10054)
> > > >
> > > > Any ideas?
> > > > --
> > > > TIA,
> > > > ChrisR
> > >
> > >|||Hard to know what your setup look like as you are on an older version (beta). On my machines, I use
the following folder structure:
SQL Server Configuration Manager
SQL Server 2005 Network Configuration
Protocols for [instancename]
In above folder I can right-click a netlib (TCP/IP, for instance) and enable it.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
news:F19474D2-3815-4B06-B549-FE357816A8C9@.microsoft.com...
> And do what to the netlibs? I dont see anything like enable remote connections.
> --
> TIA,
> ChrisR
>
> "Tibor Karaszi" wrote:
>> How about Computer Manager, under Services, you should have some SQL Server Configuration Node.
>> Here
>> you can enable the netlibs.
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>> Blog: http://solidqualitylearning.com/blogs/tibor/
>>
>> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
>> news:0AA1654F-9449-484F-9CCA-AC7472FEF91B@.microsoft.com...
>> > Sorry... start\programs\sql2k5\ there is no Configuration Tools option.
>> >
>> > --
>> > TIA,
>> > ChrisR
>> >
>> >
>> > "ChrisR" wrote:
>> >
>> >> Start\ Programs\ there is no Configuration Tools option.
>> >> --
>> >> TIA,
>> >> ChrisR
>> >>
>> >>
>> >> "burt_king" wrote:
>> >>
>> >> > Are you looking under Programs\SQL 2005\Configuration Tools\Surface Area
>> >> > Configuration tool?
>> >> >
>> >> > "ChrisR" wrote:
>> >> >
>> >> > > I don't have a Configurations tab on the remote box... I just realized its
>> >> > > Beta2. Could this have sometihng to do with it?
>> >> > > --
>> >> > > TIA,
>> >> > > ChrisR
>> >> > >
>> >> > >
>> >> > > "Corey Bunch" wrote:
>> >> > >
>> >> > > > Did you enable TCP/IP connections from remote machines in SQL Surface
>> >> > > > Area Configuration Tool? They're not turned on by default in 2005.
>> >> > > >
>> >> > > > ChrisR wrote:
>> >> > > > > I have a local instance of sql2k5, as well as a remote one. From my local
>> >> > > > > Management Studio, I try to register the remote one, and I get the message...
>> >> > > > >
>> >> > > > > A connection was successfully established to the server, but then an error
>> >> > > > > occured during the login process. (provider: TCP Provider, error:0 - An
>> >> > > > > existing connection was forcibly closed by the remote host. ) (MSSQL, Error:
>> >> > > > > 10054)
>> >> > > > >
>> >> > > > > Any ideas?
>> >> > > > > --
>> >> > > > > TIA,
>> >> > > > > ChrisR
>> >> > > >
>> >> > > >
>>|||Im going to reinstall with a more current version and see what happens.
--
TIA,
ChrisR
"Tibor Karaszi" wrote:
> Hard to know what your setup look like as you are on an older version (beta). On my machines, I use
> the following folder structure:
> SQL Server Configuration Manager
> SQL Server 2005 Network Configuration
> Protocols for [instancename]
> In above folder I can right-click a netlib (TCP/IP, for instance) and enable it.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> news:F19474D2-3815-4B06-B549-FE357816A8C9@.microsoft.com...
> > And do what to the netlibs? I dont see anything like enable remote connections.
> >
> > --
> > TIA,
> > ChrisR
> >
> >
> > "Tibor Karaszi" wrote:
> >
> >> How about Computer Manager, under Services, you should have some SQL Server Configuration Node.
> >> Here
> >> you can enable the netlibs.
> >>
> >> --
> >> Tibor Karaszi, SQL Server MVP
> >> http://www.karaszi.com/sqlserver/default.asp
> >> http://www.solidqualitylearning.com/
> >> Blog: http://solidqualitylearning.com/blogs/tibor/
> >>
> >>
> >> "ChrisR" <ChrisR@.discussions.microsoft.com> wrote in message
> >> news:0AA1654F-9449-484F-9CCA-AC7472FEF91B@.microsoft.com...
> >> > Sorry... start\programs\sql2k5\ there is no Configuration Tools option.
> >> >
> >> > --
> >> > TIA,
> >> > ChrisR
> >> >
> >> >
> >> > "ChrisR" wrote:
> >> >
> >> >> Start\ Programs\ there is no Configuration Tools option.
> >> >> --
> >> >> TIA,
> >> >> ChrisR
> >> >>
> >> >>
> >> >> "burt_king" wrote:
> >> >>
> >> >> > Are you looking under Programs\SQL 2005\Configuration Tools\Surface Area
> >> >> > Configuration tool?
> >> >> >
> >> >> > "ChrisR" wrote:
> >> >> >
> >> >> > > I don't have a Configurations tab on the remote box... I just realized its
> >> >> > > Beta2. Could this have sometihng to do with it?
> >> >> > > --
> >> >> > > TIA,
> >> >> > > ChrisR
> >> >> > >
> >> >> > >
> >> >> > > "Corey Bunch" wrote:
> >> >> > >
> >> >> > > > Did you enable TCP/IP connections from remote machines in SQL Surface
> >> >> > > > Area Configuration Tool? They're not turned on by default in 2005.
> >> >> > > >
> >> >> > > > ChrisR wrote:
> >> >> > > > > I have a local instance of sql2k5, as well as a remote one. From my local
> >> >> > > > > Management Studio, I try to register the remote one, and I get the message...
> >> >> > > > >
> >> >> > > > > A connection was successfully established to the server, but then an error
> >> >> > > > > occured during the login process. (provider: TCP Provider, error:0 - An
> >> >> > > > > existing connection was forcibly closed by the remote host. ) (MSSQL, Error:
> >> >> > > > > 10054)
> >> >> > > > >
> >> >> > > > > Any ideas?
> >> >> > > > > --
> >> >> > > > > TIA,
> >> >> > > > > ChrisR
> >> >> > > >
> >> >> > > >
> >>
> >>
>

cant register sql2k5

Cant register local instance of SQL Server on local server PLUS

I have two servers running SQL Server on the same network and I am
receiving errors registering the various instances as follows:

SERVER1 tried to register the local instance (by netname, ip address
and local)
ERROR Msg: SQL Server does not exist or access denied (ConnectionOpen |
Connect()

SERVER1 trying to register Server2's default instance (by netname, ip
address and local) COMPLETES SUCESSFULLY (THIS INSTANCE CAN BE REGISTER
FROM ANYWHERE PROVIDED THAT YOU HAVE PERMISSION(S)

SERVER2 tried to register the local instance (by netname, ip address
and local)
ERROR Msg: ssl security error -connectionopen(secdoclienthandshake)

SERVER2 trying to register Server1's default instance (by netname, ip
address and local)
ERROR Msg: SQL Server does not exist or access denied (ConnectionOpen |
Connect()

Note: SERVER2's default instance was registered locally before, but I
wanted to change the alias name so I unregistered it and tried to
register it with the new alias. I only change the alias name not the
underlying information which was previously registered. That is when I
started to receive the errors. ALSO I DON'T KNOW IF THIS MATTERS, BUT
D01 WAS CLONED FROM D02 BECAUSE OF A DISK FAILURE. I DID HOWEVER RUN
THE NEWSID UTILITY.

Any Ideas?(war_wheelan@.yahoo.com) writes:
> SERVER1 tried to register the local instance (by netname, ip address
> and local)
> ERROR Msg: SQL Server does not exist or access denied (ConnectionOpen |
> Connect()

Have you ensured that is running?

> SERVER1 trying to register Server2's default instance (by netname, ip
> address and local) COMPLETES SUCESSFULLY (THIS INSTANCE CAN BE REGISTER
> FROM ANYWHERE PROVIDED THAT YOU HAVE PERMISSION(S)
> SERVER2 tried to register the local instance (by netname, ip address
> and local)
> ERROR Msg: ssl security error -connectionopen(secdoclienthandshake)

Could http://support.microsoft.com/kb/322144/EN-US/ apply?

--
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp|||Erland,

Thanks for the pointer to the Microsoft article. In the future, I will
look on the Microsoft's web site more throughly.

Answer: Someone in my organization must of inadvertently enable
encryption for the client without my knowledge.

Thanks.

Can't register Instance Server

Hello Experts,
I send this issue in this newsgroup too, hoping have
faster response here.
I bring up with my issue again because couldn't resolve
it.
Machine Name is KMICHAS with Windows XP Pro (All Critical
Updates Applied) and SQL Server 2000 Developer Edition
(SP3).
I setup an MSDE 2000 (A) with an Instance name MYTEST and
blank password.
Setup.ini
--
[Options]
TARGETDIR="C:\PROGRAM FILES\MICROSOFT SQL
SERVER\MSSQL\BINN\"
DATADIR="C:\PROGRAM FILES\MICROSOFT SQL
SERVER\MSSQL\DATA\"
INSTANCENAME="CTSQL"
SECURITYMODE="SQL"
COLLATION="SQL_Latin1_General_CP1253_CS_AS"
BLANKSAPWD=1
I think that a problem happened in the procedure of setup
without reporting any error because the TARGET Directory
is the same with the one that SQL Server 2000 Installed
and system files messed up. Is this true?
The problem that I face up is that I can't register this
Instance using Enterprise Manager, it never ends
trying to connect without reporting any error.
PS: Services of KMICHAS\MYTEST are all running.
Thanks in advance!Hello again,
The real problem is when Install MSDE and can't
configures SQL.
a) The SQL Error Log writes: Warning: override, autoexec
procedures skipped.
b) The Windows Application Event (Log) Viewer writes:
EventID: 1013
Product: Microsoft SQL Server Desktop Engine -- Setup
failed to configure the server. Refer to the server error
logs and setup error logs for more information.
The error occured when I decide to change the path of
TARGET And DATA Directories.
Thanks in advance!
>--Original Message--
>Hello Experts,
>I send this issue in this newsgroup too, hoping have
>faster response here.
>I bring up with my issue again because couldn't resolve
>it.
>Machine Name is KMICHAS with Windows XP Pro (All
Critical
>Updates Applied) and SQL Server 2000 Developer Edition
>(SP3).
>I setup an MSDE 2000 (A) with an Instance name MYTEST
and
>blank password.
>Setup.ini
>--
>[Options]
>TARGETDIR="C:\PROGRAM FILES\MICROSOFT SQL
>SERVER\MSSQL\BINN\"
>DATADIR="C:\PROGRAM FILES\MICROSOFT SQL
>SERVER\MSSQL\DATA\"
>INSTANCENAME="CTSQL"
>SECURITYMODE="SQL"
>COLLATION="SQL_Latin1_General_CP1253_CS_AS"
>BLANKSAPWD=1
>I think that a problem happened in the procedure of
setup
>without reporting any error because the TARGET Directory
>is the same with the one that SQL Server 2000 Installed
>and system files messed up. Is this true?
>The problem that I face up is that I can't register this
>Instance using Enterprise Manager, it never ends
>trying to connect without reporting any error.
>PS: Services of KMICHAS\MYTEST are all running.
>Thanks in advance!
>.
>

Can't register 2nd SQL Server instance on Windows 2003

I created a 2nd SQL Server instance on Windows 2003. I can
register the newly created instance on the server itself,
but can't register from the client machine.
Anyone has the solution for this, please help.
Thanks!What error message did you get when you tried to register it -- I assume --
on EM?
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"pvtran@.hotmail.com" <anonymous@.discussions.microsoft.com> wrote in message
news:027901c39cbc$81b519a0$a301280a@.phx.gbl...
> I created a 2nd SQL Server instance on Windows 2003. I can
> register the newly created instance on the server itself,
> but can't register from the client machine.
> Anyone has the solution for this, please help.
> Thanks!|||Yes on EM.
The error message is: "SQL Server does not exist or access
denied. ConnectionOpen (Connect())"
>--Original Message--
>What error message did you get when you tried to register
it -- I assume --
>on EM?
>--
>Linchi Shea
>linchi_shea@.NOSPAMml.com
>
>"pvtran@.hotmail.com"
<anonymous@.discussions.microsoft.com> wrote in message
>news:027901c39cbc$81b519a0$a301280a@.phx.gbl...
>> I created a 2nd SQL Server instance on Windows 2003. I
can
>> register the newly created instance on the server
itself,
>> but can't register from the client machine.
>> Anyone has the solution for this, please help.
>> Thanks!
>
>.
>

Can't receive messages on second server instance

Hi all!

Help, please!

I am trying to send messages between 2 different server instances. I am getting the following errors in Profiler:

"This message could not be delivered because the user with ID 0 in database ID 14 does not have permission to send to the service. Service name: 'TestService1'."

"The target service name could not be found. Ensure that the service name is specified correctly and/or the routing information has been supplied."

The scripts for object creation and messaging is following at the first server instance:

USE master
GO
CREATE ENDPOINT SBroker
STATE = STARTED
AS TCP ( LISTENER_PORT = 1212 )
FOR SERVICE_BROKER (
ENCRYPTION = DISABLED
);
GO

USE Test
GO
CREATE QUEUE TestQueue
WITH STATUS=ON

CREATE SERVICE TestService
AUTHORIZATION dbo
ON QUEUE TestQueue

CREATE ROUTE TestRoute
WITH
SERVICE_NAME = 'TestService1',
BROKER_INSTANCE ='2B7CE76A-9804-46F3-9AE8-0AE59313613A',
ADDRESS = 'TCP://10.17.11.17:4037' ;

// send message script:

DECLARE @.dh UNIQUEIDENTIFIER;

BEGIN DIALOG CONVERSATION @.dh
FROM SERVICE [TestService]
TO SERVICE 'TestService1','2B7CE76A-9804-46F3-9AE8-0AE59313613A'
ON CONTRACT [DEFAULT]
WITH ENCRYPTION = OFF;

SEND ON CONVERSATION @.dh MESSAGE TYPE [DEFAULT] ('this is message1');

DECLARE @.status nvarchar(1024);
SELECT status = GET_TRANSMISSION_STATUS(@.dh);

END CONVERSATION @.dh;

on second server instance:

use master
GO
CREATE ENDPOINT SBroker2
STATE = STARTED
AS TCP ( LISTENER_PORT = 1212 )
FOR SERVICE_BROKER (
ENCRYPTION = DISABLED
);
GO

in first server, in sys.transmission_queue transmission_status is empty

Both servers in the same domain, and databases on this server has the same owner.

on both servers, select @.@.version:
Microsoft SQL Server 2005 - 9.00.2047.00 (Intel X86)
Apr 14 2006 01:12:25 Copyright (c) 1988-2005 Microsoft Corporation
Developer Edition on Windows NT 5.2 (Build 3790: Service Pack 1)

Thanks a lot for help and explanation!

Sveta.

When you begin a dialog with encryption = off and there is no remote service binding for the target service in the initiator database, the inbound dialog at the target side will appear to be coming from user public (i.e. database principal 0). You will therefore need to grant send permission on the target service to user public. Of course, doing so means anyone can send messages to the target service.

If you want to authenticate the initiator, you will need to export the initiator service owner's certificate, create a user in the target database, import the certificate and make it owned by this user, and grant send permission for target service to this user. You could use Remus' Service Listings tool, which greatly simplied this process.

|||

Thank you for help,

after granting permission :

grant send on service::TestService1 to public

all messages received in second server.

Sunday, February 19, 2012

Can't login into SQL Server Database

Hey
I get the following error when trying to connect to my named instance Sql
Server running locally on my laptop. Does anyone know how to resolve this
I get the following error : Login failed for user:acw
Here is my code:
SqlConnection sConn = new SqlConnection(server=ACLAPTOP\ACSQLSERVE
R;User
id=acw; Password=;Database=BookSpot);
Thanks,
AlAl
Open QA and try to log in with the user. Do you get the same error?
"Al Wilkerson" <ac527@.comcast.net> wrote in message
news:7aCdnUdO-Ipm37zfRVn-gA@.comcast.com...
> Hey
> I get the following error when trying to connect to my named instance Sql
> Server running locally on my laptop. Does anyone know how to resolve this
> I get the following error : Login failed for user:acw
> Here is my code:
> SqlConnection sConn = new SqlConnection(server=ACLAPTOP\ACSQLSERVE
R;User
> id=acw; Password=;Database=BookSpot);
>
> Thanks,
> --
> Al
>|||I assume this is C# code. Did you give this user a blank password?
Double-check the password for this user and the rights/roles granted to this
user in EM. I assume your connection string is properly quoted (or it
wouldn't even compile for you). Finally, are you using Integrated Security
or SQL Server Authentication?
Thx
Mike C.
"Al Wilkerson" <ac527@.comcast.net> wrote in message
news:7aCdnUdO-Ipm37zfRVn-gA@.comcast.com...
> Hey
> I get the following error when trying to connect to my named instance Sql
> Server running locally on my laptop. Does anyone know how to resolve this
> I get the following error : Login failed for user:acw
> Here is my code:
> SqlConnection sConn = new SqlConnection(server=ACLAPTOP\ACSQLSERVE
R;User
> id=acw; Password=;Database=BookSpot);
>
> Thanks,
> --
> Al
>

Tuesday, March 27, 2012

Can't start sql agent

Tuesday, March 20, 2012

Can't see the SQL Server Express Instance on SQL Browser

Cant See SQL instance from one machine

Can't see named instance

Can't see named instance

Sunday, March 11, 2012

Can't Route to another LOCAL Broker Instance

Thursday, March 8, 2012

Can't remotely access SQL 2005 named instance

Can't remotely access SQL 2005 named instance

Can't remotely access SQL 2005 named instance

Cant register to a named instance

Cant register to a named instance

Wednesday, March 7, 2012

Cant register to a named instance

cant register sql2k5

cant register sql2k5

cant register sql2k5

Cant register local instance of SQL Server on local server PLUS

Can't register Instance Server

Can't register 2nd SQL Server instance on Windows 2003

Can't receive messages on second server instance

Sunday, February 19, 2012

Can't login into SQL Server Database

sql report manager

Blog Archive

About Me