I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
application on multiple workstations.
These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
All workstations can access and ping the server under 1MS.
When the client application opens and reads data from the database server,
it takes a short time for this to be performed on the Win2000 Pro machines,
but all the XP machines take an abnormally long time to connect and to
retrieve the data.
The XP's do connect, but the retrieval is very slow, sometimes it timesout
during a retrieval.
This occurs even when nobody is connected to the database, so I've ruled out
the governer.
I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
The install process only installed MDAC 2.7 if the current version is before
that.
Anybody have an idea what might be the problem?
All responses are welcome.
TIA
Jim K
Hi Jim,
Name resolution problems perhaps? Try connecting to the IP address instead
of the server name to find out.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
> I've installed MSDE SP3a on a Windows 2000 Server, and the VB6 client
> application on multiple workstations.
> These workstations are either Win2000 Pro or WinXP Pro (both SP1 and SP2).
> All workstations can access and ping the server under 1MS.
> When the client application opens and reads data from the database server,
> it takes a short time for this to be performed on the Win2000 Pro
> machines,
> but all the XP machines take an abnormally long time to connect and to
> retrieve the data.
> The XP's do connect, but the retrieval is very slow, sometimes it timesout
> during a retrieval.
> This occurs even when nobody is connected to the database, so I've ruled
> out
> the governer.
> I'm using ADO to connect and all PC's have MDAC 2.7 or greater.
> The install process only installed MDAC 2.7 if the current version is
> before
> that.
> Anybody have an idea what might be the problem?
> All responses are welcome.
> TIA
> Jim K
>
|||Thanks, I didn't think of that.
I have connected using the IP in other apps, but that was to the default
instance.
Since I have a named instance in this case, how would I format the IP and
instance?
Ex: default instance installed on server SERVER1, I can substitute the IP
for SERVER1
for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
Thanks!
"Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...[vbcol=seagreen]
> Hi Jim,
> Name resolution problems perhaps? Try connecting to the IP address instead
> of the server name to find out.
> HTH,
> --
> Greg Low [MVP]
> MSDE Manager SQL Tools
> www.whitebearconsulting.com
> "Jim K" <krusej@.megsinet.net> wrote in message
> news:enMo6BQ7EHA.1596@.tk2msftngp13.phx.gbl...
SP2).[vbcol=seagreen]
server,[vbcol=seagreen]
timesout
>
|||Hi Jim,
I'd suggest setting a fixed port for the named instance, then just connect
to that port. Even set up an alias on the client boxes that knows about the
port. It would completely avoid the sql browser function that essentially
just maps your instance name to a port anyway. To do that:
1. Open svrnetcn.exe and for the named instance, uncheck the "dynamic port"
box and select your own port (ie 38474 or something).
2. Restart the instance.
3. On the client, run cliconfg.exe and set up an alias pointing to that port
on the server.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Jim K" <krusej@.megsinet.net> wrote in message
news:u6vH8Mo7EHA.2196@.TK2MSFTNGP11.phx.gbl...
> Thanks, I didn't think of that.
> I have connected using the IP in other apps, but that was to the default
> instance.
> Since I have a named instance in this case, how would I format the IP and
> instance?
> Ex: default instance installed on server SERVER1, I can substitute the
> IP
> for SERVER1
> for named instance SERVER1/DB1, how would I format the IP? IP#/DB1 ?
> Thanks!
> "Greg Low [MVP]" <greglow@.lowell.com.au> wrote in message
> news:u0zukkl7EHA.3124@.TK2MSFTNGP11.phx.gbl...
> SP2).
> server,
> timesout
>
sql
Showing posts with label windows. Show all posts
Showing posts with label windows. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
MSDE 2000: Authentication failed despite BLANKSAPWD
Hi!
We're having troubles on a Windows 2003 Server. MSDE 1.0 does not
install (even though we already have this setup at other customers).
So I downloaded MSDE 2000. Unfortunately, somebody else just executed the
installation procedure without setup-parameters. I wanted to have an empty
password (I know, I know. But it is a closed system) and I need SQL
security mode and network protocols.
Thus I uninstalled MSDE 2000 again and launched setup.exe this way:
setup DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL BLANKSAPWD=1
The installation went fine and I did *no* receive the error about the
trusted connections. However, I received "Authentication for user sa
failed" when simply doing this
osql -Usa -P -dmaster
Any clues?
Stefan
On Thu, 28 Oct 2004 10:31:15 +0200, Stefan M. Huber <looseleaf@.gmx.net>
wrote:
> The installation went fine and I did *no* receive the error about the
> trusted connections. However, I received "Authentication for user sa
> failed" when simply doing this
> osql -Usa -P -dmaster
> Any clues?
The only thing that I can tell you is that the MSDE instance accepts the
administrator password as sa password...So the problem is solved but not
the circumstances that produced this setup.
Stefan
We're having troubles on a Windows 2003 Server. MSDE 1.0 does not
install (even though we already have this setup at other customers).
So I downloaded MSDE 2000. Unfortunately, somebody else just executed the
installation procedure without setup-parameters. I wanted to have an empty
password (I know, I know. But it is a closed system) and I need SQL
security mode and network protocols.
Thus I uninstalled MSDE 2000 again and launched setup.exe this way:
setup DISABLENETWORKPROTOCOLS=0 SECURITYMODE=SQL BLANKSAPWD=1
The installation went fine and I did *no* receive the error about the
trusted connections. However, I received "Authentication for user sa
failed" when simply doing this
osql -Usa -P -dmaster
Any clues?
Stefan
On Thu, 28 Oct 2004 10:31:15 +0200, Stefan M. Huber <looseleaf@.gmx.net>
wrote:
> The installation went fine and I did *no* receive the error about the
> trusted connections. However, I received "Authentication for user sa
> failed" when simply doing this
> osql -Usa -P -dmaster
> Any clues?
The only thing that I can tell you is that the MSDE instance accepts the
administrator password as sa password...So the problem is solved but not
the circumstances that produced this setup.
Stefan
MSDE 2000 SP3 Merge Module does not installing on windowx XP
Dear Sirs.
MSDE 2000 SP 3a Merge Module Does not installing on Windows XP Without XP
Service Pack.
It is work if SP1 is instaled on Windows XP. But how i can use that merge
modules if SP1 is not installed on Windows XP ?
Thank you in advance.
Install SP1 on Windows XP. You can generally do this if it's a legal copy.
"Irakli Lomidze" <Irakli_Lomidze@.access.sanet.ge> wrote in message
news:uzsiaVNuEHA.2196@.TK2MSFTNGP14.phx.gbl...
> Dear Sirs.
> MSDE 2000 SP 3a Merge Module Does not installing on Windows XP Without XP
> Service Pack.
> It is work if SP1 is instaled on Windows XP. But how i can use that merge
> modules if SP1 is not installed on Windows XP ?
> Thank you in advance.
>
MSDE 2000 SP 3a Merge Module Does not installing on Windows XP Without XP
Service Pack.
It is work if SP1 is instaled on Windows XP. But how i can use that merge
modules if SP1 is not installed on Windows XP ?
Thank you in advance.
Install SP1 on Windows XP. You can generally do this if it's a legal copy.
"Irakli Lomidze" <Irakli_Lomidze@.access.sanet.ge> wrote in message
news:uzsiaVNuEHA.2196@.TK2MSFTNGP14.phx.gbl...
> Dear Sirs.
> MSDE 2000 SP 3a Merge Module Does not installing on Windows XP Without XP
> Service Pack.
> It is work if SP1 is instaled on Windows XP. But how i can use that merge
> modules if SP1 is not installed on Windows XP ?
> Thank you in advance.
>
Monday, March 26, 2012
MSDE 2000 SP3 fails to install
MSDE 2000 SP3 fails to install on a windows 2000 terminal server. The error
message I get is "MSDE 200 SP3 installation failed with exit code 1603" and
“A strong password is required for security reasons. Please use SAPWD switch
to supply the same. Refer to read me for more details. Setup will now exit.”
I have come across this once before and removed the server from the domain,
in this case that is not an option. I have denied the read right to the
default domain policy which is the only policy that is applying. Anybody have
any ideas on how I can install this.
hi bob,
bob wrote:
> MSDE 2000 SP3 fails to install on a windows 2000 terminal server. The
> error message I get is "MSDE 200 SP3 installation failed with exit
> code 1603" and "A strong password is required for security reasons.
> Please use SAPWD switch to supply the same. Refer to read me for more
> details. Setup will now exit." I have come across this once before
> and removed the server from the domain, in this case that is not an
> option. I have denied the read right to the default domain policy
> which is the only policy that is applying. Anybody have any ideas on
> how I can install this.
as indicated by the error description, you have to provide a strong password
for "sa" login as a parameter, in the form of
c:\...\>setup.exe ... SAPWD="your strong password" ...
all available parameters for the setup.exe bootstrap installer are provided
at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
or, if you really are sure (please don't) you do not need a strong sa
password, you have to provide the
BLANKSAPWD=1
parameter
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea
I tried BLANKSAPWD=1 and I even tried setting a strong password, neither one
worked. Do you have any other suggestions?
"Andrea Montanari" wrote:
> hi bob,
> bob wrote:
> as indicated by the error description, you have to provide a strong password
> for "sa" login as a parameter, in the form of
> c:\...\>setup.exe ... SAPWD="your strong password" ...
> all available parameters for the setup.exe bootstrap installer are provided
> at
> http://msdn.microsoft.com/library/de...stsql_84xl.asp
> or, if you really are sure (please don't) you do not need a strong sa
> password, you have to provide the
> BLANKSAPWD=1
> parameter
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Bob,
bob wrote:
> Andrea
> I tried BLANKSAPWD=1 and I even tried setting a strong password,
> neither one worked. Do you have any other suggestions?
>
can you please post your paramenters?
what kind of error do you get?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
message I get is "MSDE 200 SP3 installation failed with exit code 1603" and
“A strong password is required for security reasons. Please use SAPWD switch
to supply the same. Refer to read me for more details. Setup will now exit.”
I have come across this once before and removed the server from the domain,
in this case that is not an option. I have denied the read right to the
default domain policy which is the only policy that is applying. Anybody have
any ideas on how I can install this.
hi bob,
bob wrote:
> MSDE 2000 SP3 fails to install on a windows 2000 terminal server. The
> error message I get is "MSDE 200 SP3 installation failed with exit
> code 1603" and "A strong password is required for security reasons.
> Please use SAPWD switch to supply the same. Refer to read me for more
> details. Setup will now exit." I have come across this once before
> and removed the server from the domain, in this case that is not an
> option. I have denied the read right to the default domain policy
> which is the only policy that is applying. Anybody have any ideas on
> how I can install this.
as indicated by the error description, you have to provide a strong password
for "sa" login as a parameter, in the form of
c:\...\>setup.exe ... SAPWD="your strong password" ...
all available parameters for the setup.exe bootstrap installer are provided
at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
or, if you really are sure (please don't) you do not need a strong sa
password, you have to provide the
BLANKSAPWD=1
parameter
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Andrea
I tried BLANKSAPWD=1 and I even tried setting a strong password, neither one
worked. Do you have any other suggestions?
"Andrea Montanari" wrote:
> hi bob,
> bob wrote:
> as indicated by the error description, you have to provide a strong password
> for "sa" login as a parameter, in the form of
> c:\...\>setup.exe ... SAPWD="your strong password" ...
> all available parameters for the setup.exe bootstrap installer are provided
> at
> http://msdn.microsoft.com/library/de...stsql_84xl.asp
> or, if you really are sure (please don't) you do not need a strong sa
> password, you have to provide the
> BLANKSAPWD=1
> parameter
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||hi Bob,
bob wrote:
> Andrea
> I tried BLANKSAPWD=1 and I even tried setting a strong password,
> neither one worked. Do you have any other suggestions?
>
can you please post your paramenters?
what kind of error do you get?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
MSDE 2000 Revision A installation
Can MSDE 2000 Revision A be installed on Windows Server 2003 Enterprised
Version For 64-Bit?
hi Roy,
"Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
news:805C6FFA-B8EF-4B14-8C00-73FEE032232E@.microsoft.com...
> Can MSDE 2000 Revision A be installed on Windows Server 2003 Enterprised
> Version For 64-Bit?
never tried [still not own a 64bit processor =:-( ], but I think yes, as you
can install SQL Server 2000 too...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Here is something I copied from MSDE document. You can see that the 64-bit
version is not listed. That's why I am wondering if MSDE can be installed on
it, since it fails when I tried. I want to know if this is the reason for
this failure.
Operating System Requirements
To use MSDE 2000, you must have installed one of these operating systems:
Windows Server 2003 Standard Edition, Windows Server 2003 Enterprise
Edition, Windows Server 2003 Datacenter Edition.
Windows 2000 Server, Windows 2000 Advanced Server, Windows 2000 Datacenter
Server.
Windows NT Server 4.0, SP5 or later; Windows NT Server 4.0, Enterprise
Edition, SP5 or later; Windows NT Workstation 4.0, SP5 or later.
Windows XP Professional, Windows XP Home Edition.
Windows 2000 Professional.
Windows Millennium Edition.
Windows 98. Windows 98 Second Edition is required if the computer does not
have a network card.
"Andrea Montanari" wrote:
> hi Roy,
> "Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
> news:805C6FFA-B8EF-4B14-8C00-73FEE032232E@.microsoft.com...
> never tried [still not own a 64bit processor =:-( ], but I think yes, as you
> can install SQL Server 2000 too...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Roy,
"Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
news:2E2CE882-3889-46E9-9751-BB444D9EB9E3@.microsoft.com...
> Here is something I copied from MSDE document. You can see that the 64-bit
> version is not listed. That's why I am wondering if MSDE can be installed
on
> it, since it fails when I tried. I want to know if this is the reason for
> this failure.
>...
actually may be...
what kind of error do you get as installation result in the verbose log
file?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Here is the last section from the log file:
Property(C): DATABASE = C:\DOCUME~1\FOCUS\LOCALS~1\Temp\3cfe77c.msi
Property(C): OriginalDatabase = C:\cmx\MSDERelA\Setup\SqlRun01.msi
Property(C): UILevel = 3
Property(C): ACTION = INSTALL
=== Logging stopped: 9/15/2004 13:18:44 ===
MSI (c) (54:A4): Note: 1: 1708
MSI (c) (54:A4): Product: Microsoft SQL Server Desktop Engine --
Installation operation failed.
MSI (c) (54:A4): Grabbed execution mutex.
MSI (c) (54:A4): Cleaning up uninstalled install packages, if any exist
MSI (c) (54:A4): MainEngineThread is returning 1603
=== Verbose logging stopped: 9/15/2004 13:18:44 ===
What does "MSI (c) (54:A4): Note: 1: 1708 " mean?
Thanks.
Rong
"Andrea Montanari" wrote:
> hi Roy,
> "Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
> news:2E2CE882-3889-46E9-9751-BB444D9EB9E3@.microsoft.com...
> on
> actually may be...
> what kind of error do you get as installation result in the verbose log
> file?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||BTW, the error msg is "Setup failed to configure the server. Refer to the
server error logs ans setup error logs for more information" when
installation stops.
"Andrea Montanari" wrote:
> hi Roy,
> "Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
> news:2E2CE882-3889-46E9-9751-BB444D9EB9E3@.microsoft.com...
> on
> actually may be...
> what kind of error do you get as installation result in the verbose log
> file?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Roy,
"Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
news:B1D6F8B1-67F1-48F9-B7D4-80D1E29E54BD@.microsoft.com...
> BTW, the error msg is "Setup failed to configure the server. Refer to the
> server error logs ans setup error logs for more information" when
> installation stops.
>
http://support.microsoft.com/default...99&Product=sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Still not working after I remove the data folder.
Instead the log files in the data folder after a failed install shows the
following:
Error 823 Severity 24 State 2
Can not recover the master database. Exiting.
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
An error occured while attempting to start the service (1460)
Any clue?
Thanks.
"Andrea Montanari" wrote:
> hi Roy,
> "Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
> news:B1D6F8B1-67F1-48F9-B7D4-80D1E29E54BD@.microsoft.com...
> http://support.microsoft.com/default...99&Product=sql
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
Version For 64-Bit?
hi Roy,
"Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
news:805C6FFA-B8EF-4B14-8C00-73FEE032232E@.microsoft.com...
> Can MSDE 2000 Revision A be installed on Windows Server 2003 Enterprised
> Version For 64-Bit?
never tried [still not own a 64bit processor =:-( ], but I think yes, as you
can install SQL Server 2000 too...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Here is something I copied from MSDE document. You can see that the 64-bit
version is not listed. That's why I am wondering if MSDE can be installed on
it, since it fails when I tried. I want to know if this is the reason for
this failure.
Operating System Requirements
To use MSDE 2000, you must have installed one of these operating systems:
Windows Server 2003 Standard Edition, Windows Server 2003 Enterprise
Edition, Windows Server 2003 Datacenter Edition.
Windows 2000 Server, Windows 2000 Advanced Server, Windows 2000 Datacenter
Server.
Windows NT Server 4.0, SP5 or later; Windows NT Server 4.0, Enterprise
Edition, SP5 or later; Windows NT Workstation 4.0, SP5 or later.
Windows XP Professional, Windows XP Home Edition.
Windows 2000 Professional.
Windows Millennium Edition.
Windows 98. Windows 98 Second Edition is required if the computer does not
have a network card.
"Andrea Montanari" wrote:
> hi Roy,
> "Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
> news:805C6FFA-B8EF-4B14-8C00-73FEE032232E@.microsoft.com...
> never tried [still not own a 64bit processor =:-( ], but I think yes, as you
> can install SQL Server 2000 too...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Roy,
"Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
news:2E2CE882-3889-46E9-9751-BB444D9EB9E3@.microsoft.com...
> Here is something I copied from MSDE document. You can see that the 64-bit
> version is not listed. That's why I am wondering if MSDE can be installed
on
> it, since it fails when I tried. I want to know if this is the reason for
> this failure.
>...
actually may be...
what kind of error do you get as installation result in the verbose log
file?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Here is the last section from the log file:
Property(C): DATABASE = C:\DOCUME~1\FOCUS\LOCALS~1\Temp\3cfe77c.msi
Property(C): OriginalDatabase = C:\cmx\MSDERelA\Setup\SqlRun01.msi
Property(C): UILevel = 3
Property(C): ACTION = INSTALL
=== Logging stopped: 9/15/2004 13:18:44 ===
MSI (c) (54:A4): Note: 1: 1708
MSI (c) (54:A4): Product: Microsoft SQL Server Desktop Engine --
Installation operation failed.
MSI (c) (54:A4): Grabbed execution mutex.
MSI (c) (54:A4): Cleaning up uninstalled install packages, if any exist
MSI (c) (54:A4): MainEngineThread is returning 1603
=== Verbose logging stopped: 9/15/2004 13:18:44 ===
What does "MSI (c) (54:A4): Note: 1: 1708 " mean?
Thanks.
Rong
"Andrea Montanari" wrote:
> hi Roy,
> "Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
> news:2E2CE882-3889-46E9-9751-BB444D9EB9E3@.microsoft.com...
> on
> actually may be...
> what kind of error do you get as installation result in the verbose log
> file?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||BTW, the error msg is "Setup failed to configure the server. Refer to the
server error logs ans setup error logs for more information" when
installation stops.
"Andrea Montanari" wrote:
> hi Roy,
> "Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
> news:2E2CE882-3889-46E9-9751-BB444D9EB9E3@.microsoft.com...
> on
> actually may be...
> what kind of error do you get as installation result in the verbose log
> file?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||hi Roy,
"Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
news:B1D6F8B1-67F1-48F9-B7D4-80D1E29E54BD@.microsoft.com...
> BTW, the error msg is "Setup failed to configure the server. Refer to the
> server error logs ans setup error logs for more information" when
> installation stops.
>
http://support.microsoft.com/default...99&Product=sql
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Still not working after I remove the data folder.
Instead the log files in the data folder after a failed install shows the
following:
Error 823 Severity 24 State 2
Can not recover the master database. Exiting.
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
An error occured while attempting to start the service (1460)
Any clue?
Thanks.
"Andrea Montanari" wrote:
> hi Roy,
> "Roy" <Roy@.discussions.microsoft.com> ha scritto nel messaggio
> news:B1D6F8B1-67F1-48F9-B7D4-80D1E29E54BD@.microsoft.com...
> http://support.microsoft.com/default...99&Product=sql
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
MSDE 2000 Release A won't talk
MSDE 2000 Release A installed under windows 2000 pro will not
communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?
Have set DISABLENETWORKPROTOCOLS=0 at install time.
Install log shows installation successful..
Control Panel> Admin Tools> Services section shows SQL server instance
running.
Disabling firewall has no effect.
SQL Server Manager (icon at bottom right in task tray - this
starts/stops Server instances), on same computer as SQL Server
instance, shows only instance "H" which is the same as the computer
name. (This instance was uninstalled before new instance was
installed.) Typing new instance name ("H\ABC" and variations) into
top combo box produces error messages such as "wrong format for name",
"Network path not found" "RPC service not running". What is the
correct computer/name format? Key problem is clearly that Service
Manager can't communicate with this local MSDE instance.
All Windows 2000 updates from MS web site have been installed.
Objective is to operate MS Access on computer X (also running Win 2000
Pro) with computer H as a peer that hosts MSDE.
Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system?
Have you installed SP3a?
Steve
<noname@.noname.com> wrote in message
news:40d55341.11850570@.nntp.flfrd.phub.net.cable.r ogers.com...
> MSDE 2000 Release A installed under windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format? Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system?
|||Hi Steve,
MSDE 2000A already contains SQL Server SP3a updates.
Mark
Ottawa, Canada
On Tue, 22 Jun 2004 15:25:07 -0400, "Steve Thompson"
<stevethompson@.nomail.please> wrote:
>Have you installed SP3a?
>Steve
communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?
Have set DISABLENETWORKPROTOCOLS=0 at install time.
Install log shows installation successful..
Control Panel> Admin Tools> Services section shows SQL server instance
running.
Disabling firewall has no effect.
SQL Server Manager (icon at bottom right in task tray - this
starts/stops Server instances), on same computer as SQL Server
instance, shows only instance "H" which is the same as the computer
name. (This instance was uninstalled before new instance was
installed.) Typing new instance name ("H\ABC" and variations) into
top combo box produces error messages such as "wrong format for name",
"Network path not found" "RPC service not running". What is the
correct computer/name format? Key problem is clearly that Service
Manager can't communicate with this local MSDE instance.
All Windows 2000 updates from MS web site have been installed.
Objective is to operate MS Access on computer X (also running Win 2000
Pro) with computer H as a peer that hosts MSDE.
Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system?
Have you installed SP3a?
Steve
<noname@.noname.com> wrote in message
news:40d55341.11850570@.nntp.flfrd.phub.net.cable.r ogers.com...
> MSDE 2000 Release A installed under windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format? Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system?
|||Hi Steve,
MSDE 2000A already contains SQL Server SP3a updates.
Mark
Ottawa, Canada
On Tue, 22 Jun 2004 15:25:07 -0400, "Steve Thompson"
<stevethompson@.nomail.please> wrote:
>Have you installed SP3a?
>Steve
MSDE 2000 Release A won't talk
MSDE 2000 Release A installed under Windows 2000 pro will not
communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?
Have set DISABLENETWORKPROTOCOLS=0 at install time.
Install log shows installation successful..
Control Panel> Admin Tools> Services section shows SQL server instance
running.
Disabling firewall has no effect.
SQL Server Manager (icon at bottom right in task tray - this
starts/stops Server instances), on same computer as SQL Server
instance, shows only instance "H" which is the same as the computer
name. (This instance was uninstalled before new instance was
installed.) Typing new instance name ("H\ABC" and variations) into
top combo box produces error messages such as "wrong format for name",
"Network path not found" "RPC service not running". What is the
correct computer/name format' Key problem is clearly that Service
Manager can't communicate with this local MSDE instance.
All Windows 2000 updates from MS web site have been installed.
Objective is to operate MS Access on computer X (also running Win 2000
Pro) with computer H as a peer that hosts MSDE.
Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system'Have you installed SP3a?
Steve
<noname@.noname.com> wrote in message
news:40d55341.11850570@.nntp.flfrd.phub.net.cable.rogers.com...
> MSDE 2000 Release A installed under Windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format' Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system'|||Hi Steve,
MSDE 2000A already contains SQL Server SP3a updates.
Mark
Ottawa, Canada
On Tue, 22 Jun 2004 15:25:07 -0400, "Steve Thompson"
<stevethompson@.nomail.please> wrote:
>Have you installed SP3a?
>Steve
communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?
Have set DISABLENETWORKPROTOCOLS=0 at install time.
Install log shows installation successful..
Control Panel> Admin Tools> Services section shows SQL server instance
running.
Disabling firewall has no effect.
SQL Server Manager (icon at bottom right in task tray - this
starts/stops Server instances), on same computer as SQL Server
instance, shows only instance "H" which is the same as the computer
name. (This instance was uninstalled before new instance was
installed.) Typing new instance name ("H\ABC" and variations) into
top combo box produces error messages such as "wrong format for name",
"Network path not found" "RPC service not running". What is the
correct computer/name format' Key problem is clearly that Service
Manager can't communicate with this local MSDE instance.
All Windows 2000 updates from MS web site have been installed.
Objective is to operate MS Access on computer X (also running Win 2000
Pro) with computer H as a peer that hosts MSDE.
Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system'Have you installed SP3a?
Steve
<noname@.noname.com> wrote in message
news:40d55341.11850570@.nntp.flfrd.phub.net.cable.rogers.com...
> MSDE 2000 Release A installed under Windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format' Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system'|||Hi Steve,
MSDE 2000A already contains SQL Server SP3a updates.
Mark
Ottawa, Canada
On Tue, 22 Jun 2004 15:25:07 -0400, "Steve Thompson"
<stevethompson@.nomail.please> wrote:
>Have you installed SP3a?
>Steve
MSDE 2000 Release A wont talk
MSDE 2000 Release A installed under windows 2000 pro will not
communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?
communicate with SQL Server Manager nor MS Access on peer computer.
Can someone help?
Have set DISABLENETWORKPROTOCOLS=0 at install time.
Install log shows installation successful..
Control Panel> Admin Tools> Services section shows SQL server instance
running.
Disabling firewall has no effect.
SQL Server Manager (icon at bottom right in task tray - this
starts/stops Server instances), on same computer as SQL Server
instance, shows only instance "H" which is the same as the computer
name. (This instance was uninstalled before new instance was
installed.) Typing new instance name ("H\ABC" and variations) into
top combo box produces error messages such as "wrong format for name",
"Network path not found" "RPC service not running". What is the
correct computer/name format?? Key problem is clearly that Service
Manager can't communicate with this local MSDE instance.
All Windows 2000 updates from MS web site have been installed.
Objective is to operate MS Access on computer X (also running Win 2000
Pro) with computer H as a peer that hosts MSDE.
Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
--
Mark Ferguson<noname@.noname.com> wrote in message
news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
> MSDE 2000 Release A installed under windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format?? Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
> --
> Mark Ferguson
I must admit that I don't know the difference between MSDE Release A and
MSDE SP3a. There is no clear information on the MS site (or at least I
couldn't find it), but the download sizes are different, so the obvious
conclusion is that they are different versions. If this assumption is
correct, then you might be seeing this issue:
http://support.microsoft.com/defaul...010&Product=sql
However, I could be wrong, so perhaps you can check some more things. Can
you actually connect to the instance on H using a local osql.exe command
also on H? If you're logged on to Windows as an administrator, then this
should be enough:
osql -S H\ABC -E
If that works, then presumably the problem is the Service Manager itself
(possibly as described in the article above). If you can connect, you can
then check the version with this query:
1> select @.@.version
2> go
If you don't see version 8.00.760, then you don't have SP3a, so I would
completely remove MSDE and then install MSDE SP3a. See "Remove all known
instances of SQL Server" in this article:
http://support.microsoft.com/defaul...991&Product=sql
If you cannot connect with osql.exe, then what error message do you get? In
the final analysis, however, I would suggest that Server Manager is a small,
unimportant component which probably is not worth worrying about. As long as
MSDE is running and you can connect from client applications with no
problems, then I would not spend too much time trying to make it work.
Regarding connecting from a different PC (with Access or any other tool),
there are a number of possible connection issues:
http://support.microsoft.com/defaul...306&Product=sql
I guess when you say "peer" you mean that the PCs are in a workgroup, not a
domain. If this is the case, then trusted connections can be awkward - the
article above has a link to another KB article which describes a possible
workaround. Mixed security using SQL logins should work fine, but is not
generally recommended unless there is no other alternative.
Simon|||Hi
You may get more help in the microsoft.public.sqlserver.msde newsgroup.
John
<noname@.noname.com> wrote in message
news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
> MSDE 2000 Release A installed under windows 2000 pro will not
> communicate with SQL Server Manager nor MS Access on peer computer.
> Can someone help?
> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> Install log shows installation successful..
> Control Panel> Admin Tools> Services section shows SQL server instance
> running.
> Disabling firewall has no effect.
> SQL Server Manager (icon at bottom right in task tray - this
> starts/stops Server instances), on same computer as SQL Server
> instance, shows only instance "H" which is the same as the computer
> name. (This instance was uninstalled before new instance was
> installed.) Typing new instance name ("H\ABC" and variations) into
> top combo box produces error messages such as "wrong format for name",
> "Network path not found" "RPC service not running". What is the
> correct computer/name format?? Key problem is clearly that Service
> Manager can't communicate with this local MSDE instance.
> All Windows 2000 updates from MS web site have been installed.
> Objective is to operate MS Access on computer X (also running Win 2000
> Pro) with computer H as a peer that hosts MSDE.
> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
> --
> Mark Ferguson|||"Simon Hayes" <sql@.hayes.ch> wrote in message
news:40d5ade5$1_2@.news.bluewin.ch...
|
| <noname@.noname.com> wrote in message
| news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
| > MSDE 2000 Release A installed under windows 2000 pro will not
| > communicate with SQL Server Manager nor MS Access on peer computer.
| > Can someone help?
| >
| > Have set DISABLENETWORKPROTOCOLS=0 at install time.
| >
| > Install log shows installation successful..
| >
| > Control Panel> Admin Tools> Services section shows SQL server instance
| > running.
| >
| > Disabling firewall has no effect.
| >
| > SQL Server Manager (icon at bottom right in task tray - this
| > starts/stops Server instances), on same computer as SQL Server
| > instance, shows only instance "H" which is the same as the computer
| > name. (This instance was uninstalled before new instance was
| > installed.) Typing new instance name ("H\ABC" and variations) into
| > top combo box produces error messages such as "wrong format for name",
| > "Network path not found" "RPC service not running". What is the
| > correct computer/name format?? Key problem is clearly that Service
| > Manager can't communicate with this local MSDE instance.
| >
| > All Windows 2000 updates from MS web site have been installed.
| >
| > Objective is to operate MS Access on computer X (also running Win 2000
| > Pro) with computer H as a peer that hosts MSDE.
| >
| > Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
| > --
| > Mark Ferguson
|
| I must admit that I don't know the difference between MSDE Release A and
| MSDE SP3a. There is no clear information on the MS site (or at least I
| couldn't find it), but the download sizes are different, so the obvious
| conclusion is that they are different versions. If this assumption is
| correct, then you might be seeing this issue:
|
| http://support.microsoft.com/defaul...010&Product=sql
|
| However, I could be wrong, so perhaps you can check some more things. Can
| you actually connect to the instance on H using a local osql.exe command
| also on H? If you're logged on to Windows as an administrator, then this
| should be enough:
|
| osql -S H\ABC -E
|
| If that works, then presumably the problem is the Service Manager itself
| (possibly as described in the article above). If you can connect, you can
| then check the version with this query:
|
| 1> select @.@.version
| 2> go
|
| If you don't see version 8.00.760, then you don't have SP3a, so I would
| completely remove MSDE and then install MSDE SP3a. See "Remove all known
| instances of SQL Server" in this article:
|
| http://support.microsoft.com/defaul...991&Product=sql
|
| If you cannot connect with osql.exe, then what error message do you get? In
| the final analysis, however, I would suggest that Server Manager is a small,
| unimportant component which probably is not worth worrying about. As long as
| MSDE is running and you can connect from client applications with no
| problems, then I would not spend too much time trying to make it work.
|
| Regarding connecting from a different PC (with Access or any other tool),
| there are a number of possible connection issues:
|
| http://support.microsoft.com/defaul...306&Product=sql
|
| I guess when you say "peer" you mean that the PCs are in a workgroup, not a
| domain. If this is the case, then trusted connections can be awkward - the
| article above has a link to another KB article which describes a possible
| workaround. Mixed security using SQL logins should work fine, but is not
| generally recommended unless there is no other alternative.
|
| Simon
|
|
MSDE 2000 Release A is a developer version (SDK) of Microsoft SQL Server 2000
Desktop Engine SP3a. SELECT @.@.VERSION returns the same version info for both.
This brief description of Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
Release A is quoted from the download page -
<
MSDE 2000 Release A is functionally equivalent to SQL Server 2000 Desktop
Engine SP3a except for the following:
New licensing agreement
Removal of the merge modules that can be used to embed MSDE 2000 Release A
with applications
New ReadMeMSDE2000A.htm that contains information specific to this release.
This new version of MSDE contains all the fixes that are included with SQL
Server 2000 SP3a version of MSDE.
http://www.microsoft.com/downloads/...&DisplayLang=en
Additional information can be found in the Microsoft SQL Server 2000 Desktop
Engine
(MSDE 2000) Release A ReadMe
http://download.microsoft.com/downl...meMSDE2000A.htm
Additions to the SQL Server 2000 Desktop Engine (MSDE) Release A
ReadmeMSDE2000A.htm File
http://support.microsoft.com/?kbid=829925
Dan|||<noname@.noname.com> wrote in message
news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
| MSDE 2000 Release A installed under windows 2000 pro will not
| communicate with SQL Server Manager nor MS Access on peer computer.
| Can someone help?
|
| Have set DISABLENETWORKPROTOCOLS=0 at install time.
|
| Install log shows installation successful..
|
| Control Panel> Admin Tools> Services section shows SQL server instance
| running.
|
| Disabling firewall has no effect.
|
| SQL Server Manager (icon at bottom right in task tray - this
| starts/stops Server instances), on same computer as SQL Server
| instance, shows only instance "H" which is the same as the computer
| name. (This instance was uninstalled before new instance was
| installed.) Typing new instance name ("H\ABC" and variations) into
| top combo box produces error messages such as "wrong format for name",
| "Network path not found" "RPC service not running". What is the
| correct computer/name format?? Key problem is clearly that Service
| Manager can't communicate with this local MSDE instance.
|
| All Windows 2000 updates from MS web site have been installed.
|
| Objective is to operate MS Access on computer X (also running Win 2000
| Pro) with computer H as a peer that hosts MSDE.
|
| Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
| --
| Mark Ferguson
Hi Mark,
There is known bug when reinstalling with same instance name.
Follow the instructions for editing the registry keys given in
the article at:
http://support.microsoft.com/defaul...kb;en-us;823467
If that fails then you will have to uninstall MSDE 2000 Release A
and follow the instructions for editing the registry keys given in
the article at:
http://support.microsoft.com/defaul...kb;en-us;320873
Then reinstall MSDE 2000 Release A
Hope this helps.
Dan|||Thanks John, but I dont see a newsgroup named
microsoft.public.sqlserver.msde. I just checked for new groups and
that one doesn't show up there either. Not sure where i might find
this group.
On Sun, 20 Jun 2004 16:07:34 GMT, "John Bell"
<jbellnewsposts@.hotmail.com> wrote:
>Hi
>You may get more help in the microsoft.public.sqlserver.msde newsgroup.
>John
><noname@.noname.com> wrote in message
>news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
>> MSDE 2000 Release A installed under windows 2000 pro will not
>> communicate with SQL Server Manager nor MS Access on peer computer.
>> Can someone help?
>>
>> Have set DISABLENETWORKPROTOCOLS=0 at install time.
>>
>> Install log shows installation successful..
>>
>> Control Panel> Admin Tools> Services section shows SQL server instance
>> running.
>>
>> Disabling firewall has no effect.
>>
>> SQL Server Manager (icon at bottom right in task tray - this
>> starts/stops Server instances), on same computer as SQL Server
>> instance, shows only instance "H" which is the same as the computer
>> name. (This instance was uninstalled before new instance was
>> installed.) Typing new instance name ("H\ABC" and variations) into
>> top combo box produces error messages such as "wrong format for name",
>> "Network path not found" "RPC service not running". What is the
>> correct computer/name format?? Key problem is clearly that Service
>> Manager can't communicate with this local MSDE instance.
>>
>> All Windows 2000 updates from MS web site have been installed.
>>
>> Objective is to operate MS Access on computer X (also running Win 2000
>> Pro) with computer H as a peer that hosts MSDE.
>>
>> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
>> --
>> Mark Ferguson|||Hi
Try the news.microsoft.com news server or
http://groups.google.com/groups?hl=...sqlserver.msde
John
<Mark_Ferguson@.noname.com> wrote in message
news:40d736bf.12602391@.nntp.flfrd.phub.net.cable.r ogers.com...
> Thanks John, but I dont see a newsgroup named
> microsoft.public.sqlserver.msde. I just checked for new groups and
> that one doesn't show up there either. Not sure where i might find
> this group.
> On Sun, 20 Jun 2004 16:07:34 GMT, "John Bell"
> <jbellnewsposts@.hotmail.com> wrote:
> >Hi
> >You may get more help in the microsoft.public.sqlserver.msde newsgroup.
> >John
> ><noname@.noname.com> wrote in message
> >news:40d53097.2976249@.nntp.flfrd.phub.net.cable.ro gers.com...
> >> MSDE 2000 Release A installed under windows 2000 pro will not
> >> communicate with SQL Server Manager nor MS Access on peer computer.
> >> Can someone help?
> >>
> >> Have set DISABLENETWORKPROTOCOLS=0 at install time.
> >>
> >> Install log shows installation successful..
> >>
> >> Control Panel> Admin Tools> Services section shows SQL server instance
> >> running.
> >>
> >> Disabling firewall has no effect.
> >>
> >> SQL Server Manager (icon at bottom right in task tray - this
> >> starts/stops Server instances), on same computer as SQL Server
> >> instance, shows only instance "H" which is the same as the computer
> >> name. (This instance was uninstalled before new instance was
> >> installed.) Typing new instance name ("H\ABC" and variations) into
> >> top combo box produces error messages such as "wrong format for name",
> >> "Network path not found" "RPC service not running". What is the
> >> correct computer/name format?? Key problem is clearly that Service
> >> Manager can't communicate with this local MSDE instance.
> >>
> >> All Windows 2000 updates from MS web site have been installed.
> >>
> >> Objective is to operate MS Access on computer X (also running Win 2000
> >> Pro) with computer H as a peer that hosts MSDE.
> >>
> >> Has anyone else run MSDE 2000 Release A on a Windows 2000 Pro system??
> >> --
> >> Mark Ferguson|||>I must admit that I don't know the difference between MSDE Release A and
>MSDE SP3a. There is no clear information on the MS site (or at least I
>couldn't find it), but the download sizes are different, so the obvious
>conclusion is that they are different versions. If this assumption is
>correct, then you might be seeing this issue:
>http://support.microsoft.com/defaul...010&Product=sql
This article applies to MSDE Service pack . I have installed MSDE
2000A which includes Service Pack 3. The symptoms don't and conditions
don't apply, nor do the workaround instructions make sense.
>However, I could be wrong, so perhaps you can check some more things. Can
>you actually connect to the instance on H using a local osql.exe command
>also on H? If you're logged on to Windows as an administrator, then this
>should be enough:
>osql -S H\ABC -E
This works. But the SQL Server *is* running - we knew that.
>If that works, then presumably the problem is the Service Manager itself
>(possibly as described in the article above). If you can connect, you can
>then check the version with this query:
>1> select @.@.version
>2> go
Result is:
Microsoft SQL Server 2000 - 8.00.760 (Intel X86)
Dec 17 2002 14:22:05
Copy
right (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT
5.0 (Build 2195: Service Pack 4)
>If you don't see version 8.00.760, then you don't have SP3a, so I would
>completely remove MSDE and then install MSDE SP3a. See "Remove all known
>instances of SQL Server" in this article:
>http://support.microsoft.com/defaul...991&Product=sql
Thank you... This may be very useful indeed.
>If you cannot connect with osql.exe, then what error message do you get? In
>the final analysis, however, I would suggest that Server Manager is a small,
>unimportant component which probably is not worth worrying about. As long as
>MSDE is running and you can connect from client applications with no
>problems, then I would not spend too much time trying to make it work.
>Regarding connecting from a different PC (with Access or any other tool),
>there are a number of possible connection issues:
>http://support.microsoft.com/defaul...306&Product=sql
>I guess when you say "peer" you mean that the PCs are in a workgroup, not a
>domain. If this is the case, then trusted connections can be awkward - the
>article above has a link to another KB article which describes a possible
>workaround. Mixed security using SQL logins should work fine, but is not
>generally recommended unless there is no other alternative.
You are correct, the two computers are not in a domain and so there is
no user authentication provided by a domain server. Thanks for the
link I will look it up.
The Server Manager is only important in that its a good first
indication that everything is working at the local computer - an
encouraging first sign, insofar as the client computer cannot connect
to the server.
>Simon
>
I am also working on the problem of fixing ports used by the SQL
Server. The instance now installed is named and so uses dynamic ports
rather than the fixed 1433 and 1434 ports. The question is: what does
the SQL Server Manager use?|||I think you are correct. I need to uninstall MSDE2000A and then fix up
the registry or re-install windows 2000. I have already uninstalled
the old default version that came with MS office. I have also
installed the MSDE2000A version several times.
I have never checked the MDAC version (don't know how), but that may
also be a problem.
I need to try these and then request more help.
Many thanks.
Mark.
On Mon, 21 Jun 2004 05:22:56 -0400, "Daniel A. Thomas"
<dathomas@.--spam--istar.ca> wrote:
>Hi Mark,
>There is known bug when reinstalling with same instance name.
>Follow the instructions for editing the registry keys given in
>the article at:
>http://support.microsoft.com/defaul...kb;en-us;823467
>If that fails then you will have to uninstall MSDE 2000 Release A
>and follow the instructions for editing the registry keys given in
>the article at:
>http://support.microsoft.com/defaul...kb;en-us;320873
>Then reinstall MSDE 2000 Release A
>Hope this helps.
>Dan|||OK, John. The google web page is the same as the MS Discussion forum
for SQL Server. I posted a similar article there, but no help came
there.
Mark.
On Mon, 21 Jun 2004 19:56:20 GMT, "John Bell"
<jbellnewsposts@.hotmail.com> wrote:
>Hi
>Try the news.microsoft.com news server or
>http://groups.google.com/groups?hl=...sqlserver.msde
>John|||I'm grateful for the help from you all, but the one real symptom of
the problem with the Service Manager is its error message:
"The format of the computer name is inavlid."
This is the response to asking it to find the instance ABC on the
computer named "H" - (H\ABC). Recall that running osql.exe against the
name H\ABC works fine.
Mark.
MSDE 2000 Release A Supported systems
The addendum to the Readme file for MSDE 2000 Release A states "MSDE 2000 Release A is supported on Microsoft Windows Server 2003, Web Edition".
Does this mean that it executes only under Windows 2000 Server 2003 ?
I am running Windows 2000 Pro, it doesnt work. Does anyone run MSDE 2000 Rel A under other windows versions?
Mark Ferguson
hi Mark,
"Mark Ferguson" <MarkFerguson@.discussions.microsoft.com> ha scritto nel
messaggio news:F7D2BF11-BE8F-4AD7-B1AE-FAA334E68CE7@.microsoft.com...
> The addendum to the Readme file for MSDE 2000 Release A states "MSDE 2000
Release A is supported on Microsoft Windows Server 2003, Web Edition".
> Does this mean that it executes only under Windows 2000 Server 2003 ?
> I am running Windows 2000 Pro, it doesnt work. Does anyone run MSDE 2000
Rel
>A under other windows versions?
I think that extract shoul'd be intended as "Microsoft Windows Server 2003,
Web Edition can only run MSDE and not a full blown SQL Server edition"...
MSDE can be installed up to Win98 boxes, more system requirements at
http://www.microsoft.com/sql/msde/pr...fo/sysreqs.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Does this mean that it executes only under Windows 2000 Server 2003 ?
I am running Windows 2000 Pro, it doesnt work. Does anyone run MSDE 2000 Rel A under other windows versions?
Mark Ferguson
hi Mark,
"Mark Ferguson" <MarkFerguson@.discussions.microsoft.com> ha scritto nel
messaggio news:F7D2BF11-BE8F-4AD7-B1AE-FAA334E68CE7@.microsoft.com...
> The addendum to the Readme file for MSDE 2000 Release A states "MSDE 2000
Release A is supported on Microsoft Windows Server 2003, Web Edition".
> Does this mean that it executes only under Windows 2000 Server 2003 ?
> I am running Windows 2000 Pro, it doesnt work. Does anyone run MSDE 2000
Rel
>A under other windows versions?
I think that extract shoul'd be intended as "Microsoft Windows Server 2003,
Web Edition can only run MSDE and not a full blown SQL Server edition"...
MSDE can be installed up to Win98 boxes, more system requirements at
http://www.microsoft.com/sql/msde/pr...fo/sysreqs.asp
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
MSDE 2000 Release A and Windows Installer
I am currently writing an installer for our product, which needs to incorporate MSDE 2000.
Previous versions of the MSDE install included merge modules (.msm files) that could be incorporated straight into a Windows Installer .msi file. However, the latest version (Release A) does not include the merge modules, and to top that, also states tha
t "Desktop Engine does not support nested installations. You must not call an .msi file from within another .msi file".
My questions are:
- How are we supposed to install MSDE when we are distributing .msi files? We need .msi functionality for other components of our install, so using a non-Windows Installer technology is not an option. Do we need to ask our users to install MSDE separat
ely (ouch)?
- Why did the merge modules disappear? I thought that these were the Microsoft-sanctioned method for installing runtime components...
- Are there any other options - we want to distribute a single file, and we really don't want to have to mix and match .msi and other setup technologies...
Marc Durdin
Software for Specialists
Hi Andy,
Thanks for the comment. However, this page is not up to date. It recommends using the merge modules... which are not supported any more by Microsoft (and are not even included in the latest release of MSDE). Any other suggestions?
Regards,
Marc
Previous versions of the MSDE install included merge modules (.msm files) that could be incorporated straight into a Windows Installer .msi file. However, the latest version (Release A) does not include the merge modules, and to top that, also states tha
t "Desktop Engine does not support nested installations. You must not call an .msi file from within another .msi file".
My questions are:
- How are we supposed to install MSDE when we are distributing .msi files? We need .msi functionality for other components of our install, so using a non-Windows Installer technology is not an option. Do we need to ask our users to install MSDE separat
ely (ouch)?
- Why did the merge modules disappear? I thought that these were the Microsoft-sanctioned method for installing runtime components...
- Are there any other options - we want to distribute a single file, and we really don't want to have to mix and match .msi and other setup technologies...
Marc Durdin
Software for Specialists
Hi Andy,
Thanks for the comment. However, this page is not up to date. It recommends using the merge modules... which are not supported any more by Microsoft (and are not even included in the latest release of MSDE). Any other suggestions?
Regards,
Marc
MSDE 2000 Release A - Instalation Problem in Windows XP SP2
I can't install MSDE release A in Windows XP SP2. I verified if Server
Service is started and it is ok. I also verified if File and Printer sharing
is checked on network properties and it is ok. The windows firewall also is
disabled but the instalation doesn't work. I run the follow comand setup.exe
sapwd="suportebsb." /L*v C:/MSDELog.log.
Anyone can help me?
Regards,
Cicero Galdino
******** This is the lastest lines in log instalation files
*******************
2005-06-01 16:49:35.64 spid4 Default collation successfully changed.
2005-06-01 16:49:35.67 spid4 Recovery complete.
2005-06-01 16:49:35.67 spid4 SQL global counter collection task is
created.
2005-06-01 16:49:35.69 spid4 Warning: override, autoexec procedures
skipped.
2005-06-01 16:49:43.36 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
=== Logging stopped: 01/06/2005 16:59:54 ===
MSI (c) (18:48) [16:59:54:724]: Note: 1: 1708
MSI (c) (18:48) [16:59:54:724]: Product: Microsoft SQL Server Desktop Engine
-- Installation operation failed.
MSI (c) (18:48) [16:59:54:724]: Grabbed execution mutex.
MSI (c) (18:48) [16:59:54:724]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (18:48) [16:59:54:740]: MainEngineThread is returning 1603
=== Verbose logging stopped: 01/06/2005 16:59:54 ===
hi Cicero,
Cicero wrote:
> I can't install MSDE release A in Windows XP SP2. I verified if Server
> Service is started and it is ok. I also verified if File and Printer
> sharing is checked on network properties and it is ok. The windows
> firewall also is disabled but the instalation doesn't work. I run the
> follow comand setup.exe sapwd="suportebsb." /L*v C:/MSDELog.log.
please inspect your C:/MSDELog.log for
RETURN VALUE 3
entrie(s), that reports exeptions duting the install process...
about 10/15 lines before each entry some (sometime cryptic) descritpion of
the problem will be available
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Service is started and it is ok. I also verified if File and Printer sharing
is checked on network properties and it is ok. The windows firewall also is
disabled but the instalation doesn't work. I run the follow comand setup.exe
sapwd="suportebsb." /L*v C:/MSDELog.log.
Anyone can help me?
Regards,
Cicero Galdino
******** This is the lastest lines in log instalation files
*******************
2005-06-01 16:49:35.64 spid4 Default collation successfully changed.
2005-06-01 16:49:35.67 spid4 Recovery complete.
2005-06-01 16:49:35.67 spid4 SQL global counter collection task is
created.
2005-06-01 16:49:35.69 spid4 Warning: override, autoexec procedures
skipped.
2005-06-01 16:49:43.36 spid4 SQL Server is terminating due to 'stop'
request from Service Control Manager.
=== Logging stopped: 01/06/2005 16:59:54 ===
MSI (c) (18:48) [16:59:54:724]: Note: 1: 1708
MSI (c) (18:48) [16:59:54:724]: Product: Microsoft SQL Server Desktop Engine
-- Installation operation failed.
MSI (c) (18:48) [16:59:54:724]: Grabbed execution mutex.
MSI (c) (18:48) [16:59:54:724]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (18:48) [16:59:54:740]: MainEngineThread is returning 1603
=== Verbose logging stopped: 01/06/2005 16:59:54 ===
hi Cicero,
Cicero wrote:
> I can't install MSDE release A in Windows XP SP2. I verified if Server
> Service is started and it is ok. I also verified if File and Printer
> sharing is checked on network properties and it is ok. The windows
> firewall also is disabled but the instalation doesn't work. I run the
> follow comand setup.exe sapwd="suportebsb." /L*v C:/MSDELog.log.
please inspect your C:/MSDELog.log for
RETURN VALUE 3
entrie(s), that reports exeptions duting the install process...
about 10/15 lines before each entry some (sometime cryptic) descritpion of
the problem will be available
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
msde 2000 on windows 2003 server
I "Managed" to install msde on windows 2003 server but the sql service manager does list an thing to connect to.
what am i doing wrong does mdse work on windows 2003 server and how do i fix it ?
Hi,
I have found the following KB article that describes a similar scenario.
http://support.microsoft.com/default...&Product=sql2k
#appliesto
================================================== ==========================
================================================== =========
BUG: The SQL Server 2000 Service Manager Utility Does Not List Instances
That Have Not Enabled Network Connections
View products that this article applies to.
BUG #: 363267 (SHILOH_BUGS)
SYMPTOMS
If you configure an instance of SQL Server 2000 or SQL Server 2000 Desktop
Engine (also known as MSDE 2000) to disallow network connections, that
instance will not appear in the SQL Server 2000 Service Manager utility.
CAUSE
The SQL Server ODBC driver does not return instance names to the SQL
Service Manager if the instance does not support network connections.
WORKAROUND
To work around this behavior, stop and then start the service for the
instance by following these steps:
Right-click My Computer, and then click Manage.
Double-click Services and Applications in the left-hand screen.
Double-click Services.
Right-click the service for the instance of SQL Server. The name of the
service for a default instance of SQL Server 2000 is MSSQLServer. The name
of the service for a named instance of SQL Server 2000 is
MSSQL$instancename.
Click the action that you want applied to the instance, such as stop or
start.
================================================== ==========================
================================================== =========
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
what am i doing wrong does mdse work on windows 2003 server and how do i fix it ?
Hi,
I have found the following KB article that describes a similar scenario.
http://support.microsoft.com/default...&Product=sql2k
#appliesto
================================================== ==========================
================================================== =========
BUG: The SQL Server 2000 Service Manager Utility Does Not List Instances
That Have Not Enabled Network Connections
View products that this article applies to.
BUG #: 363267 (SHILOH_BUGS)
SYMPTOMS
If you configure an instance of SQL Server 2000 or SQL Server 2000 Desktop
Engine (also known as MSDE 2000) to disallow network connections, that
instance will not appear in the SQL Server 2000 Service Manager utility.
CAUSE
The SQL Server ODBC driver does not return instance names to the SQL
Service Manager if the instance does not support network connections.
WORKAROUND
To work around this behavior, stop and then start the service for the
instance by following these steps:
Right-click My Computer, and then click Manage.
Double-click Services and Applications in the left-hand screen.
Double-click Services.
Right-click the service for the instance of SQL Server. The name of the
service for a default instance of SQL Server 2000 is MSSQLServer. The name
of the service for a named instance of SQL Server 2000 is
MSSQL$instancename.
Click the action that you want applied to the instance, such as stop or
start.
================================================== ==========================
================================================== =========
HTH
Ashish
This posting is provided "AS IS" with no warranties, and confers no rights.
MSDE 2000 on Windows 2003
Hi there,
I want to know can i install on my server msde 2000
without installed sql server 2000? I mean what on my
server MSSQL server 2000 not installed and i want to
install only msde 2000.
thank you
hi,
anuk wrote:
> Hi there,
> I want to know can i install on my server msde 2000
> without installed sql server 2000? I mean what on my
> server MSSQL server 2000 not installed and i want to
> install only msde 2000.
> thank you
you can install MSDE release A, updated at service pack 3a, on Win2003
server, without installing SQL Server
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
I want to know can i install on my server msde 2000
without installed sql server 2000? I mean what on my
server MSSQL server 2000 not installed and i want to
install only msde 2000.
thank you
hi,
anuk wrote:
> Hi there,
> I want to know can i install on my server msde 2000
> without installed sql server 2000? I mean what on my
> server MSSQL server 2000 not installed and i want to
> install only msde 2000.
> thank you
you can install MSDE release A, updated at service pack 3a, on Win2003
server, without installing SQL Server
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
MSDE 2000 on a Windows 2000 machine
After I install MSDE on a windows 2000 machine I enable the network
protocols stop and start the server and everything works fine. When I
try to disable the network protocols I stop and start the server and it
doesn't work. I have to run SVRNETCN to see that the TCP/IP and Named
Pipes are disabled. I click ok and it tells me that the server has to
stopped and started for the changes to take effect. I stop and start
the server and the changes are in effect. Any way that I can set the
changes without having to run SVRNETCN
Thanks
hi,
johndoe17@.verizon.net wrote:
> After I install MSDE on a windows 2000 machine I enable the network
> protocols stop and start the server and everything works fine. When I
> try to disable the network protocols I stop and start the server and
> it doesn't work. I have to run SVRNETCN to see that the TCP/IP and
> Named Pipes are disabled. I click ok and it tells me that the server
> has to stopped and started for the changes to take effect. I stop
> and start the server and the changes are in effect. Any way that I
> can set the changes without having to run SVRNETCN
AFAIK the Server Network Utility writes all the necessary registry entries
to perform the network protocols changes.. you should be able to do the same
"simply" assigning the
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Su perSocketNetLib
ProtocolList = ....
registry value, but this does not seems to work, so I do think svrnetcn.exe
performs further writes...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Is there a command line option I can use to run svrnetcn without the
user interface, so that I can tell it which server to set the protocols
for?
|||hi,
johndoe17@.verizon.net wrote:
> Is there a command line option I can use to run svrnetcn without the
> user interface, so that I can tell it which server to set the
> protocols for?
perhaps via WMI, but never tried it out...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks for all your help. I was able to change the value in the
registry key
"HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\S uperSocketNetLib
ProtocolList = " to 0 and everything seems to be disabled.
Thanks again.
sql
protocols stop and start the server and everything works fine. When I
try to disable the network protocols I stop and start the server and it
doesn't work. I have to run SVRNETCN to see that the TCP/IP and Named
Pipes are disabled. I click ok and it tells me that the server has to
stopped and started for the changes to take effect. I stop and start
the server and the changes are in effect. Any way that I can set the
changes without having to run SVRNETCN
Thanks
hi,
johndoe17@.verizon.net wrote:
> After I install MSDE on a windows 2000 machine I enable the network
> protocols stop and start the server and everything works fine. When I
> try to disable the network protocols I stop and start the server and
> it doesn't work. I have to run SVRNETCN to see that the TCP/IP and
> Named Pipes are disabled. I click ok and it tells me that the server
> has to stopped and started for the changes to take effect. I stop
> and start the server and the changes are in effect. Any way that I
> can set the changes without having to run SVRNETCN
AFAIK the Server Network Utility writes all the necessary registry entries
to perform the network protocols changes.. you should be able to do the same
"simply" assigning the
HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\Su perSocketNetLib
ProtocolList = ....
registry value, but this does not seems to work, so I do think svrnetcn.exe
performs further writes...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Is there a command line option I can use to run svrnetcn without the
user interface, so that I can tell it which server to set the protocols
for?
|||hi,
johndoe17@.verizon.net wrote:
> Is there a command line option I can use to run svrnetcn without the
> user interface, so that I can tell it which server to set the
> protocols for?
perhaps via WMI, but never tried it out...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks for all your help. I was able to change the value in the
registry key
"HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\S uperSocketNetLib
ProtocolList = " to 0 and everything seems to be disabled.
Thanks again.
sql
Friday, March 23, 2012
MSDE 2000 installation on Windows 98 SE
Hi,
I have Installed MSDE 2000 on Windows 98 SE box After REBOOT MSDE
service is running.
I am not able to connect to the MSDE in WIndows Authentication mode
while using Login ( sa ) / password the connectivity is done.
My GUI uses the MSDE connection in "Windows Authentication Mode" which
is working fine with the 2K/XP but not with 98SE/ME.
The MSDE Readme.txt says that on 98 / ME the default Connectivity mode
is "Windows Authentication" BUT its not working in that way.
I have tried SECURITYMODE=SQL as command line to setup.exe as well but
results are same.
Any clue to run it in WMA Mode on Win98SE/ME ?
thanks
kapil
Hi Kaps,
Win98 doesn't provide the infrastructure that MSDE needs to use Windows
Authentication. You will need to use SQL Server authentication and specify
an password for sa (SAPWD) while installing it.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"kaps" <kapilkj@.gmail.com> wrote in message
news:1103617693.026085.125330@.f14g2000cwb.googlegr oups.com...
> Hi,
> I have Installed MSDE 2000 on Windows 98 SE box After REBOOT MSDE
> service is running.
> I am not able to connect to the MSDE in WIndows Authentication mode
> while using Login ( sa ) / password the connectivity is done.
> My GUI uses the MSDE connection in "Windows Authentication Mode" which
> is working fine with the 2K/XP but not with 98SE/ME.
> The MSDE Readme.txt says that on 98 / ME the default Connectivity mode
> is "Windows Authentication" BUT its not working in that way.
> I have tried SECURITYMODE=SQL as command line to setup.exe as well but
> results are same.
> Any clue to run it in WMA Mode on Win98SE/ME ?
>
> thanks
> kapil
>
I have Installed MSDE 2000 on Windows 98 SE box After REBOOT MSDE
service is running.
I am not able to connect to the MSDE in WIndows Authentication mode
while using Login ( sa ) / password the connectivity is done.
My GUI uses the MSDE connection in "Windows Authentication Mode" which
is working fine with the 2K/XP but not with 98SE/ME.
The MSDE Readme.txt says that on 98 / ME the default Connectivity mode
is "Windows Authentication" BUT its not working in that way.
I have tried SECURITYMODE=SQL as command line to setup.exe as well but
results are same.
Any clue to run it in WMA Mode on Win98SE/ME ?
thanks
kapil
Hi Kaps,
Win98 doesn't provide the infrastructure that MSDE needs to use Windows
Authentication. You will need to use SQL Server authentication and specify
an password for sa (SAPWD) while installing it.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"kaps" <kapilkj@.gmail.com> wrote in message
news:1103617693.026085.125330@.f14g2000cwb.googlegr oups.com...
> Hi,
> I have Installed MSDE 2000 on Windows 98 SE box After REBOOT MSDE
> service is running.
> I am not able to connect to the MSDE in WIndows Authentication mode
> while using Login ( sa ) / password the connectivity is done.
> My GUI uses the MSDE connection in "Windows Authentication Mode" which
> is working fine with the 2K/XP but not with 98SE/ME.
> The MSDE Readme.txt says that on 98 / ME the default Connectivity mode
> is "Windows Authentication" BUT its not working in that way.
> I have tried SECURITYMODE=SQL as command line to setup.exe as well but
> results are same.
> Any clue to run it in WMA Mode on Win98SE/ME ?
>
> thanks
> kapil
>
MSDE 2000 installation fails on Windows Vista 64-bit
Installation of MSDE 2000 fails on 64-bit Windows Vista (Build 5308).
The error message is "Setup failed to configure the server.Please refer the error logs for more information". No error log can be found on the machine at the time of installation. Please let me know if anyone else has encountered this problem?
Is it possible to install MSDE 2000 on 64-bit Windows Vista(Build 5308)?
Thanks in advance.
I don't believe any version of SQL Server or MSDE prior to SQL Server 2005 is supported on Vista. Someone else on the team who works on SQL Server 2000 should reply with a definitive answer...
Paul
|||Vista is still under development, so the right place to post your questions is Vista Newsgroups under "Application Compatibility" issues. I think the OS group has a AppCompat team that should be able to help you.|||"Earlier versions of SQL Server, including SQL Server 2000 (all editions including Desktop Engine edition, a.k.a MSDE), SQL Server 7.0, and SQL Server 6.5, will not be supported on Windows Server "Longhorn" or Windows Vista."
from http://www.microsoft.com/sql/howtobuy/sqlonvista.mspx
sqlMSDE 2000 installation fails on Windows Vista 64-bit
Installation of MSDE 2000 fails on 64-bit Windows Vista (Build 5308).
The error message is "Setup failed to configure the server.Please refer the error logs for more information". No error log can be found on the machine at the time of installation. Please let me know if anyone else has encountered this problem?
Is it possible to install MSDE 2000 on 64-bit Windows Vista(Build 5308)?
Thanks in advance.
I don't believe any version of SQL Server or MSDE prior to SQL Server 2005 is supported on Vista. Someone else on the team who works on SQL Server 2000 should reply with a definitive answer...
Paul
|||Vista is still under development, so the right place to post your questions is Vista Newsgroups under "Application Compatibility" issues. I think the OS group has a AppCompat team that should be able to help you.|||"Earlier versions of SQL Server, including SQL Server 2000 (all editions including Desktop Engine edition, a.k.a MSDE), SQL Server 7.0, and SQL Server 6.5, will not be supported on Windows Server "Longhorn" or Windows Vista."
from http://www.microsoft.com/sql/howtobuy/sqlonvista.mspx
MSDE 2000 Install Problem
Hi
I am trying to install MSDE 2000 sp3 on a Windows XP that has had a previous
installation in the past. The previous installation has been removed, but
when I try installing MSDE again from the command prompt, it starts to set
up the gives me an error saying installation failed.
I have deleted the Microsoft SQL Server directory from Program Files,
cleaned out all registry entries for the instance name and have run the
install using the following command:
Setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1
SAPWD=<password>
Obviously replacing <password> with an appropriate password.
Are there any other known issues that anyone knows that will get this
installation working? Any advice would be appreciated.
Regards
Jason
hi Jason,
please add the
/L*v 'c:\...\log.txt'
parameter, in order to get a 2mb log file for the installation, where you
can search for
"value 3"
as error indication
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
I am trying to install MSDE 2000 sp3 on a Windows XP that has had a previous
installation in the past. The previous installation has been removed, but
when I try installing MSDE again from the command prompt, it starts to set
up the gives me an error saying installation failed.
I have deleted the Microsoft SQL Server directory from Program Files,
cleaned out all registry entries for the instance name and have run the
install using the following command:
Setup.exe /qb+ INSTANCENAME=VSDOTNET DISABLENETWORKPROTOCOLS=1
SAPWD=<password>
Obviously replacing <password> with an appropriate password.
Are there any other known issues that anyone knows that will get this
installation working? Any advice would be appreciated.
Regards
Jason
hi Jason,
please add the
/L*v 'c:\...\log.txt'
parameter, in order to get a 2mb log file for the installation, where you
can search for
"value 3"
as error indication
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
MSDE 2000 Install - setup.ini
I have installed MSDE 2000 on my Windows 2000 laptop using the SP3 setup.exe and associated setup.ini file.
So far I have included the following parameters in the setup.ini file -
SAPWD=<my own SA password>
SECURITYMODE=SQL
COLLATION=SQL_Latin1_General_CP1_CI_AS
My next test is to connect to a database on the laptop from my desktop (via my LAN) using SQL Server 2000 Enterprise Manager and/or Query Analyser.
The problem is that although I can 'see' my laptop (ping/My Network Places etc.), I can not see the MSDE installation hense my database on the laptop. The message I get is '[Microsoft]ODBC SQL server driver [DBNETLIB] SQL Server does not exist or access denied'
Have I missed a parameter i.e. do I need to set up a parameter to ensure I can connect to the installation from remote?
Being new to installing MSDE, are there any other parameters I have missed?
Ian
p.s. Anyone know of a simple to follow install instruction set for MSDE 2000 which shows what parameters can be set upSolved the problem myself.
With Service Pack 3, msde has added a new parameter to the install = DISABLENETWORKPROTOCOLS. This parameter is defaulted to 1 which blocks remote access to the database. By adding the parameter with a value of 0 to the setup.ini file I can now connect from remote.
Ian
Originally posted by Ian Grant
I have installed MSDE 2000 on my Windows 2000 laptop using the SP3 setup.exe and associated setup.ini file.
So far I have included the following parameters in the setup.ini file -
SAPWD=<my own SA password>
SECURITYMODE=SQL
COLLATION=SQL_Latin1_General_CP1_CI_AS
My next test is to connect to a database on the laptop from my desktop (via my LAN) using SQL Server 2000 Enterprise Manager and/or Query Analyser.
The problem is that although I can 'see' my laptop (ping/My Network Places etc.), I can not see the MSDE installation hense my database on the laptop. The message I get is '[Microsoft]ODBC SQL server driver [DBNETLIB] SQL Server does not exist or access denied'
Have I missed a parameter i.e. do I need to set up a parameter to ensure I can connect to the installation from remote?
Being new to installing MSDE, are there any other parameters I have missed?
Ian
p.s. Anyone know of a simple to follow install instruction set for MSDE 2000 which shows what parameters can be set up
So far I have included the following parameters in the setup.ini file -
SAPWD=<my own SA password>
SECURITYMODE=SQL
COLLATION=SQL_Latin1_General_CP1_CI_AS
My next test is to connect to a database on the laptop from my desktop (via my LAN) using SQL Server 2000 Enterprise Manager and/or Query Analyser.
The problem is that although I can 'see' my laptop (ping/My Network Places etc.), I can not see the MSDE installation hense my database on the laptop. The message I get is '[Microsoft]ODBC SQL server driver [DBNETLIB] SQL Server does not exist or access denied'
Have I missed a parameter i.e. do I need to set up a parameter to ensure I can connect to the installation from remote?
Being new to installing MSDE, are there any other parameters I have missed?
Ian
p.s. Anyone know of a simple to follow install instruction set for MSDE 2000 which shows what parameters can be set upSolved the problem myself.
With Service Pack 3, msde has added a new parameter to the install = DISABLENETWORKPROTOCOLS. This parameter is defaulted to 1 which blocks remote access to the database. By adding the parameter with a value of 0 to the setup.ini file I can now connect from remote.
Ian
Originally posted by Ian Grant
I have installed MSDE 2000 on my Windows 2000 laptop using the SP3 setup.exe and associated setup.ini file.
So far I have included the following parameters in the setup.ini file -
SAPWD=<my own SA password>
SECURITYMODE=SQL
COLLATION=SQL_Latin1_General_CP1_CI_AS
My next test is to connect to a database on the laptop from my desktop (via my LAN) using SQL Server 2000 Enterprise Manager and/or Query Analyser.
The problem is that although I can 'see' my laptop (ping/My Network Places etc.), I can not see the MSDE installation hense my database on the laptop. The message I get is '[Microsoft]ODBC SQL server driver [DBNETLIB] SQL Server does not exist or access denied'
Have I missed a parameter i.e. do I need to set up a parameter to ensure I can connect to the installation from remote?
Being new to installing MSDE, are there any other parameters I have missed?
Ian
p.s. Anyone know of a simple to follow install instruction set for MSDE 2000 which shows what parameters can be set up
MSDE 2000 behind WSUS server
Hello,
I'm a network / server guy at heart who has been given a quasi-DBA hat
to wear lately, so bear with me.
I have a WSUS (localized Windows updates) server that uses MSDE 2000
as its back end. Since last weekend I started to get an error that
points to a database problem. For the curious, read this:
http://support.microsoft.com/kb/910847
I am disgusted that I cannot go somewhere to download the hotfix, but
rather, I have to call and ask for it. And hope to not get charged for
the call. So, what I'm looking for are utilities that will allow me to
peek inside the database and try to do some cleanup. I'm not finding
much.
I found some command line utilities buried in the directory structure,
like the query tool osql.exe, and dtsrun.exe for DTS packages. But
anything this low level quickly puts me out of my comfort zone. It
seems as though Microsoft has gone to great lengths to keep the
innards of WSUS a secret. Anybody have any ideas how to expose them?
Thanks,
Justin
what.. you want to know more about the schema?
I don't think that it's reccomended that anyone go into the schema and
change anything.. if that's what you're referring to
I know in a heartbeat a real SQL person can dig through a 100 tables in an
hour and have a clue whats going on
<jschick@.aafp.org> wrote in message
news:1177614911.411800.103200@.r3g2000prh.googlegro ups.com...
> Hello,
> I'm a network / server guy at heart who has been given a quasi-DBA hat
> to wear lately, so bear with me.
> I have a WSUS (localized Windows updates) server that uses MSDE 2000
> as its back end. Since last weekend I started to get an error that
> points to a database problem. For the curious, read this:
> http://support.microsoft.com/kb/910847
> I am disgusted that I cannot go somewhere to download the hotfix, but
> rather, I have to call and ask for it. And hope to not get charged for
> the call. So, what I'm looking for are utilities that will allow me to
> peek inside the database and try to do some cleanup. I'm not finding
> much.
> I found some command line utilities buried in the directory structure,
> like the query tool osql.exe, and dtsrun.exe for DTS packages. But
> anything this low level quickly puts me out of my comfort zone. It
> seems as though Microsoft has gone to great lengths to keep the
> innards of WSUS a secret. Anybody have any ideas how to expose them?
> Thanks,
> Justin
>
I'm a network / server guy at heart who has been given a quasi-DBA hat
to wear lately, so bear with me.
I have a WSUS (localized Windows updates) server that uses MSDE 2000
as its back end. Since last weekend I started to get an error that
points to a database problem. For the curious, read this:
http://support.microsoft.com/kb/910847
I am disgusted that I cannot go somewhere to download the hotfix, but
rather, I have to call and ask for it. And hope to not get charged for
the call. So, what I'm looking for are utilities that will allow me to
peek inside the database and try to do some cleanup. I'm not finding
much.
I found some command line utilities buried in the directory structure,
like the query tool osql.exe, and dtsrun.exe for DTS packages. But
anything this low level quickly puts me out of my comfort zone. It
seems as though Microsoft has gone to great lengths to keep the
innards of WSUS a secret. Anybody have any ideas how to expose them?
Thanks,
Justin
what.. you want to know more about the schema?
I don't think that it's reccomended that anyone go into the schema and
change anything.. if that's what you're referring to
I know in a heartbeat a real SQL person can dig through a 100 tables in an
hour and have a clue whats going on
<jschick@.aafp.org> wrote in message
news:1177614911.411800.103200@.r3g2000prh.googlegro ups.com...
> Hello,
> I'm a network / server guy at heart who has been given a quasi-DBA hat
> to wear lately, so bear with me.
> I have a WSUS (localized Windows updates) server that uses MSDE 2000
> as its back end. Since last weekend I started to get an error that
> points to a database problem. For the curious, read this:
> http://support.microsoft.com/kb/910847
> I am disgusted that I cannot go somewhere to download the hotfix, but
> rather, I have to call and ask for it. And hope to not get charged for
> the call. So, what I'm looking for are utilities that will allow me to
> peek inside the database and try to do some cleanup. I'm not finding
> much.
> I found some command line utilities buried in the directory structure,
> like the query tool osql.exe, and dtsrun.exe for DTS packages. But
> anything this low level quickly puts me out of my comfort zone. It
> seems as though Microsoft has gone to great lengths to keep the
> innards of WSUS a secret. Anybody have any ideas how to expose them?
> Thanks,
> Justin
>
Subscribe to:
Posts (Atom)