I can install instances of MSDE without any problem. But
for some reasons the password (or the instance) get
corrupted after I try to upsize a table from MS Access to
an existing database in MSDE (I'll stop doing this).
But now I have multiple instances which I would like to
clean up. Does anybody know how to uninstall them?
Thanks
Perry
Hi ,
You can use the following information to uninstall msde.
A)Remove the following registry:
1) Remove the following ID_Number from your MSDE 2.0 instance
HKEY_CLASSES_ROOT\Installer\Products\ID_Number
-- It has key value name 'ProductName' which displays the instance name.
For example, "ProductName" = Microsoft SQL Server Desktop Engine
(MYINSTANCE)
2)If you had patch applied on this MSDE 2.0 instance, you need to remove
ID_Number
for that MSDE 2.0 instance:
HKEY_CLASSES_ROOT\Installer\Patches\ID_Number
3) For MSDE 2.0 Default instance, remove
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
For MSDE 2.0 named instance, remove
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Your_instance_name
4)If you have the following key points to MSDE 2.0 productGUID, then remove
the
InstanceComponentSet.x
For example, HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL
Server\Component
SetInstanceComponentSet.x
-- For example, InstanceComponentSet.1 the has value matching the
productGUID of
sqlrun01.msi.
5)Remove :
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Uninstall\Produ
ctGUID
-- the Product GUID which refers to your MSDE 2.0 instance.
6)Remove the Sql server service key:
For MSDE 2.0 default instance, remove
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQLServer
For MSDE 2.0 named instance, remove
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\MSSQL$Your_Instance_Nam
e
7)Remove the Sql server agent service key:
For MSDE 2.0 default instance, remove
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLServerAgent
For MSDE 2.0 named instance, remove
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\SQLAgent$Your_Instance_
Name
B)Remove the MSDE 2.0 instance data and program install directory:
For example, G:\Program Files\Microsoft SQL
Server\MSSQL$Your_instanceName\data
For example, G:\Program Files\Microsoft SQL
Server\MSSQL$Your_instanceName\binn
Now rerun the msde setup from the command prompt
Girish Sundaram
This posting is provided "AS IS" with no warranties, and confers no rights.
Showing posts with label msde. Show all posts
Showing posts with label msde. Show all posts
Friday, March 30, 2012
Instance specified not valid
Hi,
I'm trying to install MSDE SP3 which I downloaded from MS at http://www.asp.net/msde/.
Following the instructions as best I can I unzipped the file into a Folder now called MSDE located on C: I then went to a command prompt and typed in the command given to start the install:
setup SAPWD=testsite SecurityMode=SQL
Hit enter and the installer started up and ran for a few secs and then came back with
The Instance named specified is invalid
There was no mention of including an instance name or the format for it.
Suggestions please?
Also, if I want to completly uninstall MSDE if I need to how would I do it?
Thanks,
BobWell, I had this message come up if I tried to run setup for the instance that was already on the system.
I used this setup to install msde on my machine.
setup instancename="netsdk" sapwd="your password for sa" securitymode=sql
Reason for using instance name netsdk was that it seems that SDK kit needs this instance to install pubs and nwind database.
After executing this i did not get any error messages but when I started service manager I could not see any servers listed. It took me solid two hours to come up with idea to look into error log and there it was.
2004-03-09 11:57:44.50 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 1)
2004-03-09 11:57:44.50 server Copyright (C) 1988-2002 Microsoft Corporation.
2004-03-09 11:57:44.50 server All rights reserved.
2004-03-09 11:57:44.50 server Server Process ID is 3456.
2004-03-09 11:57:44.50 server Logging SQL Server messages in file 'C:\Program Files\Microsoft SQL Server\MSSQL$NETSDK\LOG\ERRORLOG'.
2004-03-09 11:57:44.52 server SQL Server is starting at priority class 'normal'(2 CPUs detected).
2004-03-09 11:57:44.63 server SQL Server configured for thread mode processing.
2004-03-09 11:57:44.63 server Using dynamic lock allocation. [500] Lock Blocks, [1000] Lock Owner Blocks.
2004-03-09 11:57:44.63 spid2 Warning ******************
2004-03-09 11:57:44.63 spid2 SQL Server started in single user mode. Updates allowed to system catalogs.
2004-03-09 11:57:44.63 spid2 Starting up database 'master'.
2004-03-09 11:57:44.98 spid5 Starting up database 'model'.
2004-03-09 11:57:44.98 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-03-09 11:57:45.03 spid2 Server name is 'PC0491-EPITKA\NETSDK'.
2004-03-09 11:57:45.03 spid2 Skipping startup of clean database id 5
2004-03-09 11:57:45.03 spid2 Skipping startup of clean database id 6
2004-03-09 11:57:45.03 spid2 Starting up database 'msdb'.
2004-03-09 11:57:45.17 server SQL server listening on Shared Memory.
2004-03-09 11:57:45.17 server SQL Server is ready for client connections
2004-03-09 11:57:45.38 spid5 Clearing tempdb database.
2004-03-09 11:57:46.12 spid5 Starting up database 'tempdb'.
2004-03-09 11:57:46.20 spid2 Recovery complete.
2004-03-09 11:57:46.20 spid2 SQL global counter collection task is created.
2004-03-09 11:57:46.22 spid2 Warning: override, autoexec procedures skipped.
2004-03-09 11:57:56.94 spid51 Error: 15457, Severity: 0, State: 1
2004-03-09 11:57:56.94 spid51 Configuration option 'allow updates' changed from 0 to 1. Run the RECONFIGURE statement to install..
2004-03-09 11:57:57.08 spid51 Error: 15457, Severity: 0, State: 1
2004-03-09 11:57:57.08 spid51 Configuration option 'allow updates' changed from 1 to 0. Run the RECONFIGURE statement to install..
2004-03-09 11:57:57.34 spid2 SQL Server is terminating due to 'stop' request from Service Control Manager.
There is a line that says servername, I typed it in and I was able to start service. Log should be under c:\program files\microsoft sql server\mssql${your instance name}\log.
I am very new to windows world since I worked on Unix platform for past six years, so for you gurus out there this migth be something that does not need to be explained. Anyway I hope this helps.sql
Instance not showning up
Hello,
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed on the
network. Then there are four XP SP2 workstations that connect to the
databases on
(server1\manufacturing). Three of the workstations see the
(server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
What would cause other system to see the SQL instance fine but one system to
only see the //servername and not the last part of the instance?
Any help really appreciated!Christopher Knapp wrote:
> Hello,
> I have MSDE installed on the Win2003 server named 'server1' and it's
> instance is called 'manufacturing' so it's name should be (
> server1\manufacturing ). That is the only place SQL is installed on
> the network. Then there are four XP SP2 workstations that connect to
> the databases on
> (server1\manufacturing). Three of the workstations see the
> (server1\manufacturing ) when they look at available SQL instances.
> The fourth system , when looking for available SQL instances, sees
> (server1) but without the instance name (manufacturing).
> What would cause other system to see the SQL instance fine but one
> system to only see the //servername and not the last part of the
> instance?
> Any help really appreciated!
Can this PC connect to the server, despite no "seeing" it in whatever
utility you are using to browse for available servers?
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply!
This machine can connect to the server and onther workstation over the
network without any p roblems.
Chris
> Can this PC connect to the server, despite no "seeing" it in whatever
> utility you are using to browse for available servers?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Christopher Knapp wrote:
> Thank you for the reply!
> This machine can connect to the server and onther workstation over the
> network without any p roblems.
> Chris
Does that mean it's working properly or is not working properly?
David Gugick
Imceda Software
www.imceda.com
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed on the
network. Then there are four XP SP2 workstations that connect to the
databases on
(server1\manufacturing). Three of the workstations see the
(server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
What would cause other system to see the SQL instance fine but one system to
only see the //servername and not the last part of the instance?
Any help really appreciated!Christopher Knapp wrote:
> Hello,
> I have MSDE installed on the Win2003 server named 'server1' and it's
> instance is called 'manufacturing' so it's name should be (
> server1\manufacturing ). That is the only place SQL is installed on
> the network. Then there are four XP SP2 workstations that connect to
> the databases on
> (server1\manufacturing). Three of the workstations see the
> (server1\manufacturing ) when they look at available SQL instances.
> The fourth system , when looking for available SQL instances, sees
> (server1) but without the instance name (manufacturing).
> What would cause other system to see the SQL instance fine but one
> system to only see the //servername and not the last part of the
> instance?
> Any help really appreciated!
Can this PC connect to the server, despite no "seeing" it in whatever
utility you are using to browse for available servers?
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply!
This machine can connect to the server and onther workstation over the
network without any p roblems.
Chris
> Can this PC connect to the server, despite no "seeing" it in whatever
> utility you are using to browse for available servers?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Christopher Knapp wrote:
> Thank you for the reply!
> This machine can connect to the server and onther workstation over the
> network without any p roblems.
> Chris
Does that mean it's working properly or is not working properly?
David Gugick
Imceda Software
www.imceda.com
Instance not showning up
Hello,
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed on the
network. Then there are four XP SP2 workstations that connect to the
databases on
(server1\manufacturing). Three of the workstations see the
(server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
What would cause other system to see the SQL instance fine but one system to
only see the //servername and not the last part of the instance?
Any help really appreciated!
Christopher Knapp wrote:
> Hello,
> I have MSDE installed on the Win2003 server named 'server1' and it's
> instance is called 'manufacturing' so it's name should be (
> server1\manufacturing ). That is the only place SQL is installed on
> the network. Then there are four XP SP2 workstations that connect to
> the databases on
> (server1\manufacturing). Three of the workstations see the
> (server1\manufacturing ) when they look at available SQL instances.
> The fourth system , when looking for available SQL instances, sees
> (server1) but without the instance name (manufacturing).
> What would cause other system to see the SQL instance fine but one
> system to only see the //servername and not the last part of the
> instance?
> Any help really appreciated!
Can this PC connect to the server, despite no "seeing" it in whatever
utility you are using to browse for available servers?
David Gugick
Imceda Software
www.imceda.com
|||Thank you for the reply!
This machine can connect to the server and onther workstation over the
network without any p roblems.
Chris
> Can this PC connect to the server, despite no "seeing" it in whatever
> utility you are using to browse for available servers?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Christopher Knapp wrote:
> Thank you for the reply!
> This machine can connect to the server and onther workstation over the
> network without any p roblems.
> Chris
Does that mean it's working properly or is not working properly?
David Gugick
Imceda Software
www.imceda.com
sql
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed on the
network. Then there are four XP SP2 workstations that connect to the
databases on
(server1\manufacturing). Three of the workstations see the
(server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
What would cause other system to see the SQL instance fine but one system to
only see the //servername and not the last part of the instance?
Any help really appreciated!
Christopher Knapp wrote:
> Hello,
> I have MSDE installed on the Win2003 server named 'server1' and it's
> instance is called 'manufacturing' so it's name should be (
> server1\manufacturing ). That is the only place SQL is installed on
> the network. Then there are four XP SP2 workstations that connect to
> the databases on
> (server1\manufacturing). Three of the workstations see the
> (server1\manufacturing ) when they look at available SQL instances.
> The fourth system , when looking for available SQL instances, sees
> (server1) but without the instance name (manufacturing).
> What would cause other system to see the SQL instance fine but one
> system to only see the //servername and not the last part of the
> instance?
> Any help really appreciated!
Can this PC connect to the server, despite no "seeing" it in whatever
utility you are using to browse for available servers?
David Gugick
Imceda Software
www.imceda.com
|||Thank you for the reply!
This machine can connect to the server and onther workstation over the
network without any p roblems.
Chris
> Can this PC connect to the server, despite no "seeing" it in whatever
> utility you are using to browse for available servers?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>
|||Christopher Knapp wrote:
> Thank you for the reply!
> This machine can connect to the server and onther workstation over the
> network without any p roblems.
> Chris
Does that mean it's working properly or is not working properly?
David Gugick
Imceda Software
www.imceda.com
sql
Instance not showning up
Hello,
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed on the
network. Then there are four XP SP2 workstations that connect to the
databases on
(server1\manufacturing). Three of the workstations see the
(server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
What would cause other system to see the SQL instance fine but one system to
only see the //servername and not the last part of the instance?
Any help really appreciated!Christopher Knapp wrote:
> Hello,
> I have MSDE installed on the Win2003 server named 'server1' and it's
> instance is called 'manufacturing' so it's name should be (
> server1\manufacturing ). That is the only place SQL is installed on
> the network. Then there are four XP SP2 workstations that connect to
> the databases on
> (server1\manufacturing). Three of the workstations see the
> (server1\manufacturing ) when they look at available SQL instances.
> The fourth system , when looking for available SQL instances, sees
> (server1) but without the instance name (manufacturing).
> What would cause other system to see the SQL instance fine but one
> system to only see the //servername and not the last part of the
> instance?
> Any help really appreciated!
Can this PC connect to the server, despite no "seeing" it in whatever
utility you are using to browse for available servers?
--
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply!
This machine can connect to the server and onther workstation over the
network without any p roblems.
Chris
> Can this PC connect to the server, despite no "seeing" it in whatever
> utility you are using to browse for available servers?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Christopher Knapp wrote:
> Thank you for the reply!
> This machine can connect to the server and onther workstation over the
> network without any p roblems.
> Chris
Does that mean it's working properly or is not working properly?
--
David Gugick
Imceda Software
www.imceda.com
I have MSDE installed on the Win2003 server named 'server1' and it's
instance is called 'manufacturing' so it's name should be (
server1\manufacturing ). That is the only place SQL is installed on the
network. Then there are four XP SP2 workstations that connect to the
databases on
(server1\manufacturing). Three of the workstations see the
(server1\manufacturing ) when they look at available SQL instances. The
fourth system , when looking for available SQL instances, sees (server1) but
without the instance name (manufacturing).
What would cause other system to see the SQL instance fine but one system to
only see the //servername and not the last part of the instance?
Any help really appreciated!Christopher Knapp wrote:
> Hello,
> I have MSDE installed on the Win2003 server named 'server1' and it's
> instance is called 'manufacturing' so it's name should be (
> server1\manufacturing ). That is the only place SQL is installed on
> the network. Then there are four XP SP2 workstations that connect to
> the databases on
> (server1\manufacturing). Three of the workstations see the
> (server1\manufacturing ) when they look at available SQL instances.
> The fourth system , when looking for available SQL instances, sees
> (server1) but without the instance name (manufacturing).
> What would cause other system to see the SQL instance fine but one
> system to only see the //servername and not the last part of the
> instance?
> Any help really appreciated!
Can this PC connect to the server, despite no "seeing" it in whatever
utility you are using to browse for available servers?
--
David Gugick
Imceda Software
www.imceda.com|||Thank you for the reply!
This machine can connect to the server and onther workstation over the
network without any p roblems.
Chris
> Can this PC connect to the server, despite no "seeing" it in whatever
> utility you are using to browse for available servers?
> --
> David Gugick
> Imceda Software
> www.imceda.com
>|||Christopher Knapp wrote:
> Thank you for the reply!
> This machine can connect to the server and onther workstation over the
> network without any p roblems.
> Chris
Does that mean it's working properly or is not working properly?
--
David Gugick
Imceda Software
www.imceda.com
Instance NetSDK
Dear
I have a question about SQL Server / MSDE. Iâ'm trying install and to configure the documentation of the .NET Framework 1.1 but I have a problem because is necessary contain a instance: â'Local\NetSDKâ' (Local is the same the principal instance) second information about details of the configuration
Iâ'm working with Microsoft SQL Server 2000 â' Personal Edition and I have listed in SQL Server Service Manager only: â'Localâ'
How I make to create the instance: â'NetSDKâ'
Your
ThankI'm not sure why that SDK needs an instance of SQL Server with that
particular name, but I'd have thought it would create the instance during
it's installation...
Anyway, to create a named instance of SQL Server, you have to install it
again & you get the chance to provide the instance name during the
installation process.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Rogério Toledo" <anonymous@.discussions.microsoft.com> wrote in message
news:B75B10E3-3740-45BC-93D5-39158618C2D1@.microsoft.com...
> Dear,
> I have a question about SQL Server / MSDE. I'm trying install and to
configure the documentation of the .NET Framework 1.1 but I have a problem
because is necessary contain a instance: "Local\NetSDK" (Local is the same
the principal instance) second information about details of the
configuration.
> I'm working with Microsoft SQL Server 2000 - Personal Edition and I have
listed in SQL Server Service Manager only: "Local".
> How I make to create the instance: "NetSDK"?
> Yours
> Thanks
>
I have a question about SQL Server / MSDE. Iâ'm trying install and to configure the documentation of the .NET Framework 1.1 but I have a problem because is necessary contain a instance: â'Local\NetSDKâ' (Local is the same the principal instance) second information about details of the configuration
Iâ'm working with Microsoft SQL Server 2000 â' Personal Edition and I have listed in SQL Server Service Manager only: â'Localâ'
How I make to create the instance: â'NetSDKâ'
Your
ThankI'm not sure why that SDK needs an instance of SQL Server with that
particular name, but I'd have thought it would create the instance during
it's installation...
Anyway, to create a named instance of SQL Server, you have to install it
again & you get the chance to provide the instance name during the
installation process.
HTH
Regards,
Greg Linwood
SQL Server MVP
"Rogério Toledo" <anonymous@.discussions.microsoft.com> wrote in message
news:B75B10E3-3740-45BC-93D5-39158618C2D1@.microsoft.com...
> Dear,
> I have a question about SQL Server / MSDE. I'm trying install and to
configure the documentation of the .NET Framework 1.1 but I have a problem
because is necessary contain a instance: "Local\NetSDK" (Local is the same
the principal instance) second information about details of the
configuration.
> I'm working with Microsoft SQL Server 2000 - Personal Edition and I have
listed in SQL Server Service Manager only: "Local".
> How I make to create the instance: "NetSDK"?
> Yours
> Thanks
>
instance name
Hi,
I just install msde SQL2kdesksp3.exe and also WebMatrix.To use WebMatrix and manage database, i need something like: myservername\instancename to connect but how do i know my instance name ?i found, i needed to reboot. actually i can connect with my SERVERNAME but can i use my IP address instead SERVERNAME cause i would like to connect remotly. MSDE and Webmatrix are installed in my Windows 2003 Server and i would like to connect that database remotly.
Is it possible ?|||fixed
Wednesday, March 28, 2012
InstallSQLAgentSecurity failed (XXXXX,LocalSystem,87)
hi all,
i'd like to install MSDE that comes bundled with ms livecomm server.
but during the installation i get (using cmd params: /l*v ):
...
Starting custom action CallSQLAdHlp
C:\Programme\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}
TempFolder is
C:\DOKUME~1\ADMINI~1.ABS\LOKALE~1\Temp\{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}\
Loading extended custom action library
C:\DOKUME~1\ADMINI~1.ABS\LOKALE~1\Temp\{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (EXMAIL,LocalSystem,87).
Action ended 13:17:10: InstallFinalize. Return value 3.
...
i read about this behavior in ms's knowledgebase, but i dont
know how to update to sp3 of this msde cause its bundles with
the server...
any ideas how i get this msde installed on my win2003 server ?
tia !
cheers
joerg
hi Joerg,
"Joerg Mauz" <Joerg_MauzREMOVETHIS@.abs.org> ha scritto nel messaggio
news:uMTHNkBlEHA.2680@.TK2MSFTNGP15.phx.gbl...
> hi all,
> i'd like to install MSDE that comes bundled with ms livecomm server.
> but during the installation i get (using cmd params: /l*v ):
> ----
> ...
> Starting custom action CallSQLAdHlp
> C:\Programme\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
> SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}
> TempFolder is
>
C:\DOKUME~1\ADMINI~1.ABS\LOKALE~1\Temp\{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE
}\
> Loading extended custom action library
>
C:\DOKUME~1\ADMINI~1.ABS\LOKALE~1\Temp\{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE
}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity failed (EXMAIL,LocalSystem,87).
> Action ended 13:17:10: InstallFinalize. Return value 3.
> ...
> ----
> i read about this behavior in ms's knowledgebase, but i dont
> know how to update to sp3 of this msde cause its bundles with
> the server...
> any ideas how i get this msde installed on my win2003 server ?
>
if the bundle is not updated to service pack 3a, you can get it for free at
http://www.microsoft.com/sql/msde/do...s/download.asp
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
i'd like to install MSDE that comes bundled with ms livecomm server.
but during the installation i get (using cmd params: /l*v ):
...
Starting custom action CallSQLAdHlp
C:\Programme\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}
TempFolder is
C:\DOKUME~1\ADMINI~1.ABS\LOKALE~1\Temp\{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}\
Loading extended custom action library
C:\DOKUME~1\ADMINI~1.ABS\LOKALE~1\Temp\{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (EXMAIL,LocalSystem,87).
Action ended 13:17:10: InstallFinalize. Return value 3.
...
i read about this behavior in ms's knowledgebase, but i dont
know how to update to sp3 of this msde cause its bundles with
the server...
any ideas how i get this msde installed on my win2003 server ?
tia !
cheers
joerg
hi Joerg,
"Joerg Mauz" <Joerg_MauzREMOVETHIS@.abs.org> ha scritto nel messaggio
news:uMTHNkBlEHA.2680@.TK2MSFTNGP15.phx.gbl...
> hi all,
> i'd like to install MSDE that comes bundled with ms livecomm server.
> but during the installation i get (using cmd params: /l*v ):
> ----
> ...
> Starting custom action CallSQLAdHlp
> C:\Programme\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
> SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}
> TempFolder is
>
C:\DOKUME~1\ADMINI~1.ABS\LOKALE~1\Temp\{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE
}\
> Loading extended custom action library
>
C:\DOKUME~1\ADMINI~1.ABS\LOKALE~1\Temp\{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE
}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{5B5BFFF9-9D55-45AF-9390-AA4DC1C4EEFE}
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity failed (EXMAIL,LocalSystem,87).
> Action ended 13:17:10: InstallFinalize. Return value 3.
> ...
> ----
> i read about this behavior in ms's knowledgebase, but i dont
> know how to update to sp3 of this msde cause its bundles with
> the server...
> any ideas how i get this msde installed on my win2003 server ?
>
if the bundle is not updated to service pack 3a, you can get it for free at
http://www.microsoft.com/sql/msde/do...s/download.asp
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
InstallSQLAgentSecurity failed
I (actually one of our clients) is receiving an InstallSQLAgentSecurity
failed error in the msde install log.
*************************************
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (LORIH,LocalSystem,87).
Action ended 14:11:24: InstallFinalize. Return value 3.
*************************************
I've seen the following article
http://support.microsoft.com/default...en-us%3B829386
However, the Server service is running and it still won't start up. The
user is logged in as the Administrator, so is there anything else this can
be. We have this come up every now and then and we really don't have many
options to solve this.
Lance Johnson
Your solution is here:
http://seer.support.veritas.com/docs/265613.htm
I had the same problem and solution #2 fixed it. Tell me how it goes.
"Lance Johnson" <ljohnson@.docs.com> wrote in message news:<OM2SSmgXEHA.3292@.TK2MSFTNGP09.phx.gbl>...
> I (actually one of our clients) is receiving an InstallSQLAgentSecurity
> failed error in the msde install log.
> *************************************
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity failed (LORIH,LocalSystem,87).
> Action ended 14:11:24: InstallFinalize. Return value 3.
> *************************************
> I've seen the following article
> http://support.microsoft.com/default...en-us%3B829386
> However, the Server service is running and it still won't start up. The
> user is logged in as the Administrator, so is there anything else this can
> be. We have this come up every now and then and we really don't have many
> options to solve this.
> Lance Johnson
|||"Lance Johnson" <ljohnson@.docs.com> wrote in message
http://seer.support.veritas.com/docs/265613.htm
Is where the solution is.
news:<OM2SSmgXEHA.3292@.TK2MSFTNGP09.phx.gbl>...
> I (actually one of our clients) is receiving an InstallSQLAgentSecurity
> failed error in the msde install log.
> *************************************
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity failed (LORIH,LocalSystem,87).
> Action ended 14:11:24: InstallFinalize. Return value 3.
> *************************************
> I've seen the following article
> http://support.microsoft.com/default...en-us%3B829386
> However, the Server service is running and it still won't start up. The
> user is logged in as the Administrator, so is there anything else this can
> be. We have this come up every now and then and we really don't have many
> options to solve this.
> Lance Johnson
|||Check solution #2 @. the veritas page. I changed the roles and all
worked fine. Changed them back after and all continued to work.
[vbcol=seagreen]
> "Lance Johnson" <ljohnson@.docs.com> wrote in message
> http://seer.support.veritas.com/docs/265613.htm
> Is where the solution is.
> news:<OM2SSmgXEHA.3292@.TK2MSFTNGP09.phx.gbl>...
sql
failed error in the msde install log.
*************************************
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity failed (LORIH,LocalSystem,87).
Action ended 14:11:24: InstallFinalize. Return value 3.
*************************************
I've seen the following article
http://support.microsoft.com/default...en-us%3B829386
However, the Server service is running and it still won't start up. The
user is logged in as the Administrator, so is there anything else this can
be. We have this come up every now and then and we really don't have many
options to solve this.
Lance Johnson
Your solution is here:
http://seer.support.veritas.com/docs/265613.htm
I had the same problem and solution #2 fixed it. Tell me how it goes.
"Lance Johnson" <ljohnson@.docs.com> wrote in message news:<OM2SSmgXEHA.3292@.TK2MSFTNGP09.phx.gbl>...
> I (actually one of our clients) is receiving an InstallSQLAgentSecurity
> failed error in the msde install log.
> *************************************
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity failed (LORIH,LocalSystem,87).
> Action ended 14:11:24: InstallFinalize. Return value 3.
> *************************************
> I've seen the following article
> http://support.microsoft.com/default...en-us%3B829386
> However, the Server service is running and it still won't start up. The
> user is logged in as the Administrator, so is there anything else this can
> be. We have this come up every now and then and we really don't have many
> options to solve this.
> Lance Johnson
|||"Lance Johnson" <ljohnson@.docs.com> wrote in message
http://seer.support.veritas.com/docs/265613.htm
Is where the solution is.
news:<OM2SSmgXEHA.3292@.TK2MSFTNGP09.phx.gbl>...
> I (actually one of our clients) is receiving an InstallSQLAgentSecurity
> failed error in the msde install log.
> *************************************
> Starting custom action InstallSQLAgentSecurity
> InstallSQLAgentSecurity failed (LORIH,LocalSystem,87).
> Action ended 14:11:24: InstallFinalize. Return value 3.
> *************************************
> I've seen the following article
> http://support.microsoft.com/default...en-us%3B829386
> However, the Server service is running and it still won't start up. The
> user is logged in as the Administrator, so is there anything else this can
> be. We have this come up every now and then and we really don't have many
> options to solve this.
> Lance Johnson
|||Check solution #2 @. the veritas page. I changed the roles and all
worked fine. Changed them back after and all continued to work.
[vbcol=seagreen]
> "Lance Johnson" <ljohnson@.docs.com> wrote in message
> http://seer.support.veritas.com/docs/265613.htm
> Is where the solution is.
> news:<OM2SSmgXEHA.3292@.TK2MSFTNGP09.phx.gbl>...
sql
Installing with MSDE on XP
I would like to install MSDE in Windows XP Professional. When I tried
to install it gave me an error A strong SA password is required for
security reasons. Please use SAPWD switch
I do not know how it handle this error if you can please let me how to
install in XP.
Step by Step process.
Thanking You
Your's Truly
Raj
hi Raj,
Raj wrote:
> I would like to install MSDE in Windows XP Professional. When I tried
> to install it gave me an error A strong SA password is required for
> security reasons. Please use SAPWD switch
> I do not know how it handle this error if you can please let me how to
> install in XP.
> Step by Step process.
Setup.exe is a boostrap intaller for MSDE and accepts parameters you can
provide at the command line as long as in a companion .Ini file..
at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
you can find the list of all supported parameters...
please open a DOS command window and navigate to the folder hosting the
setup.exe file...
there you can run setup.exe with all the parameters of your choice..
- usually you have to provide the SAPWD parameter to specify a strong
password for the "sa" builtin login in order to protect it from both
internal and external attacks..
specify then
SAPWD=your_strong_password
- additional parameters let you specify if you want a named instance or a
default instance... specify
INSTANCENAME=your_instance_name
if you want a named instance...
- another parameter let you specify if you want to allow remote connections
from other PCs in your lan to your MSDE instance.. specify
DISABLENETWORKPROTOCOLS=0
if you need this feature...
- by default, MSDE is installed allowing only WindowsNT authenticated
connections and preventing standard SQL Server authenticated ones.. more on
this at http://support.microsoft.com/default...b;en-us;325022
you can specify
SECURITYMODE=SQL
to allow mixed mode security, thus allowing both WInNT integrated security
and standard SQL Server authenticated connections..
- the final important parameter is
/L*v "c:\msdelog.txt"
where you will allow verbose logging of the installation process, resulting
in a text file of about 2mb for a successfull installation you can inspect,
in case of problems, for
RETURN VALUE 3
entries... about 10 lines before each entry some (sometime cryptic)
description of the problwm will be reported..
so, if you like to install a "named instace" named "Raj" with mixed security
and enabled network protocols for remote connections you can run setup.exe
boostrap installer providing all parameters as
c:\..\>setup.exe /qb INSTANCENAME=Raj SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0 SAPWD=your_strong_password /L*v "c:\msdelog.txt"
you can later manage your installed instance via the native character tool
oSql.exe as described at
http://support.microsoft.com/default...;EN-US;q325003 or use a
third party tool, both commercial or free, like the ones listed at
http://www.microsoft.com/sql/msde/partners/ or
http://www.aspfaq.com/show.asp?id=2442... google for further..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
to install it gave me an error A strong SA password is required for
security reasons. Please use SAPWD switch
I do not know how it handle this error if you can please let me how to
install in XP.
Step by Step process.
Thanking You
Your's Truly
Raj
hi Raj,
Raj wrote:
> I would like to install MSDE in Windows XP Professional. When I tried
> to install it gave me an error A strong SA password is required for
> security reasons. Please use SAPWD switch
> I do not know how it handle this error if you can please let me how to
> install in XP.
> Step by Step process.
Setup.exe is a boostrap intaller for MSDE and accepts parameters you can
provide at the command line as long as in a companion .Ini file..
at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
you can find the list of all supported parameters...
please open a DOS command window and navigate to the folder hosting the
setup.exe file...
there you can run setup.exe with all the parameters of your choice..
- usually you have to provide the SAPWD parameter to specify a strong
password for the "sa" builtin login in order to protect it from both
internal and external attacks..
specify then
SAPWD=your_strong_password
- additional parameters let you specify if you want a named instance or a
default instance... specify
INSTANCENAME=your_instance_name
if you want a named instance...
- another parameter let you specify if you want to allow remote connections
from other PCs in your lan to your MSDE instance.. specify
DISABLENETWORKPROTOCOLS=0
if you need this feature...
- by default, MSDE is installed allowing only WindowsNT authenticated
connections and preventing standard SQL Server authenticated ones.. more on
this at http://support.microsoft.com/default...b;en-us;325022
you can specify
SECURITYMODE=SQL
to allow mixed mode security, thus allowing both WInNT integrated security
and standard SQL Server authenticated connections..
- the final important parameter is
/L*v "c:\msdelog.txt"
where you will allow verbose logging of the installation process, resulting
in a text file of about 2mb for a successfull installation you can inspect,
in case of problems, for
RETURN VALUE 3
entries... about 10 lines before each entry some (sometime cryptic)
description of the problwm will be reported..
so, if you like to install a "named instace" named "Raj" with mixed security
and enabled network protocols for remote connections you can run setup.exe
boostrap installer providing all parameters as
c:\..\>setup.exe /qb INSTANCENAME=Raj SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0 SAPWD=your_strong_password /L*v "c:\msdelog.txt"
you can later manage your installed instance via the native character tool
oSql.exe as described at
http://support.microsoft.com/default...;EN-US;q325003 or use a
third party tool, both commercial or free, like the ones listed at
http://www.microsoft.com/sql/msde/partners/ or
http://www.aspfaq.com/show.asp?id=2442... google for further..
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.18.0 - DbaMgr ver 0.62.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
Monday, March 26, 2012
Installing SQL service on its own
We Managed to install the MSDE system but it did not
install the SQL service again.
Is there a way to setup a MSSQL SERVER service manually on
Windows NT4.
Many Thanks
ITS Support
hi again,
"ITS Support" <anonymous@.discussions.microsoft.com> ha scritto nel
messaggio news:047b01c4dec3$effb0150$a501280a@.phx.gbl
> We Managed to install the MSDE system but it did not
> install the SQL service again.
> Is there a way to setup a MSSQL SERVER service manually on
> Windows NT4.
> Many Thanks
> ITS Support
what problems are raised and reported in the installation log text file?
search for
RETURN VALUE 3
about 10/15 lines before or after each entry a description of the problem(s)
is reported
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
install the SQL service again.
Is there a way to setup a MSSQL SERVER service manually on
Windows NT4.
Many Thanks
ITS Support
hi again,
"ITS Support" <anonymous@.discussions.microsoft.com> ha scritto nel
messaggio news:047b01c4dec3$effb0150$a501280a@.phx.gbl
> We Managed to install the MSDE system but it did not
> install the SQL service again.
> Is there a way to setup a MSSQL SERVER service manually on
> Windows NT4.
> Many Thanks
> ITS Support
what problems are raised and reported in the installation log text file?
search for
RETURN VALUE 3
about 10/15 lines before or after each entry a description of the problem(s)
is reported
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
Monday, March 12, 2012
Integrate changes into MSDE Database?
I have a module that requires modifcation to the database. How do I adopt the following instructuions for use with MSDE?
1. Create a MSSQL structure.
2. Open a query anylizer and copy the CreateDB.SQL file. Run it.
Thanks,
ScottYou should be able to use the osql.exe utility. To run the CreateDB.SQL file, you can go to the Windows command prompt, go to the directory containing the .SQL file, and issue a command such as:
osql -E -i CreateDB.SQL
Terri|||Thanks for responding Terri.
I have created a seperate MSDE for each on the Starter Kits I'm tinkering with. When I run CreateDB, do I need to specify which MSDE?
Scott
Subscribe to:
Posts (Atom)