MSDE SP4 Upgrade problem

Recently when I try to upgrade my current MSDE2000 (SP3a) to SP4 in Windows
XP – SP2, the system just keep on failing me. He is the scenario:
1. Download the MSDE 2000 SP4 from Microsoft site
2. Extract the MSDE SP4
3. Run the following command via command prompt or batch file:
echo off
echo "Start to Upgrade MSDE SP4 ... "
setup.exe /UPGRADESP SQLRUN INSTANCENAME=JSNG SECURITYMODE=SQL
UPGRADEUSER=sa UPGRADEPWD=Th3B3st /L*v c:\MSDE_Log.log
echo "SP4 Upgrade Process completed!"
4. Once the above batch file was run, the standard configuration
screen (gathering information) will be triggered
5. However, after a while the installation will just stopped (before
the title of the windows has changed to show the instance name)
6. When I checked on the verbose log, I have found out that the failure
of the installation is due to the system has failed to configure the server.
PFB for the last few rows of the verbose log:
=== Logging stopped: 8/22/2006 17:36:49 ===
MSI (c) (90:88) [17:36:49:865]: Note: 1: 1729
MSI (c) (90:88) [17:36:49:865]: Product: Microsoft SQL Server Desktop Engine
-- Configuration failed.
MSI (c) (90:88) [17:36:49:865]: Grabbed execution mutex.
MSI (c) (90:88) [17:36:49:865]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (90:88) [17:36:49:865]: MainEngineThread is returning 1603
=== Verbose logging stopped: 8/22/2006 17:36:49 ===
7. Since this is the configuration error, so I have tried to locate
the cnfgsvr.out and hope to get some hints from there, but unfortunately the
config server file is still not updated yet where it still keep the old info
during the installation of MSDE 2000 SP3a.
8. When I try to locate the error (value = 3), I have found out the
its due to the system has detected blank sa password, but I am sure that the
password that I has provided is correct. PFB for the error recorded in the
verbose log:
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{EFB70B01-B1F3-4960-AB69-4A280084A60C}
Starting custom action UpgDetectBlankSaLogin()
Entering Function MyMsiEvaluateCondition
MsiEvaluateCondition for VersionNT returned TRUE
End Function MyMsiEvaluateCondition
An error was encountered during connection to server: 1
Ending custom action UpgDetectBlankSaLogin().
Action ended 9:37:45:
UpgDetectBlankSaLogin.2D02443E_7002_4C0B_ABC9_EAB2 C064397B. Return value 3.
Action ended 9:37:45: INSTALL. Return value 3.
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlProgramDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlInstanceName = EASYSHIP
Property(S): SqlSecurityMode = SQL
Property(S): SqlSa...
Property(S): SqlDisableNetworkProtocols = 0
Property(S): SqlDoUpgrade = 1
Property(S): ProductName = Microsoft SQL Server Desktop Engine (EASYSHIP)
Property(S): VersionNT = 501
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
Property(S): DefaultUIFont = Tahoma8
9. I have even try to use a different command line and yet it failed.
PFB for the alternative command line that I have used:
setup.exe /UPGRADESP SQLRUN INSTANCENAME=JSNG SECURITYMODE=SQL SAPWD=Th3B3st
/L*v
10. I have tried the same in a Windows 2000 Std Server - SP4, and yet it
failed.
During my testing, I have closed down all SQL related activities, including
the followings:
1. Microsoft OutLook
2. SQL Agent Service
3. Easyship Scheduler
But I still experience the above.
I have tried to re-run the same in one of my fresh Windows XP (in virtual
machine), and everything just works fine. Could it be any unclean registry
entry that fail this? Or could it be any software component that is
incompatible with this? Does it have anything to do with the version of MS
Installer being installed in my machine? FYI, I have installed the latest MS
Installer 3.1 before when I tried to install SQL Express, however after I
have remove it, the problem still persist.
Do you have any idea on the above? PFA for the versbose log.
HI,
I am also facing the same issue in my domain.
Unable to find much details.
Is your issue resolved?If yes kindly help me out.
Thanks in advance,
Harish K
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
|||HI,
I am also facing the same issue in my domain.
Unable to find much details.
Is your issue resolved?If yes kindly help me out.
Thanks in advance,
Harish K
EggHeadCafe.com - .NET Developer Portal of Choice
http://www.eggheadcafe.com
sql

MSDE SP4 install problem

I attempted to install MSDE SP4 (file SQL2000.MSDE-KB884525-SP4-x86-ENU) on a WinXP Pro SP2 machine.

Command used:

setup SAPWD="ourpw" SECURITYMODE=SQL /L*v c:\MSDELog.log

Install log shows successful install.

MSDE appears to function properly, service starts automatically after reboot, etc.

I can open and work with DB's with a freebie 3rd party GUI called DbaMGR2K, through which I have added the necessary DB user for our locally running ASP application to use the db.

However, when I try to use the DB with our locally running ASP application - connecting with ADO from a dll we wrote, I get the following:

"[DNETLIB]{ConnectionOpen (Connect()).]SQL Server does not exist or access denied"

Any help appreciated.

day10

Hi,

make sure that you connect to the same database and you are using a valid login for connecting. Perhaps you have chosen another authentication mode within the ADO code ? That could explain either the one or the other error message you are getting.

HTH, Jens Suessmeyer.

http://www.sqlserver2005.de

|||

I think we have solved the issue. We used the SQL Server Network Utility to enable TCP/IP (apparently not enabled by default) and now all appears well.

I wonder if there is a way to enable TCP/IP during the install process. Is there an install flag/option?

|||

>> Is there an install flag/option?

Most likely. The flag for this when installing SP3 was "DISABLENETWORKPROTOCOLS=0". I wouldn't think that they would have removed it for SP4.

sql

MSDE SP3a directly on top of SP2?

Hi,
Can MSDE SP3a be installed on top of SP2 without first uninstalling the
latter?
Cheers,
Adrian
hi Adrian,
Adrian wrote:
> Hi,
> Can MSDE SP3a be installed on top of SP2 without first uninstalling
> the latter?
> Cheers,
> Adrian
MSDE Rel A, updated at sp3a level, from the
http://www.microsoft.com/sql/msde/do...s/download.asp package, can not
upgrad existing instances at this service pack level, but only install new
instances..
but you can use the package from
http://www.microsoft.com/sql/downloads/2000/sp3.mspx , or better
http://www.microsoft.com/sql/downloads/2000/sp4.mspx for service pack 4, to
upgrade existing instances to the current/desired sp level without removing
them...
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
|||Thanks!
Adrian
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3j25l7Fnt9l6U1@.individual.net...
> hi Adrian,
> Adrian wrote:
> MSDE Rel A, updated at sp3a level, from the
> http://www.microsoft.com/sql/msde/do...s/download.asp package, can not
> upgrad existing instances at this service pack level, but only install new
> instances..
> but you can use the package from
> http://www.microsoft.com/sql/downloads/2000/sp3.mspx , or better
> http://www.microsoft.com/sql/downloads/2000/sp4.mspx for service pack 4,
> to upgrade existing instances to the current/desired sp level without
> removing them...
> --
> 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 SP3a and XP SP2 on Localhost

I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
default instance on localhost (i.e. not over the network). I found where an
upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
and it's still not working.
Is there something else I'm missing?
thanks in advance
XP SP2 installs a new local firewall that prevents applications from opening
listening ports. You will need to configure the local firewall to allow
sqlservr.exe open listening ports.
See:
http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
Jim
"tg2" <tg2@.discussions.microsoft.com> wrote in message
news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> I've upgraded to SP 2 for Windows XP and now none of my apps can see MSDE
> default instance on localhost (i.e. not over the network). I found where
an
> upgrade to SP3 was required for MSDE to coexist with XP SP2, so I upgraded
> and it's still not working.
> Is there something else I'm missing?
> thanks in advance
|||Except when running on the localhost (i.e. NOT using the network), the
firewall doesn't come into play. My application is using shared memory to
connect to the MSDE database and as such, never opens a network library --
thus opening the firewall doesn't fix the problem.
But thank you for your reply anyway...
"Jim Young" wrote:

> XP SP2 installs a new local firewall that prevents applications from opening
> listening ports. You will need to configure the local firewall to allow
> sqlservr.exe open listening ports.
> See:
> http://www.microsoft.com/sql/techinf...inxpsp2faq.asp
> Jim
> "tg2" <tg2@.discussions.microsoft.com> wrote in message
> news:344BFC99-5751-46FB-B637-75A70398763B@.microsoft.com...
> an
>
>
|||I have precisely the same problem. My application relies entirely on local
instance of MSDE.
Process associated with sqlservr does not show any port to be opened when
checked with "netstat" command. Any ideas how to work around it?
"tg2" wrote:

> Except when running on the localhost (i.e. NOT using the network), the
> firewall doesn't come into play. My application is using shared memory to
> connect to the MSDE database and as such, never opens a network library --
> thus opening the firewall doesn't fix the problem.
> But thank you for your reply anyway...
>
sql

MSDE SP3a and XP SP2

Hi
According to various things I've read, XP SP2 will close off SQL Server
ports unless SQL/MSDE SP3 is installed.
However, I've installed MSDE 2000a (equivalent to MSDE 2000 SP3a) with
XP Pro SP2 and no network machine can see the DB server.
I uninstall XP SP2 and the network can see the DB server fine.
Can anybody throw any light onto this?
Thanks
Tony
Hi Tony,
XP SP2 installs an Internet Connection Firewall by default. It will block
the ports you need. You will need to "punch a hole" in the firewall for the
MSDE port (normally 1433 but you can change it using svrnetcn.exe).
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Tony Taylor" <tony@.postopticsNOSPAM.co.uk> wrote in message
news:e1DMi4dhEHA.2052@.tk2msftngp13.phx.gbl...
> Hi
> According to various things I've read, XP SP2 will close off SQL Server
> ports unless SQL/MSDE SP3 is installed.
> However, I've installed MSDE 2000a (equivalent to MSDE 2000 SP3a) with
> XP Pro SP2 and no network machine can see the DB server.
> I uninstall XP SP2 and the network can see the DB server fine.
> Can anybody throw any light onto this?
> Thanks
> Tony
|||Greg Low [MVP] wrote:

> Hi Tony,
> XP SP2 installs an Internet Connection Firewall by default. It will block
> the ports you need. You will need to "punch a hole" in the firewall for the
> MSDE port (normally 1433 but you can change it using svrnetcn.exe).
> HTH,
>
Hi Greg
Thanks for getting back quickly.
How can I find which port the server is listening on?
We're using a named instance which won't use the standard 1433.
With XP SP2, I've run netstat and the sqlservr.exe PID is not listed so
I can't get the port from that. svrnetcn.exe tells me the port is 0 (I
assume that's because XP SP2 has switched it off).
Thanks again
Tony
|||hi Tony,
"Tony Taylor" <tony@.postopticsNOSPAM.co.uk> ha scritto nel messaggio
news:%23tWgd9ehEHA.3912@.TK2MSFTNGP11.phx.gbl...
> How can I find which port the server is listening on?
> We're using a named instance which won't use the standard 1433.
> With XP SP2, I've run netstat and the sqlservr.exe PID is not listed so
> I can't get the port from that. svrnetcn.exe tells me the port is 0 (I
> assume that's because XP SP2 has switched it off).
Named instaces are resolved by the host listening on UDP port 1434, which
then redirect tha specific calls to a dinamically assigned port (as
default)... this is a dynamic port assignement behaviour...
with Windows XP sp2 Windows Firewall which blocs all these connections, you
have to manual set the port you want them to use, so chose a fixed port for
your named instance with Server Network Utility (svrnetcn.exe), open that
port on the Windows Firewall, and, for all remote client, use Client Network
Utility (cloconfg.exe) to map connections to that static port
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
|||You can also add a firewall exception for sqlserver.exe, rather than opening
the port wide open. If other executables need to accept connections, also add
exceptions for them. That will cover any port, but only for that executable.
"Andrea Montanari" wrote:

> hi Tony,
> "Tony Taylor" <tony@.postopticsNOSPAM.co.uk> ha scritto nel messaggio
> news:%23tWgd9ehEHA.3912@.TK2MSFTNGP11.phx.gbl...
> Named instaces are resolved by the host listening on UDP port 1434, which
> then redirect tha specific calls to a dinamically assigned port (as
> default)... this is a dynamic port assignement behaviour...
> with Windows XP sp2 Windows Firewall which blocs all these connections, you
> have to manual set the port you want them to use, so chose a fixed port for
> your named instance with Server Network Utility (svrnetcn.exe), open that
> port on the Windows Firewall, and, for all remote client, use Client Network
> Utility (cloconfg.exe) to map connections to that static port
> --
> 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
>
|||hi Damian,
"Damian" <Damian@.discussions.microsoft.com> ha scritto nel messaggio
news:9F11A754-13A0-4033-81E4-C8354D510EEA@.microsoft.com...
> You can also add a firewall exception for sqlserver.exe, rather than
opening
> the port wide open. If other executables need to accept connections, also
add
> exceptions for them. That will cover any port, but only for that
executable.
still do not have Windows Firewall enabled, but I do think the problem is
outside calls to SQL Server and not the opposite, requiring that
sqlserver.exe should be added to the exceptions list..
but will investigate as soon as I get WinXP sp2 installed
you have to cover outside calls from IIS, winforms apps and so on...
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
|||Damian wrote:
[vbcol=seagreen]
> You can also add a firewall exception for sqlserver.exe, rather than opening
> the port wide open. If other executables need to accept connections, also add
> exceptions for them. That will cover any port, but only for that executable.
> "Andrea Montanari" wrote:
>
Hi chaps
I've tried the follwing:
use svrnetcn.exe to assign a static port to the named instance, open
that port in Windows Firewall and use cliconfg.exe to map connections to
that port
and
allow sqlservr.exe through as an exception in Windows Firewall
but neither have worked. Maybe I've missed something.
Has anyone actually had any success connecting across a network with XP
SP2 on the MSDE box?
Thanks
Tony

MSDE Service Manager on XP Pro SP2

I recently installed MSDE 2K on a Windows XP SP2 system. Everything appears
to be working fine, with the exception of the service manager. For some
reason, it will not find the system on the local network and will not
connect to it if I type the name in the server name area. Is this normal or
am I just missing something? Thanks in advance.
hi David,
"David Young" <cdyoung@.uta.edu> ha scritto nel messaggio
news:eBToEMg3EHA.3840@.tk2msftngp13.phx.gbl
> I recently installed MSDE 2K on a Windows XP SP2 system. Everything
> appears to be working fine, with the exception of the service
> manager. For some reason, it will not find the system on the local
> network and will not connect to it if I type the name in the server
> name area. Is this normal or am I just missing something? Thanks in
> advance.
actually, for local instances connections, WinXP sp2 should not be a
problem, but only for remote connections :D
as regard the Service Manager not showing the instance name, this is a known
issue when network protocols are disabled (default setting) as you can see
in http://support.microsoft.com/default...b;EN-US;814132
as regard directly typing in the instance name... did you provide the name
in the ComputerName\InstanceName format ( or just (local)\InstanceName) ?
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 remote connection failure

Hi all,

I installed a MSDE on a Windows XP SP2 and configured it for accepting remote connections. But It shows the "SQL Server doesnot exist or connection denied" message whenever I try to connect to this server. For more information I am adding more facts

* It is an MSDE and not a WMSDE
* Firewall is turned off
* Server process is listening on 0.0.0.0:1433
* TCP/IP and Named Pipes are enabled using server network utility
* LoginMode=2 is set for mixed mode authentication in the registry
* Tried restaring the Process and even windows after the changes.

Please help me !!

Thanks in advanceHi friends,
I got the issue fixed. :angel:

I dont know how it works but it worked.

On the client side; using the client network utility, I added an alias to my server.

My server's instance name was SLIMSHADY\SSIT and it was listening on 8001(I changed it thru the registry) in mixed mode authentication.

It wasted my 4-5 hours of playing with the registry and googling. The final attempt succeeded in which I created an alias to the server Indicating its exact port number and Instance name.

Then I tried connecting using this alias .... IT WORKED !!

I DONT KNOW HOW IT WORKS BUT IT WORKED IN MY CASE

HAPPY COMPUTING

MSDE remote connection failure

Hi all,

I installed a MSDE on a Windows XP SP2 and configured it for accepting remote connections. But It shows the "SQL Server doesnot exist or connection denied" message whenever I try to connect to this server. For more information I am adding more facts

* It is an MSDE and not a WMSDE
* Firewall is turned off
* Server process is listening on 0.0.0.0:1433
* TCP/IP and Named Pipes are enabled using server network utility
* LoginMode=2 is set for mixed mode authentication in the registry
* Tried restaring the Process and even windows after the changes.

Please help me !!

Thanks in advanceHi friends,
I got the issue fixed. :angel:

I dont know how it works but it worked.

On the client side; using the client network utility, I added an alias to my server.

My server's instance name was SLIMSHADY\SSIT and it was listening on 8001(I changed it thru the registry) in mixed mode authentication.

It wasted my 4-5 hours of playing with the registry and googling. The final attempt succeeded in which I created an alias to the server Indicating its exact port number and Instance name.

Then I tried connecting using this alias .... IT WORKED !!

I DONT KNOW HOW IT WORKS BUT IT WORKED IN MY CASE

HAPPY COMPUTING

MSDE Remote Connect strange problem

I'm trying to connect to the SharePoint MSDE database from Windows XP
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not
exist or access denied.
I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?

Did you ever get an answer to this problem? I'm having a similar error on Windows XP SP2 machines that have MDAC 2.8SP1. I have an MS Access front end that links to SQL Server database using ODBC connections. The report will run, but keeps asking for SQL Server login info, then finally I get the same Connection failed error you listed with the exception on the line: SQL Server Error: 10048. However, the report actually finishes with all the data requested.

I have this same Access front end running on other XP machines with SP1 and Windows 2000 machines with MDAC 2.7 SP1. When the report runs on those machines it only asks for SQL Server login info when the program is first connecting to the db.

Any ideas?

|||

Thank you thank you for letting me know about the svrnetcn.exe tool. I have been trying for hours to get a Sharepoint portal going and whilst for the error I had MS KB said enable tcp/ip, it didn't say how to do it for msde. Where did you find out about svrnetcn.exe and are there other useful tools I should know about? I'm ok with osql.

I have seen the error you are getting. It will happen if I'm not using Windows integrated authentication. If I try to connect with osql -U sa -S servername\instancename it doesn't work and gives a server does not exist or access denied. I have to use osql -E -S servername\instancename and it goes in fine.

Hope this helps - even if its a bit late!

Nath

|||

Nathan,

here is the linke which might be useful to you guys

http://www.codeproject.com/database/ConfigureMSDE.asp

Best regards,
Web

MSDE Remote Connect strange problem

I'm trying to connect to the SharePoint MSDE database from Windows XP
SP2 machine over Ethernet LAN. I was getting server not found or access
denied, until I enabled TCP/IP via svrnetcn.exe. Now, I'm getting
OK
Connection failed:
SQLState: '01000'
SQL Server Error: 10061
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]ConnectionOpen
(Connect()).
Connection failed:
SQLState: '08001'
SQL Server Error: 17
[Microsoft][ODBC SQL Server Driver][TCP/IP Sockets]SQL Server does not
exist or access denied.
I just did an netstat -an and I don't see the server listening on 1433.
What am I not doing?
The svrnetcn tool has no effect. I make a change and check the logs,
but nothing happens. What would be causing this?

Did you ever get an answer to this problem? I'm having a similar error on Windows XP SP2 machines that have MDAC 2.8SP1. I have an MS Access front end that links to SQL Server database using ODBC connections. The report will run, but keeps asking for SQL Server login info, then finally I get the same Connection failed error you listed with the exception on the line: SQL Server Error: 10048. However, the report actually finishes with all the data requested.

I have this same Access front end running on other XP machines with SP1 and Windows 2000 machines with MDAC 2.7 SP1. When the report runs on those machines it only asks for SQL Server login info when the program is first connecting to the db.

Any ideas?

|||

Thank you thank you for letting me know about the svrnetcn.exe tool. I have been trying for hours to get a Sharepoint portal going and whilst for the error I had MS KB said enable tcp/ip, it didn't say how to do it for msde. Where did you find out about svrnetcn.exe and are there other useful tools I should know about? I'm ok with osql.

I have seen the error you are getting. It will happen if I'm not using Windows integrated authentication. If I try to connect with osql -U sa -S servername\instancename it doesn't work and gives a server does not exist or access denied. I have to use osql -E -S servername\instancename and it goes in fine.

Hope this helps - even if its a bit late!

Nath

|||

Nathan,

here is the linke which might be useful to you guys

http://www.codeproject.com/database/ConfigureMSDE.asp

Best regards,
Web

MSDE periodically fails to start at startup in restricted account

I am currently running Windows XP SP2 Tablet Edition running MSDE v 8.00.761.
The problem I am having is that at random intervals MSDE fails to start. I
can only duplicate this problem while running under a restricted user
account. In the error logs the only difference I can see is that when the
service fails the “xpsqlbot.dll” starts before the database starts. I have
the restricted user account setup so that it logs in automatically using
tweak UI. Could this be a timing issue with MSDE startup? If any one could
help I would really appreciate it.
What is the error message in the system event log say?
Jim
"Avail Developer" <AvailDeveloper@.discussions.microsoft.com> wrote in
message news:72217B26-BE67-49D7-8781-F332605D6FE4@.microsoft.com...
>I am currently running Windows XP SP2 Tablet Edition running MSDE v
>8.00.761.
> The problem I am having is that at random intervals MSDE fails to start.
> I
> can only duplicate this problem while running under a restricted user
> account. In the error logs the only difference I can see is that when
> the
> service fails the "xpsqlbot.dll" starts before the database starts. I
> have
> the restricted user account setup so that it logs in automatically using
> tweak UI. Could this be a timing issue with MSDE startup? If any one
> could
> help I would really appreciate it.
>

MSDE on WinXP Pro SP2 joined to a domain

Hi,
I have a problem that I cannot find a resolution to.
Recently, I got a laptop and I installed WinXP Pro SP2 on it.
I did this at home so was not near my office domain so I temporarily setup
the laptop as a workgroup computer instead of joining the domain.
Once installed, I then installed MSDE2000RelA.
Everything was working fine.
Then I took the laptop to work, joined the domain, and now MSDE can no
longer connect. All I get in the system tray is a computer tower icon with a
white circle on it. Hovering over that pops up "Cannot connect \\". There
should be a green arrow in the circle when services start.
I have tried uninstalling, re-installing, changing user permissions in group
policy for the guest account? - all sorts of things, but nothing fixes this
issue - and I desperately need MSDE to work on the laptop.
I think it has something to do with the laptop being on the domain, but I
don't know (and that doesn't really make sense to me either).
Can anyone point me to a solution?
Cheers,
Rob
hi Rob
Did u set DISABLENETWORKPROTOCOLS=0 parameter while setup?
by default the setup will take 1 (means disable).
just check out
Dil
|||Ah, no I didn't!
Do I have to reinstall or can I update a previous installation with this
setting?
Cheers,
Rob
|||hi Rob,
RobGT wrote:
> Ah, no I didn't!
> Do I have to reinstall or can I update a previous installation with
> this setting?
please run the Server Network Utility (svrnetcn.exe) to enable the desired
network protocol..
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
|||Perfect, thankyou.
It appears to now be working fine.
Shame I found it so difficult to locate this information (I searched online
for ages before coming here to ask the question!)
Thanks a million for resolving this so quickly for me!
Cheers,
Rob

MSDE on Windows 2003

I am trying to connect to a MSDE from XP pro SP2, the MSDE is running on Windows 2003 server and the only way I can connect to the MSDE is if I make the network user an Administrator of the Windows 2003 server.
How can I connect to MSDE without making the user an Admin?
Thanks
Peter
hi Peter,
Peter wrote:
> I am trying to connect to a MSDE from XP pro SP2, the MSDE is running
> on Windows 2003 server and the only way I can connect to the MSDE is
> if I make the network user an Administrator of the Windows 2003
> server.
> How can I connect to MSDE without making the user an Admin?
assuming you've no network problem ( :-D ), what kind of authentication are
you using for that?
I guess you are using Windows authentication (trusted connection)... MSDE
installs by default granting local Windows admins membership to the SQL
Server sysadmins role (BUILTIN\Administrator) so that they are "naturally"
granted login to the MSDE instance... if you want your power/limited users
to be granted to, you have to manually create a SQL Server "Windows"
Login(s) or Windows Group login for all your required users...
please have a look at
http://msdn.microsoft.com/library/de...ga-gz_8dri.asp
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
|||I have added a domain user the the database
EXEC sp_grantlogin 'MyDomain\Peter'
Go
but still user Peter can not connect to the database unless Peter is an
Admin
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3ngpceF1f9poU1@.individual.net...
> hi Peter,
> Peter wrote:
> assuming you've no network problem ( :-D ), what kind of authentication
> are you using for that?
> I guess you are using Windows authentication (trusted connection)... MSDE
> installs by default granting local Windows admins membership to the SQL
> Server sysadmins role (BUILTIN\Administrator) so that they are "naturally"
> granted login to the MSDE instance... if you want your power/limited users
> to be granted to, you have to manually create a SQL Server "Windows"
> Login(s) or Windows Group login for all your required users...
> please have a look at
> http://msdn.microsoft.com/library/de...ga-gz_8dri.asp
> --
> 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
>
|||hi Peter,
Peter wrote:
> I have added a domain user the the database
> EXEC sp_grantlogin 'MyDomain\Peter'
> Go
> but still user Peter can not connect to the database unless Peter is
> an Admin
using and accessing MSDE/SQL Server and it's databases belongs to an
authentication area of the product...
SQL Server uses a sort of 2 phase authentication..
the first one regards login, where someone try to connect to a particular
instance using WinNT (trusted) connections or standard SQL Server
connections (yes, handling both is known as "mixed authentication")
in the second case, standard SQL Server connections, a user id and a
password must be provided, and this information has to be matched against
available SQL Server logins... if a match is found the connecting person has
provided correct information and can log in...
the WinNT (trusted) method does not require this kind of information as the
underlaying OS provides the sid of the against the DC authenticated OS
login, that only need to be matched against a WinNT SQL Server already
granted login or WinNT granted group..
that's to say both kind of authentications need a match in the granted
logins...
Standard SQL Server logins must all be manually added via sp_addlogin system
stored procedure but "sa" "super" login, which is provided by default and
that can not be removed..
as regard WinNT connections, the setup automatically adds a WinNT group
including all WinNT administrators, and this is the reason you can log in
MSDE when logged in Windows as admin...
but all other Windows users/groups have to be manually added via sytem
stored procedure sp_grantlogin
so you have to add you specific WinNT group (say "powerusers") in order to
grant all them permission to log in, or only your specific WinNT account
Domain\Account if you want only him to be granted login...
as regard the second authentication phase, it regards specific access to
each database, and this is done via the sp_grantdbaccess system stored
procedures, that adds an entry in each specific database.dbo.sysusers system
table matching the master.dbo.syslogins system view in the join of the sid
column... this operation generate a database user mapped to a specific
login, allowing him/her to access the desired database with the provided
database role privileges... additional permission can be granted/denied to
each db user, defining the specific security design as required on every db
object and so on, but this is a successive step...
please start reading at
http://msdn.microsoft.com/library/de...ar_da_0n77.asp
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
|||Andrea,
Thanks for all of your help. I ran both cleanup tools. Still did not solve
problem. I would not give up! After many hours of trial and error I
determine the problem was with a corrupted MDAC component. Reinstall MDAC on
XP sp2? Yes there is a way to do that (very simple). Once I reinstalled
MDAC the client application connected and installed just fine. --RS
"Andrea Montanari" wrote:

> hi Peter,
> Peter wrote:
> using and accessing MSDE/SQL Server and it's databases belongs to an
> authentication area of the product...
> SQL Server uses a sort of 2 phase authentication..
> the first one regards login, where someone try to connect to a particular
> instance using WinNT (trusted) connections or standard SQL Server
> connections (yes, handling both is known as "mixed authentication")
> in the second case, standard SQL Server connections, a user id and a
> password must be provided, and this information has to be matched against
> available SQL Server logins... if a match is found the connecting person has
> provided correct information and can log in...
> the WinNT (trusted) method does not require this kind of information as the
> underlaying OS provides the sid of the against the DC authenticated OS
> login, that only need to be matched against a WinNT SQL Server already
> granted login or WinNT granted group..
> that's to say both kind of authentications need a match in the granted
> logins...
> Standard SQL Server logins must all be manually added via sp_addlogin system
> stored procedure but "sa" "super" login, which is provided by default and
> that can not be removed..
> as regard WinNT connections, the setup automatically adds a WinNT group
> including all WinNT administrators, and this is the reason you can log in
> MSDE when logged in Windows as admin...
> but all other Windows users/groups have to be manually added via sytem
> stored procedure sp_grantlogin
> so you have to add you specific WinNT group (say "powerusers") in order to
> grant all them permission to log in, or only your specific WinNT account
> Domain\Account if you want only him to be granted login...
> as regard the second authentication phase, it regards specific access to
> each database, and this is done via the sp_grantdbaccess system stored
> procedures, that adds an entry in each specific database.dbo.sysusers system
> table matching the master.dbo.syslogins system view in the join of the sid
> column... this operation generate a database user mapped to a specific
> login, allowing him/her to access the desired database with the provided
> database role privileges... additional permission can be granted/denied to
> each db user, defining the specific security design as required on every db
> object and so on, but this is a successive step...
> please start reading at
> http://msdn.microsoft.com/library/de...ar_da_0n77.asp
> --
> 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
>
>
|||Wrong thread, see above... RS
"Andrea Montanari" wrote:

> hi Peter,
> Peter wrote:
> using and accessing MSDE/SQL Server and it's databases belongs to an
> authentication area of the product...
> SQL Server uses a sort of 2 phase authentication..
> the first one regards login, where someone try to connect to a particular
> instance using WinNT (trusted) connections or standard SQL Server
> connections (yes, handling both is known as "mixed authentication")
> in the second case, standard SQL Server connections, a user id and a
> password must be provided, and this information has to be matched against
> available SQL Server logins... if a match is found the connecting person has
> provided correct information and can log in...
> the WinNT (trusted) method does not require this kind of information as the
> underlaying OS provides the sid of the against the DC authenticated OS
> login, that only need to be matched against a WinNT SQL Server already
> granted login or WinNT granted group..
> that's to say both kind of authentications need a match in the granted
> logins...
> Standard SQL Server logins must all be manually added via sp_addlogin system
> stored procedure but "sa" "super" login, which is provided by default and
> that can not be removed..
> as regard WinNT connections, the setup automatically adds a WinNT group
> including all WinNT administrators, and this is the reason you can log in
> MSDE when logged in Windows as admin...
> but all other Windows users/groups have to be manually added via sytem
> stored procedure sp_grantlogin
> so you have to add you specific WinNT group (say "powerusers") in order to
> grant all them permission to log in, or only your specific WinNT account
> Domain\Account if you want only him to be granted login...
> as regard the second authentication phase, it regards specific access to
> each database, and this is done via the sp_grantdbaccess system stored
> procedures, that adds an entry in each specific database.dbo.sysusers system
> table matching the master.dbo.syslogins system view in the join of the sid
> column... this operation generate a database user mapped to a specific
> login, allowing him/her to access the desired database with the provided
> database role privileges... additional permission can be granted/denied to
> each db user, defining the specific security design as required on every db
> object and so on, but this is a successive step...
> please start reading at
> http://msdn.microsoft.com/library/de...ar_da_0n77.asp
> --
> 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
>
>

MSDE installation woes

I have tried 3 times to install MSDE on my laptop,
different problem each time. I have wiped the hard drive
and reinstalled XP sp2 to try again, downloaded MSDE 2000
rel A. Installed with the command Setup SAPWD="eight"
SECURITYMODE=SQL
COLLATION="SQL_Latin1_General_CP1_Cl_AS" /L*v c:\MSDE.log.
The installation just terminates abruptly. Search
for 'return value 3' turns up this:
An error was encountered during connection to server: 3
Ending custom action UpgDetectBlankSaLogin().
Action ended 9:19:42:
UpgDetectBlankSaLogin.2D02443E_7002_4C0B_ABC9_EAB2 C064397B
.. Return value 3.
Action ended 9:19:42: INSTALL. Return value 3.
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-
253F2FBCCE49}
Property(S): SqlCollation = SQL_Latin1_General_CP1_Cl_AS
Property(S): SqlDataDir = C:\Program Files\Microsoft SQL
Server\
Property(S): SqlProgramDir = C:\Program Files\Microsoft
SQL Server\
Property(S): SqlInstanceName = MSSQLSERVER
Property(S): SqlSecurityMode = SQL
Property(S): SqlSa...
Property(S): SqlDisableNetworkProtocols = 0
Property(S): VersionNT = 501
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
I've lost a week on this, getting desparate!
Thanks, Brian
hi Brian,
"Brian" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:167e01c4b551$02b56fc0$a301280a@.phx.gbl
> I have tried 3 times to install MSDE on my laptop,
> different problem each time. I have wiped the hard drive
> and reinstalled XP sp2 to try again, downloaded MSDE 2000
> rel A. Installed with the command Setup SAPWD="eight"
> SECURITYMODE=SQL
> COLLATION="SQL_Latin1_General_CP1_Cl_AS" /L*v c:\MSDE.log.
> The installation just terminates abruptly. Search
> for 'return value 3' turns up this:
> An error was encountered during connection to server: 3
> Ending custom action UpgDetectBlankSaLogin().
> Action ended 9:19:42:
> UpgDetectBlankSaLogin.2D02443E_7002_4C0B_ABC9_EAB2 C064397B
> . Return value 3.
> Action ended 9:19:42: INSTALL. Return value 3.
> Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-
> 253F2FBCCE49}
> Property(S): SqlCollation = SQL_Latin1_General_CP1_Cl_AS
> Property(S): SqlDataDir = C:\Program Files\Microsoft SQL
> Server\
> Property(S): SqlProgramDir = C:\Program Files\Microsoft
> SQL Server\
> Property(S): SqlInstanceName = MSSQLSERVER
> Property(S): SqlSecurityMode = SQL
> Property(S): SqlSa...
> Property(S): SqlDisableNetworkProtocols = 0
> Property(S): VersionNT = 501
> Property(S): ALLUSERS = 1
> Property(S): ARPNOMODIFY = 1
> I've lost a week on this, getting desparate!
> Thanks, Brian
the only info I've found are listed in
http://www.google.it/groups?as_q=Upg...&num=100&hl=it
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
|||try a stronger password than "eight." I had the same issue and the problem
is that rel A wants a secure SA password. It will reject a simple one and
you are left with the error saying there is no password, hence "Ending
custom action 'UpgDetectBlankSaLogin' "
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:2tkeqmF21euj1U1@.uni-berlin.de...
> hi Brian,
> "Brian" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
> news:167e01c4b551$02b56fc0$a301280a@.phx.gbl
> the only info I've found are listed in
>
http://www.google.it/groups?as_q=Upg...&num=100&hl=it
> --
> 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 Installation problem.

I have recently installed MSDE and SP3a on my Windows XP
Pro machine. XP SP2 was installed prior to the MSDE
installation. The installation of both MSDE & SP3a
completed without error.
When I log in the server icon appears on the taskbar.
When I place the mouse pointer over the icon "Unknown -
\\ - MSSQLServer" appears.
When I right click the icon and attempt to start, I
receive the following.
"Error The handle is invalid."
I click OK.
The following error appears.
"An error 6 - (The handle is invalid.) occurred while
performing the service operation on the MSSQLSeerver
service."
I click stop and then receive the same errors in the same
order after being asked if I am sure I wish to stop.
I applied a strong password when installing.
Thoughts?
I am seeing the same symptoms as you are. I just installed VS.Net 2003 and MSDE on a brand spanking new hard disk with windows xp sp2 on it. Though, I don't know if it is the latest version of MSDE.
If I open the sql manager there is nothing in the server field. When I try using "local" and click on the refresh services button I get an error saying "The network path is not found."
Any ideas how I can get MSDE running?
thanks!|||Likewise, same problem, though I'm working off win2k and reached msde need
through a limited period copy of Visual.net (for learning purposes).
I'm afraid I'm not at the pc at the moment, but I installed the msde desktop
patch and wasn't sure whether should also have installed the two other
patches that were available.
I await with interest!
Ivor
"anonymous@.discussions.microsoft.com" wrote:

> I have recently installed MSDE and SP3a on my Windows XP
> Pro machine. XP SP2 was installed prior to the MSDE
> installation. The installation of both MSDE & SP3a
> completed without error.
> When I log in the server icon appears on the taskbar.
> When I place the mouse pointer over the icon "Unknown -
> \\ - MSSQLServer" appears.
> When I right click the icon and attempt to start, I
> receive the following.
> "Error The handle is invalid."
> I click OK.
> The following error appears.
> "An error 6 - (The handle is invalid.) occurred while
> performing the service operation on the MSSQLSeerver
> service."
> I click stop and then receive the same errors in the same
> order after being asked if I am sure I wish to stop.
> I applied a strong password when installing.
> Thoughts?
>
|||I have the same problem.... Any help would really be appreciated..
_cCp

Quote:

Originally posted by Ivor
Likewise, same problem, though I'm working off win2k and reached msde need
through a limited period copy of Visual.net (for learning purposes).
I'm afraid I'm not at the pc at the moment, but I installed the msde desktop
patch and wasn't sure whether should also have installed the two other
patches that were available.
I await with interest!
Ivor
"anonymous@.discussions.microsoft.com" wrote:

> I have recently installed MSDE and SP3a on my Windows XP
> Pro machine. XP SP2 was installed prior to the MSDE
> installation. The installation of both MSDE & SP3a
> completed without error.
> When I log in the server icon appears on the taskbar.
> When I place the mouse pointer over the icon "Unknown -
> \\ - MSSQLServer" appears.
> When I right click the icon and attempt to start, I
> receive the following.
> "Error The handle is invalid."
> I click OK.
> The following error appears.
> "An error 6 - (The handle is invalid.) occurred while
> performing the service operation on the MSSQLSeerver
> service."
> I click stop and then receive the same errors in the same
> order after being asked if I am sure I wish to stop.
> I applied a strong password when installing.
> Thoughts?
>

|||I found out the problem, it's to do with, if I remember rightly, the IWAM_USR
account in windows, you need to change some of the security policies. I'm
not on the machine at the moment, try a search in Knowledge Base or email me
on marmite REMOVE THIS BIT@.fastmail.fm
"plummernh" wrote:

> I have the same problem.... Any help would really be appreciated..
> _cCp
> Ivor wrote:
>
> --
> plummernh
> Posted via http://www.mcse.ms
> View this thread: http://www.mcse.ms/message1050720.html
>

MSDE Installation Problem - very urgent

Hi,
I'm facing a strange problem with MSDE. I installed MSDE 2000 in a newly formatted Window 2000 professional Machine with SP2 and IE5.5. I restarted the machine after MSDE installation. Installed my application, which creates a database. Database creation failed, I got this error "Login failed for user 'spsadmin'. Reason: Not associated with a trusted SQL
Server connection.". I tried again, this time I restarted the machine thrice after installing MSDE, then ran my setup. Database installation was through. We can't ask the end user to restart the machine these many times. Any help will be appreciated.
Thanks in advance,
VardhiniHi,
I solved the problem. It was because of the authentication. In the setup the login mode was changed to 2 and it was not getting reflected as the service was running. So from the setup I stopped the service, changed the mode and started the service again, this time database had been created successfully.
Thanks,
Vardhini

MSDE Installation Help

Hi
I am trying to instal MSDE 2000 on a Windows XP Pro SP2 machine. I type in
....
"Setup.exe /qb+ INSTANCENAME=NetSDK DISABLENETWORKPROTOCOLS=1 SAPWD=<YOUR SA
PASSWORD>" at the command prompt and the MSDE setup begins to take place. At
the nearly the end of the install, I get a pop-up dialog stating the the
instalation failed.
I checked setupapi.log file under C:\winnt and the follwoing error was in
their...
"
[2005/01/03 21:29:08 2672.1]
#-199 Executing "C:\Documents and Settings\Owner\Local
Settings\Temp\IXP000.TMP\dasetup.exe" with command line: /Q /N
#E077 Could not locate a non-empty section [DefaultInstall] when calculating
disk space in "C:\Documents and Settings\Owner\Local
Settings\Temp\IXP000.TMP\noop.inf". Error 0xe0000102: The required line was
not found in the INF."
Anyone have any ideas as to what the above means. Also, I checked the
dasetup.log file that was created when attempting to install MSDE and I
noticed the following...
: ****************************************
: * Beginning of Install *
: ****************************************
Starting Install: Current Date/Time (U.S. Local Time): 01/03/2005 : 21:29:07
Path: C:\WINNT;C:\WINNT\system32;
Localization: Machine Locale set to: English_United States.1252
Command Line Parameters:
Suppress Reboot: 0
Quiet/Silent Mode: 1
Logging Level: 3
INI File: dasetup.ini
Windows Directory: C:\WINNT
Progress: Loading Resource Library.
Progress: Parsing INI File.
*************************:
** Begin INI File Dump **:
*************************:
Ini Section: General
: ProductName = Microsoft Data Access Components 2.7
: ProductBuild = 2.71.9040.2
: ProductUrl = http://www.microsoft.com/data
: ProductVersionKey = SOFTWARE\Microsoft\DataAccess
: ProductVersionValue = FullInstallVer
: InstanceName = MDAC
: CheckInUseFiles = 1
: EULAFile = MDACEULA.RTF
: EULAType = rtf
: SupportsTS = 1
: SupportsMUI = 0
: CheckForDiskSpace = 1
: ValidOs = 4294967295
I find it starnge that the install is trying to use MDAC 2.7 when I
currently have MDAC 2.8 SP1 installed on my machine (I verified this through
the MDAC compcheck app).
Anyone have any ideas as to what is going on?
PS Sorry for the long message
Thanks
I also found this error in the dahotfix.log
"
[05:03:12]: An error occurred while setup was trying to verify the version
of Microsoft Data Access Components current installed on the machine.
Either the version currently installed does not match the version of this
hotfix package, or setup was unable to determine the version currently
installed.
["
"John Rydenbark" wrote:

> Hi
> I am trying to instal MSDE 2000 on a Windows XP Pro SP2 machine. I type in
> ...
> "Setup.exe /qb+ INSTANCENAME=NetSDK DISABLENETWORKPROTOCOLS=1 SAPWD=<YOUR SA
> PASSWORD>" at the command prompt and the MSDE setup begins to take place. At
> the nearly the end of the install, I get a pop-up dialog stating the the
> instalation failed.
> I checked setupapi.log file under C:\winnt and the follwoing error was in
> their...
> "
> [2005/01/03 21:29:08 2672.1]
> #-199 Executing "C:\Documents and Settings\Owner\Local
> Settings\Temp\IXP000.TMP\dasetup.exe" with command line: /Q /N
> #E077 Could not locate a non-empty section [DefaultInstall] when calculating
> disk space in "C:\Documents and Settings\Owner\Local
> Settings\Temp\IXP000.TMP\noop.inf". Error 0xe0000102: The required line was
> not found in the INF."
> Anyone have any ideas as to what the above means. Also, I checked the
> dasetup.log file that was created when attempting to install MSDE and I
> noticed the following...
> : ****************************************
> : * Beginning of Install *
> : ****************************************
> Starting Install: Current Date/Time (U.S. Local Time): 01/03/2005 : 21:29:07
> Path: C:\WINNT;C:\WINNT\system32;
> Localization: Machine Locale set to: English_United States.1252
> Command Line Parameters:
> Suppress Reboot: 0
> Quiet/Silent Mode: 1
> Logging Level: 3
> INI File: dasetup.ini
> Windows Directory: C:\WINNT
> Progress: Loading Resource Library.
> Progress: Parsing INI File.
> *************************:
> ** Begin INI File Dump **:
> *************************:
> Ini Section: General
> : ProductName = Microsoft Data Access Components 2.7
> : ProductBuild = 2.71.9040.2
> : ProductUrl = http://www.microsoft.com/data
> : ProductVersionKey = SOFTWARE\Microsoft\DataAccess
> : ProductVersionValue = FullInstallVer
> : InstanceName = MDAC
> : CheckInUseFiles = 1
> : EULAFile = MDACEULA.RTF
> : EULAType = rtf
> : SupportsTS = 1
> : SupportsMUI = 0
> : CheckForDiskSpace = 1
> : ValidOs = 4294967295
> I find it starnge that the install is trying to use MDAC 2.7 when I
> currently have MDAC 2.8 SP1 installed on my machine (I verified this through
> the MDAC compcheck app).
> Anyone have any ideas as to what is going on?
> PS Sorry for the long message
> Thanks
>

MSDE Installation Help

Hi
I am trying to instal MSDE 2000 on a Windows XP Pro SP2 machine. I type in
...
"Setup.exe /qb+ INSTANCENAME=NetSDK DISABLENETWORKPROTOCOLS=1 SAPWD=<YOUR SA
PASSWORD>" at the command prompt and the MSDE setup begins to take place. At
the nearly the end of the install, I get a pop-up dialog stating the the
instalation failed.
I checked setupapi.log file under C:\winnt and the follwoing error was in
their...
"
[2005/01/03 21:29:08 2672.1]
#-199 Executing "C:\Documents and Settings\Owner\Local
Settings\Temp\IXP000.TMP\dasetup.exe" with command line: /Q /N
#E077 Could not locate a non-empty section [DefaultInstall] when calcula
ting
disk space in "C:\Documents and Settings\Owner\Local
Settings\Temp\IXP000.TMP\noop.inf". Error 0xe0000102: The required line was
not found in the INF."
Anyone have any ideas as to what the above means. Also, I checked the
dasetup.log file that was created when attempting to install MSDE and I
noticed the following...
: ****************************************
: * Beginning of Install *
: ****************************************
Starting Install: Current Date/Time (U.S. Local Time): 01/03/2005 : 21:29:07
Path: C:\WINNT;C:\WINNT\system32;
Localization: Machine Locale set to: English_United States.1252
Command Line Parameters:
Suppress Reboot: 0
Quiet/Silent Mode: 1
Logging Level: 3
INI File: dasetup.ini
Windows Directory: C:\WINNT
Progress: Loading Resource Library.
Progress: Parsing INI File.
*************************:
** Begin INI File Dump **:
*************************:
Ini Section: General
: ProductName = Microsoft Data Access Components 2.7
: ProductBuild = 2.71.9040.2
: ProductUrl = http://www.microsoft.com/data
: ProductVersionKey = SOFTWARE\Microsoft\DataAccess
: ProductVersionValue = FullInstallVer
: InstanceName = MDAC
: CheckInUseFiles = 1
: EULAFile = MDACEULA.RTF
: EULAType = rtf
: SupportsTS = 1
: SupportsMUI = 0
: CheckForDiskSpace = 1
: ValidOs = 4294967295
I find it starnge that the install is trying to use MDAC 2.7 when I
currently have MDAC 2.8 SP1 installed on my machine (I verified this through
the MDAC compcheck app).
Anyone have any ideas as to what is going on?
PS Sorry for the long message
ThanksI also found this error in the dahotfix.log
"
[05:03:12]: An error occurred while setup was trying to verify the versi
on
of Microsoft Data Access Components current installed on the machine.
Either the version currently installed does not match the version of this
hotfix package, or setup was unable to determine the version currently
installed.
["
"John Rydenbark" wrote:

> Hi
> I am trying to instal MSDE 2000 on a Windows XP Pro SP2 machine. I type in
> ...
> "Setup.exe /qb+ INSTANCENAME=NetSDK DISABLENETWORKPROTOCOLS=1 SAPWD=<YOUR
SA
> PASSWORD>" at the command prompt and the MSDE setup begins to take place.
At
> the nearly the end of the install, I get a pop-up dialog stating the the
> instalation failed.
> I checked setupapi.log file under C:\winnt and the follwoing error was in
> their...
> "
> [2005/01/03 21:29:08 2672.1]
> #-199 Executing "C:\Documents and Settings\Owner\Local
> Settings\Temp\IXP000.TMP\dasetup.exe" with command line: /Q /N
> #E077 Could not locate a non-empty section [DefaultInstall] when calcu
lating
> disk space in "C:\Documents and Settings\Owner\Local
> Settings\Temp\IXP000.TMP\noop.inf". Error 0xe0000102: The required line wa
s
> not found in the INF."
> Anyone have any ideas as to what the above means. Also, I checked the
> dasetup.log file that was created when attempting to install MSDE and I
> noticed the following...
> : ****************************************
> : * Beginning of Install *
> : ****************************************
> Starting Install: Current Date/Time (U.S. Local Time): 01/03/2005 : 21:29:
07
> Path: C:\WINNT;C:\WINNT\system32;
> Localization: Machine Locale set to: English_United States.1252
> Command Line Parameters:
> Suppress Reboot: 0
> Quiet/Silent Mode: 1
> Logging Level: 3
> INI File: dasetup.ini
> Windows Directory: C:\WINNT
> Progress: Loading Resource Library.
> Progress: Parsing INI File.
> *************************:
> ** Begin INI File Dump **:
> *************************:
> Ini Section: General
> : ProductName = Microsoft Data Access Components 2.7
> : ProductBuild = 2.71.9040.2
> : ProductUrl = http://www.microsoft.com/data
> : ProductVersionKey = SOFTWARE\Microsoft\DataAccess
> : ProductVersionValue = FullInstallVer
> : InstanceName = MDAC
> : CheckInUseFiles = 1
> : EULAFile = MDACEULA.RTF
> : EULAType = rtf
> : SupportsTS = 1
> : SupportsMUI = 0
> : CheckForDiskSpace = 1
> : ValidOs = 4294967295
> I find it starnge that the install is trying to use MDAC 2.7 when I
> currently have MDAC 2.8 SP1 installed on my machine (I verified this throu
gh
> the MDAC compcheck app).
> Anyone have any ideas as to what is going on?
> PS Sorry for the long message
> Thanks
>

MSDE Installation failure in Windows XP

Dear all,
during an MSDE installation by a client on windows XP SP1, as well as SP2,
occurs the following error:
"InstallSQLAgentSecurity failed (IP45,LocalSystem,87)"
After this error message in the log file, one could see that the entire
installation is rolled back. The user doesn't get any message.
The server service is on.
On a windows XP SP1 by me the same installation process works fine. The
specified client has normally high security standards and it's the first time
that an MSDE is installed by them.
Any help would be highly appreciated!
Thanks in advance for the help,
Avi Joshua
CRM systems consultant
LOGO consult AG
Head office
Enzianstrasse 4a
82319 Starnberg am See
Germany
mailto:avi@.logo-consult.de
tel +49 (0700) 100 55 100
Hi Avi,
Check that Sharing is enabled on the system.
HTH,
Greg Low [MVP]
MSDE Manager SQL Tools
www.whitebearconsulting.com
"Avi Joshua" <Avi Joshua@.discussions.microsoft.com> wrote in message
news:CFA84BD4-18A8-4AC4-8AEE-B065ED28E77E@.microsoft.com...
> Dear all,
> during an MSDE installation by a client on windows XP SP1, as well as SP2,
> occurs the following error:
> "InstallSQLAgentSecurity failed (IP45,LocalSystem,87)"
> After this error message in the log file, one could see that the entire
> installation is rolled back. The user doesn't get any message.
> The server service is on.
> On a windows XP SP1 by me the same installation process works fine. The
> specified client has normally high security standards and it's the first
time
> that an MSDE is installed by them.
> Any help would be highly appreciated!
> Thanks in advance for the help,
> Avi Joshua
> CRM systems consultant
> LOGO consult AG
> Head office
> Enzianstrasse 4a
> 82319 Starnberg am See
> Germany
> mailto:avi@.logo-consult.de
> tel +49 (0700) 100 55 100
>
|||Thanks, Greg!
The file and printer sharing component was not installed on the computer.
Have a pleasant weekend,
Avi

MSDE Installation failure

Hi,
I've downloaded MSDE 2000 R1 from Internet. Tried to install on my PC with
running on Windows XP Pro with SP2.
When everytime i runned the Setup.exe, it will prompt for "A Strong SA
password is required for security reasons. Please use SAPWD switch to supply
the same. Refer to readme for more details. Setup will now exit".
Everyone know about this ? anyway to proceed the installation ?
Thank you
You need to either supply commandline arguments, or edit the empty
setup.ini file and supply them as options there. Go to
msdn.microsoft.com and search for articles like: installing MSDE.
-nick
On Tue, 3 May 2005 01:08:05 -0700, "CK" <CK@.discussions.microsoft.com>
wrote:

>Hi,
>I've downloaded MSDE 2000 R1 from Internet. Tried to install on my PC with
>running on Windows XP Pro with SP2.
>When everytime i runned the Setup.exe, it will prompt for "A Strong SA
>password is required for security reasons. Please use SAPWD switch to supply
>the same. Refer to readme for more details. Setup will now exit".
>Everyone know about this ? anyway to proceed the installation ?
>Thank you
|||hi,
CK wrote:
> Hi,
> I've downloaded MSDE 2000 R1 from Internet. Tried to install on my PC
> with running on Windows XP Pro with SP2.
> When everytime i runned the Setup.exe, it will prompt for "A Strong SA
> password is required for security reasons. Please use SAPWD switch to
> supply the same. Refer to readme for more details. Setup will now
> exit".
> Everyone know about this ? anyway to proceed the installation ?
> Thank you
please have a look at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for all setup parameter...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.11.1 - DbaMgr ver 0.57.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply