Having a real problem installing SP4 on MSDE. I've read the notes that come
along with the install files and I've tried most every combination that
makes sense in the command line. Here's just one example:
setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
UPGRADEPWD=apasswoord
DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
It's the default instance. The setup command simply returns immediately, no
log created etc.
I'm at a loss to know what's wrong here.
Thanks for any input you can offer.
jim
I believe I have fixed this, appears to be in the comand line arguments. I
couldn't get them to work as in the supplied examples, but still haven't
solved the original problem, which is my other post -'Dist Query Problem'
"Jim Bailey" <jimREMOVETHIS@.ANDTHISjbaileygroup.com> wrote in message
news:3uSve.169016$IO.100652@.tornado.tampabay.rr.co m...
> Having a real problem installing SP4 on MSDE. I've read the notes that
come
> along with the install files and I've tried most every combination that
> makes sense in the command line. Here's just one example:
> setup /upgradesp sqlrun SECURITYMODE=sql UPGRADEUSER=sa
> UPGRADEPWD=apasswoord
> DISABLENETWORKPROTOCOLS=0 /L*v c:\mylog.log
> It's the default instance. The setup command simply returns immediately,
no
> log created etc.
> I'm at a loss to know what's wrong here.
> Thanks for any input you can offer.
> jim
>
Showing posts with label ive. Show all posts
Showing posts with label ive. Show all posts
Friday, March 30, 2012
Wednesday, March 28, 2012
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
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
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 Setup fails...
I don't think I've ever worked so long and tried so many suggestions,
recommendations and followed KB article processes in my life with so little
success -- in fact, none -- and so intransigent a set of symptoms. I hope
that there is someone here that will be able to help me.
To set the hardware scene: I have a 3 year old Sony Vaio with P4 HT 3.2
ghz, 1GB ram, 560 GB of hard drive and a new ATI video card. It has had
lots of software installed and removed over the last couple of years. My
wife has an almost identical eMachine that is 9 months old and is still in
the exact state that it was when it came out of the box. Both run XP Pro
sp2.
The problem: I purchased a copy of Pinnacle Studio Plus vers 10 video
editing software. With it I got also their media manager which uses MSDE.
I have not been able to successfully install that software. It gets to the
exact same spot (says that it is 5 sec from finishing the MSDE setup) and
then quits with an error every time. I've tried manually installing MSDE
and the symptoms and results are exactly the same -- each and every time.
I've verified that File & print sharing are installed and enabled. I've
verified that my policy is to install unsigned drivers. I've cleaned out
the registry of failed attempt entries. I've removed all of the file
directories. I've run the MDAC repair that I found in another post here.
I've got the setup logs and the error logs, including the verbose log from
my manual attempt but it has not helped me.
Nothing has made one single iota of a difference. Kinda like trying to
teach a pig to tell time -- won't work, just irritates the pig and
frustrates you.
Now, here's the kicker: I tried the install on my wife's machine and it
went perfectly. Installed without a hitch.
The logs (setup & error) are similar, but as you might guess, differ in a
couple of key respects. I have put the successful setup log and error log
into a spreadsheet along with the unsuccessful setup log and error log.
I've matched the common entries from both on the same row and hi-lighted the
differences.
If there is someone here that can help me I can provide this file, or
anything else related that you might need, via e-mail.
Can someone give me a hand with this?
Frustrated in Seattle
I ran the verification software and it showed that I had all MDAC 2.8 sp1
components installed with no differences/issues detected.
I noticed that I don't have a service, much less one running, for MSSQL. So
I installed MS SQL Server 2005 Express. It installed perfectly and
afterwards the service was there and running. However, MSDE still wouldn't
install -- exact same behavior.
I did find another log [extension was ".out"] and it also is pointing to an
ODBC problem. Nowhere in any instructions does it say anything about
setting up any ODBC connections so I suspect this may be a red herring. But
I did put it right after this note for reference.
I clearly don't know what I'm talking about but I'm getting the sense that I
don't really need SQL Server installed because MSDE is supposed to be some
sort of "light" version for the desktop. So the fact that MSDE is not
installing may account for why there was no MSSQL service before I installed
SQL Server 2005 Express.
Btw, I've verified that File & Print sharing is enabled and that unsigned
drivers are set to install automatically -- two things that MS KB identified
as potential related issues. I've gone through and completely removed all
registry vestiges of the product and the file directories and started over
from scratch. The result was exactly the same.
The first error that it encounters is when it tries to configure the new
server it's installing and it's an unrecoverable error. I've included the
log entries for that as well.
Still looking for help. Sigh...
Howard
################################################## #######################
====SQL Server Error Log====
2006-01-26 20:40:34.31 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
2006-01-26 20:40:34.32 server Copyright (C) 1988-2002 Microsoft Corporation.
2006-01-26 20:40:34.32 server All rights reserved.
2006-01-26 20:40:34.32 server Server Process ID is 2460.
2006-01-26 20:40:34.32 server Logging SQL Server messages in file
'C:\Program Files\Pinnacle\MediaServer\Microsoft SQL
Server\MSSQL$PINNACLESYS\LOG\ERRORLOG'.
2006-01-26 20:40:34.34 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2006-01-26 20:40:34.49 server SQL Server configured for thread mode
processing.
2006-01-26 20:40:34.49 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2006-01-26 20:40:34.53 spid3 Warning ******************
2006-01-26 20:40:34.53 spid3 SQL Server started in single user mode. Updates
allowed to system catalogs.
2006-01-26 20:40:34.68 spid3 Starting up database 'master'.
2006-01-26 20:40:35.15 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-01-26 20:40:35.17 spid5 Starting up database 'model'.
2006-01-26 20:40:35.28 spid3 Server name is 'OFFICE\PINNACLESYS'.
2006-01-26 20:40:35.28 spid3 Skipping startup of clean database id 5
2006-01-26 20:40:35.28 spid3 Skipping startup of clean database id 6
2006-01-26 20:40:35.28 spid3 Starting up database 'msdb'.
2006-01-26 20:40:35.28 server SQL server listening on 192.168.1.100: 1465.
2006-01-26 20:40:35.28 server SQL server listening on 127.0.0.1: 1465.
2006-01-26 20:40:35.28 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-01-26 20:40:35.28 server SQL Server is ready for client connections
2006-01-26 20:40:35.78 spid5 Clearing tempdb database.
2006-01-26 20:40:36.84 spid5 Starting up database 'tempdb'.
2006-01-26 20:40:37.03 spid3 Recovery complete.
2006-01-26 20:40:37.03 spid3 SQL global counter collection task is created.
2006-01-26 20:40:37.12 spid3 Warning: override, autoexec procedures skipped.
2006-01-26 20:40:44.71 spid3 SQL Server is terminating due to 'stop' request
from Service Control Manager.
================================================== =====================
====Verbose MSDE Install Log=====
Starting custom action SkuIt
MSI (s) (A4:A4) [22:15:37:640]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (A4:A4) [22:15:37:640]: Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (A4:A0) [22:15:37:656]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI3F.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Howard\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Howard\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q
"SQL_Latin1_General_CP1_CI_AS""
MSI (c) (54:98) [22:16:04:703]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (A4!20) [22:16:08:500]: Product: Microsoft SQL Server Desktop
Engine -- Setup failed to configure the server. Refer to the server error
logs and setup error logs for more information.
Action ended 22:16:08: InstallFinalize. Return value 3.
################################################## ##########################===Configure.out===Start ing Service ...SQL_Latin1_General_CP1_CI_AS -m -Q -T4022 -T3659Connecting to Server ...driver={sql server};server=OFFICE\PINNACLESYS;UID=sa;PWD=;data base=
master[Microsoft][ODBC Driver Manager] Data source name not found and no defaultdriver specifieddriver={sql server};server=OFFICE\PINNACLESYS;UID=sa;PWD=;data base=master[Microsoft][ODBC Driver Manager] Data source name not found and no defaultdriver speci
fieddriver={sql server};server=OFFICE\PINNACLESYS;UID=sa;PWD=;data base=master[Microsoft][ODBC Driver Manager] Data source name not found and no defaultdriver specifiedSQL Server configuration failed.########################################### #############
####################
|||hi Howard,
Howard Woodard wrote:
> MSI (s) (A4!20) [22:16:08:500]: Product: Microsoft SQL Server Desktop
> Engine -- Setup failed to configure the server. Refer to the server
> error logs and setup error logs for more information.
> Action ended 22:16:08: InstallFinalize. Return value 3.
this error is usually related to
http://support.microsoft.com/default...9&Product=sql,
but I do think you already noticed and tried it's advices...
another non indicated cause I'm aware of is related to MDAC stack
corruption, as you alredy reported, tha could be fixed as reported in
http://www.macropool.com/en/download/mdac_xp_sp2.html.. but it seems to me
you already checked that...
other causes... to the besto of my knowledge, unfortunately I can not help
further...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea. There is one more thing that you can help me with if you
would. It appears that there is some expectation that I would already have
a Microsoft Sql Server directory under the Program Files directory and
possibly even an SQLSERVER service running. Is that right? I have neither
and see no option for installing it from my XP Pro CD.
Can you confirm what I should be looking for please?
Tia,
Howard
==========================================
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:44eh20F1qf9sU1@.individual.net...
> hi Howard,
> Howard Woodard wrote:
> this error is usually related to
> http://support.microsoft.com/default...9&Product=sql,
> but I do think you already noticed and tried it's advices...
> another non indicated cause I'm aware of is related to MDAC stack
> corruption, as you alredy reported, tha could be fixed as reported in
> http://www.macropool.com/en/download/mdac_xp_sp2.html.. but it seems to me
> you already checked that...
> other causes... to the besto of my knowledge, unfortunately I can not help
> further...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Never mind. I got this figured out. MSDE installs from the XP Office CD,
not from the XP Pro CD.
I reinstalled it and then my video editing software was able to install the
instance that it needed.
Thanks for helping me.
==============================
"Howard Woodard" <woodard@.msn.com> wrote in message
news:uqrrZUGKGHA.740@.TK2MSFTNGP12.phx.gbl...
> Thanks Andrea. There is one more thing that you can help me with if you
> would. It appears that there is some expectation that I would already
> have a Microsoft Sql Server directory under the Program Files directory
> and possibly even an SQLSERVER service running. Is that right? I have
> neither and see no option for installing it from my XP Pro CD.
> Can you confirm what I should be looking for please?
> Tia,
> Howard
> ==========================================
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:44eh20F1qf9sU1@.individual.net...
>
sql
recommendations and followed KB article processes in my life with so little
success -- in fact, none -- and so intransigent a set of symptoms. I hope
that there is someone here that will be able to help me.
To set the hardware scene: I have a 3 year old Sony Vaio with P4 HT 3.2
ghz, 1GB ram, 560 GB of hard drive and a new ATI video card. It has had
lots of software installed and removed over the last couple of years. My
wife has an almost identical eMachine that is 9 months old and is still in
the exact state that it was when it came out of the box. Both run XP Pro
sp2.
The problem: I purchased a copy of Pinnacle Studio Plus vers 10 video
editing software. With it I got also their media manager which uses MSDE.
I have not been able to successfully install that software. It gets to the
exact same spot (says that it is 5 sec from finishing the MSDE setup) and
then quits with an error every time. I've tried manually installing MSDE
and the symptoms and results are exactly the same -- each and every time.
I've verified that File & print sharing are installed and enabled. I've
verified that my policy is to install unsigned drivers. I've cleaned out
the registry of failed attempt entries. I've removed all of the file
directories. I've run the MDAC repair that I found in another post here.
I've got the setup logs and the error logs, including the verbose log from
my manual attempt but it has not helped me.
Nothing has made one single iota of a difference. Kinda like trying to
teach a pig to tell time -- won't work, just irritates the pig and
frustrates you.
Now, here's the kicker: I tried the install on my wife's machine and it
went perfectly. Installed without a hitch.
The logs (setup & error) are similar, but as you might guess, differ in a
couple of key respects. I have put the successful setup log and error log
into a spreadsheet along with the unsuccessful setup log and error log.
I've matched the common entries from both on the same row and hi-lighted the
differences.
If there is someone here that can help me I can provide this file, or
anything else related that you might need, via e-mail.
Can someone give me a hand with this?
Frustrated in Seattle
I ran the verification software and it showed that I had all MDAC 2.8 sp1
components installed with no differences/issues detected.
I noticed that I don't have a service, much less one running, for MSSQL. So
I installed MS SQL Server 2005 Express. It installed perfectly and
afterwards the service was there and running. However, MSDE still wouldn't
install -- exact same behavior.
I did find another log [extension was ".out"] and it also is pointing to an
ODBC problem. Nowhere in any instructions does it say anything about
setting up any ODBC connections so I suspect this may be a red herring. But
I did put it right after this note for reference.
I clearly don't know what I'm talking about but I'm getting the sense that I
don't really need SQL Server installed because MSDE is supposed to be some
sort of "light" version for the desktop. So the fact that MSDE is not
installing may account for why there was no MSSQL service before I installed
SQL Server 2005 Express.
Btw, I've verified that File & Print sharing is enabled and that unsigned
drivers are set to install automatically -- two things that MS KB identified
as potential related issues. I've gone through and completely removed all
registry vestiges of the product and the file directories and started over
from scratch. The result was exactly the same.
The first error that it encounters is when it tries to configure the new
server it's installing and it's an unrecoverable error. I've included the
log entries for that as well.
Still looking for help. Sigh...
Howard
################################################## #######################
====SQL Server Error Log====
2006-01-26 20:40:34.31 server Microsoft SQL Server 2000 - 8.00.760 (Intel
X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.1 (Build 2600: Service Pack 2)
2006-01-26 20:40:34.32 server Copyright (C) 1988-2002 Microsoft Corporation.
2006-01-26 20:40:34.32 server All rights reserved.
2006-01-26 20:40:34.32 server Server Process ID is 2460.
2006-01-26 20:40:34.32 server Logging SQL Server messages in file
'C:\Program Files\Pinnacle\MediaServer\Microsoft SQL
Server\MSSQL$PINNACLESYS\LOG\ERRORLOG'.
2006-01-26 20:40:34.34 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2006-01-26 20:40:34.49 server SQL Server configured for thread mode
processing.
2006-01-26 20:40:34.49 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2006-01-26 20:40:34.53 spid3 Warning ******************
2006-01-26 20:40:34.53 spid3 SQL Server started in single user mode. Updates
allowed to system catalogs.
2006-01-26 20:40:34.68 spid3 Starting up database 'master'.
2006-01-26 20:40:35.15 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-01-26 20:40:35.17 spid5 Starting up database 'model'.
2006-01-26 20:40:35.28 spid3 Server name is 'OFFICE\PINNACLESYS'.
2006-01-26 20:40:35.28 spid3 Skipping startup of clean database id 5
2006-01-26 20:40:35.28 spid3 Skipping startup of clean database id 6
2006-01-26 20:40:35.28 spid3 Starting up database 'msdb'.
2006-01-26 20:40:35.28 server SQL server listening on 192.168.1.100: 1465.
2006-01-26 20:40:35.28 server SQL server listening on 127.0.0.1: 1465.
2006-01-26 20:40:35.28 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-01-26 20:40:35.28 server SQL Server is ready for client connections
2006-01-26 20:40:35.78 spid5 Clearing tempdb database.
2006-01-26 20:40:36.84 spid5 Starting up database 'tempdb'.
2006-01-26 20:40:37.03 spid3 Recovery complete.
2006-01-26 20:40:37.03 spid3 SQL global counter collection task is created.
2006-01-26 20:40:37.12 spid3 Warning: override, autoexec procedures skipped.
2006-01-26 20:40:44.71 spid3 SQL Server is terminating due to 'stop' request
from Service Control Manager.
================================================== =====================
====Verbose MSDE Install Log=====
Starting custom action SkuIt
MSI (s) (A4:A4) [22:15:37:640]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (A4:A4) [22:15:37:640]: Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (A4:A0) [22:15:37:656]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI3F.tmp, Entrypoint: ConfigServer
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\Howard\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\Howard\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action ConfigServer
Executing "C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\cnfgsvr.exe -V 1 -M 1 -U sa -I "MSSQLSERVER" -Q
"SQL_Latin1_General_CP1_CI_AS""
MSI (c) (54:98) [22:16:04:703]: Font created. Charset: Req=0, Ret=0, Font:
Req=MS Shell Dlg, Ret=MS Shell Dlg
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (A4!20) [22:16:08:500]: Product: Microsoft SQL Server Desktop
Engine -- Setup failed to configure the server. Refer to the server error
logs and setup error logs for more information.
Action ended 22:16:08: InstallFinalize. Return value 3.
################################################## ##########################===Configure.out===Start ing Service ...SQL_Latin1_General_CP1_CI_AS -m -Q -T4022 -T3659Connecting to Server ...driver={sql server};server=OFFICE\PINNACLESYS;UID=sa;PWD=;data base=
master[Microsoft][ODBC Driver Manager] Data source name not found and no defaultdriver specifieddriver={sql server};server=OFFICE\PINNACLESYS;UID=sa;PWD=;data base=master[Microsoft][ODBC Driver Manager] Data source name not found and no defaultdriver speci
fieddriver={sql server};server=OFFICE\PINNACLESYS;UID=sa;PWD=;data base=master[Microsoft][ODBC Driver Manager] Data source name not found and no defaultdriver specifiedSQL Server configuration failed.########################################### #############
####################
|||hi Howard,
Howard Woodard wrote:
> MSI (s) (A4!20) [22:16:08:500]: Product: Microsoft SQL Server Desktop
> Engine -- Setup failed to configure the server. Refer to the server
> error logs and setup error logs for more information.
> Action ended 22:16:08: InstallFinalize. Return value 3.
this error is usually related to
http://support.microsoft.com/default...9&Product=sql,
but I do think you already noticed and tried it's advices...
another non indicated cause I'm aware of is related to MDAC stack
corruption, as you alredy reported, tha could be fixed as reported in
http://www.macropool.com/en/download/mdac_xp_sp2.html.. but it seems to me
you already checked that...
other causes... to the besto of my knowledge, unfortunately I can not help
further...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Thanks Andrea. There is one more thing that you can help me with if you
would. It appears that there is some expectation that I would already have
a Microsoft Sql Server directory under the Program Files directory and
possibly even an SQLSERVER service running. Is that right? I have neither
and see no option for installing it from my XP Pro CD.
Can you confirm what I should be looking for please?
Tia,
Howard
==========================================
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:44eh20F1qf9sU1@.individual.net...
> hi Howard,
> Howard Woodard wrote:
> this error is usually related to
> http://support.microsoft.com/default...9&Product=sql,
> but I do think you already noticed and tried it's advices...
> another non indicated cause I'm aware of is related to MDAC stack
> corruption, as you alredy reported, tha could be fixed as reported in
> http://www.macropool.com/en/download/mdac_xp_sp2.html.. but it seems to me
> you already checked that...
> other causes... to the besto of my knowledge, unfortunately I can not help
> further...
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
|||Never mind. I got this figured out. MSDE installs from the XP Office CD,
not from the XP Pro CD.
I reinstalled it and then my video editing software was able to install the
instance that it needed.
Thanks for helping me.
==============================
"Howard Woodard" <woodard@.msn.com> wrote in message
news:uqrrZUGKGHA.740@.TK2MSFTNGP12.phx.gbl...
> Thanks Andrea. There is one more thing that you can help me with if you
> would. It appears that there is some expectation that I would already
> have a Microsoft Sql Server directory under the Program Files directory
> and possibly even an SQLSERVER service running. Is that right? I have
> neither and see no option for installing it from my XP Pro CD.
> Can you confirm what I should be looking for please?
> Tia,
> Howard
> ==========================================
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:44eh20F1qf9sU1@.individual.net...
>
sql
Monday, March 26, 2012
MSDE Security (aka users looking at my apps database)
Is there a way to secure a database on MSDE so that my users cannot be
poking around my applications database? I've been reading up on it and see
that MSDE installs with a mixed security mode.
Does that mean if I secure my database with sql security someone who is an
admin on the machine can look at my database regardless of what I set?
I am concerned that my users (and competition) will try to hack into my
instance and steal my data & data structures so I'm trying to figure out
how I can prevent that. I understand I can encrypt my stored procedure at
least I hope that is still the case with MSDE.
Any thoughts?
Thanks.
This is a desktop app and not a web app btw.
hi Jason,
"Jason" <yo@.yo.com> ha scritto nel messaggio
news:%234bvqLoeEHA.3016@.tk2msftngp13.phx.gbl...
> Is there a way to secure a database on MSDE so that my users cannot be
> poking around my applications database? I've been reading up on it and see
> that MSDE installs with a mixed security mode.
> Does that mean if I secure my database with sql security someone who is an
> admin on the machine can look at my database regardless of what I set?
> I am concerned that my users (and competition) will try to hack into my
> instance and steal my data & data structures so I'm trying to figure out
> how I can prevent that. I understand I can encrypt my stored procedure at
> least I hope that is still the case with MSDE.
> Any thoughts?
> Thanks.
> This is a desktop app and not a web app btw.
you can only protect stored procedures, views and user define function with
WITH ENCRYPTION in order to hide their text, but for base table you are out
of luck... there's actually non way for preventing sysadmins role members to
dig into your metaschema...
as regard data, that can only be encripted using third parties tools like
http://www.activecrypt.com/index.htm or tools like that
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
|||Hello,
It is also possible to use SQL autentification, then create only one login
that the user doesn't know.
After that, your application connect as the login you 've just created. (for
example Log = marc PWD = marc)
In you database, you make a login table. This table contain the login of the
user and his password, and your application will test this table to see if
the user can connect. With this method you can even forbid a part of the
application or a time to connect ... easily.
For example UID Andre PWD Andre.
After that, your user will enter the login and password to your application
(Andre/ Andre).
your application connect as marc, see if Andre can login and if Andre can
login, your application can work with the user name marc with the database
(and show the user the login Andre)
So your user will never be able to work on the database as his login is not
a database login
Marc Allard
"Jason" <yo@.yo.com> a crit dans le message de
news:%234bvqLoeEHA.3016@.tk2msftngp13.phx.gbl...
> Is there a way to secure a database on MSDE so that my users cannot be
> poking around my applications database? I've been reading up on it and see
> that MSDE installs with a mixed security mode.
> Does that mean if I secure my database with sql security someone who is an
> admin on the machine can look at my database regardless of what I set?
> I am concerned that my users (and competition) will try to hack into my
> instance and steal my data & data structures so I'm trying to figure out
> how I can prevent that. I understand I can encrypt my stored procedure at
> least I hope that is still the case with MSDE.
> Any thoughts?
> Thanks.
>
> This is a desktop app and not a web app btw.
>
|||The only way you can lock the data down is to encrypt it. If a user has
Local Admin rights in the OS (NT/2K/XP), then they can see the data anyway,
irrespective of SQL Auth as NT Auth is always available.
Administrator ALWAYS gets to the data!
On Fri, 6 Aug 2004 11:05:29 +0200, Allcomp wrote:
[vbcol=seagreen]
> Hello,
> It is also possible to use SQL autentification, then create only one login
> that the user doesn't know.
> After that, your application connect as the login you 've just created. (for
> example Log = marc PWD = marc)
> In you database, you make a login table. This table contain the login of the
> user and his password, and your application will test this table to see if
> the user can connect. With this method you can even forbid a part of the
> application or a time to connect ... easily.
> For example UID Andre PWD Andre.
> After that, your user will enter the login and password to your application
> (Andre/ Andre).
> your application connect as marc, see if Andre can login and if Andre can
> login, your application can work with the user name marc with the database
> (and show the user the login Andre)
> So your user will never be able to work on the database as his login is not
> a database login
> Marc Allard
>
> "Jason" <yo@.yo.com> a crit dans le message de
> news:%234bvqLoeEHA.3016@.tk2msftngp13.phx.gbl...
|||Hello,
I didn't know it was possible to connect as Administrator in a sql server
when the installation was mado to allow only SQL autentification. How can
you make it?
Thank you
Marc Allard
"Paul Buxton" <psb@.NOSPAMspireite.demon.co.uk> a crit dans le message de
news:1opgizeso0jib$.ywf1zot73zdg.dlg@.40tude.net...
> The only way you can lock the data down is to encrypt it. If a user has
> Local Admin rights in the OS (NT/2K/XP), then they can see the data
anyway,[vbcol=seagreen]
> irrespective of SQL Auth as NT Auth is always available.
> Administrator ALWAYS gets to the data!
> On Fri, 6 Aug 2004 11:05:29 +0200, Allcomp wrote:
login[vbcol=seagreen]
(for[vbcol=seagreen]
the[vbcol=seagreen]
if[vbcol=seagreen]
application[vbcol=seagreen]
can[vbcol=seagreen]
database[vbcol=seagreen]
not[vbcol=seagreen]
see[vbcol=seagreen]
an[vbcol=seagreen]
out[vbcol=seagreen]
at[vbcol=seagreen]
|||hi,
"Allcomp" <fa097770@.nospam.skynet.be> ha scritto nel messaggio
news:41136323$0$296$ba620e4c@.news.skynet.be...
> Hello,
> I didn't know it was possible to connect as Administrator in a sql server
> when the installation was mado to allow only SQL autentification. How can
> you make it?
just log in in Windows as a member of sysadmins; sysadmis are member of
Builtin\Administrator SQL Server role, which has administrative privileges
by default...
the method you previously exposed only prevents user of YOUR application not
to access that data, but using ad-hoc query tools like QA, oSql or simply
Visual Data Manager (VB3 to VB6 <g>) an administrator can perform whatever
activity...
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
|||Only One JASON, FORGET IT.
I have been called in more than once to untangle all sorts of developer
installed security, I do it and will continue to do it.
Developers who think that business data should be locked up from the
Business should be locked up themselves. If your data is proprietary,
then I suggest you create your own encrypted storage system! But give up on
trying to lock the rightful owners of data out from it by denying them
access to the database.
Your schema etc. Might be your work, but locking out legitimate uses of
the data is in my opinion about as quick a way to get your application
dumped as you can get. Companies expect to be able to throw a copy of
Crystal Reports onto a machine and interogate the database for the
information that they want, in the manner that they want it, when they want
it.
As foir competitors using your schema in their own products, you must be
joking! They might however write conversion routines to 'upgrade' from your
product. This is a fairly normal business practice.
You sound like Apple complaining about Real Networks, or an IBM salesman
from the 1970s, telling the customer that MS-Dos on a compatible PC is just
not as good as an IBM PC-XT with PC-Dos for running Lotus 1-2-3
Matt
|||hi Matt,
"Unicorn" <unicorn@.somewhere.com> ha scritto nel messaggio
news:epy96HEfEHA.2604@.TK2MSFTNGP12.phx.gbl...
> Only One JASON, FORGET IT.
> I have been called in more than once to untangle all sorts of developer
> installed security, I do it and will continue to do it.
> Developers who think that business data should be locked up from the
> Business should be locked up themselves. If your data is proprietary,
> then I suggest you create your own encrypted storage system! But give up
on
> trying to lock the rightful owners of data out from it by denying them
> access to the database.
not to start a flame, but just a consideration...
I think it really depends... if you "sell" data, that's to say an aggregated
and/or particular kind of sensible data, perhaps having it not accessible to
external application but your(s), could be a legitimated pray for a
particular protection system, and perhaps external encryption is a way to go
for, as you already pointed out... perhaps not the best as it will be not
integrated.. but acceptable...
the same is true for sensible code you provide in form of stored
procedures/udf/views...
let's think about a genious tool, RAC by SQL Server MVP Thanh Ngo (AKA OJ)..
my understanding is it provides a set of stored procedures to manipulate
data, with unique features like CROSSTAB rotations and so on... this is
valuable code and think is provided as encrypted code... as it should
but you actually have no way to protect your metaschema(s) the same way...
even if SQL Server encryption has been defeated... I do personally think
this could be a valuable feature in some scenario...
> Your schema etc. Might be your work, but locking out legitimate uses of
> the data is in my opinion about as quick a way to get your application
> dumped as you can get. Companies expect to be able to throw a copy of
> Crystal Reports onto a machine and interogate the database for the
> information that they want, in the manner that they want it, when they
want
> it.
this could violate certain EULAs and/or rules, both private and/or
legislative...
recently I've been asked to buy a mailing for german (potential)
customers... the selling company provided a well defined license for 1 use,
n uses of the same data... don't know what kind of database they would
provide as our choice went to mailing labels directly, just for one shot...
but this scenario certainly does not grant you the possibility for multi
server analysis and or use...
another issue... think to privacy protection for sensible data... medical
data... there are both european and USA (as other countries too..) acts that
state and (strictly) discipline the use of this kind of data...
a recent article by Sean Maloney on SQL Server Magazine
(http://www.winnetmag.com/SQLServer/A...731/42731.html for
subscribers only) presents a way to protect data from unlegitimated users
with row level security granularity.. but if you manually bypass that kind
of security (which you can, as a syasdmin) you are elegible for legal
repercussions...
> As foir competitors using your schema in their own products, you must be
> joking! They might however write conversion routines to 'upgrade' from
your
> product. This is a fairly normal business practice.
>
agree =;-D
again... not to flame but just my 2 (euro)cents
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
|||Thank you for your answer
Marc Allard
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> a crit dans le message de
news:2nhjgsFud2mU1@.uni-berlin.de...[vbcol=seagreen]
> hi,
> "Allcomp" <fa097770@.nospam.skynet.be> ha scritto nel messaggio
> news:41136323$0$296$ba620e4c@.news.skynet.be...
server[vbcol=seagreen]
can
> just log in in Windows as a member of sysadmins; sysadmis are member of
> Builtin\Administrator SQL Server role, which has administrative privileges
> by default...
> the method you previously exposed only prevents user of YOUR application
not
> to access that data, but using ad-hoc query tools like QA, oSql or simply
> Visual Data Manager (VB3 to VB6 <g>) an administrator can perform whatever
> activity...
> --
> 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
>
|||A possible solution may be to use dbLockdown. It will encrypt ALL (or
selected) database object scripts for stored procedures, triggers, user
defined functions and views in your MSDE database using the WITH
ENCRYPTION clause. The tool will also automatically archive the script
source so you can restore it again at any time. Check out
http://www.ecatenate.com/dblockdown_product_info.html
Regards, Simon
"Jason" <yo@.yo.com> wrote in message news:<#4bvqLoeEHA.3016@.tk2msftngp13.phx.gbl>...
> Is there a way to secure a database on MSDE so that my users cannot be
> poking around my applications database? I've been reading up on it and see
> that MSDE installs with a mixed security mode.
> Does that mean if I secure my database with sql security someone who is an
> admin on the machine can look at my database regardless of what I set?
> I am concerned that my users (and competition) will try to hack into my
> instance and steal my data & data structures so I'm trying to figure out
> how I can prevent that. I understand I can encrypt my stored procedure at
> least I hope that is still the case with MSDE.
> Any thoughts?
> Thanks.
>
> This is a desktop app and not a web app btw.
poking around my applications database? I've been reading up on it and see
that MSDE installs with a mixed security mode.
Does that mean if I secure my database with sql security someone who is an
admin on the machine can look at my database regardless of what I set?
I am concerned that my users (and competition) will try to hack into my
instance and steal my data & data structures so I'm trying to figure out
how I can prevent that. I understand I can encrypt my stored procedure at
least I hope that is still the case with MSDE.
Any thoughts?
Thanks.
This is a desktop app and not a web app btw.
hi Jason,
"Jason" <yo@.yo.com> ha scritto nel messaggio
news:%234bvqLoeEHA.3016@.tk2msftngp13.phx.gbl...
> Is there a way to secure a database on MSDE so that my users cannot be
> poking around my applications database? I've been reading up on it and see
> that MSDE installs with a mixed security mode.
> Does that mean if I secure my database with sql security someone who is an
> admin on the machine can look at my database regardless of what I set?
> I am concerned that my users (and competition) will try to hack into my
> instance and steal my data & data structures so I'm trying to figure out
> how I can prevent that. I understand I can encrypt my stored procedure at
> least I hope that is still the case with MSDE.
> Any thoughts?
> Thanks.
> This is a desktop app and not a web app btw.
you can only protect stored procedures, views and user define function with
WITH ENCRYPTION in order to hide their text, but for base table you are out
of luck... there's actually non way for preventing sysadmins role members to
dig into your metaschema...
as regard data, that can only be encripted using third parties tools like
http://www.activecrypt.com/index.htm or tools like that
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
|||Hello,
It is also possible to use SQL autentification, then create only one login
that the user doesn't know.
After that, your application connect as the login you 've just created. (for
example Log = marc PWD = marc)
In you database, you make a login table. This table contain the login of the
user and his password, and your application will test this table to see if
the user can connect. With this method you can even forbid a part of the
application or a time to connect ... easily.
For example UID Andre PWD Andre.
After that, your user will enter the login and password to your application
(Andre/ Andre).
your application connect as marc, see if Andre can login and if Andre can
login, your application can work with the user name marc with the database
(and show the user the login Andre)
So your user will never be able to work on the database as his login is not
a database login
Marc Allard
"Jason" <yo@.yo.com> a crit dans le message de
news:%234bvqLoeEHA.3016@.tk2msftngp13.phx.gbl...
> Is there a way to secure a database on MSDE so that my users cannot be
> poking around my applications database? I've been reading up on it and see
> that MSDE installs with a mixed security mode.
> Does that mean if I secure my database with sql security someone who is an
> admin on the machine can look at my database regardless of what I set?
> I am concerned that my users (and competition) will try to hack into my
> instance and steal my data & data structures so I'm trying to figure out
> how I can prevent that. I understand I can encrypt my stored procedure at
> least I hope that is still the case with MSDE.
> Any thoughts?
> Thanks.
>
> This is a desktop app and not a web app btw.
>
|||The only way you can lock the data down is to encrypt it. If a user has
Local Admin rights in the OS (NT/2K/XP), then they can see the data anyway,
irrespective of SQL Auth as NT Auth is always available.
Administrator ALWAYS gets to the data!
On Fri, 6 Aug 2004 11:05:29 +0200, Allcomp wrote:
[vbcol=seagreen]
> Hello,
> It is also possible to use SQL autentification, then create only one login
> that the user doesn't know.
> After that, your application connect as the login you 've just created. (for
> example Log = marc PWD = marc)
> In you database, you make a login table. This table contain the login of the
> user and his password, and your application will test this table to see if
> the user can connect. With this method you can even forbid a part of the
> application or a time to connect ... easily.
> For example UID Andre PWD Andre.
> After that, your user will enter the login and password to your application
> (Andre/ Andre).
> your application connect as marc, see if Andre can login and if Andre can
> login, your application can work with the user name marc with the database
> (and show the user the login Andre)
> So your user will never be able to work on the database as his login is not
> a database login
> Marc Allard
>
> "Jason" <yo@.yo.com> a crit dans le message de
> news:%234bvqLoeEHA.3016@.tk2msftngp13.phx.gbl...
|||Hello,
I didn't know it was possible to connect as Administrator in a sql server
when the installation was mado to allow only SQL autentification. How can
you make it?
Thank you
Marc Allard
"Paul Buxton" <psb@.NOSPAMspireite.demon.co.uk> a crit dans le message de
news:1opgizeso0jib$.ywf1zot73zdg.dlg@.40tude.net...
> The only way you can lock the data down is to encrypt it. If a user has
> Local Admin rights in the OS (NT/2K/XP), then they can see the data
anyway,[vbcol=seagreen]
> irrespective of SQL Auth as NT Auth is always available.
> Administrator ALWAYS gets to the data!
> On Fri, 6 Aug 2004 11:05:29 +0200, Allcomp wrote:
login[vbcol=seagreen]
(for[vbcol=seagreen]
the[vbcol=seagreen]
if[vbcol=seagreen]
application[vbcol=seagreen]
can[vbcol=seagreen]
database[vbcol=seagreen]
not[vbcol=seagreen]
see[vbcol=seagreen]
an[vbcol=seagreen]
out[vbcol=seagreen]
at[vbcol=seagreen]
|||hi,
"Allcomp" <fa097770@.nospam.skynet.be> ha scritto nel messaggio
news:41136323$0$296$ba620e4c@.news.skynet.be...
> Hello,
> I didn't know it was possible to connect as Administrator in a sql server
> when the installation was mado to allow only SQL autentification. How can
> you make it?
just log in in Windows as a member of sysadmins; sysadmis are member of
Builtin\Administrator SQL Server role, which has administrative privileges
by default...
the method you previously exposed only prevents user of YOUR application not
to access that data, but using ad-hoc query tools like QA, oSql or simply
Visual Data Manager (VB3 to VB6 <g>) an administrator can perform whatever
activity...
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
|||Only One JASON, FORGET IT.
I have been called in more than once to untangle all sorts of developer
installed security, I do it and will continue to do it.
Developers who think that business data should be locked up from the
Business should be locked up themselves. If your data is proprietary,
then I suggest you create your own encrypted storage system! But give up on
trying to lock the rightful owners of data out from it by denying them
access to the database.
Your schema etc. Might be your work, but locking out legitimate uses of
the data is in my opinion about as quick a way to get your application
dumped as you can get. Companies expect to be able to throw a copy of
Crystal Reports onto a machine and interogate the database for the
information that they want, in the manner that they want it, when they want
it.
As foir competitors using your schema in their own products, you must be
joking! They might however write conversion routines to 'upgrade' from your
product. This is a fairly normal business practice.
You sound like Apple complaining about Real Networks, or an IBM salesman
from the 1970s, telling the customer that MS-Dos on a compatible PC is just
not as good as an IBM PC-XT with PC-Dos for running Lotus 1-2-3
Matt
|||hi Matt,
"Unicorn" <unicorn@.somewhere.com> ha scritto nel messaggio
news:epy96HEfEHA.2604@.TK2MSFTNGP12.phx.gbl...
> Only One JASON, FORGET IT.
> I have been called in more than once to untangle all sorts of developer
> installed security, I do it and will continue to do it.
> Developers who think that business data should be locked up from the
> Business should be locked up themselves. If your data is proprietary,
> then I suggest you create your own encrypted storage system! But give up
on
> trying to lock the rightful owners of data out from it by denying them
> access to the database.
not to start a flame, but just a consideration...
I think it really depends... if you "sell" data, that's to say an aggregated
and/or particular kind of sensible data, perhaps having it not accessible to
external application but your(s), could be a legitimated pray for a
particular protection system, and perhaps external encryption is a way to go
for, as you already pointed out... perhaps not the best as it will be not
integrated.. but acceptable...
the same is true for sensible code you provide in form of stored
procedures/udf/views...
let's think about a genious tool, RAC by SQL Server MVP Thanh Ngo (AKA OJ)..
my understanding is it provides a set of stored procedures to manipulate
data, with unique features like CROSSTAB rotations and so on... this is
valuable code and think is provided as encrypted code... as it should
but you actually have no way to protect your metaschema(s) the same way...
even if SQL Server encryption has been defeated... I do personally think
this could be a valuable feature in some scenario...
> Your schema etc. Might be your work, but locking out legitimate uses of
> the data is in my opinion about as quick a way to get your application
> dumped as you can get. Companies expect to be able to throw a copy of
> Crystal Reports onto a machine and interogate the database for the
> information that they want, in the manner that they want it, when they
want
> it.
this could violate certain EULAs and/or rules, both private and/or
legislative...
recently I've been asked to buy a mailing for german (potential)
customers... the selling company provided a well defined license for 1 use,
n uses of the same data... don't know what kind of database they would
provide as our choice went to mailing labels directly, just for one shot...
but this scenario certainly does not grant you the possibility for multi
server analysis and or use...
another issue... think to privacy protection for sensible data... medical
data... there are both european and USA (as other countries too..) acts that
state and (strictly) discipline the use of this kind of data...
a recent article by Sean Maloney on SQL Server Magazine
(http://www.winnetmag.com/SQLServer/A...731/42731.html for
subscribers only) presents a way to protect data from unlegitimated users
with row level security granularity.. but if you manually bypass that kind
of security (which you can, as a syasdmin) you are elegible for legal
repercussions...
> As foir competitors using your schema in their own products, you must be
> joking! They might however write conversion routines to 'upgrade' from
your
> product. This is a fairly normal business practice.
>
agree =;-D
again... not to flame but just my 2 (euro)cents
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
|||Thank you for your answer
Marc Allard
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> a crit dans le message de
news:2nhjgsFud2mU1@.uni-berlin.de...[vbcol=seagreen]
> hi,
> "Allcomp" <fa097770@.nospam.skynet.be> ha scritto nel messaggio
> news:41136323$0$296$ba620e4c@.news.skynet.be...
server[vbcol=seagreen]
can
> just log in in Windows as a member of sysadmins; sysadmis are member of
> Builtin\Administrator SQL Server role, which has administrative privileges
> by default...
> the method you previously exposed only prevents user of YOUR application
not
> to access that data, but using ad-hoc query tools like QA, oSql or simply
> Visual Data Manager (VB3 to VB6 <g>) an administrator can perform whatever
> activity...
> --
> 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
>
|||A possible solution may be to use dbLockdown. It will encrypt ALL (or
selected) database object scripts for stored procedures, triggers, user
defined functions and views in your MSDE database using the WITH
ENCRYPTION clause. The tool will also automatically archive the script
source so you can restore it again at any time. Check out
http://www.ecatenate.com/dblockdown_product_info.html
Regards, Simon
"Jason" <yo@.yo.com> wrote in message news:<#4bvqLoeEHA.3016@.tk2msftngp13.phx.gbl>...
> Is there a way to secure a database on MSDE so that my users cannot be
> poking around my applications database? I've been reading up on it and see
> that MSDE installs with a mixed security mode.
> Does that mean if I secure my database with sql security someone who is an
> admin on the machine can look at my database regardless of what I set?
> I am concerned that my users (and competition) will try to hack into my
> instance and steal my data & data structures so I'm trying to figure out
> how I can prevent that. I understand I can encrypt my stored procedure at
> least I hope that is still the case with MSDE.
> Any thoughts?
> Thanks.
>
> This is a desktop app and not a web app btw.
Friday, March 23, 2012
MSDE Problem
I've been having hassles with MSDE 2000a. When attempting to install our
Product, when our DLL's are supposed to be registered, Windows Installer
dialogs ("Preparing to install..")are popped up for every DLL. When we check
the Application log, we see the following error message :
Detection of product '{E09B48B5-E141-427A-AB0C-D3605127224A}', feature
'SqlRun' failed during request for component
'{436D7A23-36BE-11D2-ACBB-0080C7FCBB84}'
I have a feeling that MSDE doesn't correctly reference the SqlRun feature -
because if I change the GUID under:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Feat ures\*GUID*
that contains the SqlRun key, to E09B48B5E141427AAB0CD3605127224A - then it
seems to work fine.
What the %$#^%$# is going on here?!?
Is this an MSDE problem? Am I simply installing MSDE incorrectly?
hi Don,
"don" <don@.discussions.microsoft.com> ha scritto nel messaggio
news:7A84DFDC-2165-49B9-9864-0C33A040262D@.microsoft.com...
> I've been having hassles with MSDE 2000a. When attempting to install our
> Product, when our DLL's are supposed to be registered, Windows Installer
> dialogs ("Preparing to install..")are popped up for every DLL. When we
check
> the Application log, we see the following error message :
> Detection of product '{E09B48B5-E141-427A-AB0C-D3605127224A}', feature
> 'SqlRun' failed during request for component
> '{436D7A23-36BE-11D2-ACBB-0080C7FCBB84}'
> I have a feeling that MSDE doesn't correctly reference the SqlRun
feature -
> because if I change the GUID under:
> HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Feat ures\*GUID*
> that contains the SqlRun key, to E09B48B5E141427AAB0CD3605127224A - then
it
> seems to work fine.
> What the %$#^%$# is going on here?!?
> Is this an MSDE problem? Am I simply installing MSDE incorrectly?
>
how are you installing MSDE?
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
Product, when our DLL's are supposed to be registered, Windows Installer
dialogs ("Preparing to install..")are popped up for every DLL. When we check
the Application log, we see the following error message :
Detection of product '{E09B48B5-E141-427A-AB0C-D3605127224A}', feature
'SqlRun' failed during request for component
'{436D7A23-36BE-11D2-ACBB-0080C7FCBB84}'
I have a feeling that MSDE doesn't correctly reference the SqlRun feature -
because if I change the GUID under:
HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Feat ures\*GUID*
that contains the SqlRun key, to E09B48B5E141427AAB0CD3605127224A - then it
seems to work fine.
What the %$#^%$# is going on here?!?
Is this an MSDE problem? Am I simply installing MSDE incorrectly?
hi Don,
"don" <don@.discussions.microsoft.com> ha scritto nel messaggio
news:7A84DFDC-2165-49B9-9864-0C33A040262D@.microsoft.com...
> I've been having hassles with MSDE 2000a. When attempting to install our
> Product, when our DLL's are supposed to be registered, Windows Installer
> dialogs ("Preparing to install..")are popped up for every DLL. When we
check
> the Application log, we see the following error message :
> Detection of product '{E09B48B5-E141-427A-AB0C-D3605127224A}', feature
> 'SqlRun' failed during request for component
> '{436D7A23-36BE-11D2-ACBB-0080C7FCBB84}'
> I have a feeling that MSDE doesn't correctly reference the SqlRun
feature -
> because if I change the GUID under:
> HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Feat ures\*GUID*
> that contains the SqlRun key, to E09B48B5E141427AAB0CD3605127224A - then
it
> seems to work fine.
> What the %$#^%$# is going on here?!?
> Is this an MSDE problem? Am I simply installing MSDE incorrectly?
>
how are you installing MSDE?
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 Performance Against Concurrent Access
Thx Andrea, Thx William,
Since u told me, I've made some test on the SQL model I
have running and the queries use to take just 1/100 sec (I
use to have up to 10 queries in chain per ASP page) due to
the volume of the info related (this intranet wouldnt
reach 100.000 records total in 38 tables, ever I think)
and the easyness of the queries (it has as maximum 2
subqueries) but there is more inner joins, up to 5 in the
same query, there is also 100's of relations between the
tables (38 total tables).
I think this information make sence to migrate the model
to MSDE and use it without translating the cost of a SQL
licence to my client since it wouldnt worth it.
Any other sugest?
Thx in advance...
>--Original Message--
>Hello,
>Can anybody tell me about your own experience using IIS
>with MSDE as repository?
>Would the concurrent access of the anonymous internet
user
>to the MSDE engine affect its performance if the
>concurrent access reach more than 5 at a time?
>Im planning to deploy an Intranet Application for
>consultant office and Im affraid the MSDE to cause a
>dregradation in performance if it gets more than 5
>concurrent access.
>Thx in Advance.
>Mike.
>.
>
1) MSDE is free
2) JET is not intended for use in a web site for several reasons.
3) JET will outperform MSDE for some queries but it does not scale.
4) See 1.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:b13701c47973$8f7843c0$a501280a@.phx.gbl...[vbcol=seagreen]
> Thx Andrea, Thx William,
> Since u told me, I've made some test on the SQL model I
> have running and the queries use to take just 1/100 sec (I
> use to have up to 10 queries in chain per ASP page) due to
> the volume of the info related (this intranet wouldnt
> reach 100.000 records total in 38 tables, ever I think)
> and the easyness of the queries (it has as maximum 2
> subqueries) but there is more inner joins, up to 5 in the
> same query, there is also 100's of relations between the
> tables (38 total tables).
> I think this information make sence to migrate the model
> to MSDE and use it without translating the cost of a SQL
> licence to my client since it wouldnt worth it.
> Any other sugest?
> Thx in advance...
>
> user
Since u told me, I've made some test on the SQL model I
have running and the queries use to take just 1/100 sec (I
use to have up to 10 queries in chain per ASP page) due to
the volume of the info related (this intranet wouldnt
reach 100.000 records total in 38 tables, ever I think)
and the easyness of the queries (it has as maximum 2
subqueries) but there is more inner joins, up to 5 in the
same query, there is also 100's of relations between the
tables (38 total tables).
I think this information make sence to migrate the model
to MSDE and use it without translating the cost of a SQL
licence to my client since it wouldnt worth it.
Any other sugest?
Thx in advance...
>--Original Message--
>Hello,
>Can anybody tell me about your own experience using IIS
>with MSDE as repository?
>Would the concurrent access of the anonymous internet
user
>to the MSDE engine affect its performance if the
>concurrent access reach more than 5 at a time?
>Im planning to deploy an Intranet Application for
>consultant office and Im affraid the MSDE to cause a
>dregradation in performance if it gets more than 5
>concurrent access.
>Thx in Advance.
>Mike.
>.
>
1) MSDE is free
2) JET is not intended for use in a web site for several reasons.
3) JET will outperform MSDE for some queries but it does not scale.
4) See 1.
____________________________________
William (Bill) Vaughn
Author, Mentor, Consultant
Microsoft MVP
www.betav.com
Please reply only to the newsgroup so that others can benefit.
This posting is provided "AS IS" with no warranties, and confers no rights.
__________________________________
"Mike" <anonymous@.discussions.microsoft.com> wrote in message
news:b13701c47973$8f7843c0$a501280a@.phx.gbl...[vbcol=seagreen]
> Thx Andrea, Thx William,
> Since u told me, I've made some test on the SQL model I
> have running and the queries use to take just 1/100 sec (I
> use to have up to 10 queries in chain per ASP page) due to
> the volume of the info related (this intranet wouldnt
> reach 100.000 records total in 38 tables, ever I think)
> and the easyness of the queries (it has as maximum 2
> subqueries) but there is more inner joins, up to 5 in the
> same query, there is also 100's of relations between the
> tables (38 total tables).
> I think this information make sence to migrate the model
> to MSDE and use it without translating the cost of a SQL
> licence to my client since it wouldnt worth it.
> Any other sugest?
> Thx in advance...
>
> user
MSDE over the network
Please help! I've had this problem for FOREVER. It's driving me batty.
I'm installing MSDE in a networked environment. I'm using SQL-DMO to find all
instances of MSDE on the network. *Usually*, this works great.
Unfortunately, sometimes MSDE instances refuse to advertise on the network.
I can't register them in Enterprise Manager or see them with SQL-DMO. I'm
using setup.exe to install these instances, and I'm setting
DISABLENETWORKPROTOCOLS=0. I've run the svrnetcn.exe program, and each
vanished instance is in fact listening via TCP/IP and Remote Procedure Calls.
I've added each instance as an exception in the Windows Firewall on XP SP2.
Each disappeared instance has in fact been started. Local applications can
see these vanished instances, but networked applications cannot. There are no
other firewalls or packet filtering on the network. I'm behind a Microsoft
Wireless Base Station Router. Am I missing something?
This problem is about to drive me insane. I'm using the exact same
installation program and parameters to setup.exe, but some instances just
don't want to play on the network. Any help would be greatly appreciated.
Thanks in advance.
Rob Reagan
rob at digitallabsinc.com
Are any of the MSDE instances installed on XP SP2? If the MSDE instance does
not have SP3 installed then XP will block MSDE from broadcasting its status.
You can see warnings about this in the system event log. This is the same
with Windows Server 2003.
Jim
"Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
news:ED94255F-732F-4DFF-B994-CEAD94B90354@.microsoft.com...
> Please help! I've had this problem for FOREVER. It's driving me batty.
> I'm installing MSDE in a networked environment. I'm using SQL-DMO to find
all
> instances of MSDE on the network. *Usually*, this works great.
> Unfortunately, sometimes MSDE instances refuse to advertise on the
network.
> I can't register them in Enterprise Manager or see them with SQL-DMO. I'm
> using setup.exe to install these instances, and I'm setting
> DISABLENETWORKPROTOCOLS=0. I've run the svrnetcn.exe program, and each
> vanished instance is in fact listening via TCP/IP and Remote Procedure
Calls.
> I've added each instance as an exception in the Windows Firewall on XP
SP2.
> Each disappeared instance has in fact been started. Local applications can
> see these vanished instances, but networked applications cannot. There are
no
> other firewalls or packet filtering on the network. I'm behind a Microsoft
> Wireless Base Station Router. Am I missing something?
> This problem is about to drive me insane. I'm using the exact same
> installation program and parameters to setup.exe, but some instances just
> don't want to play on the network. Any help would be greatly appreciated.
> Thanks in advance.
> Rob Reagan
> rob at digitallabsinc.com
>
|||YOU ARE THE MAN! Thanks so much for that response.
"Jim Young" wrote:
> Are any of the MSDE instances installed on XP SP2? If the MSDE instance does
> not have SP3 installed then XP will block MSDE from broadcasting its status.
> You can see warnings about this in the system event log. This is the same
> with Windows Server 2003.
> Jim
> "Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
> news:ED94255F-732F-4DFF-B994-CEAD94B90354@.microsoft.com...
> all
> network.
> Calls.
> SP2.
> no
>
>
I'm installing MSDE in a networked environment. I'm using SQL-DMO to find all
instances of MSDE on the network. *Usually*, this works great.
Unfortunately, sometimes MSDE instances refuse to advertise on the network.
I can't register them in Enterprise Manager or see them with SQL-DMO. I'm
using setup.exe to install these instances, and I'm setting
DISABLENETWORKPROTOCOLS=0. I've run the svrnetcn.exe program, and each
vanished instance is in fact listening via TCP/IP and Remote Procedure Calls.
I've added each instance as an exception in the Windows Firewall on XP SP2.
Each disappeared instance has in fact been started. Local applications can
see these vanished instances, but networked applications cannot. There are no
other firewalls or packet filtering on the network. I'm behind a Microsoft
Wireless Base Station Router. Am I missing something?
This problem is about to drive me insane. I'm using the exact same
installation program and parameters to setup.exe, but some instances just
don't want to play on the network. Any help would be greatly appreciated.
Thanks in advance.
Rob Reagan
rob at digitallabsinc.com
Are any of the MSDE instances installed on XP SP2? If the MSDE instance does
not have SP3 installed then XP will block MSDE from broadcasting its status.
You can see warnings about this in the system event log. This is the same
with Windows Server 2003.
Jim
"Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
news:ED94255F-732F-4DFF-B994-CEAD94B90354@.microsoft.com...
> Please help! I've had this problem for FOREVER. It's driving me batty.
> I'm installing MSDE in a networked environment. I'm using SQL-DMO to find
all
> instances of MSDE on the network. *Usually*, this works great.
> Unfortunately, sometimes MSDE instances refuse to advertise on the
network.
> I can't register them in Enterprise Manager or see them with SQL-DMO. I'm
> using setup.exe to install these instances, and I'm setting
> DISABLENETWORKPROTOCOLS=0. I've run the svrnetcn.exe program, and each
> vanished instance is in fact listening via TCP/IP and Remote Procedure
Calls.
> I've added each instance as an exception in the Windows Firewall on XP
SP2.
> Each disappeared instance has in fact been started. Local applications can
> see these vanished instances, but networked applications cannot. There are
no
> other firewalls or packet filtering on the network. I'm behind a Microsoft
> Wireless Base Station Router. Am I missing something?
> This problem is about to drive me insane. I'm using the exact same
> installation program and parameters to setup.exe, but some instances just
> don't want to play on the network. Any help would be greatly appreciated.
> Thanks in advance.
> Rob Reagan
> rob at digitallabsinc.com
>
|||YOU ARE THE MAN! Thanks so much for that response.
"Jim Young" wrote:
> Are any of the MSDE instances installed on XP SP2? If the MSDE instance does
> not have SP3 installed then XP will block MSDE from broadcasting its status.
> You can see warnings about this in the system event log. This is the same
> with Windows Server 2003.
> Jim
> "Rob Reagan" <RobReagan@.discussions.microsoft.com> wrote in message
> news:ED94255F-732F-4DFF-B994-CEAD94B90354@.microsoft.com...
> all
> network.
> Calls.
> SP2.
> no
>
>
MSDE over TCP/IP
I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4) installation
running our SharePoint site. I now need to connect to this database remotely
via TCP/IP, but can't get it to enable the protocol.
The log file always just says:
2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-12-11 12:13:46.39 server SQL server listening on Shared Memory.
I've tried all the suggestions I've heard on the internet. What I've tried:
Install the latest MSDE Service Pack (SP4)
Use SVRNETCN.exe to enable the TCP/IP Protocol
Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433, Restart
Service.
I've hard reset the machine, I've installed all the latest service packs on
this machine. I've disabled the firewall. I've tried ports other than 1433.
I've tried enabling Named Pipes & NWLink at various times as well. No matter
what I do, the log still shows it listening only on shared memory.
Any assistance would be greatly appreciated as I'm completely stumped.
Andrew Faust
http://www.andrewfaust.com
=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
> I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4)
> installation running our SharePoint site. I now need to connect to
> this database remotely via TCP/IP, but can't get it to enable the
> protocol.
> The log file always just says:
> 2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version
> '8.0.2039'. 2007-12-11 12:13:46.39 server SQL server listening on
> Shared Memory.
> I've tried all the suggestions I've heard on the internet. What I've
> tried:
> Install the latest MSDE Service Pack (SP4)
> Use SVRNETCN.exe to enable the TCP/IP Protocol
> Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433,
> Restart Service.
> I've hard reset the machine, I've installed all the latest service
> packs on this machine. I've disabled the firewall. I've tried ports
> other than 1433. I've tried enabling Named Pipes & NWLink at various
> times as well. No matter what I do, the log still shows it listening
> only on shared memory.
> Any assistance would be greatly appreciated as I'm completely stumped.
If you see no effects at all from using svrnetcn.exe, perhaps you have got
multiple instances installed. Drop down the "Instances on this server"
combo at the top of the General tab of the svrnetcn.exe dialog (similarly
the Server combo at the top of the SQL Server Service Manager dialog).
|||Thanks for the response.
Unfortunately, that's not the problem. There is only 1 instance installed on
this server. I forgot to mention this before and don't know if it makes a
difference, but this is a named instance. It's called DOCMGR\SHAREPOINT. It's
also running on Windows Server 2003 with all the latest service packs
installed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:
> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
>
> If you see no effects at all from using svrnetcn.exe, perhaps you have got
> multiple instances installed. Drop down the "Instances on this server"
> combo at the top of the General tab of the svrnetcn.exe dialog (similarly
> the Server combo at the top of the SQL Server Service Manager dialog).
>
|||=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
> Thanks for the response.
> Unfortunately, that's not the problem. There is only 1 instance
> installed on this server. I forgot to mention this before and don't
> know if it makes a difference, but this is a named instance. It's
> called DOCMGR\SHAREPOINT. It's also running on Windows Server 2003
> with all the latest service packs installed.
>
Well, it was something that was possible, given the symptoms you described.
Sorry, I'm out of further ideas. Good luck!
|||I appreciate the effort. I've finally given up on trying to make it work and
have moved my SharePoint to a full install of SQL Server 2000 and gotten the
functionality I needed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:
> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
>
> Well, it was something that was possible, given the symptoms you described.
> Sorry, I'm out of further ideas. Good luck!
>
running our SharePoint site. I now need to connect to this database remotely
via TCP/IP, but can't get it to enable the protocol.
The log file always just says:
2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version '8.0.2039'.
2007-12-11 12:13:46.39 server SQL server listening on Shared Memory.
I've tried all the suggestions I've heard on the internet. What I've tried:
Install the latest MSDE Service Pack (SP4)
Use SVRNETCN.exe to enable the TCP/IP Protocol
Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433, Restart
Service.
I've hard reset the machine, I've installed all the latest service packs on
this machine. I've disabled the firewall. I've tried ports other than 1433.
I've tried enabling Named Pipes & NWLink at various times as well. No matter
what I do, the log still shows it listening only on shared memory.
Any assistance would be greatly appreciated as I'm completely stumped.
Andrew Faust
http://www.andrewfaust.com
=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
> I've got a SQL Server Desktop Engine (version 8.00.2039 - SP4)
> installation running our SharePoint site. I now need to connect to
> this database remotely via TCP/IP, but can't get it to enable the
> protocol.
> The log file always just says:
> 2007-12-11 12:13:46.39 server Using 'SSNETLIB.DLL' version
> '8.0.2039'. 2007-12-11 12:13:46.39 server SQL server listening on
> Shared Memory.
> I've tried all the suggestions I've heard on the internet. What I've
> tried:
> Install the latest MSDE Service Pack (SP4)
> Use SVRNETCN.exe to enable the TCP/IP Protocol
> Enable TCP/IP, Set to Port 0, Restart Service, Set to Port 1433,
> Restart Service.
> I've hard reset the machine, I've installed all the latest service
> packs on this machine. I've disabled the firewall. I've tried ports
> other than 1433. I've tried enabling Named Pipes & NWLink at various
> times as well. No matter what I do, the log still shows it listening
> only on shared memory.
> Any assistance would be greatly appreciated as I'm completely stumped.
If you see no effects at all from using svrnetcn.exe, perhaps you have got
multiple instances installed. Drop down the "Instances on this server"
combo at the top of the General tab of the svrnetcn.exe dialog (similarly
the Server combo at the top of the SQL Server Service Manager dialog).
|||Thanks for the response.
Unfortunately, that's not the problem. There is only 1 instance installed on
this server. I forgot to mention this before and don't know if it makes a
difference, but this is a named instance. It's called DOCMGR\SHAREPOINT. It's
also running on Windows Server 2003 with all the latest service packs
installed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:
> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:23AE3B12-517E-4970-8F7D-3E094BE07541@.microsoft.com:
>
> If you see no effects at all from using svrnetcn.exe, perhaps you have got
> multiple instances installed. Drop down the "Instances on this server"
> combo at the top of the General tab of the svrnetcn.exe dialog (similarly
> the Server combo at the top of the SQL Server Service Manager dialog).
>
|||=?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
> Thanks for the response.
> Unfortunately, that's not the problem. There is only 1 instance
> installed on this server. I forgot to mention this before and don't
> know if it makes a difference, but this is a named instance. It's
> called DOCMGR\SHAREPOINT. It's also running on Windows Server 2003
> with all the latest service packs installed.
>
Well, it was something that was possible, given the symptoms you described.
Sorry, I'm out of further ideas. Good luck!
|||I appreciate the effort. I've finally given up on trying to make it work and
have moved my SharePoint to a full install of SQL Server 2000 and gotten the
functionality I needed.
Andrew Faust
http://www.andrewfaust.com
"Chris.Cheney" wrote:
> =?Utf-8?B?QW5kcmV3IEZhdXN0?= <andrew [at] andrewfaust.com> wrote in
> news:B66EA507-0750-48F2-8E5F-F7B8FC60ED9F@.microsoft.com:
>
> Well, it was something that was possible, given the symptoms you described.
> Sorry, I'm out of further ideas. Good luck!
>
Monday, March 19, 2012
MSDE newbie quetsion: importing data from SQL Server
I've been given a file with no extension, and told that it's "a full
export from our SQL server tables".
What sort of file is this likely to be, and is there any way I can
import it into MSDE?
Simon Elliott http://www.ctsn.co.uk
hi Simon,
"Simon Elliott" <Simon at ctsn.co.uk> ha scritto nel messaggio
news:u5XG0NwQEHA.3728@.TK2MSFTNGP10.phx.gbl...
> I've been given a file with no extension, and told that it's "a full
> export from our SQL server tables".
> What sort of file is this likely to be, and is there any way I can
> import it into MSDE?
it really depend what kind of file it is...
it can be a full backup of a database, and you can test it executing from
any query tool
RESTORE HEADERONLY
FROM DISK = 'c:\....\filename'
which returns a result set indicating the content, if any and valid, of the
potential backup, or something like
Server: Msg 3242, Level 16, State 1, Line 1
The file on device 'd:\cursor.txt' is not a valid Microsoft Tape Format
backup set.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE HEADERONLY is terminating abnormally.
it can even be a DML sql file, containing a list of INSERT INTO statements
you have to execute to load an existing table... or a bulk copy export you
have to bulk insert..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi Simon,
"Simon Elliott" <Simon at ctsn.co.uk> ha scritto nel messaggio
news:%23ba4YhDREHA.3124@.TK2MSFTNGP12.phx.gbl...
> On 27/05/2004, Simon Elliott wrote:
> Is there a MSDE based on SQL Server 2000 available for free download?
>
yese, you can get the package at
http://www.microsoft.com/sql/msde/do...s/download.asp
> If so, how do I uninstall the current version? I've had no luck trying
> to uninstall it so far, as the uninstaller tells me that the service is
> still running, even if I have stopped it.
>
the uninstall applet shoul'd work as expected, but you can read
http://support.microsoft.com/default...oduct=sql&FR=1
for some hints on how to manually uninstall SQL Server 7.0 version...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||On 28/05/2004, Andrea Montanari wrote:
> yese, you can get the package at
> http://www.microsoft.com/sql/msde/do...s/download.asp
>
> the uninstall applet shoul'd work as expected, but you can read
> http://support.microsoft.com/default...276044&Product
> =sql&FR=1 for some hints on how to manually uninstall SQL Server 7.0
> version... --
OK, I'll give that a try. Thanks again for all your help.
Simon Elliott http://www.ctsn.co.uk
export from our SQL server tables".
What sort of file is this likely to be, and is there any way I can
import it into MSDE?
Simon Elliott http://www.ctsn.co.uk
hi Simon,
"Simon Elliott" <Simon at ctsn.co.uk> ha scritto nel messaggio
news:u5XG0NwQEHA.3728@.TK2MSFTNGP10.phx.gbl...
> I've been given a file with no extension, and told that it's "a full
> export from our SQL server tables".
> What sort of file is this likely to be, and is there any way I can
> import it into MSDE?
it really depend what kind of file it is...
it can be a full backup of a database, and you can test it executing from
any query tool
RESTORE HEADERONLY
FROM DISK = 'c:\....\filename'
which returns a result set indicating the content, if any and valid, of the
potential backup, or something like
Server: Msg 3242, Level 16, State 1, Line 1
The file on device 'd:\cursor.txt' is not a valid Microsoft Tape Format
backup set.
Server: Msg 3013, Level 16, State 1, Line 1
RESTORE HEADERONLY is terminating abnormally.
it can even be a DML sql file, containing a list of INSERT INTO statements
you have to execute to load an existing table... or a bulk copy export you
have to bulk insert..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi Simon,
"Simon Elliott" <Simon at ctsn.co.uk> ha scritto nel messaggio
news:%23ba4YhDREHA.3124@.TK2MSFTNGP12.phx.gbl...
> On 27/05/2004, Simon Elliott wrote:
> Is there a MSDE based on SQL Server 2000 available for free download?
>
yese, you can get the package at
http://www.microsoft.com/sql/msde/do...s/download.asp
> If so, how do I uninstall the current version? I've had no luck trying
> to uninstall it so far, as the uninstaller tells me that the service is
> still running, even if I have stopped it.
>
the uninstall applet shoul'd work as expected, but you can read
http://support.microsoft.com/default...oduct=sql&FR=1
for some hints on how to manually uninstall SQL Server 7.0 version...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.7.0 - DbaMgr ver 0.53.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||On 28/05/2004, Andrea Montanari wrote:
> yese, you can get the package at
> http://www.microsoft.com/sql/msde/do...s/download.asp
>
> the uninstall applet shoul'd work as expected, but you can read
> http://support.microsoft.com/default...276044&Product
> =sql&FR=1 for some hints on how to manually uninstall SQL Server 7.0
> version... --
OK, I'll give that a try. Thanks again for all your help.
Simon Elliott http://www.ctsn.co.uk
Friday, March 9, 2012
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
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
Wednesday, March 7, 2012
MSDE installation
Hi!
If I've installed SQLServer 7 and I install (for error or not) MSDE 2000 ... what happens? I mean, MSDE overwrites SQLServer 7.0 engine? My SQLServer will be crash?
Thanks in advance.
hi Han,
"Han" <Han@.discussions.microsoft.com> ha scritto nel messaggio
news:F5B956A9-6C1F-4889-B57D-C3598C97C6E4@.microsoft.com...
> Hi!
> If I've installed SQLServer 7 and I install (for error or not) MSDE 2000
... what happens?
>I mean, MSDE overwrites SQLServer 7.0 engine? My SQLServer will be crash?
>
SQL Server/MSDE 7.0 and SQL Server/MSDE 2000 can cohexist on the same PC...
the 7.0 code based installation can only be the "default" instances, while
the 2000 will be a named instance...
SQL Server 2000 intruduced instances support, where up to 16 of them, with
different service pack level, can happily be present at the same time, with
their own binaries... only the client tools will be shared among all
instances, usually at the higher installed service pack
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
If I've installed SQLServer 7 and I install (for error or not) MSDE 2000 ... what happens? I mean, MSDE overwrites SQLServer 7.0 engine? My SQLServer will be crash?
Thanks in advance.
hi Han,
"Han" <Han@.discussions.microsoft.com> ha scritto nel messaggio
news:F5B956A9-6C1F-4889-B57D-C3598C97C6E4@.microsoft.com...
> Hi!
> If I've installed SQLServer 7 and I install (for error or not) MSDE 2000
... what happens?
>I mean, MSDE overwrites SQLServer 7.0 engine? My SQLServer will be crash?
>
SQL Server/MSDE 7.0 and SQL Server/MSDE 2000 can cohexist on the same PC...
the 7.0 code based installation can only be the "default" instances, while
the 2000 will be a named instance...
SQL Server 2000 intruduced instances support, where up to 16 of them, with
different service pack level, can happily be present at the same time, with
their own binaries... only the client tools will be shared among all
instances, usually at the higher installed service pack
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 install worked 20 times now doesn't
Hi Group,
I've installed msde already about 20times and they all went ok, except one
but that had to do with file and printer sharing. Now I'm trying to install
it on win 2000 sp4 like all the others, but I can't get it to install, the
pc has got file and printer sharing enabled, it has got internet explorer 6
sp1, I checked HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Component Set
Value name: InstanceComponentSet.x Value and it's emtpy, there's no value
name: InstanceComponentSet.x
I already searched on google and something that seems to be returning is
that I should post the lines from the log file where I find return value 3
so here they are with some lines that are in front and some lines that are
behind it, (btw you won't find return value 3 but you have to search for
retourwaarde 3, it logs some words in dutch)
Any help would be very welcome
thanks in advance Peter
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: CategoryCount, Waarde: #8
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
urces\1043\sqlevn70.rll,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: CategoryMessageFile, Waarde:
C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1043\sqlevn70.r ll
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
es\1043\sqlevn70.rll,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: EventMessageFile, Waarde:
C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1043\sqlevn70.r ll
MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: TypesSupported, Waarde: #255
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\PFD\MSSQLServer\CurrentVersion,,BinaryType= 0)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=Language,Value=#1043,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\PFD\MSSQLServer\CurrentVersion, Naam: Language, Waarde: #1043
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
pplication\PFD,,BinaryType=0)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=CategoryCount,Value=#8,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: CategoryCount, Waarde: #8
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
urces\1033\sqlevn70.rll,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: CategoryMessageFile, Waarde:
C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70.r ll
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
es\1033\sqlevn70.rll,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: EventMessageFile, Waarde:
C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70.r ll
MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: TypesSupported, Waarde: #255
MSI (s) (7C:B0): Executing op:
ActionStart(Name=WriteEnvironmentStrings,Descripti on=Bezig met het bijwerken
van omgevingsstrings,Template=Naam: , waarde: , actie )
Actie 11:48:29: WriteEnvironmentStrings. Bezig met het bijwerken van
omgevingsstrings
MSI (s) (7C:B0): Executing op:
ProgressTotal(Total=1,Type=1,ByteEquivalent=13200)
MSI (s) (7C:B0): Executing op:
UpdateEnvironmentStrings(Name=PATH,Value=C:\Progra m Files\Microsoft SQL
Server\80\Tools\Binn\,Delimiter=;,Action=161061273 8,)
WriteEnvironmentStrings: Naam: PATH, waarde: C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\, actie 1610612738
MSI (s) (7C:B0): Executing op:
ActionStart(Name=RegisterTypeLibraries,Description =Bezig met het registreren
van typebibliotheken,Template=Bibliotheek-id: )
Actie 11:48:29: RegisterTypeLibraries. Bezig met het registreren van
typebibliotheken
MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
,Version=-2147483648,,Language=0,,BinaryType=0)
RegisterTypeLibraries: Bibliotheek-id:
{10010001-E260-11CF-AE68-00AA004A34D5}
MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
context. Path is ''
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
,Version=-2147483648,,Language=0,,BinaryType=0)
RegisterTypeLibraries: Bibliotheek-id:
{10010001-EB1C-11CF-AE6E-00AA004A34D5}
MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
context. Path is ''
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
},Version=-2147483648,,Language=0,,BinaryType=0)
RegisterTypeLibraries: Bibliotheek-id:
{10010200-740B-11D0-AE7B-00AA004A34D5}
MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
context. Path is ''
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op:
ActionStart(Name=InstallServices,Description=Bezig met het installeren van
nieuwe services,Template=Service: )
Actie 11:48:30: InstallServices. Bezig met het installeren van nieuwe
services
MSI (s) (7C:B0): Executing op:
ProgressTotal(Total=2,Type=1,ByteEquivalent=130000 0)
MSI (s) (7C:B0): Executing op:
ServiceInstall(Name=SQLAgent$PFD,DisplayName=SQLAg ent$PFD,ImagePath=C:\Profe
lExec\MSSQL$PFD\Binn\sqlagent.EXE -i
PFD,ServiceType=16,StartType=3,ErrorControl=1,,Dep endencies=MSSQL$PFD
MSI (s) (7C:B0): Executing op:
ServiceInstall(Name=MSSQL$PFD,DisplayName=MSSQL$PF D,ImagePath=C:\ProfelExec\
MSSQL$PFD\Binn\sqlservr.exe -sPFD,ServiceType=16,StartType=2,ErrorControl=1,
,,,,,)
MSI (s) (7C:B0): Executing op:
ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
Actie 11:48:32: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B.
MSI (s) (7C:B0): Executing op:
CustomActionSchedule(Action=InstallPerfMon.2D02443 E_7002_4C0B_ABC9_EAB2C0643
97B,ActionType=1025,Source=BinaryData,Target=Insta llPerfMon,)
MSI (s) (7C:B0): Creating MSIHANDLE (496) of type 790536 for thread 688
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sq
lcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallPerfMon
Registering performance counters from sqlctr.ini
PerfmonLoad routine returned error code 6
Actie beindigd 11:48:34: InstallFinalize. Retourwaarde 3.
MSI (s) (7C:B0): User policy value 'DisableRollback' is 0
MSI (s) (7C:B0): Machine policy value 'DisableRollback' is 0
MSI (s) (7C:B0): Executing op:
Header(Signature=1397708873,Version=200,Timestamp= 846618063,LangId=1043,Plat
form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMi norVersion=4,ScriptAttribu
tes=1)
MSI (s) (7C:B0): Executing op: DialogInfo(Type=0,Argument=1043)
MSI (s) (7C:B0): Executing op: DialogInfo(Type=1,Argument=Microsoft SQL
Server Desktop Engine)
MSI (s) (7C:B0): Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Terugdraai-actie:,
RollbackTemplate=,CleanupAction=RollbackCleanup,Cl eanupDescription=Bezig met
het verwijderen van reservekopiebestanden,CleanupTemplate=Bestand: [
1])
Actie 11:48:34: Rollback. Terugdraai-actie:
Rollback: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B
MSI (s) (7C:B0): Executing op:
ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
MSI (s) (7C:B0): Executing op:
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Mi
crosoft SQL Server Desktop
Engine,PackageName=SqlRun01.msi,Language=1043,Vers ion=134218489,Assignment=1
,ObsoleteArg=0,,,PackageCode={D29DCF7A-8199-4
373-BA0D-2F3635EC940C},,,InstanceType=0)
Rollback: Bezig met het installeren van nieuwe services
MSI (s) (7C:B0): Executing op:
ActionStart(Name=InstallServices,Description=Bezig met het installeren van
nieuwe services,Template=Service: )
MSI (s) (7C:B0): Executing op: ServiceControl(,Name=MSSQL$PFD,Action=8,,)
MSI (s) (7C:B0): Executing op: ServiceControl(,Name=SQLAgent$PFD,Action=8,,)
Rollback: Bezig met het registreren van typebibliotheken
MSI (s) (7C:B0): Executing op:
ActionStart(Name=RegisterTypeLibraries,Description =Bezig met het registreren
van typebibliotheken,Template=Bibliotheek-id: )
MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (7C:B0): Note: 1: 1402 2:
UNKNOWN\TypeLib\{10010200-740B-11D0-AE7B-00AA004A34D5}\0.0\0\win32 3: 2
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
,Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (7C:B0): Note: 1: 1402 2:
UNKNOWN\TypeLib\{10010001-EB1C-11CF-AE6E-00AA004A34D5}\0.0\0\win32 3: 2
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
,Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (7C:B0): Note: 1: 1402 2:
UNKNOWN\TypeLib\{10010001-E260-11CF-AE68-00AA004A34D5}\0.0\0\win32 3: 2
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
Rollback: Bezig met het bijwerken van omgevingsstrings
MSI (s) (7C:B0): Executing op:
ActionStart(Name=WriteEnvironmentStrings,Descripti on=Bezig met het bijwerken
van omgevingsstrings,Template=Naam: , waarde: , actie )
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=System\CurrentControlSet\Control\Se ssion
Manager\Environment,,)
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=PATH,Value=#%C:\PROGRA~1\MICROS~1 \OFFICE;%SYSTEMROOT%;%SYST
EMROOT%\COMMAND;"C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\";C:\PROGRA~1\MICROS~5\80\TOO LS\BINN;%SYSTEMROOT%\syste
m32;%SYSTEMROOT%\system3
2\WBEM,)
Rollback: Bezig met het schrijven van systeemregisterwaarden
MSI (s) (7C:B0): Executing op:
ActionStart(Name=WriteRegistryValues,Description=B ezig met het schrijven van
systeemregisterwaarden,Template=Sleutel: , Naam: , Waarde: )
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
pplication\PFD,,BinaryType=0)
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=TypesSupported,Value=#255,)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
1\1033\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=EventMessageFile,Value=C:\PROFEL~ 2\MSSQL$~1\Binn\RESOUR~1\1
043\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
UR~1\1033\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=CategoryMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
1\1043\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=CategoryCount,Value=#8,)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=CategoryCount,Value=#8,)
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\PFD\MSSQLServer\CurrentVersion,,BinaryType= 0)
MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=Language,Value=#1043,)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=Language,Value=#1043,)
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
pplication\PFD,,BinaryType=0)
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=TypesSupported,Value=#255,)
MSI (s) (7C:B0): Executing op: RegCreateKey()
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
1\1043\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op: RegCreateKey()
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
UR~1\1043\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op: RegCreateKey()
MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=CategoryCount,Value=#8,)
MSI (s) (7C:B0): Executing op: RegRemoveKey()
Peter,
I have exactly the same problem. I cannot install MSDE 2000 on a Windows XP
Pro SP2 machine. The install rolls back every time at exactly the same point
as yours. I posted here but did not get the answer. It may have something to
do with with manually deleting registry keys and Windows Installer parameters
to enable a "clean" install. I thought I did all the necessary steps but have
never been able to make it work. I will be watching your replies with
interest to see if you are able to get it installed.
Good luck!
"Peter Proost" wrote:
> Hi Group,
> I've installed msde already about 20times and they all went ok, except one
> but that had to do with file and printer sharing. Now I'm trying to install
> it on win 2000 sp4 like all the others, but I can't get it to install, the
> pc has got file and printer sharing enabled, it has got internet explorer 6
> sp1, I checked HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\Component Set
> Value name: InstanceComponentSet.x Value and it's emtpy, there's no value
> name: InstanceComponentSet.x
> I already searched on google and something that seems to be returning is
> that I should post the lines from the log file where I find return value 3
> so here they are with some lines that are in front and some lines that are
> behind it, (btw you won't find return value 3 but you have to search for
> retourwaarde 3, it logs some words in dutch)
> Any help would be very welcome
> thanks in advance Peter
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: CategoryCount, Waarde: #8
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
> urces\1043\sqlevn70.rll,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: CategoryMessageFile, Waarde:
> C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1043\sqlevn70.r ll
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
> es\1043\sqlevn70.rll,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: EventMessageFile, Waarde:
> C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1043\sqlevn70.r ll
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: TypesSupported, Waarde: #255
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
> Server\PFD\MSSQLServer\CurrentVersion,,BinaryType= 0)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=Language,Value=#1043,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\PFD\MSSQLServer\CurrentVersion, Naam: Language, Waarde: #1043
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> pplication\PFD,,BinaryType=0)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=CategoryCount,Value=#8,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: CategoryCount, Waarde: #8
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
> urces\1033\sqlevn70.rll,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: CategoryMessageFile, Waarde:
> C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70.r ll
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
> es\1033\sqlevn70.rll,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: EventMessageFile, Waarde:
> C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70.r ll
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: TypesSupported, Waarde: #255
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=WriteEnvironmentStrings,Descripti on=Bezig met het bijwerken
> van omgevingsstrings,Template=Naam: , waarde: , actie )
> Actie 11:48:29: WriteEnvironmentStrings. Bezig met het bijwerken van
> omgevingsstrings
> MSI (s) (7C:B0): Executing op:
> ProgressTotal(Total=1,Type=1,ByteEquivalent=13200)
> MSI (s) (7C:B0): Executing op:
> UpdateEnvironmentStrings(Name=PATH,Value=C:\Progra m Files\Microsoft SQL
> Server\80\Tools\Binn\,Delimiter=;,Action=161061273 8,)
> WriteEnvironmentStrings: Naam: PATH, waarde: C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\, actie 1610612738
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=RegisterTypeLibraries,Description =Bezig met het registreren
> van typebibliotheken,Template=Bibliotheek-id: )
> Actie 11:48:29: RegisterTypeLibraries. Bezig met het registreren van
> typebibliotheken
> MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
> ,Version=-2147483648,,Language=0,,BinaryType=0)
> RegisterTypeLibraries: Bibliotheek-id:
> {10010001-E260-11CF-AE68-00AA004A34D5}
> MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
> context. Path is ''
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
> ,Version=-2147483648,,Language=0,,BinaryType=0)
> RegisterTypeLibraries: Bibliotheek-id:
> {10010001-EB1C-11CF-AE6E-00AA004A34D5}
> MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
> context. Path is ''
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
> },Version=-2147483648,,Language=0,,BinaryType=0)
> RegisterTypeLibraries: Bibliotheek-id:
> {10010200-740B-11D0-AE7B-00AA004A34D5}
> MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
> context. Path is ''
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=InstallServices,Description=Bezig met het installeren van
> nieuwe services,Template=Service: )
> Actie 11:48:30: InstallServices. Bezig met het installeren van nieuwe
> services
> MSI (s) (7C:B0): Executing op:
> ProgressTotal(Total=2,Type=1,ByteEquivalent=130000 0)
> MSI (s) (7C:B0): Executing op:
> ServiceInstall(Name=SQLAgent$PFD,DisplayName=SQLAg ent$PFD,ImagePath=C:\Profe
> lExec\MSSQL$PFD\Binn\sqlagent.EXE -i
> PFD,ServiceType=16,StartType=3,ErrorControl=1,,Dep endencies=MSSQL$PFD
> MSI (s) (7C:B0): Executing op:
> ServiceInstall(Name=MSSQL$PFD,DisplayName=MSSQL$PF D,ImagePath=C:\ProfelExec\
> MSSQL$PFD\Binn\sqlservr.exe -sPFD,ServiceType=16,StartType=2,ErrorControl=1,
> ,,,,,)
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
> Actie 11:48:32: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B.
> MSI (s) (7C:B0): Executing op:
> CustomActionSchedule(Action=InstallPerfMon.2D02443 E_7002_4C0B_ABC9_EAB2C0643
> 97B,ActionType=1025,Source=BinaryData,Target=Insta llPerfMon,)
> MSI (s) (7C:B0): Creating MSIHANDLE (496) of type 790536 for thread 688
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sq
> lcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action InstallPerfMon
> Registering performance counters from sqlctr.ini
> PerfmonLoad routine returned error code 6
> Actie be?indigd 11:48:34: InstallFinalize. Retourwaarde 3.
> MSI (s) (7C:B0): User policy value 'DisableRollback' is 0
> MSI (s) (7C:B0): Machine policy value 'DisableRollback' is 0
> MSI (s) (7C:B0): Executing op:
> Header(Signature=1397708873,Version=200,Timestamp= 846618063,LangId=1043,Plat
> form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMi norVersion=4,ScriptAttribu
> tes=1)
> MSI (s) (7C:B0): Executing op: DialogInfo(Type=0,Argument=1043)
> MSI (s) (7C:B0): Executing op: DialogInfo(Type=1,Argument=Microsoft SQL
> Server Desktop Engine)
> MSI (s) (7C:B0): Executing op:
> RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Terugdraai-actie:,
> RollbackTemplate=,CleanupAction=RollbackCleanup,Cl eanupDescription=Bezig met
> het verwijderen van reservekopiebestanden,CleanupTemplate=Bestand: [
> 1])
> Actie 11:48:34: Rollback. Terugdraai-actie:
> Rollback: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
> MSI (s) (7C:B0): Executing op:
> ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Mi
> crosoft SQL Server Desktop
> Engine,PackageName=SqlRun01.msi,Language=1043,Vers ion=134218489,Assignment=1
> ,ObsoleteArg=0,,,PackageCode={D29DCF7A-8199-4
> 373-BA0D-2F3635EC940C},,,InstanceType=0)
> Rollback: Bezig met het installeren van nieuwe services
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=InstallServices,Description=Bezig met het installeren van
> nieuwe services,Template=Service: )
> MSI (s) (7C:B0): Executing op: ServiceControl(,Name=MSSQL$PFD,Action=8,,)
> MSI (s) (7C:B0): Executing op: ServiceControl(,Name=SQLAgent$PFD,Action=8,,)
> Rollback: Bezig met het registreren van typebibliotheken
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=RegisterTypeLibraries,Description =Bezig met het registreren
> van typebibliotheken,Template=Bibliotheek-id: )
> MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
> },Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (7C:B0): Note: 1: 1402 2:
> UNKNOWN\TypeLib\{10010200-740B-11D0-AE7B-00AA004A34D5}\0.0\0\win32 3: 2
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
> ,Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (7C:B0): Note: 1: 1402 2:
> UNKNOWN\TypeLib\{10010001-EB1C-11CF-AE6E-00AA004A34D5}\0.0\0\win32 3: 2
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
> ,Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (7C:B0): Note: 1: 1402 2:
> UNKNOWN\TypeLib\{10010001-E260-11CF-AE68-00AA004A34D5}\0.0\0\win32 3: 2
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> Rollback: Bezig met het bijwerken van omgevingsstrings
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=WriteEnvironmentStrings,Descripti on=Bezig met het bijwerken
> van omgevingsstrings,Template=Naam: , waarde: , actie )
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=System\CurrentControlSet\Control\Se ssion
> Manager\Environment,,)
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=PATH,Value=#%C:\PROGRA~1\MICROS~1 \OFFICE;%SYSTEMROOT%;%SYST
> EMROOT%\COMMAND;"C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\";C:\PROGRA~1\MICROS~5\80\TOO LS\BINN;%SYSTEMROOT%\syste
> m32;%SYSTEMROOT%\system3
> 2\WBEM,)
> Rollback: Bezig met het schrijven van systeemregisterwaarden
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=WriteRegistryValues,Description=B ezig met het schrijven van
> systeemregisterwaarden,Template=Sleutel: , Naam: , Waarde: )
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> pplication\PFD,,BinaryType=0)
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=TypesSupported,Value=#255,)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> 1\1033\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=EventMessageFile,Value=C:\PROFEL~ 2\MSSQL$~1\Binn\RESOUR~1\1
> 043\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
> UR~1\1033\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=CategoryMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> 1\1043\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=CategoryCount,Value=#8,)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=CategoryCount,Value=#8,)
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
> Server\PFD\MSSQLServer\CurrentVersion,,BinaryType= 0)
> MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=Language,Value=#1043,)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=Language,Value=#1043,)
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> pplication\PFD,,BinaryType=0)
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=TypesSupported,Value=#255,)
> MSI (s) (7C:B0): Executing op: RegCreateKey()
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> 1\1043\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op: RegCreateKey()
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
> UR~1\1043\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op: RegCreateKey()
> MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=CategoryCount,Value=#8,)
> MSI (s) (7C:B0): Executing op: RegRemoveKey()
>
>
|||Hi Stephen,
I got it to work, but hold your breath, only after reinstalling windows
because it had something to do with corrupted performance counters in the
registry. I tried evertyhting in this link
http://support.microsoft.com/default...microsoft.com:
80/support/kb/articles/q315/0/83.asp&NoWebContent=1
but I didn't get it to work, just for your info the pc was an upgraded one,
I upgraded it from me to 2000 I think there went something wrong there.
Maybe this link can help you
greetz Peter
"Stephen Bishop" <StephenBishop@.discussions.microsoft.com> schreef in
bericht news:9197FA53-F560-4CDC-847E-E81D354D1CE5@.microsoft.com...
> Peter,
> I have exactly the same problem. I cannot install MSDE 2000 on a Windows
XP
> Pro SP2 machine. The install rolls back every time at exactly the same
point
> as yours. I posted here but did not get the answer. It may have something
to
> do with with manually deleting registry keys and Windows Installer
parameters
> to enable a "clean" install. I thought I did all the necessary steps but
have[vbcol=seagreen]
> never been able to make it work. I will be watching your replies with
> interest to see if you are able to get it installed.
> Good luck!
> "Peter Proost" wrote:
one[vbcol=seagreen]
install[vbcol=seagreen]
the[vbcol=seagreen]
explorer 6[vbcol=seagreen]
value[vbcol=seagreen]
3[vbcol=seagreen]
are[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=TypesSupported,Value=#255,)[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=TypesSupported,Value=#255,)[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
bijwerken[vbcol=seagreen]
SQL[vbcol=seagreen]
registreren[vbcol=seagreen]
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}[vbcol=seagreen]
not[vbcol=seagreen]
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}[vbcol=seagreen]
not[vbcol=seagreen]
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5[vbcol=seagreen]
not[vbcol=seagreen]
van[vbcol=seagreen]
ServiceInstall(Name=SQLAgent$PFD,DisplayName=SQLAg ent$PFD,ImagePath=C:\Profe[vbcol=seagreen]
ServiceInstall(Name=MSSQL$PFD,DisplayName=MSSQL$PF D,ImagePath=C:\ProfelExec\[vbcol=seagreen]
MSSQL$PFD\Binn\sqlservr.exe -sPFD,ServiceType=16,StartType=2,ErrorControl=1,[vbcol=seagreen]
CustomActionSchedule(Action=InstallPerfMon.2D02443 E_7002_4C0B_ABC9_EAB2C0643[vbcol=seagreen]
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\[vbcol=seagreen]
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sq[vbcol=seagreen]
Header(Signature=1397708873,Version=200,Timestamp= 846618063,LangId=1043,Plat[vbcol=seagreen]
form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMi norVersion=4,ScriptAttribu[vbcol=seagreen]
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Terugdraai-actie:,[vbcol=seagreen]
met[vbcol=seagreen]
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Mi[vbcol=seagreen]
Engine,PackageName=SqlRun01.msi,Language=1043,Vers ion=134218489,Assignment=1[vbcol=seagreen]
van[vbcol=seagreen]
ServiceControl(,Name=MSSQL$PFD,Action=8,,)[vbcol=seagreen]
ServiceControl(,Name=SQLAgent$PFD,Action=8,,)[vbcol=seagreen]
registreren[vbcol=seagreen]
TypeLibraryUnregister(,,FilePath=C:\Program[vbcol=seagreen]
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5[vbcol=seagreen]
not[vbcol=seagreen]
TypeLibraryUnregister(,,FilePath=C:\Program[vbcol=seagreen]
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}[vbcol=seagreen]
not[vbcol=seagreen]
TypeLibraryUnregister(,,FilePath=C:\Program[vbcol=seagreen]
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}[vbcol=seagreen]
not[vbcol=seagreen]
bijwerken[vbcol=seagreen]
RegAddValue(Name=PATH,Value=#%C:\PROGRA~1\MICROS~1 \OFFICE;%SYSTEMROOT%;%SYST[vbcol=seagreen]
Server\80\Tools\Binn\";C:\PROGRA~1\MICROS~5\80\TOO LS\BINN;%SYSTEMROOT%\syste[vbcol=seagreen]
van[vbcol=seagreen]
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A[vbcol=seagreen]
RegAddValue(Name=TypesSupported,Value=#255,)[vbcol=seagreen]
RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~[vbcol=seagreen]
RegAddValue(Name=EventMessageFile,Value=C:\PROFEL~ 2\MSSQL$~1\Binn\RESOUR~1\1[vbcol=seagreen]
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO[vbcol=seagreen]
RegAddValue(Name=CategoryMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~[vbcol=seagreen]
RegRemoveValue(Name=CategoryCount,Value=#8,)[vbcol=seagreen]
RegRemoveValue(Name=Language,Value=#1043,)[vbcol=seagreen]
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A[vbcol=seagreen]
RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~[vbcol=seagreen]
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO[vbcol=seagreen]
RegRemoveValue(Name=CategoryCount,Value=#8,)[vbcol=seagreen]
|||Hi Peter,
Thanks for the reply. We have identical scenarios! I upgraded from ME to XP
Home, then upgraded again to XP Pro, SP2. I will take a look at the link you
posted, but it appears that I am probably headed toward the same conclusion
you reached - a complete reinstall of XP!
Thanks again and good luck!
"Peter Proost" wrote:
> Hi Stephen,
> I got it to work, but hold your breath, only after reinstalling windows
> because it had something to do with corrupted performance counters in the
> registry. I tried evertyhting in this link
> http://support.microsoft.com/default...microsoft.com:
> 80/support/kb/articles/q315/0/83.asp&NoWebContent=1
> but I didn't get it to work, just for your info the pc was an upgraded one,
> I upgraded it from me to 2000 I think there went something wrong there.
> Maybe this link can help you
> greetz Peter
>
> "Stephen Bishop" <StephenBishop@.discussions.microsoft.com> schreef in
> bericht news:9197FA53-F560-4CDC-847E-E81D354D1CE5@.microsoft.com...
> XP
> point
> to
> parameters
> have
> one
> install
> the
> explorer 6
> value
> 3
> are
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=TypesSupported,Value=#255,)
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=TypesSupported,Value=#255,)
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> bijwerken
> SQL
> registreren
> Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
> not
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
> not
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
> not
> van
> ServiceInstall(Name=SQLAgent$PFD,DisplayName=SQLAg ent$PFD,ImagePath=C:\Profe
> ServiceInstall(Name=MSSQL$PFD,DisplayName=MSSQL$PF D,ImagePath=C:\ProfelExec\
> MSSQL$PFD\Binn\sqlservr.exe -sPFD,ServiceType=16,StartType=2,ErrorControl=1,
> CustomActionSchedule(Action=InstallPerfMon.2D02443 E_7002_4C0B_ABC9_EAB2C0643
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sq
> Header(Signature=1397708873,Version=200,Timestamp= 846618063,LangId=1043,Plat
> form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMi norVersion=4,ScriptAttribu
> RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Terugdraai-actie:,
> met
> ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Mi
> Engine,PackageName=SqlRun01.msi,Language=1043,Vers ion=134218489,Assignment=1
> van
> ServiceControl(,Name=MSSQL$PFD,Action=8,,)
> ServiceControl(,Name=SQLAgent$PFD,Action=8,,)
> registreren
> TypeLibraryUnregister(,,FilePath=C:\Program
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
> not
> TypeLibraryUnregister(,,FilePath=C:\Program
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
> not
> TypeLibraryUnregister(,,FilePath=C:\Program
> Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
> not
> bijwerken
> RegAddValue(Name=PATH,Value=#%C:\PROGRA~1\MICROS~1 \OFFICE;%SYSTEMROOT%;%SYST
> Server\80\Tools\Binn\";C:\PROGRA~1\MICROS~5\80\TOO LS\BINN;%SYSTEMROOT%\syste
> van
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> RegAddValue(Name=TypesSupported,Value=#255,)
> RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> RegAddValue(Name=EventMessageFile,Value=C:\PROFEL~ 2\MSSQL$~1\Binn\RESOUR~1\1
> RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
> RegAddValue(Name=CategoryMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> RegRemoveValue(Name=CategoryCount,Value=#8,)
> RegRemoveValue(Name=Language,Value=#1043,)
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
> RegRemoveValue(Name=CategoryCount,Value=#8,)
>
>
I've installed msde already about 20times and they all went ok, except one
but that had to do with file and printer sharing. Now I'm trying to install
it on win 2000 sp4 like all the others, but I can't get it to install, the
pc has got file and printer sharing enabled, it has got internet explorer 6
sp1, I checked HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Component Set
Value name: InstanceComponentSet.x Value and it's emtpy, there's no value
name: InstanceComponentSet.x
I already searched on google and something that seems to be returning is
that I should post the lines from the log file where I find return value 3
so here they are with some lines that are in front and some lines that are
behind it, (btw you won't find return value 3 but you have to search for
retourwaarde 3, it logs some words in dutch)
Any help would be very welcome
thanks in advance Peter
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: CategoryCount, Waarde: #8
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
urces\1043\sqlevn70.rll,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: CategoryMessageFile, Waarde:
C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1043\sqlevn70.r ll
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
es\1043\sqlevn70.rll,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: EventMessageFile, Waarde:
C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1043\sqlevn70.r ll
MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: TypesSupported, Waarde: #255
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\PFD\MSSQLServer\CurrentVersion,,BinaryType= 0)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=Language,Value=#1043,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\PFD\MSSQLServer\CurrentVersion, Naam: Language, Waarde: #1043
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
pplication\PFD,,BinaryType=0)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=CategoryCount,Value=#8,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: CategoryCount, Waarde: #8
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
urces\1033\sqlevn70.rll,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: CategoryMessageFile, Waarde:
C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70.r ll
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
es\1033\sqlevn70.rll,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: EventMessageFile, Waarde:
C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70.r ll
MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
WriteRegistryValues: Sleutel:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
D, Naam: TypesSupported, Waarde: #255
MSI (s) (7C:B0): Executing op:
ActionStart(Name=WriteEnvironmentStrings,Descripti on=Bezig met het bijwerken
van omgevingsstrings,Template=Naam: , waarde: , actie )
Actie 11:48:29: WriteEnvironmentStrings. Bezig met het bijwerken van
omgevingsstrings
MSI (s) (7C:B0): Executing op:
ProgressTotal(Total=1,Type=1,ByteEquivalent=13200)
MSI (s) (7C:B0): Executing op:
UpdateEnvironmentStrings(Name=PATH,Value=C:\Progra m Files\Microsoft SQL
Server\80\Tools\Binn\,Delimiter=;,Action=161061273 8,)
WriteEnvironmentStrings: Naam: PATH, waarde: C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\, actie 1610612738
MSI (s) (7C:B0): Executing op:
ActionStart(Name=RegisterTypeLibraries,Description =Bezig met het registreren
van typebibliotheken,Template=Bibliotheek-id: )
Actie 11:48:29: RegisterTypeLibraries. Bezig met het registreren van
typebibliotheken
MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
,Version=-2147483648,,Language=0,,BinaryType=0)
RegisterTypeLibraries: Bibliotheek-id:
{10010001-E260-11CF-AE68-00AA004A34D5}
MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
context. Path is ''
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
,Version=-2147483648,,Language=0,,BinaryType=0)
RegisterTypeLibraries: Bibliotheek-id:
{10010001-EB1C-11CF-AE6E-00AA004A34D5}
MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
context. Path is ''
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
},Version=-2147483648,,Language=0,,BinaryType=0)
RegisterTypeLibraries: Bibliotheek-id:
{10010200-740B-11D0-AE7B-00AA004A34D5}
MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
context. Path is ''
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op:
ActionStart(Name=InstallServices,Description=Bezig met het installeren van
nieuwe services,Template=Service: )
Actie 11:48:30: InstallServices. Bezig met het installeren van nieuwe
services
MSI (s) (7C:B0): Executing op:
ProgressTotal(Total=2,Type=1,ByteEquivalent=130000 0)
MSI (s) (7C:B0): Executing op:
ServiceInstall(Name=SQLAgent$PFD,DisplayName=SQLAg ent$PFD,ImagePath=C:\Profe
lExec\MSSQL$PFD\Binn\sqlagent.EXE -i
PFD,ServiceType=16,StartType=3,ErrorControl=1,,Dep endencies=MSSQL$PFD
MSI (s) (7C:B0): Executing op:
ServiceInstall(Name=MSSQL$PFD,DisplayName=MSSQL$PF D,ImagePath=C:\ProfelExec\
MSSQL$PFD\Binn\sqlservr.exe -sPFD,ServiceType=16,StartType=2,ErrorControl=1,
,,,,,)
MSI (s) (7C:B0): Executing op:
ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
Actie 11:48:32: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B.
MSI (s) (7C:B0): Executing op:
CustomActionSchedule(Action=InstallPerfMon.2D02443 E_7002_4C0B_ABC9_EAB2C0643
97B,ActionType=1025,Source=BinaryData,Target=Insta llPerfMon,)
MSI (s) (7C:B0): Creating MSIHANDLE (496) of type 790536 for thread 688
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
TempFolder is
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sq
lcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallPerfMon
Registering performance counters from sqlctr.ini
PerfmonLoad routine returned error code 6
Actie beindigd 11:48:34: InstallFinalize. Retourwaarde 3.
MSI (s) (7C:B0): User policy value 'DisableRollback' is 0
MSI (s) (7C:B0): Machine policy value 'DisableRollback' is 0
MSI (s) (7C:B0): Executing op:
Header(Signature=1397708873,Version=200,Timestamp= 846618063,LangId=1043,Plat
form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMi norVersion=4,ScriptAttribu
tes=1)
MSI (s) (7C:B0): Executing op: DialogInfo(Type=0,Argument=1043)
MSI (s) (7C:B0): Executing op: DialogInfo(Type=1,Argument=Microsoft SQL
Server Desktop Engine)
MSI (s) (7C:B0): Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Terugdraai-actie:,
RollbackTemplate=,CleanupAction=RollbackCleanup,Cl eanupDescription=Bezig met
het verwijderen van reservekopiebestanden,CleanupTemplate=Bestand: [
1])
Actie 11:48:34: Rollback. Terugdraai-actie:
Rollback: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B
MSI (s) (7C:B0): Executing op:
ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
MSI (s) (7C:B0): Executing op:
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Mi
crosoft SQL Server Desktop
Engine,PackageName=SqlRun01.msi,Language=1043,Vers ion=134218489,Assignment=1
,ObsoleteArg=0,,,PackageCode={D29DCF7A-8199-4
373-BA0D-2F3635EC940C},,,InstanceType=0)
Rollback: Bezig met het installeren van nieuwe services
MSI (s) (7C:B0): Executing op:
ActionStart(Name=InstallServices,Description=Bezig met het installeren van
nieuwe services,Template=Service: )
MSI (s) (7C:B0): Executing op: ServiceControl(,Name=MSSQL$PFD,Action=8,,)
MSI (s) (7C:B0): Executing op: ServiceControl(,Name=SQLAgent$PFD,Action=8,,)
Rollback: Bezig met het registreren van typebibliotheken
MSI (s) (7C:B0): Executing op:
ActionStart(Name=RegisterTypeLibraries,Description =Bezig met het registreren
van typebibliotheken,Template=Bibliotheek-id: )
MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
},Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (7C:B0): Note: 1: 1402 2:
UNKNOWN\TypeLib\{10010200-740B-11D0-AE7B-00AA004A34D5}\0.0\0\win32 3: 2
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
,Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (7C:B0): Note: 1: 1402 2:
UNKNOWN\TypeLib\{10010001-EB1C-11CF-AE6E-00AA004A34D5}\0.0\0\win32 3: 2
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
Files\Microsoft SQL
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
,Version=-2147483648,,Language=0,,BinaryType=0)
MSI (s) (7C:B0): Note: 1: 1402 2:
UNKNOWN\TypeLib\{10010001-E260-11CF-AE68-00AA004A34D5}\0.0\0\win32 3: 2
MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
impersonated.
MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
Rollback: Bezig met het bijwerken van omgevingsstrings
MSI (s) (7C:B0): Executing op:
ActionStart(Name=WriteEnvironmentStrings,Descripti on=Bezig met het bijwerken
van omgevingsstrings,Template=Naam: , waarde: , actie )
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=System\CurrentControlSet\Control\Se ssion
Manager\Environment,,)
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=PATH,Value=#%C:\PROGRA~1\MICROS~1 \OFFICE;%SYSTEMROOT%;%SYST
EMROOT%\COMMAND;"C:\Program Files\Microsoft SQL
Server\80\Tools\Binn\";C:\PROGRA~1\MICROS~5\80\TOO LS\BINN;%SYSTEMROOT%\syste
m32;%SYSTEMROOT%\system3
2\WBEM,)
Rollback: Bezig met het schrijven van systeemregisterwaarden
MSI (s) (7C:B0): Executing op:
ActionStart(Name=WriteRegistryValues,Description=B ezig met het schrijven van
systeemregisterwaarden,Template=Sleutel: , Naam: , Waarde: )
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
pplication\PFD,,BinaryType=0)
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=TypesSupported,Value=#255,)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
1\1033\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=EventMessageFile,Value=C:\PROFEL~ 2\MSSQL$~1\Binn\RESOUR~1\1
043\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
UR~1\1033\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op:
RegAddValue(Name=CategoryMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
1\1043\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=CategoryCount,Value=#8,)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=CategoryCount,Value=#8,)
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
Server\PFD\MSSQLServer\CurrentVersion,,BinaryType= 0)
MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=Language,Value=#1043,)
MSI (s) (7C:B0): Executing op: RegAddValue(Name=Language,Value=#1043,)
MSI (s) (7C:B0): Executing op:
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
pplication\PFD,,BinaryType=0)
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=TypesSupported,Value=#255,)
MSI (s) (7C:B0): Executing op: RegCreateKey()
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
1\1043\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op: RegCreateKey()
MSI (s) (7C:B0): Executing op:
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
UR~1\1043\sqlevn70.rll,)
MSI (s) (7C:B0): Executing op: RegCreateKey()
MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=CategoryCount,Value=#8,)
MSI (s) (7C:B0): Executing op: RegRemoveKey()
Peter,
I have exactly the same problem. I cannot install MSDE 2000 on a Windows XP
Pro SP2 machine. The install rolls back every time at exactly the same point
as yours. I posted here but did not get the answer. It may have something to
do with with manually deleting registry keys and Windows Installer parameters
to enable a "clean" install. I thought I did all the necessary steps but have
never been able to make it work. I will be watching your replies with
interest to see if you are able to get it installed.
Good luck!
"Peter Proost" wrote:
> Hi Group,
> I've installed msde already about 20times and they all went ok, except one
> but that had to do with file and printer sharing. Now I'm trying to install
> it on win 2000 sp4 like all the others, but I can't get it to install, the
> pc has got file and printer sharing enabled, it has got internet explorer 6
> sp1, I checked HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\Component Set
> Value name: InstanceComponentSet.x Value and it's emtpy, there's no value
> name: InstanceComponentSet.x
> I already searched on google and something that seems to be returning is
> that I should post the lines from the log file where I find return value 3
> so here they are with some lines that are in front and some lines that are
> behind it, (btw you won't find return value 3 but you have to search for
> retourwaarde 3, it logs some words in dutch)
> Any help would be very welcome
> thanks in advance Peter
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: CategoryCount, Waarde: #8
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
> urces\1043\sqlevn70.rll,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: CategoryMessageFile, Waarde:
> C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1043\sqlevn70.r ll
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
> es\1043\sqlevn70.rll,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: EventMessageFile, Waarde:
> C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1043\sqlevn70.r ll
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: TypesSupported, Waarde: #255
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
> Server\PFD\MSSQLServer\CurrentVersion,,BinaryType= 0)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=Language,Value=#1043,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
> Server\PFD\MSSQLServer\CurrentVersion, Naam: Language, Waarde: #1043
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> pplication\PFD,,BinaryType=0)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=CategoryCount,Value=#8,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: CategoryCount, Waarde: #8
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
> urces\1033\sqlevn70.rll,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: CategoryMessageFile, Waarde:
> C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70.r ll
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
> es\1033\sqlevn70.rll,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: EventMessageFile, Waarde:
> C:\PROFEL~2\MSSQL$~1\Binn\RESOUR~1\1033\sqlevn70.r ll
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
> WriteRegistryValues: Sleutel:
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> D, Naam: TypesSupported, Waarde: #255
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=WriteEnvironmentStrings,Descripti on=Bezig met het bijwerken
> van omgevingsstrings,Template=Naam: , waarde: , actie )
> Actie 11:48:29: WriteEnvironmentStrings. Bezig met het bijwerken van
> omgevingsstrings
> MSI (s) (7C:B0): Executing op:
> ProgressTotal(Total=1,Type=1,ByteEquivalent=13200)
> MSI (s) (7C:B0): Executing op:
> UpdateEnvironmentStrings(Name=PATH,Value=C:\Progra m Files\Microsoft SQL
> Server\80\Tools\Binn\,Delimiter=;,Action=161061273 8,)
> WriteEnvironmentStrings: Naam: PATH, waarde: C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\, actie 1610612738
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=RegisterTypeLibraries,Description =Bezig met het registreren
> van typebibliotheken,Template=Bibliotheek-id: )
> Actie 11:48:29: RegisterTypeLibraries. Bezig met het registreren van
> typebibliotheken
> MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
> ,Version=-2147483648,,Language=0,,BinaryType=0)
> RegisterTypeLibraries: Bibliotheek-id:
> {10010001-E260-11CF-AE68-00AA004A34D5}
> MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
> context. Path is ''
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
> ,Version=-2147483648,,Language=0,,BinaryType=0)
> RegisterTypeLibraries: Bibliotheek-id:
> {10010001-EB1C-11CF-AE6E-00AA004A34D5}
> MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
> context. Path is ''
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op: TypeLibraryRegister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
> },Version=-2147483648,,Language=0,,BinaryType=0)
> RegisterTypeLibraries: Bibliotheek-id:
> {10010200-740B-11D0-AE7B-00AA004A34D5}
> MSI (s) (7C:B0): QueryPathOfRegTypeLib returned -2147319779 in local
> context. Path is ''
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=InstallServices,Description=Bezig met het installeren van
> nieuwe services,Template=Service: )
> Actie 11:48:30: InstallServices. Bezig met het installeren van nieuwe
> services
> MSI (s) (7C:B0): Executing op:
> ProgressTotal(Total=2,Type=1,ByteEquivalent=130000 0)
> MSI (s) (7C:B0): Executing op:
> ServiceInstall(Name=SQLAgent$PFD,DisplayName=SQLAg ent$PFD,ImagePath=C:\Profe
> lExec\MSSQL$PFD\Binn\sqlagent.EXE -i
> PFD,ServiceType=16,StartType=3,ErrorControl=1,,Dep endencies=MSSQL$PFD
> MSI (s) (7C:B0): Executing op:
> ServiceInstall(Name=MSSQL$PFD,DisplayName=MSSQL$PF D,ImagePath=C:\ProfelExec\
> MSSQL$PFD\Binn\sqlservr.exe -sPFD,ServiceType=16,StartType=2,ErrorControl=1,
> ,,,,,)
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
> Actie 11:48:32: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B.
> MSI (s) (7C:B0): Executing op:
> CustomActionSchedule(Action=InstallPerfMon.2D02443 E_7002_4C0B_ABC9_EAB2C0643
> 97B,ActionType=1025,Source=BinaryData,Target=Insta llPerfMon,)
> MSI (s) (7C:B0): Creating MSIHANDLE (496) of type 790536 for thread 688
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> TempFolder is
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sq
> lcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
> Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
> Starting custom action InstallPerfMon
> Registering performance counters from sqlctr.ini
> PerfmonLoad routine returned error code 6
> Actie be?indigd 11:48:34: InstallFinalize. Retourwaarde 3.
> MSI (s) (7C:B0): User policy value 'DisableRollback' is 0
> MSI (s) (7C:B0): Machine policy value 'DisableRollback' is 0
> MSI (s) (7C:B0): Executing op:
> Header(Signature=1397708873,Version=200,Timestamp= 846618063,LangId=1043,Plat
> form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMi norVersion=4,ScriptAttribu
> tes=1)
> MSI (s) (7C:B0): Executing op: DialogInfo(Type=0,Argument=1043)
> MSI (s) (7C:B0): Executing op: DialogInfo(Type=1,Argument=Microsoft SQL
> Server Desktop Engine)
> MSI (s) (7C:B0): Executing op:
> RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Terugdraai-actie:,
> RollbackTemplate=,CleanupAction=RollbackCleanup,Cl eanupDescription=Bezig met
> het verwijderen van reservekopiebestanden,CleanupTemplate=Bestand: [
> 1])
> Actie 11:48:34: Rollback. Terugdraai-actie:
> Rollback: InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=InstallPerfMon.2D02443E_7002_4C0B _ABC9_EAB2C064397B,,)
> MSI (s) (7C:B0): Executing op:
> ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Mi
> crosoft SQL Server Desktop
> Engine,PackageName=SqlRun01.msi,Language=1043,Vers ion=134218489,Assignment=1
> ,ObsoleteArg=0,,,PackageCode={D29DCF7A-8199-4
> 373-BA0D-2F3635EC940C},,,InstanceType=0)
> Rollback: Bezig met het installeren van nieuwe services
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=InstallServices,Description=Bezig met het installeren van
> nieuwe services,Template=Service: )
> MSI (s) (7C:B0): Executing op: ServiceControl(,Name=MSSQL$PFD,Action=8,,)
> MSI (s) (7C:B0): Executing op: ServiceControl(,Name=SQLAgent$PFD,Action=8,,)
> Rollback: Bezig met het registreren van typebibliotheken
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=RegisterTypeLibraries,Description =Bezig met het registreren
> van typebibliotheken,Template=Bibliotheek-id: )
> MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
> },Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (7C:B0): Note: 1: 1402 2:
> UNKNOWN\TypeLib\{10010200-740B-11D0-AE7B-00AA004A34D5}\0.0\0\win32 3: 2
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
> ,Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (7C:B0): Note: 1: 1402 2:
> UNKNOWN\TypeLib\{10010001-EB1C-11CF-AE6E-00AA004A34D5}\0.0\0\win32 3: 2
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> MSI (s) (7C:B0): Executing op: TypeLibraryUnregister(,,FilePath=C:\Program
> Files\Microsoft SQL
> Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
> ,Version=-2147483648,,Language=0,,BinaryType=0)
> MSI (s) (7C:B0): Note: 1: 1402 2:
> UNKNOWN\TypeLib\{10010001-E260-11CF-AE68-00AA004A34D5}\0.0\0\win32 3: 2
> MSI (s) (7C:B0): CMsiServices::ProcessTypeLibrary runs in local context, not
> impersonated.
> MSI (s) (7C:B0): ProcessTypeLibraryCore returns: 0. (0 means OK)
> Rollback: Bezig met het bijwerken van omgevingsstrings
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=WriteEnvironmentStrings,Descripti on=Bezig met het bijwerken
> van omgevingsstrings,Template=Naam: , waarde: , actie )
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=System\CurrentControlSet\Control\Se ssion
> Manager\Environment,,)
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=PATH,Value=#%C:\PROGRA~1\MICROS~1 \OFFICE;%SYSTEMROOT%;%SYST
> EMROOT%\COMMAND;"C:\Program Files\Microsoft SQL
> Server\80\Tools\Binn\";C:\PROGRA~1\MICROS~5\80\TOO LS\BINN;%SYSTEMROOT%\syste
> m32;%SYSTEMROOT%\system3
> 2\WBEM,)
> Rollback: Bezig met het schrijven van systeemregisterwaarden
> MSI (s) (7C:B0): Executing op:
> ActionStart(Name=WriteRegistryValues,Description=B ezig met het schrijven van
> systeemregisterwaarden,Template=Sleutel: , Naam: , Waarde: )
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> pplication\PFD,,BinaryType=0)
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=TypesSupported,Value=#255,)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=TypesSupported,Value=#255,)
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> 1\1033\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=EventMessageFile,Value=C:\PROFEL~ 2\MSSQL$~1\Binn\RESOUR~1\1
> 043\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
> UR~1\1033\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op:
> RegAddValue(Name=CategoryMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> 1\1043\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=CategoryCount,Value=#8,)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=CategoryCount,Value=#8,)
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SOFTWARE\Microsoft\Microsoft SQL
> Server\PFD\MSSQLServer\CurrentVersion,,BinaryType= 0)
> MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=Language,Value=#1043,)
> MSI (s) (7C:B0): Executing op: RegAddValue(Name=Language,Value=#1043,)
> MSI (s) (7C:B0): Executing op:
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> pplication\PFD,,BinaryType=0)
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=TypesSupported,Value=#255,)
> MSI (s) (7C:B0): Executing op: RegCreateKey()
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> 1\1043\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op: RegCreateKey()
> MSI (s) (7C:B0): Executing op:
> RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
> UR~1\1043\sqlevn70.rll,)
> MSI (s) (7C:B0): Executing op: RegCreateKey()
> MSI (s) (7C:B0): Executing op: RegRemoveValue(Name=CategoryCount,Value=#8,)
> MSI (s) (7C:B0): Executing op: RegRemoveKey()
>
>
|||Hi Stephen,
I got it to work, but hold your breath, only after reinstalling windows
because it had something to do with corrupted performance counters in the
registry. I tried evertyhting in this link
http://support.microsoft.com/default...microsoft.com:
80/support/kb/articles/q315/0/83.asp&NoWebContent=1
but I didn't get it to work, just for your info the pc was an upgraded one,
I upgraded it from me to 2000 I think there went something wrong there.
Maybe this link can help you
greetz Peter
"Stephen Bishop" <StephenBishop@.discussions.microsoft.com> schreef in
bericht news:9197FA53-F560-4CDC-847E-E81D354D1CE5@.microsoft.com...
> Peter,
> I have exactly the same problem. I cannot install MSDE 2000 on a Windows
XP
> Pro SP2 machine. The install rolls back every time at exactly the same
point
> as yours. I posted here but did not get the answer. It may have something
to
> do with with manually deleting registry keys and Windows Installer
parameters
> to enable a "clean" install. I thought I did all the necessary steps but
have[vbcol=seagreen]
> never been able to make it work. I will be watching your replies with
> interest to see if you are able to get it installed.
> Good luck!
> "Peter Proost" wrote:
one[vbcol=seagreen]
install[vbcol=seagreen]
the[vbcol=seagreen]
explorer 6[vbcol=seagreen]
value[vbcol=seagreen]
3[vbcol=seagreen]
are[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=TypesSupported,Value=#255,)[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
RegAddValue(Name=TypesSupported,Value=#255,)[vbcol=seagreen]
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF[vbcol=seagreen]
bijwerken[vbcol=seagreen]
SQL[vbcol=seagreen]
registreren[vbcol=seagreen]
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}[vbcol=seagreen]
not[vbcol=seagreen]
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}[vbcol=seagreen]
not[vbcol=seagreen]
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5[vbcol=seagreen]
not[vbcol=seagreen]
van[vbcol=seagreen]
ServiceInstall(Name=SQLAgent$PFD,DisplayName=SQLAg ent$PFD,ImagePath=C:\Profe[vbcol=seagreen]
ServiceInstall(Name=MSSQL$PFD,DisplayName=MSSQL$PF D,ImagePath=C:\ProfelExec\[vbcol=seagreen]
MSSQL$PFD\Binn\sqlservr.exe -sPFD,ServiceType=16,StartType=2,ErrorControl=1,[vbcol=seagreen]
CustomActionSchedule(Action=InstallPerfMon.2D02443 E_7002_4C0B_ABC9_EAB2C0643[vbcol=seagreen]
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\[vbcol=seagreen]
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sq[vbcol=seagreen]
Header(Signature=1397708873,Version=200,Timestamp= 846618063,LangId=1043,Plat[vbcol=seagreen]
form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMi norVersion=4,ScriptAttribu[vbcol=seagreen]
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Terugdraai-actie:,[vbcol=seagreen]
met[vbcol=seagreen]
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Mi[vbcol=seagreen]
Engine,PackageName=SqlRun01.msi,Language=1043,Vers ion=134218489,Assignment=1[vbcol=seagreen]
van[vbcol=seagreen]
ServiceControl(,Name=MSSQL$PFD,Action=8,,)[vbcol=seagreen]
ServiceControl(,Name=SQLAgent$PFD,Action=8,,)[vbcol=seagreen]
registreren[vbcol=seagreen]
TypeLibraryUnregister(,,FilePath=C:\Program[vbcol=seagreen]
Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5[vbcol=seagreen]
not[vbcol=seagreen]
TypeLibraryUnregister(,,FilePath=C:\Program[vbcol=seagreen]
Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}[vbcol=seagreen]
not[vbcol=seagreen]
TypeLibraryUnregister(,,FilePath=C:\Program[vbcol=seagreen]
Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}[vbcol=seagreen]
not[vbcol=seagreen]
bijwerken[vbcol=seagreen]
RegAddValue(Name=PATH,Value=#%C:\PROGRA~1\MICROS~1 \OFFICE;%SYSTEMROOT%;%SYST[vbcol=seagreen]
Server\80\Tools\Binn\";C:\PROGRA~1\MICROS~5\80\TOO LS\BINN;%SYSTEMROOT%\syste[vbcol=seagreen]
van[vbcol=seagreen]
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A[vbcol=seagreen]
RegAddValue(Name=TypesSupported,Value=#255,)[vbcol=seagreen]
RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~[vbcol=seagreen]
RegAddValue(Name=EventMessageFile,Value=C:\PROFEL~ 2\MSSQL$~1\Binn\RESOUR~1\1[vbcol=seagreen]
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO[vbcol=seagreen]
RegAddValue(Name=CategoryMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~[vbcol=seagreen]
RegRemoveValue(Name=CategoryCount,Value=#8,)[vbcol=seagreen]
RegRemoveValue(Name=Language,Value=#1043,)[vbcol=seagreen]
RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A[vbcol=seagreen]
RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~[vbcol=seagreen]
RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO[vbcol=seagreen]
RegRemoveValue(Name=CategoryCount,Value=#8,)[vbcol=seagreen]
|||Hi Peter,
Thanks for the reply. We have identical scenarios! I upgraded from ME to XP
Home, then upgraded again to XP Pro, SP2. I will take a look at the link you
posted, but it appears that I am probably headed toward the same conclusion
you reached - a complete reinstall of XP!
Thanks again and good luck!
"Peter Proost" wrote:
> Hi Stephen,
> I got it to work, but hold your breath, only after reinstalling windows
> because it had something to do with corrupted performance counters in the
> registry. I tried evertyhting in this link
> http://support.microsoft.com/default...microsoft.com:
> 80/support/kb/articles/q315/0/83.asp&NoWebContent=1
> but I didn't get it to work, just for your info the pc was an upgraded one,
> I upgraded it from me to 2000 I think there went something wrong there.
> Maybe this link can help you
> greetz Peter
>
> "Stephen Bishop" <StephenBishop@.discussions.microsoft.com> schreef in
> bericht news:9197FA53-F560-4CDC-847E-E81D354D1CE5@.microsoft.com...
> XP
> point
> to
> parameters
> have
> one
> install
> the
> explorer 6
> value
> 3
> are
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=TypesSupported,Value=#255,)
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=CategoryMessageFile,Value=C:\Prof elExec\MSSQL$PFD\Binn\Reso
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=EventMessageFile,Value=C:\ProfelE xec\MSSQL$PFD\Binn\Resourc
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> RegAddValue(Name=TypesSupported,Value=#255,)
> HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\EventLog\Application\PF
> bijwerken
> SQL
> registreren
> Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
> not
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
> not
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
> not
> van
> ServiceInstall(Name=SQLAgent$PFD,DisplayName=SQLAg ent$PFD,ImagePath=C:\Profe
> ServiceInstall(Name=MSSQL$PFD,DisplayName=MSSQL$PF D,ImagePath=C:\ProfelExec\
> MSSQL$PFD\Binn\sqlservr.exe -sPFD,ServiceType=16,StartType=2,ErrorControl=1,
> CustomActionSchedule(Action=InstallPerfMon.2D02443 E_7002_4C0B_ABC9_EAB2C0643
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\sq
> Header(Signature=1397708873,Version=200,Timestamp= 846618063,LangId=1043,Plat
> form=0,ScriptType=2,ScriptMajorVersion=21,ScriptMi norVersion=4,ScriptAttribu
> RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Terugdraai-actie:,
> met
> ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Mi
> Engine,PackageName=SqlRun01.msi,Language=1043,Vers ion=134218489,Assignment=1
> van
> ServiceControl(,Name=MSSQL$PFD,Action=8,,)
> ServiceControl(,Name=SQLAgent$PFD,Action=8,,)
> registreren
> TypeLibraryUnregister(,,FilePath=C:\Program
> Server\80\Tools\Binn\dtspump.DLL,LibID={10010200-740B-11D0-AE7B-00AA004A34D5
> not
> TypeLibraryUnregister(,,FilePath=C:\Program
> Server\80\Tools\Binn\dtspkg.DLL,LibID={10010001-EB1C-11CF-AE6E-00AA004A34D5}
> not
> TypeLibraryUnregister(,,FilePath=C:\Program
> Server\80\Tools\Binn\SQLDMO.dll,LibID={10010001-E260-11CF-AE68-00AA004A34D5}
> not
> bijwerken
> RegAddValue(Name=PATH,Value=#%C:\PROGRA~1\MICROS~1 \OFFICE;%SYSTEMROOT%;%SYST
> Server\80\Tools\Binn\";C:\PROGRA~1\MICROS~5\80\TOO LS\BINN;%SYSTEMROOT%\syste
> van
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> RegAddValue(Name=TypesSupported,Value=#255,)
> RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> RegAddValue(Name=EventMessageFile,Value=C:\PROFEL~ 2\MSSQL$~1\Binn\RESOUR~1\1
> RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
> RegAddValue(Name=CategoryMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> RegRemoveValue(Name=CategoryCount,Value=#8,)
> RegRemoveValue(Name=Language,Value=#1043,)
> RegOpenKey(Root=-2147483646,Key=SYSTEM\CurrentControlSet\Services\E ventLog\A
> RegRemoveValue(Name=EventMessageFile,Value=C:\PROF EL~2\MSSQL$~1\Binn\RESOUR~
> RegRemoveValue(Name=CategoryMessageFile,Value=C:\P ROFEL~2\MSSQL$~1\Binn\RESO
> RegRemoveValue(Name=CategoryCount,Value=#8,)
>
>
Subscribe to:
Posts (Atom)