MSDE SP4 installation problem

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.
jimI 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.com...
> 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
>

MSDE Productcode

Hello,
I am installing MSDE along with my app using the MS Toolkit. When I install MSDE and then my app, everything works fine. However if later I uninstall my app (not MSDE instance) and rerun the setup.exe, it disables my app setup saying that MSDE prerequis
ite has to be installed. But MSDE is already on my machine as I did not uninstall it.
Someone pointed out that the productcode should remain the same for the setup. But I never change it. It's a fixed GUID.
Any ideas anyone. Thanks
Dev,
This is a known issue with the RC build of the Toolkit. We'll be fixing it
for RTM.
Cheers,
Brian A. Randell
MCW Technologies
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:2A575001-D9A3-47EA-9142-C1E5546D3CD8@.microsoft.com...
> Hello,
> I am installing MSDE along with my app using the MS Toolkit. When I
install MSDE and then my app, everything works fine. However if later I
uninstall my app (not MSDE instance) and rerun the setup.exe, it disables my
app setup saying that MSDE prerequisite has to be installed. But MSDE is
already on my machine as I did not uninstall it.
> Someone pointed out that the productcode should remain the same for the
setup. But I never change it. It's a fixed GUID.
> Any ideas anyone. Thanks
|||Great, Thanks
|||On Tue, 27 Apr 2004 16:33:49 -0700, "Brian A. Randell"
<brianr@.nospam.mcwtech.com> wrote:

>Dev,
>This is a known issue with the RC build of the Toolkit. We'll be fixing it
>for RTM.
Any indication of when that might be?
|||Dates are a funny thing. They move. In time for Tech Ed US is our goal. But
as always, could be sooner or later.
Cheers,
Brian A. Randell
MCW Technologies
"Brady Kelly" <bkelly@.icom-it.co.za> wrote in message
news:e6iv80praetf3cp77legif9a1i4tloovre@.4ax.com... [vbcol=seagreen]
> On Tue, 27 Apr 2004 16:33:49 -0700, "Brian A. Randell"
> <brianr@.nospam.mcwtech.com> wrote:
it
> Any indication of when that might be?

MSDE patching

If I do a windows update, would MSDE get updated along with it or should I
download MSDE patches separately?
Thanks,
hi,
sai wrote:
> If I do a windows update, would MSDE get updated along with it or
> should I download MSDE patches separately?
>
at the moment, Windows Update does not provide a SQL Server/MSDE update
too... you have to manually install all required available service packs/hot
fixes..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.12.0 - DbaMgr ver 0.58.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE on machine with SQL Server

Hello,
A named instance of MSDE will be installed on our clients machines along with our VB.Net during the installation. Will this work fine even if the client already has SQL Server on his/her machine. I mean will the installation of named instance of MSDE wor
k smoothly even if SQL Server already exists. If yes, then does that apply for both SQL Server 7 & 2000. If no, then what should I do.
Thanks
dev
You should have no problems, as long as you are installing a uniquely named
instance. This is true even if SQL Server 7 is already installed on the
system.
Jim
"dev" <anonymous@.discussions.microsoft.com> wrote in message
news:B46C4961-748E-47E1-AD22-2A712100428F@.microsoft.com...
> Hello,
> A named instance of MSDE will be installed on our clients machines along
with our VB.Net during the installation. Will this work fine even if the
client already has SQL Server on his/her machine. I mean will the
installation of named instance of MSDE work smoothly even if SQL Server
already exists. If yes, then does that apply for both SQL Server 7 & 2000.
If no, then what should I do.
> Thanks
> dev
sql

MSDE Lockdown scripts

We are installing MSDE along with one of our applications.
But with the current security threats, we want to make sure
that the installed MSDE is secure. So is there any lock
down scripts available publicly that can be used for the same.
Thanks in Advance.
hi,
"Arunkumar Viswanathan" <anonymous@.discussions.microsoft.com> ha scritto nel
messaggio news:012101c4904c$0eea0af0$a401280a@.phx.gbl...
> We are installing MSDE along with one of our applications.
> But with the current security threats, we want to make sure
> that the installed MSDE is secure. So is there any lock
> down scripts available publicly that can be used for the same.
not that I'm aware of... anyway, MSDE installs by default disabling network
protocols and with Windows NT authentication only... you only have to set a
strong "sa" password...
this is the *standard*, and should be quite secure... but usually you will
need remote connections (which require TCP/IP or other preferred network
protocol to be enabled) ... if you do not need SQL Server authenticated
connections, you can go with the default "trusted" only...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Hi Andrea,
Thanks for replying. As you rightly said the we have to
provide a strong password to the sa user. But generally in
a stand alone MSDE installation some stored procedures are
given public previleges and that can cause problems with
advanced users. So if you of know of any lock down scripts
pls post the link here.
Thanks
Arunkumar

>--Original Message--
>not that I'm aware of... anyway, MSDE installs by default
disabling network
>protocols and with Windows NT authentication only... you
only have to set a
>strong "sa" password...
>this is the *standard*, and should be quite secure... but
usually you will
>need remote connections (which require TCP/IP or other
preferred network
>protocol to be enabled) ... if you do not need SQL Server
authenticated
>connections, you can go with the default "trusted" only...
>--
>Andrea Montanari (Microsoft MVP - SQL Server)
>http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
>DbaMgr2k ver 0.9.1 - DbaMgr ver 0.55.1
>(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE
2000 a visual
>interface)
>-- remove DMO to reply
>.
>
|||hi Arunkumar,
<anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:452d01c49052$8853d550$a601280a@.phx.gbl...
> Hi Andrea,
> Thanks for replying. As you rightly said the we have to
> provide a strong password to the sa user. But generally in
> a stand alone MSDE installation some stored procedures are
> given public previleges and that can cause problems with
> advanced users. So if you of know of any lock down scripts
> pls post the link here.
again... unfortunately I do not know one :-(
but, again, it all depends on what you want to secure...
if you mean system stored procedures, usually (at least the problematic,
like xp_cmdshell and so on) they are "protected" requiring sysadmins
privileges
on the other side, if you mena your own procedures, it' up to you to remove
"guest" permission to them =;-D
so I usually remove guest login and deny public involvement... and I do
manage privileges in user's groups...
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