Problem registering server in Enterprise manager

Hi,
I've recently installed SQL Server 2000 on a laptop. The laptop has a
wireless connection to the LAN. I am able to register the other SQL Servers
on the network on the intance on the laptop, but I cannot register the
instance on the laptop from the others; I get the error message "SQL Server
does not existor access denied.|ConnectionOpen (Connect()"
*SQL Server is running on the laptop
*SQL Server agent is also running
*The login and password I use are correct (and I use SQL Server
authentication).
*I have installed SP3a
*I have disabled the Windows XP SP2 firewall and even uninstalled my other
firewall.
*The instance of SQL Server I am trying to register does show up as an
available server in the Register SQL Server Wizard.
What might be the problem? I would also very much appreciate if someone
could point me in the right direction regarding how to troubleshoot this
better, so I can find out where the failure occurs.Try registering the instance of SQL on the laptop FROM the laptop, but do no
t
use the localhost syntax, use the same syntax which is failing from across
the wireless network, whether that's using a netbios name, or rcpip
addresss... What happens then?
"Daniel" wrote:

> Hi,
> I've recently installed SQL Server 2000 on a laptop. The laptop has a
> wireless connection to the LAN. I am able to register the other SQL Server
s
> on the network on the intance on the laptop, but I cannot register the
> instance on the laptop from the others; I get the error message "SQL Serve
r
> does not existor access denied.|ConnectionOpen (Connect()"
> *SQL Server is running on the laptop
> *SQL Server agent is also running
> *The login and password I use are correct (and I use SQL Server
> authentication).
> *I have installed SP3a
> *I have disabled the Windows XP SP2 firewall and even uninstalled my other
> firewall.
> *The instance of SQL Server I am trying to register does show up as an
> available server in the Register SQL Server Wizard.
> What might be the problem? I would also very much appreciate if someone
> could point me in the right direction regarding how to troubleshoot this
> better, so I can find out where the failure occurs.
>|||I am using the Register SQL Server Wizard in Enterprise manager. From the
list of available servers, I choose Laptop3 (the name of the laptop). If I d
o
the same thing FROM the laptop there are no problems. Does this indicate tha
t
the problem is not actually SQL Server related, but rather something with th
e
network? I had the same symptoms a while back when registering other
instances of SQL Server, and that time I solved it by allowing incoming
traffic on ports TCP 1433, UDP 1434 and file and printer sharing in the
Windows XP Firewall. This time that didn't solve the problem and neither did
deactivating the firewall altogether.
Perhaps I should also say that when I installed SQL Server on the laptop, I
had to choose to let SQL Server and SQL Server Agent log in on the local
system account, because for some reason the domain user account I tried coul
d
not be validated. I changed this after the installation so now they both log
in on a domain user account.
The activated protocols are TCP/IP (1433) and named pipes.
"CBretana" wrote:

> Try registering the instance of SQL on the laptop FROM the laptop, but do
not
> use the localhost syntax, use the same syntax which is failing from across
> the wireless network, whether that's using a netbios name, or rcpip
> addresss... What happens then?|||I'd have whoever is responsible for your wireless access point check it out.
Sometimes traffic is filtered either to or from the wireless network for
security reasons. There may be necessary components of the registration
process that aren't allowed to pass through the wireless access point.
"Daniel" <daXniel_kriXstensXen_@.hotmail.com (remove the Xs)> wrote in
message news:26EEB241-9BAA-40D5-8846-DAC1AB702E7D@.microsoft.com...
> Hi,
> I've recently installed SQL Server 2000 on a laptop. The laptop has a
> wireless connection to the LAN. I am able to register the other SQL
Servers
> on the network on the intance on the laptop, but I cannot register the
> instance on the laptop from the others; I get the error message "SQL
Server
> does not existor access denied.|ConnectionOpen (Connect()"
> *SQL Server is running on the laptop
> *SQL Server agent is also running
> *The login and password I use are correct (and I use SQL Server
> authentication).
> *I have installed SP3a
> *I have disabled the Windows XP SP2 firewall and even uninstalled my other
> firewall.
> *The instance of SQL Server I am trying to register does show up as an
> available server in the Register SQL Server Wizard.
> What might be the problem? I would also very much appreciate if someone
> could point me in the right direction regarding how to troubleshoot this
> better, so I can find out where the failure occurs.
>|||When you attempt to register the server, you are logging in. There are two
ways to do this, with a userID and password, or using what is called
"Integrated security" which uses the userID / password of whomever is logged
on to the box you're doing it from. Which of these you are using depends on
how you installed SQL Server. When you installed SQL, did you select
Integrated Secutrity only, or did you choose Itegrated security AND SQL
Server Security ?
When you attempt to register the SQL Server, are you asked to enter a UserID
And Password? My guess is that you are not.. If that's true, then when you
attempt to register from another box, the SQL Server is not recognozing the
UserID of whomever is logged on there as being a valid Login...
Try to actually enter the "sa" and the sa password from the remote
Enterprise manager, AND from the laptop Enterprise Manager, and see if
there's a difference...
"Daniel" wrote:

> I am using the Register SQL Server Wizard in Enterprise manager. From the
> list of available servers, I choose Laptop3 (the name of the laptop). If I
do
> the same thing FROM the laptop there are no problems. Does this indicate t
hat
> the problem is not actually SQL Server related, but rather something with
the
> network? I had the same symptoms a while back when registering other
> instances of SQL Server, and that time I solved it by allowing incoming
> traffic on ports TCP 1433, UDP 1434 and file and printer sharing in the
> Windows XP Firewall. This time that didn't solve the problem and neither d
id
> deactivating the firewall altogether.
> Perhaps I should also say that when I installed SQL Server on the laptop,
I
> had to choose to let SQL Server and SQL Server Agent log in on the local
> system account, because for some reason the domain user account I tried co
uld
> not be validated. I changed this after the installation so now they both l
og
> in on a domain user account.
> The activated protocols are TCP/IP (1433) and named pipes.
>
> "CBretana" wrote:
>
>|||"CBretana" wrote:
> When you attempt to register the server, you are logging in. There are tw
o
> ways to do this, with a userID and password, or using what is called
> "Integrated security" which uses the userID / password of whomever is logg
ed
> on to the box you're doing it from. Which of these you are using depends
on
> how you installed SQL Server. When you installed SQL, did you select
> Integrated Secutrity only, or did you choose Itegrated security AND SQL
> Server Security ?
I chose mixed mode.

> When you attempt to register the SQL Server, are you asked to enter a User
ID
> And Password? My guess is that you are not.. If that's true, then when yo
u
> attempt to register from another box, the SQL Server is not recognozing th
e
> UserID of whomever is logged on there as being a valid Login...
> Try to actually enter the "sa" and the sa password from the remote
> Enterprise manager, AND from the laptop Enterprise Manager, and see if
> there's a difference...
Actually that's precisely what I do, and it only works from the laptop.
Sorry I didn't mention this already.|||Unfortunately, the guy responsible for these things are on vacation. I've
been able to register SQL Servers on laptops connected to the wireless acces
s
point previously. However, I did tamper with the wireless access point to ge
t
the new laptops to be able to connect to it. Pretty stupid of me not to chec
k
whether the SQL Servers on the old laptops are still accesible... That will
be the first thing I'll do on Monday. Even if it doesn't solve the problem i
t
will narrow down the possible causes of it.
"Mike Jansen" wrote:

> I'd have whoever is responsible for your wireless access point check it ou
t.
> Sometimes traffic is filtered either to or from the wireless network for
> security reasons. There may be necessary components of the registration
> process that aren't allowed to pass through the wireless access point.
> "Daniel" <daXniel_kriXstensXen_@.hotmail.com (remove the Xs)> wrote in
> message news:26EEB241-9BAA-40D5-8846-DAC1AB702E7D@.microsoft.com...
> Servers
> Server
>
>|||Ok, sorry, I should have asked this last time but forgot, since I askedit
first time...
From laptop, when you register, are you using "local" or typing the
laptop's server name, or IP Address to specify the server?
If you are using "local", then try using the same thing, on the laptop, that
is failing from over the network...
Say it's ServerName...
If that then also fails, on laptop, same as it fails from over network,
then your problem is related to networking. Try using the IPAddress
directly instead of server name. If that works, then problem is name
resolution (DNS or WINs resolution) issues.
"Daniel" wrote:

> "CBretana" wrote:
> I chose mixed mode.
>
> Actually that's precisely what I do, and it only works from the laptop.
> Sorry I didn't mention this already.

Problem Installing MS-SQLSERVER on Laptop

Hello Friends at dBForum !!

:confused: I have a strange problem, and I need to know what would be the source of this. I have a laptop computer with the following configuration:

Pentium III
Brand : Toshiba
Speed : 500 Mhz
RAM : 192 MB
Hard Disk : 6 GB
Space Available : 4 GB
O.S. : Windows 98

The computer works pretty good and run different applications. I was trying to install MS-SQLSERVER 2000 and I checked out the software and hardware requierements for that and everything seems to be fine. The reason that I need it its because of my trips, and its incredible I have a desktop computer with almost the same configuration and runs pretty good.

When you have a problem installing SQL-SERVER 2000 you have a file called cnfgsvr with all the explanation. I got this at hand so you can see better the problem:

Iniciando servicio ...

Conectando con el servidor ...

driver={sql server};server=3110CT;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][Shared Memory]No existe el servidor SQL Server o se ha denegado el acceso al mismo.

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).

driver={sql server};server=3110CT;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][Shared Memory]No existe el servidor SQL Server o se ha denegado el acceso al mismo.

[Microsoft][ODBC SQL Server Driver][Shared Memory]ConnectionOpen (Connect()).

driver={sql server};server=.;UID=sa;PWD=;database=master

[Microsoft][ODBC SQL Server Driver][Named Pipes]No existe el servidor SQL Server o se ha denegado el acceso al mismo.

[Microsoft][ODBC SQL Server Driver][Named Pipes]ConnectionOpen (Connect()).

Error de configuracin del servidor SQL Server.

This is what I got after the installation fails: Here is the log sequence, and I got this from a file called sqlstp2000:

14:37:28 CoreCOM
14:37:28 CoreCOM\Res1033
14:37:28 CoreCOM\ResIntl
14:37:28 CoreTool
14:37:28 CoreTool\Res1033
14:37:28 CoreTool\ResOther
14:37:28 DBLibCli
14:37:28 SFExt
14:37:28 SFExt\ActiveX
14:37:28 SFExt\ActiveX\Res1033
14:37:28 SFExt\ActiveX\ResIntl
14:37:28 SFExt\Res1033
14:37:28 SFExt\ResIntl
14:37:28 Trace
14:37:28 Trace\Res1033
14:37:28 Trace\ResOther
14:37:28 MiscCore
14:37:28 MC
14:37:28 MC\MC1033
14:37:28 MC\MCIntl
14:37:28 MC\Help
14:37:28 SQLMgr
14:37:28 SQLMgr\Res1033
14:37:28 SQLMgr\ResIntl
14:37:28 SvrTool
14:37:28 SvrTool\Res1033
14:37:28 SvrTool\ResIntl
14:37:28 DTSUI
14:37:28 DTSUI\Res1033
14:37:28 DTSUI\ResIntl
14:37:28 MSOlap
14:37:28 MSOlap\Res1033
14:37:28 MSOlap\ResIntl
14:37:28 ATL
14:37:28 ATL\winnt
14:37:28 ATL\win9x
14:37:28 MFC42U
14:37:28 VC
14:37:28 VB
14:37:28 SQLAdHlp
14:37:28 SQLAdHlp\Res1033
14:37:28 SQLAdHlp\ResOther
14:37:28 {E07FDDC8-5A21-11d2-9DAD-00C04F79D434}
14:37:28 {E07FDDBE-5A21-11d2-9DAD-00C04F79D434}
14:37:28 {E07FDDC7-5A21-11d2-9DAD-00C04F79D434}
14:37:28 {E07FDDC0-5A21-11d2-9DAD-00C04F79D434}
14:37:28 {E07FDDBF-5A21-11d2-9DAD-00C04F79D434}
14:37:28 End Action LogSelectedComponents
14:37:28 Begin Action InstallPkgs:
14:37:28 Begin Action: Locked Connectivity Files Check
14:37:29 ConnectivityLocked returned: 0
14:37:29 The operation completed successfully.

14:37:29 End Action: Locked Connectivity Files Check
14:37:29 El programa de instalacin est instalando Microsoft Data Access Components (MDAC)...
14:37:29 E:\X86\Other\sqlredis.exe /q:a /C:"setupre.exe WARN=1 -s -SMS"
14:38:10 ExitCode: 0
14:38:10 El programa de instalacin est instalando Microsoft Management Console (MMC) ...
14:38:10 E:\X86\Other\instmmc.exe /Q
14:38:36 Process Exit Code: (0)
14:38:36 Se est instalando el Coordinador de transacciones distribuidas de Microsoft (MSDTC)...
14:38:36 E:\X86\Other\dtcsetup.exe /q:a /r:n
14:38:53 Process Exit Code: (0)
14:38:53 /Q:A /T:C:\WINDOWS\TEMP\ixp001.tmp
14:38:53 El programa de instalacin est instalando la Ayuda HTML...
14:38:55 HTML Help installer exit code: 0
14:39:18 End Action InstallPkgs
14:39:18 Begin Action MoveFileData:
14:39:18 Enabled SELFREGISTERBATCH
14:39:18 Enabled CORECOMPONENTHANDLING
14:42:27 ComponentMoveData exit code: -117
14:42:27 ComponentMoveData: -117
14:42:51 No se puede leer el archivo especificado. Puede ser a causa de una conexin de red de bajo rendimiento. Corrija el problema y reinicie el programa de instalacin. ( This message says that the computer can not read the specified file or its a problem related to a network connection of low performance. According to the message here shown, I have to fix the problem and reinstall. ) I did it, even I deleted the entries related to this on the windows registry and after restarting the problem stills...

Archivo: E:\X86\SETUP\..\..\Install\replmerg.sql

14:42:51 Begin Action: MoveFileDataSpecial
14:42:52 End Action: MoveFileDataSpecial
14:42:52 Action CleanUpInstall:
14:42:52 StatsGenerate returned: 2
14:42:52 StatsGenerate (0x0,0x1,0xf0000,0x0,1034,303,0x0,0x1,0,0,0
14:42:52 StatsGenerate -1,Alessandro)
14:42:52 Installation Failed.

On the other hand, I tried to install MS-SQLSERVER 7.0 ( you know if I can get do it with MS-SQLSERVER 2000 ) and this is what I got :

2005-02-17 13:08:26.77 kernel Microsoft SQL Server 7.00 - 7.00.623 (Intel X86)
Nov 27 1998 22:20:07
Copyright (c) 1988-1998 Microsoft Corporation
Desktop Edition on Windows 4.10 (Build 2222: A )

2005-02-17 13:08:26.84 kernel Copyright 1987-1998 Microsoft Corporation.
2005-02-17 13:08:26.84 kernel Reservados todos los derechos.
2005-02-17 13:08:26.84 kernel Registrando los mensajes de SQL Server en el archivo 'C:\MSSQL7\log\ERRORLOG'.
2005-02-17 13:08:27.00 kernel initconfig: nmero de conexiones de usuario limitado a 32767.
2005-02-17 13:08:27.01 kernel SQL Server se iniciar con clase de prioridad 'normal'( se detect 1 CPU).
2005-02-17 13:08:27.21 kernel User Mode Scheduler configured for thread processing
2005-02-17 13:08:28.61 server Directory Size: 8087
2005-02-17 13:08:28.68 spid1 Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks
2005-02-17 13:08:28.74 spid1 failed to get sqlservr image range
2005-02-17 13:08:28.78 spid1 Advertencia ******************
2005-02-17 13:08:28.79 spid1 SQL Server iniciado en modo de usuario nico. Se permiten las actualizaciones en los catlogos del sistema.
2005-02-17 13:08:28.79 spid1 Advertencia ******************
2005-02-17 13:08:28.79 spid1 Recovering only master database
2005-02-17 13:08:28.85 spid1 Iniciando la base de datos 'master'.
2005-02-17 13:08:28.85 spid1 Opening file C:\MSSQL7\data\master.mdf.
2005-02-17 13:08:28.97 spid1 Opening file C:\MSSQL7\data\mastlog.ldf.
2005-02-17 13:08:29.06 spid1 Cargando el mtodo de intercalacin Unicode de SQL Server.
2005-02-17 13:08:29.16 spid1 Cargando el orden y conjunto de caracteres no Unicode de SQL Server.
2005-02-17 13:08:29.41 spid1 4 transacciones confirmadas en la base de datos 'master' (1).
2005-02-17 13:08:29.41 spid1 0 transacciones deshechas en la base de datos 'master' (1).
2005-02-17 13:08:29.65 spid1 El servidor no tiene nombre.
2005-02-17 13:08:29.65 kernel Se utiliza 'SQLEVN70.DLL' versin '7.00.623'.
2005-02-17 13:08:29.72 kernel Se utiliza 'OPENDS60.DLL' versin '7.00.00.0623'.
2005-02-17 13:08:29.83 ods Utilizando 'SSMSSH70.DLL' versin '7.0.623' para escuchar en ''.
2005-02-17 13:08:29.89 ods Utilizando 'SSMSSO70.DLL' versin '7.0.623' para escuchar en '1433'.
2005-02-17 13:08:30.09 ods Utilizando 'SSMSRP70.DLL' versin '7.0.623' para escuchar en '3110CT'.
2005-02-17 13:08:31.11 spid1 El mtodo de intercalacin Unicode de SQL Server es:
2005-02-17 13:08:31.11 spid1 'English' (Id. = 1033).
2005-02-17 13:08:31.11 spid1 estilo de comparacin = 196609.
2005-02-17 13:08:31.11 spid1 El orden no Unicode de SQL Server es:
2005-02-17 13:08:31.11 spid1 'nocase_iso' (Id. = 52).
2005-02-17 13:08:31.11 spid1 El juego de caracteres no Unicode de SQL Server es:
2005-02-17 13:08:31.11 spid1 'iso_1' (Id. = 1).
2005-02-17 13:08:31.19 kernel Warning: override, autoexec procedures skipped.
2005-02-17 13:10:23.67 kernel SQL Server terminar debido a una peticin de 'detencin' del Administrador de control de servicios.

Accordiing to the message shown in the bottom line, we may see its like the installation were stopped because of a request of the Control Service Manager. I never stop the installation or something like that but I dont have a clue why or where is the problem here.

My desktop computer is standalone and works without problems. Of course I read that if you have PWS ( Personal Web Server ) running you may need to stop that first, and then proceed. I did it and it never worked.

If you have any suggestion about it, this would be greatly appreciated.

Thank you so much,

Cordially,

Alessandro Barbieri - PeruHi

Remove SQL Server and use MSDE insted.|||I will try it. Thanks