Netbios and SQL Server Startup Procedure

Is there any way to configure MS SQL Server 2000 standard/developer to choose
a different name other than the netbios machine name as the "server" identity
during startup.
We are currently haveing issues with the assignment of a netbios alias that
SQL Server 2000 reads on it's startup that is different than the name of the
default instance.
TIA,
Hi
Have you checked out
http://msdn.microsoft.com/library/de...stall_5r8f.asp
John
"Dax Lawless" wrote:

> Is there any way to configure MS SQL Server 2000 standard/developer to choose
> a different name other than the netbios machine name as the "server" identity
> during startup.
> We are currently haveing issues with the assignment of a netbios alias that
> SQL Server 2000 reads on it's startup that is different than the name of the
> default instance.
> TIA,
|||That is interesting, however, that is not actually what is happening. The
machine name is actually staying the same as far as the TCP/IP properties are
concerned. We are simply assigning an alias during the startup sequence of
our failover maintenance software (Legato AAM) for a piece of 3rd party
software to use.
Unfortunately, it seems that SQL Server 2000 is reading this netbios alias
and thinks that the servername and when it compares that name with the name
of the default instance (which is not the alias), it treats the default
instance as a named instance and refuses to start listening at port 1433 as
it should with the default instance (we are not using any named instances in
our SQL Server 2000 configuration).
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you checked out
> http://msdn.microsoft.com/library/de...stall_5r8f.asp
> John
> "Dax Lawless" wrote:
|||Hi
Have you looked at creating an alias in the client networking utility,
or you may possibly be able to overcome it by adding the name to the
the hosts file?
John

Netbios and SQL Server Startup Procedure

Is there any way to configure MS SQL Server 2000 standard/developer to choose
a different name other than the netbios machine name as the "server" identity
during startup.
We are currently haveing issues with the assignment of a netbios alias that
SQL Server 2000 reads on it's startup that is different than the name of the
default instance.
TIA,Hi
Have you checked ou
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_afterinstall_5r8f.asp
John
"Dax Lawless" wrote:
> Is there any way to configure MS SQL Server 2000 standard/developer to choose
> a different name other than the netbios machine name as the "server" identity
> during startup.
> We are currently haveing issues with the assignment of a netbios alias that
> SQL Server 2000 reads on it's startup that is different than the name of the
> default instance.
> TIA,|||That is interesting, however, that is not actually what is happening. The
machine name is actually staying the same as far as the TCP/IP properties are
concerned. We are simply assigning an alias during the startup sequence of
our failover maintenance software (Legato AAM) for a piece of 3rd party
software to use.
Unfortunately, it seems that SQL Server 2000 is reading this netbios alias
and thinks that the servername and when it compares that name with the name
of the default instance (which is not the alias), it treats the default
instance as a named instance and refuses to start listening at port 1433 as
it should with the default instance (we are not using any named instances in
our SQL Server 2000 configuration).
"John Bell" wrote:
> Hi
> Have you checked out
> http://msdn.microsoft.com/library/default.asp?url=/library/en-us/instsql/in_afterinstall_5r8f.asp
> John
> "Dax Lawless" wrote:
> > Is there any way to configure MS SQL Server 2000 standard/developer to choose
> > a different name other than the netbios machine name as the "server" identity
> > during startup.
> >
> > We are currently haveing issues with the assignment of a netbios alias that
> > SQL Server 2000 reads on it's startup that is different than the name of the
> > default instance.
> >
> > TIA,|||Hi
Have you looked at creating an alias in the client networking utility,
or you may possibly be able to overcome it by adding the name to the
the hosts file?
John

Netbios and SQL Server Startup Procedure

Is there any way to configure MS SQL Server 2000 standard/developer to choos
e
a different name other than the netbios machine name as the "server" identit
y
during startup.
We are currently haveing issues with the assignment of a netbios alias that
SQL Server 2000 reads on it's startup that is different than the name of the
default instance.
TIA,Hi
Have you checked out
http://msdn.microsoft.com/library/d...nstall_5r8f.asp
John
"Dax Lawless" wrote:

> Is there any way to configure MS SQL Server 2000 standard/developer to cho
ose
> a different name other than the netbios machine name as the "server" ident
ity
> during startup.
> We are currently haveing issues with the assignment of a netbios alias tha
t
> SQL Server 2000 reads on it's startup that is different than the name of t
he
> default instance.
> TIA,|||That is interesting, however, that is not actually what is happening. The
machine name is actually staying the same as far as the TCP/IP properties ar
e
concerned. We are simply assigning an alias during the startup sequence of
our failover maintenance software (Legato AAM) for a piece of 3rd party
software to use.
Unfortunately, it seems that SQL Server 2000 is reading this netbios alias
and thinks that the servername and when it compares that name with the name
of the default instance (which is not the alias), it treats the default
instance as a named instance and refuses to start listening at port 1433 as
it should with the default instance (we are not using any named instances in
our SQL Server 2000 configuration).
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> Have you checked out
> http://msdn.microsoft.com/library/d...nstall_5r8f.asp
> John
> "Dax Lawless" wrote:
>|||Hi
Have you looked at creating an alias in the client networking utility,
or you may possibly be able to overcome it by adding the name to the
the hosts file?
John

Net Send Failure

On a Windows 2000 Server in MYDomain I can do the following
successfully:

Net Send JoeUser "test"

However on a Windows Server 2003 (Standard Edition) in MyDomain I get:

An error occurred while sending a message to JoeUser.
The message alias could not be found on the network.
More help is available by typing NET HELPMSG 2273.

If I enter: net send /DOMAIN:MyDomain joeuser "test"
net send comes back with:

The message was successfully sent to domain MyDomain

BUT... no popups are received.

Is there something common to a Windows Server 2003 server that I need
to configure to get this to work?

How does this relate to SQL Server 2000? I figure that if I can get it
to work via a command prompt that it will work for notification as well
-- which at this point it doesn't.

Thanks for any help.

RBollingerIn article <1114705456.439354.148620@.o13g2000cwo.googlegroups. com>, "robboll" <robboll@.hotmail.com> wrote:
>On a Windows 2000 Server in MYDomain I can do the following
>successfully:
>Net Send JoeUser "test"
>However on a Windows Server 2003 (Standard Edition) in MyDomain I get:
>An error occurred while sending a message to JoeUser.
>The message alias could not be found on the network.
>More help is available by typing NET HELPMSG 2273.

Most likely the messenger service is not enabled by default in Windows 2003.
This is a good thing; there is no authentication with the messenger service,
so that anyone at all can send those "popup" messages to you claiming to be
anyone they want. I rejoiced when I saw SP2 for XP turned that service off.

If you have to use this, you'll need to enable the messager service. It's
probably set to "disabled", so you'll need a reboot once you've set it to
"automatic" for it to start.

>How does this relate to SQL Server 2000? I figure that if I can get it
>to work via a command prompt that it will work for notification as well
>-- which at this point it doesn't.

Hmm. I think the same logic would apply to fixing an SQL server that doesn't
boot because the hard-drive failed; that too would prevent you from using SQL.

But I figured I'd be nice and answer it, anyway :)|||Enabling the "Messenger" service under the Services Applet corrected
the problem. No reboot was necessary. Yes it seems that a lot of the
services previously available by default in previous OS' are locked
down in Windows Server 2003.

It's people like you who make the newsgroups my first source for
finding solutions.

Thank you!

RBollinger

John C. Ring, Jr. wrote:
> In article <1114705456.439354.148620@.o13g2000cwo.googlegroups. com>,
"robboll" <robboll@.hotmail.com> wrote:
> >On a Windows 2000 Server in MYDomain I can do the following
> >successfully:
> >Net Send JoeUser "test"
> >However on a Windows Server 2003 (Standard Edition) in MyDomain I
get:
> >An error occurred while sending a message to JoeUser.
> >The message alias could not be found on the network.
> >More help is available by typing NET HELPMSG 2273.
> Most likely the messenger service is not enabled by default in
Windows 2003.
> This is a good thing; there is no authentication with the messenger
service,
> so that anyone at all can send those "popup" messages to you claiming
to be
> anyone they want. I rejoiced when I saw SP2 for XP turned that
service off.
> If you have to use this, you'll need to enable the messager service.
It's
> probably set to "disabled", so you'll need a reboot once you've set
it to
> "automatic" for it to start.
> >How does this relate to SQL Server 2000? I figure that if I can get
it
> >to work via a command prompt that it will work for notification as
well
> >-- which at this point it doesn't.
> Hmm. I think the same logic would apply to fixing an SQL server that
doesn't
> boot because the hard-drive failed; that too would prevent you from
using SQL.
> But I figured I'd be nice and answer it, anyway :)

nested "starting up database" in the logs

Hi,
I noticed from the logs that, my sql server 2000 Standard Ed (runs on a
windows 2k Advanced server) is starting up the databases over and over again
every second. This goes on and on without stopping, like a nested loop. each
time it does it with a different SPID. When I check the SPID, actually it is
doing something else (such as running a query on a database). It is
currently running SP3, and I am going to install SP4. I wonder if this
resolves it. But before applying the SP4, I wonder if has anyone else run
the similar or same problem. If, so is there a solution for that, or would
SP4 takes care of this problem ?
Thanks for any feedback.
Regards.
Murtix.
Turn off the autoclose database option for your databases...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Murtix Van Basten" <nospam@.nospam.org> wrote in message news:428e0b2c$1_1@.alt.athenanews.com...
> Hi,
> I noticed from the logs that, my sql server 2000 Standard Ed (runs on a
> windows 2k Advanced server) is starting up the databases over and over again
> every second. This goes on and on without stopping, like a nested loop. each
> time it does it with a different SPID. When I check the SPID, actually it is
> doing something else (such as running a query on a database). It is
> currently running SP3, and I am going to install SP4. I wonder if this
> resolves it. But before applying the SP4, I wonder if has anyone else run
> the similar or same problem. If, so is there a solution for that, or would
> SP4 takes care of this problem ?
> Thanks for any feedback.
> Regards.
> Murtix.
>
|||How do I turn off the autoclose for databases ? (I dont remember I turned it
on).
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23IwjkyVXFHA.3320@.TK2MSFTNGP12.phx.gbl...
> Turn off the autoclose database option for your databases...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Murtix Van Basten" <nospam@.nospam.org> wrote in message
> news:428e0b2c$1_1@.alt.athenanews.com...
>
>
|||I found how to turn it off. I will post the result here. It may fix another
issue I am having, too.
"Murtix Van Basten" <nospam@.nospam.org> wrote in message
news:428e3b35$1_1@.alt.athenanews.com...
> How do I turn off the autoclose for databases ? (I dont remember I turned
> it on).
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%23IwjkyVXFHA.3320@.TK2MSFTNGP12.phx.gbl...
>

nested "starting up database" in the logs

Hi,
I noticed from the logs that, my sql server 2000 Standard Ed (runs on a
windows 2k Advanced server) is starting up the databases over and over again
every second. This goes on and on without stopping, like a nested loop. each
time it does it with a different SPID. When I check the SPID, actually it is
doing something else (such as running a query on a database). It is
currently running SP3, and I am going to install SP4. I wonder if this
resolves it. But before applying the SP4, I wonder if has anyone else run
the similar or same problem. If, so is there a solution for that, or would
SP4 takes care of this problem ?
Thanks for any feedback.
Regards.
Murtix.Turn off the autoclose database option for your databases...
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Murtix Van Basten" <nospam@.nospam.org> wrote in message news:428e0b2c$1_1@.alt.athenanews.co
m...
> Hi,
> I noticed from the logs that, my sql server 2000 Standard Ed (runs on a
> windows 2k Advanced server) is starting up the databases over and over aga
in
> every second. This goes on and on without stopping, like a nested loop. ea
ch
> time it does it with a different SPID. When I check the SPID, actually it
is
> doing something else (such as running a query on a database). It is
> currently running SP3, and I am going to install SP4. I wonder if this
> resolves it. But before applying the SP4, I wonder if has anyone else run
> the similar or same problem. If, so is there a solution for that, or would
> SP4 takes care of this problem ?
> Thanks for any feedback.
> Regards.
> Murtix.
>|||How do I turn off the autoclose for databases ? (I dont remember I turned it
on).
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23IwjkyVXFHA.3320@.TK2MSFTNGP12.phx.gbl...
> Turn off the autoclose database option for your databases...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Murtix Van Basten" <nospam@.nospam.org> wrote in message
> news:428e0b2c$1_1@.alt.athenanews.com...
>
>|||I found how to turn it off. I will post the result here. It may fix another
issue I am having, too.
"Murtix Van Basten" <nospam@.nospam.org> wrote in message
news:428e3b35$1_1@.alt.athenanews.com...
> How do I turn off the autoclose for databases ? (I dont remember I turned
> it on).
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%23IwjkyVXFHA.3320@.TK2MSFTNGP12.phx.gbl...
>

nested "starting up database" in the logs

Hi,
I noticed from the logs that, my sql server 2000 Standard Ed (runs on a
windows 2k Advanced server) is starting up the databases over and over again
every second. This goes on and on without stopping, like a nested loop. each
time it does it with a different SPID. When I check the SPID, actually it is
doing something else (such as running a query on a database). It is
currently running SP3, and I am going to install SP4. I wonder if this
resolves it. But before applying the SP4, I wonder if has anyone else run
the similar or same problem. If, so is there a solution for that, or would
SP4 takes care of this problem ?
Thanks for any feedback.
Regards.
Murtix.Turn off the autoclose database option for your databases...
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Murtix Van Basten" <nospam@.nospam.org> wrote in message news:428e0b2c$1_1@.alt.athenanews.com...
> Hi,
> I noticed from the logs that, my sql server 2000 Standard Ed (runs on a
> windows 2k Advanced server) is starting up the databases over and over again
> every second. This goes on and on without stopping, like a nested loop. each
> time it does it with a different SPID. When I check the SPID, actually it is
> doing something else (such as running a query on a database). It is
> currently running SP3, and I am going to install SP4. I wonder if this
> resolves it. But before applying the SP4, I wonder if has anyone else run
> the similar or same problem. If, so is there a solution for that, or would
> SP4 takes care of this problem ?
> Thanks for any feedback.
> Regards.
> Murtix.
>|||How do I turn off the autoclose for databases ? (I dont remember I turned it
on).
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23IwjkyVXFHA.3320@.TK2MSFTNGP12.phx.gbl...
> Turn off the autoclose database option for your databases...
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Murtix Van Basten" <nospam@.nospam.org> wrote in message
> news:428e0b2c$1_1@.alt.athenanews.com...
>> Hi,
>> I noticed from the logs that, my sql server 2000 Standard Ed (runs on a
>> windows 2k Advanced server) is starting up the databases over and over
>> again
>> every second. This goes on and on without stopping, like a nested loop.
>> each
>> time it does it with a different SPID. When I check the SPID, actually it
>> is
>> doing something else (such as running a query on a database). It is
>> currently running SP3, and I am going to install SP4. I wonder if this
>> resolves it. But before applying the SP4, I wonder if has anyone else run
>> the similar or same problem. If, so is there a solution for that, or
>> would
>> SP4 takes care of this problem ?
>> Thanks for any feedback.
>> Regards.
>> Murtix.
>
>|||I found how to turn it off. I will post the result here. It may fix another
issue I am having, too.
"Murtix Van Basten" <nospam@.nospam.org> wrote in message
news:428e3b35$1_1@.alt.athenanews.com...
> How do I turn off the autoclose for databases ? (I dont remember I turned
> it on).
> "Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote
> in message news:%23IwjkyVXFHA.3320@.TK2MSFTNGP12.phx.gbl...
>> Turn off the autoclose database option for your databases...
>> --
>> Tibor Karaszi, SQL Server MVP
>> http://www.karaszi.com/sqlserver/default.asp
>> http://www.solidqualitylearning.com/
>>
>> "Murtix Van Basten" <nospam@.nospam.org> wrote in message
>> news:428e0b2c$1_1@.alt.athenanews.com...
>> Hi,
>> I noticed from the logs that, my sql server 2000 Standard Ed (runs on
>> a
>> windows 2k Advanced server) is starting up the databases over and over
>> again
>> every second. This goes on and on without stopping, like a nested loop.
>> each
>> time it does it with a different SPID. When I check the SPID, actually
>> it is
>> doing something else (such as running a query on a database). It is
>> currently running SP3, and I am going to install SP4. I wonder if this
>> resolves it. But before applying the SP4, I wonder if has anyone else
>> run
>> the similar or same problem. If, so is there a solution for that, or
>> would
>> SP4 takes care of this problem ?
>> Thanks for any feedback.
>> Regards.
>> Murtix.
>>
>>
>