Install rolls back

Hi NG,
I have a installation problem on MSDE and install to window 2000
MSI (s) (34:FC): MainEngineThread is returning 1603
MSI (c) (54:58): Back from server. Return value: 1603
MSI (c) (54:58): Decrementing counter to disable shutdown. If counter >= 0,
shutdown will be denied. Counter after decrement: -1
Aktion beendet um 10:57:35: INSTALL. Rckgabewert 3.
MSI (c) (54:58): Note: 1: 2262 2: Control 3: -2147287038
then rolling back.
Does anyone experienced the same problem?
Thank you very much for any suggestion.
Regards
Roland
Hi
Try running the install with verbose logging switched on:
setup.exe /L*v <Setup Log File Path>
You may get a better error that describes the problem.
Regard
sMike
"Roland Skottke" wrote:

> Hi NG,
> I have a installation problem on MSDE and install to window 2000
> MSI (s) (34:FC): MainEngineThread is returning 1603
> MSI (c) (54:58): Back from server. Return value: 1603
> MSI (c) (54:58): Decrementing counter to disable shutdown. If counter >= 0,
> shutdown will be denied. Counter after decrement: -1
> Aktion beendet um 10:57:35: INSTALL. Rückgabewert 3.
> MSI (c) (54:58): Note: 1: 2262 2: Control 3: -2147287038
> then rolling back.
> Does anyone experienced the same problem?
> Thank you very much for any suggestion.
> Regards
> Roland
>
>
|||hi Roland Skottke
I have the same experienced before! I fixed this problem with error code of
1603 by start up the "server" service and re-install MSDE !
hope this can help you!
"Roland Skottke" <spam_roland.skottke@.arrisa.com>
??:cvhu96$ov2$01$1@.news.t-online.com...
> Hi NG,
> I have a installation problem on MSDE and install to window 2000
> MSI (s) (34:FC): MainEngineThread is returning 1603
> MSI (c) (54:58): Back from server. Return value: 1603
> MSI (c) (54:58): Decrementing counter to disable shutdown. If counter >=
0,
> shutdown will be denied. Counter after decrement: -1
> Aktion beendet um 10:57:35: INSTALL. Rckgabewert 3.
> MSI (c) (54:58): Note: 1: 2262 2: Control 3: -2147287038
> then rolling back.
> Does anyone experienced the same problem?
> Thank you very much for any suggestion.
> Regards
> Roland
>
|||Hi sMike,
this errors are a part of the log. The log have a lot of text, but i can't
find the error.
regards
Roland
"Mike Epprecht (SQL MVP)" <mike@.epprecht.net> schrieb im Newsbeitrag
news:ABD89029-6E6F-4E7B-97D3-4EA1EF90F98B@.microsoft.com...[vbcol=seagreen]
> Hi
> Try running the install with verbose logging switched on:
> setup.exe /L*v <Setup Log File Path>
> You may get a better error that describes the problem.
> Regard
> sMike
> "Roland Skottke" wrote:
0,[vbcol=seagreen]
|||Hi Angus,
where can i find the "server" service?
I can't count the numbers of re-install on this machine.
regards
Roland
"ANGUS" <angusgod@.theworld.com> schrieb im Newsbeitrag
news:O9q2LNcGFHA.2136@.TK2MSFTNGP14.phx.gbl...
> hi Roland Skottke
> I have the same experienced before! I fixed this problem with error code
of
> 1603 by start up the "server" service and re-install MSDE !
> hope this can help you!
>
> "Roland Skottke" <spam_roland.skottke@.arrisa.com>
> ??:cvhu96$ov2$01$1@.news.t-online.com...
> 0,
>

Install report server in msde

Dear all,
Is this possible to install report server in msde
If not, i am a new in reporting services, is it possible to develop and test
just install the report designer?Joe, the simple answer is no, as a minimum you'll need VB.Net 2003 and
SQL2000 Dev. Ed. around £30-£50 each in UK. You can almost fully test
reports in VB.Net but the Report Manager uses an HTML renderer where
the Development environment uses the RS.exe renderer so there can be
differences.
I think RS/SQL2005 is supposed to be able run reports completely stand
alone from SQL server. This is currently in a fairly advanced beta
stage.
Regards
Chris
Joe wrote:
> Dear all,
> Is this possible to install report server in msde
> If not, i am a new in reporting services, is it possible to develop
> and test just install the report designer?

Install Problem...Please Help!

A third party application is trying to install MSDE 2000 on our XP Professional machine. Install gets to about "2 seconds remaining" then backs out and simply quits. No error messages. Saw a similar post on here but it was never resolved. I've made sure t
he Server service is running and that File and Print Sharing for Microsoft Networks is installed and enabled. Any help would be greatly appreciated...this is a very important application we are trying to install. Thanks.
Floyd
Thanks for the reply. The application never installs so there is no .ini file...not that I would know what to change in it if it was there. Why won't this stupid thing just install? This is driving me batty!
"sthomas" wrote:

> hi :
> Check the .ini file if you have any that is coming with
> the application and do modifications if it is required
>
> on our XP Professional machine. Install gets to about "2
> seconds remaining" then backs out and simply quits. No
> error messages. Saw a similar post on here but it was
> never resolved. I've made sure the Server service is
> running and that File and Print Sharing for Microsoft
> Networks is installed and enabled. Any help would be
> greatly appreciated...this is a very important
> application we are trying to install. Thanks.
>

Install problem

I'am trying to install MSDE Rel A but when installer starts to extract files
to installation folder i get error message saying i don't have enough space
on hard disk.
Disk is 40GB anf there's 28GB free space left...
-mikko
Try running CHKDSK on the drive you are having the problem with. Also, what
OS and file system are you running?
Jim
"Jeter" <ei@.oo.ei> wrote in message
news:ODdmFxcFFHA.1348@.TK2MSFTNGP14.phx.gbl...
> I'am trying to install MSDE Rel A but when installer starts to extract
> files
> to installation folder i get error message saying i don't have enough
> space
> on hard disk.
> Disk is 40GB anf there's 28GB free space left...
> -mikko
>

Install on alternate TCP Port

I am trying to create an unattended install of MSDE 2000 sp3a that will set the default tcp port to something other than 1433. I am using a setup.ini file and have tried the following with out any success - any ideas would be great! Thanks
[Options]
SECURITYMODE=SQL
DISABLENETWORKPROTOCOLS=0
[SdServerNetwork-0]
TCPPort=1433
hi Kelly
"Kelly" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:D1F4F952-218E-46F9-BF44-ED0F083F0AAD@.microsoft.com...
> I am trying to create an unattended install of MSDE 2000 sp3a that will
set the default tcp port to something other than 1433. I am using a
setup.ini file and have tried the following with out any success - any ideas
would be great! Thanks
> [Options]
> SECURITYMODE=SQL
> DISABLENETWORKPROTOCOLS=0
> [SdServerNetwork-0]
> TCPPort=1433
the MSDE 2000 setup boostrapper does not support TCP/IP port redirecting
the
[SdServerNetwork-0]
TCPPort=1433
parameter you provided is only valid for a full blown SQL Server unattended
installations and not for MSDE...
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
|||Thanks Andrea!
What is the best method to change the tcp port after MSDE has been installed on the client machine?
Is it acceptable to modify the TcpPort via the registry:
HKLM\Software\Microsoft\MSSQLServer\SuperSocketNet Lib\Tcp
|||hi Kelly,
"Kelly" <anonymous@.discussions.microsoft.com> ha scritto nel messaggio
news:36ACB0E9-2A4E-45A1-A0A3-C430B364D324@.microsoft.com...
> Thanks Andrea!
> What is the best method to change the tcp port after MSDE has been
installed on the client machine?
> Is it acceptable to modify the TcpPort via the registry:
> HKLM\Software\Microsoft\MSSQLServer\SuperSocketNet Lib\Tcp
this can be a viable solution as, in order to install MSDE, admin privileges
are required, so you have access to the full registry, but remember you have
to modify that value using the Client Network Utility on all clients...
as regard the server, please have a look at
http://support.microsoft.com/?kbid=823938
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
|||Thanks for all of your help

Install of SQL/MSDE not completing HELP!

I am a new user working in Windows XP, and I already have the Web Matrix installed. I am trying to download and install MSDE but I am never prompted to restart my computer. When I do restart the PC symbol w/ the green arrow appears but when I click the data connection to establish a new database it comes with an error message:

Unable to connect to database server.

SQL Server does not exist or access denied.
Connection Open (Connect()).

I'm sure I'm entering the right user name (sa) and password. Please help!!

LaurenHi Lauren,

This is a common problem, and there are serveral reasons this can happen. Are you using Windows Authentication or Mixed (SQL Server and Windows) Authentication? What does your connection string look like?

Also, did you try searching for "access denied" in this forum? There are a lot of posts on this topic.

Terri

Install of SQL Server 2000 dev edition over MSDE. Any advice appreciated.

It's arriving from ebuyer tomorrow for 32 quid. I already have an
instance of MSDE running on the laptop and ideally i would like SQL
server to be installed and use the current instance and not install
any other additional services. [hope i got my terminology correct
here.] Basically all i would like is to use the Enterprise Manager
with my existing MSDE database. I was wondering if there is anything i
should be doing before I install. Should i shut down the service or
leave it running for instance.

Thanks for any tips,
AndyB"Andy B" <coastalrocket@.yahoo.co.uk> wrote in message
news:f1523bf.0407290650.46b411b8@.posting.google.co m...
> It's arriving from ebuyer tomorrow for 32 quid. I already have an
> instance of MSDE running on the laptop and ideally i would like SQL
> server to be installed and use the current instance and not install
> any other additional services. [hope i got my terminology correct
> here.] Basically all i would like is to use the Enterprise Manager
> with my existing MSDE database. I was wondering if there is anything i
> should be doing before I install. Should i shut down the service or
> leave it running for instance.
> Thanks for any tips,
> AndyB

You could install only the client tools, if that's all you want (don't
forget to install SP3a as well). Or you can install Developer Edition
anyway, as a named instance - you don't have to start it if you don't need
it.

Simon|||"Simon Hayes" <sql@.hayes.ch> wrote in message news:<41093871$1_2@.news.bluewin.ch>...
> "Andy B" <coastalrocket@.yahoo.co.uk> wrote in message
> news:f1523bf.0407290650.46b411b8@.posting.google.co m...
> > It's arriving from ebuyer tomorrow for 32 quid. I already have an
> > instance of MSDE running on the laptop and ideally i would like SQL
> > server to be installed and use the current instance and not install
> > any other additional services. [hope i got my terminology correct
> > here.] Basically all i would like is to use the Enterprise Manager
> > with my existing MSDE database. I was wondering if there is anything i
> > should be doing before I install. Should i shut down the service or
> > leave it running for instance.
> > Thanks for any tips,
> > AndyB
> You could install only the client tools, if that's all you want (don't
> forget to install SP3a as well). Or you can install Developer Edition
> anyway, as a named instance - you don't have to start it if you don't need
> it.
> Simon

Thanks Simon. I did just that.

Install of MSDE on XP Pro Failed, HELP Please ANYONE!

I have for the past 1.5 weeks been trying to get MSDE installed on a Windows
XP computer. We are installing MSDE sp3 which we have installed on more
than 20+ computers. Some computers Windows 2003 Servers some Windows XP
Pro. We have NEVER had a problem. So before anyone suggest it, I don't
think going to MSDE sp4 will help with this problem. We have formatted the
computer MANY times and started over. We have updated with ALL of the
Windows update and it did not work. We formatted and install only SP2 on
Windows XP. We have taken off all other software, virus scanners, office,
etc. The computer is BLANK. It is on the network and I am remote
desktopped in when I try to install. Now I have done this MANY time remote
desktopped to a machine and no problem. We have made sure that network
items like File and Print Sharing are on. I have tried to install as the
administrator of the computer, as a user who have administrative priveleges,
etc. This computer is a Windows XP computer, not on a domain, the software
is XP Pro, and everything looks good. I am at a lost.
When I install I have it dump out the logs, here is some of the log I get,
it is
to long to post all of it. I have also added the SQL
Error logs that are left below this log. Then below that I have attached
the cnfgsvr.out
Any help is GREATLY appriecated, I can not blank out and install XP any
more.
=== Verbose logging started: 7/25/2007 17:43:02 Build type: SHIP UNICODE
3.00.3790.2180 Calling process: C:\WINDOWS\system32\msiexec.exe ===
MSI (c) (10:C0) [17:43:02:687]: Resetting cached policy values
MSI (c) (10:C0) [17:43:02:687]: Machine policy value 'Debug' is 0
MSI (c) (10:C0) [17:43:02:687]: ******* RunEngine:
******* Product: C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi
******* Action:
******* CommandLine: **********
MSI (c) (10:C0) [17:43:02:718]: Machine policy value 'DisableUserInstalls'
is 0
MSI (c) (10:C0) [17:43:02:843]: SOFTWARE RESTRICTION POLICY: Verifying
package --> 'C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi' against
software restriction policy
MSI (c) (10:C0) [17:43:02:843]: Note: 1: 2262 2: DigitalSignature
3: -2147287038
MSI (c) (10:C0) [17:43:02:843]: SOFTWARE RESTRICTION POLICY:
C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi is not digitally signed
MSI (c) (10:C0) [17:43:02:843]: SOFTWARE RESTRICTION POLICY:
C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi is permitted to run at the
'unrestricted' authorization level.
MSI (c) (10:C0) [17:43:02:968]: Cloaking enabled.
MSI (c) (10:C0) [17:43:02:968]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (10:C0) [17:43:03:000]: End dialog not enabled
MSI (c) (10:C0) [17:43:03:000]: Original package ==>
C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi
MSI (c) (10:C0) [17:43:03:000]: Package we're running from ==>
C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\2557a1.msi
MSI (c) (10:C0) [17:43:03:015]: APPCOMPAT: looking for appcompat database
entry with ProductCode '{E09B48B5-E141-427A-AB0C-D3605127224A}'.
MSI (c) (10:C0) [17:43:03:015]: APPCOMPAT: no matching ProductCode found in
database.
MSI (c) (10:C0) [17:43:03:015]: MSCOREE not loaded loading copy from
system32
MSI (c) (10:C0) [17:43:03:015]: Machine policy value 'TransformsSecure' is 0
MSI (c) (10:C0) [17:43:03:015]: User policy value 'TransformsAtSource' is 0
MSI (c) (10:C0) [17:43:03:015]: Note: 1: 2205 2: 3: MsiFileHash
MSI (c) (10:C0) [17:43:03:015]: Machine policy value 'DisablePatch' is 0
MSI (c) (10:C0) [17:43:03:015]: Machine policy value 'AllowLockdownPatch' is
0
MSI (c) (10:C0) [17:43:03:015]: Machine policy value 'DisableLUAPatching' is
0
MSI (c) (10:C0) [17:43:03:015]: Machine policy value
'DisableFlyWeightPatching' is 0
MSI (c) (10:C0) [17:43:03:015]: APPCOMPAT: looking for appcompat database
entry with ProductCode '{E09B48B5-E141-427A-AB0C-D3605127224A}'.
MSI (c) (10:C0) [17:43:03:015]: APPCOMPAT: no matching ProductCode found in
database.
MSI (c) (10:C0) [17:43:03:015]: Transforms are not secure.
MSI (c) (10:C0) [17:43:03:015]: Note: 1: 2262 2: Control 3: -2147287038
MSI (c) (10:C0) [17:43:03:015]: Command Line: instancename=ThinkHealth
SECURITYMODE=SQL SA...
MSI (c) (10:C0) [17:43:03:015]: PROPERTY CHANGE: Adding PackageCode
property. Its value is '{D29DCF7A-8199-4373-BA0D-2F3635EC940C}'.
MSI (c) (10:C0) [17:43:03:015]: Product Code passed to Engine.Initialize:
''
MSI (c) (10:C0) [17:43:03:015]: Product Code from property table before
transforms: '{E09B48B5-E141-427A-AB0C-D3605127224A}'
MSI (c) (10:C0) [17:43:03:015]: Product Code from property table after
transforms: '{E09B48B5-E141-427A-AB0C-D3605127224A}'
MSI (c) (10:C0) [17:43:03:015]: Product not registered: beginning first-time
install
MSI (c) (10:C0) [17:43:03:015]: PROPERTY CHANGE: Adding ProductState
property. Its value is '-1'.
MSI (c) (10:C0) [17:43:03:015]: Entering
CMsiConfigurationManager::SetLastUsedSource.
MSI (c) (10:C0) [17:43:03:015]: User policy value 'SearchOrder' is 'nmu'
MSI (c) (10:C0) [17:43:03:015]: Adding new sources is allowed.
MSI (c) (10:C0) [17:43:03:015]: PROPERTY CHANGE: Adding PackagecodeChanging
property. Its value is '1'.
MSI (c) (10:C0) [17:43:03:015]: Package name extracted from package path:
'SqlRun01.msi'
MSI (c) (10:C0) [17:43:03:015]: Package to be registered: 'SqlRun01.msi'
MSI (c) (10:C0) [17:43:03:031]: Note: 1: 2262 2: AdminProperties
3: -2147287038
MSI (c) (10:C0) [17:43:03:031]: Machine policy value 'DisableMsi' is 0
MSI (c) (10:C0) [17:43:03:031]: Machine policy value 'AlwaysInstallElevated'
is 0
MSI (c) (10:C0) [17:43:03:031]: User policy value 'AlwaysInstallElevated' is
0
MSI (c) (10:C0) [17:43:03:031]: Product installation will be elevated
because user is admin and product is being installed per-machine.
MSI (c) (10:C0) [17:43:03:031]: Running product
'{E09B48B5-E141-427A-AB0C-D3605127224A}' with elevated privileges: Product
is assigned.
*********************************
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}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallPerfMon
Registering performance counters from sqlctr.ini
MSI (s) (00:4C) [17:43:38:156]: Executing op:
ActionStart(Name=InstallSQLAdHlp.2D02443E_7002_4C0 B_ABC9_EAB2C064397B,,)
MSI (s) (00:4C) [17:43:38:156]: Executing op:
CustomActionSchedule(Action=InstallSQLAdHlp.2D0244 3E_7002_4C0B_ABC9_EAB2C064397B,ActionType=1025,Sou rce=BinaryData,Target=InstallSQLAdHlp,)
MSI (s) (00:BC) [17:43:38:171]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI2A.tmp, Entrypoint: InstallSQLAdHlp
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}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action CallSQLAdHlp
C:\Program Files\Microsoft SQL Server\80\Tools\Binn\sqladhlp.exe : 0
MSI (s) (00:4C) [17:43:38:593]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (00:4C) [17:43:38:593]: Executing op:
CustomActionSchedule(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (00:4C) [17:43:38:593]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (00:4C) [17:43:38:593]: Executing op:
CustomActionSchedule(Action=InstallAgentSecurity.2 D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=102 5,Source=BinaryData,Target=InstallSQLAgentSecurity ,)
MSI (s) (00:90) [17:43:38:609]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI2B.tmp, Entrypoint: InstallSQLAgentSecurity
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}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action InstallSQLAgentSecurity
InstallSQLAgentSecurity succeeded
MSI (s) (00:4C) [17:43:38:671]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (00:4C) [17:43:38:687]: Executing op:
CustomActionSchedule(Action=SkuIt.2D02443E_7002_4C 0B_ABC9_EAB2C064397B,ActionType=1025,Source=Binary Data,Target=SkuIt,)
MSI (s) (00:78) [17:43:38:687]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI2C.tmp, Entrypoint: SkuIt
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}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action SkuIt
MSI (s) (00:4C) [17:43:38:796]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (00:4C) [17:43:38:796]: Executing op:
CustomActionSchedule(Action=ConfigServer.2D02443E_ 7002_4C0B_ABC9_EAB2C064397B...
MSI (s) (00:10) [17:43:38:796]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI2D.tmp, Entrypoint: ConfigServer
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}\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 "THINKHEALTH" -Q
"SQL_Latin1_General_CP1_CI_AS""
MSI (c) (10:50) [17:45:59:531]: 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) (00!F4) [17:46:12:140]: 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 17:46:12: InstallFinalize. Return value 3.
MSI (s) (00:4C) [17:46:12:171]: User policy value 'DisableRollback' is 0
MSI (s) (00:4C) [17:46:12:171]: Machine policy value 'DisableRollback' is 0
MSI (s) (00:4C) [17:46:12:187]: Executing op:
Header(Signature=1397708873,Version=300,Timestamp= 922324328,LangId=1033,Platform=0,ScriptType=2,Scri ptMajorVersion=21,ScriptMinorVersion=4,ScriptAttri butes=1)
MSI (s) (00:4C) [17:46:12:187]: Executing op:
DialogInfo(Type=0,Argument=1033)
MSI (s) (00:4C) [17:46:12:187]: Executing op:
DialogInfo(Type=1,Argument=Microsoft SQL Server Desktop Engine)
MSI (s) (00:4C) [17:46:12:187]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDesc ription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription= Removing
backup files,CleanupTemplate=File: [1])
MSI (s) (00:4C) [17:46:12:203]: Executing op:
ActionStart(Name=ConfigServer.2D02443E_7002_4C0B_A BC9_EAB2C064397B...
MSI (s) (00:4C) [17:46:12:203]: Executing op:
ProductInfo(ProductKey={E09B48B5-E141-427A-AB0C-D3605127224A},ProductName=Microsoft
SQL Server Desktop
Engine,PackageName=SqlRun01.msi,Language=1033,Vers ion=134218489,Assignment=1,ObsoleteArg=0,,,Package Code={D29DCF7A-8199-4373-BA0D-2F3635EC940C},,,InstanceType=0,LUASetting=0)
MSI (s) (00:4C) [17:46:12:203]: Executing op:
ActionStart(Name=SkuIt.2D02443E_7002_4C0B_ABC9_EAB 2C064397B,,)
MSI (s) (00:4C) [17:46:12:203]: Executing op:
ActionStart(Name=InstallAgentSecurity.2D02443E_700 2_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (00:4C) [17:46:12:203]: Executing op:
ActionStart(Name=RollbackAgentSecurity.2D02443E_70 02_4C0B_ABC9_EAB2C064397B,,)
MSI (s) (00:4C) [17:46:12:203]: Executing op:
CustomActionRollback(Action=RollbackAgentSecurity. 2D02443E_7002_4C0B_ABC9_EAB2C064397B,ActionType=12 81,Source=BinaryData,Target=UnInstSQLAgentSecurity ,)
MSI (s) (00:28) [17:46:12:218]: Invoking remote custom action. DLL:
C:\WINDOWS\Installer\MSI2E.tmp, Entrypoint: UnInstSQLAgentSecurity
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}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Starting custom action UnInstSQLAgentSecurity
Starting custom action UnInstSQLAgentSecurity
************************************************** ***
Property(S): ProductState = -1
Property(S): PackagecodeChanging = 1
Property(S): INSTANCENAME = ThinkHealth
Property(S): SA...
Property(S): SECURITYMODE = SQL
Property(S): CURRENTDIRECTORY = C:\ONSInstall\sql2ksp3\MSDE
Property(S): CLIENTUILEVEL = 0
Property(S): CLIENTPROCESSID = 1808
Property(S): USERNAME = Discovery
Property(S): COMPANYNAME = Discovery-uttuwah
Property(S): ACTION = INSTALL
Property(S): VersionDatabase = 110
Property(S): VersionMsi = 3.00
Property(S): WindowsBuild = 2600
Property(S): ServicePackLevel = 2
Property(S): ServicePackLevelMinor = 0
Property(S): MsiNTProductType = 1
Property(S): WindowsFolder = C:\WINDOWS\
Property(S): WindowsVolume = C:\
Property(S): System16Folder = C:\WINDOWS\system\
Property(S): RemoteAdminTS = 1
Property(S): TempFolder = C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\
Property(S): ProgramFilesFolder = C:\Program Files\
Property(S): CommonFilesFolder = C:\Program Files\Common Files\
Property(S): AppDataFolder = C:\Documents and
Settings\Administrator\Application Data\
Property(S): FavoritesFolder = C:\Documents and
Settings\Administrator\Favorites\
Property(S): NetHoodFolder = C:\Documents and
Settings\Administrator\NetHood\
Property(S): PersonalFolder = C:\Documents and Settings\Administrator\My
Documents\
Property(S): PrintHoodFolder = C:\Documents and
Settings\Administrator\PrintHood\
Property(S): RecentFolder = C:\Documents and Settings\Administrator\Recent\
Property(S): SendToFolder = C:\Documents and Settings\Administrator\SendTo\
Property(S): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(S): CommonAppDataFolder = C:\Documents and Settings\All
Users\Application Data\
Property(S): LocalAppDataFolder = C:\Documents and
Settings\Administrator\Local Settings\Application Data\
Property(S): MyPicturesFolder = C:\Documents and Settings\Administrator\My
Documents\My Pictures\
Property(S): AdminToolsFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\Administrative Tools\
Property(S): StartupFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\Startup\
Property(S): ProgramMenuFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\
Property(S): StartMenuFolder = C:\Documents and Settings\All Users\Start
Menu\
Property(S): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(S): FontsFolder = C:\WINDOWS\Fonts\
Property(S): GPTSupport = 1
Property(S): OLEAdvtSupport = 1
Property(S): ShellAdvtSupport = 1
Property(S): Intel = 15
Property(S): PhysicalMemory = 447
Property(S): VirtualMemory = 933
Property(S): AdminUser = 1
Property(S): LogonUser = Administrator
Property(S): UserSID = S-1-5-21-1202660629-1450960922-725345543-500
Property(S): UserLanguageID = 1033
Property(S): ComputerName = DISCOVSERVER
Property(S): SystemLanguageID = 1033
Property(S): ScreenX = 1024
Property(S): ScreenY = 768
Property(S): CaptionHeight = 26
Property(S): BorderTop = 1
Property(S): BorderSide = 1
Property(S): TextHeight = 16
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): MsiWin32AssemblySupport = 5.1.2600.2180
Property(S): RedirectedDllSupport = 2
Property(S): Time = 17:46:21
Property(S): Date = 7/25/2007
Property(S): Privileged = 1
Property(S): DATABASE = C:\WINDOWS\Installer\255937.msi
Property(S): OriginalDatabase =
C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi
Property(S): UILevel = 3
Property(S): AgentServiceName = SQLAgent$THINKHEALTH
Property(S): InstanceRegKey = Microsoft SQL Server\THINKHEALTH
Property(S): InstanceSubDir = MSSQL$THINKHEALTH
Property(S): SqlPerfMonRegKey = SQLCTR$THINKHEALTH
Property(S): SQLServiceName = MSSQL$THINKHEALTH
Property(S): SqlStates = 0
Property(S): ROOTDRIVE = C:\
Property(S): CostingComplete = 1
Property(S): OutOfDiskSpace = 0
Property(S): OutOfNoRbDiskSpace = 0
Property(S): PrimaryVolumeSpaceAvailable = 0
Property(S): PrimaryVolumeSpaceRequired = 0
Property(S): PrimaryVolumeSpaceRemaining = 0
Property(S): SqlFeature = SqlRun
Property(S): SOURCEDIR = C:\ONSInstall\sql2ksp3\MSDE\Setup\
Property(S): SourcedirProduct = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(S): ProductToBeRegistered = 1
MSI (s) (00:4C) [17:46:21:453]: MainEngineThread is returning 1603
MSI (s) (00:38) [17:46:21:453]: Destroying RemoteAPI object.
MSI (s) (00:5C) [17:46:21:453]: Custom Action Manager thread ending.
MSI (c) (10:C0) [17:46:21:484]: Back from server. Return value: 1603
MSI (c) (10:C0) [17:46:21:484]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
Action ended 17:46:21: INSTALL. Return value 3.
Property(C): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(C): VersionNT = 501
Property(C): ALLUSERS = 1
Property(C): ARPNOMODIFY = 1
Property(C): DefaultUIFont = Tahoma8
Property(C): INSTALLLEVEL = 3
Property(C): LIMITUI = 1
Property(C): Manufacturer = Microsoft Corporation
Property(C): ProductCode = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(C): ProductLanguage = 1033
Property(C): ProductName = Microsoft SQL Server Desktop Engine
Property(C): ProductVersion = 8.00.761
Property(C): MsiHiddenProperties = SqlSa...
Property(C): SQLVersion.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 8.00.194
Property(C): SQLExitCode.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 1603
Property(C): APPS_TEST = 1
Property(C): SQLMSDESelected = 1
Property(C): CSDVersionNumber = 768
Property(C): CSDVersion = 8.00.761
Property(C): SystemFolder = C:\WINDOWS\system32\
Property(C): PackageCode = {D29DCF7A-8199-4373-BA0D-2F3635EC940C}
Property(C): ProductState = -1
Property(C): PackagecodeChanging = 1
Property(C): INSTANCENAME = ThinkHealth
Property(C): SA...
Property(C): SECURITYMODE = SQL
Property(C): CURRENTDIRECTORY = C:\ONSInstall\sql2ksp3\MSDE
Property(C): CLIENTUILEVEL = 0
Property(C): CLIENTPROCESSID = 1808
Property(C): VersionDatabase = 110
Property(C): VersionMsi = 3.00
Property(C): WindowsBuild = 2600
Property(C): ServicePackLevel = 2
Property(C): ServicePackLevelMinor = 0
Property(C): MsiNTProductType = 1
Property(C): WindowsFolder = C:\WINDOWS\
Property(C): WindowsVolume = C:\
Property(C): System16Folder = C:\WINDOWS\system\
Property(C): RemoteAdminTS = 1
Property(C): TempFolder = C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\
Property(C): ProgramFilesFolder = C:\Program Files\
Property(C): CommonFilesFolder = C:\Program Files\Common Files\
Property(C): AppDataFolder = C:\Documents and
Settings\Administrator\Application Data\
Property(C): FavoritesFolder = C:\Documents and
Settings\Administrator\Favorites\
Property(C): NetHoodFolder = C:\Documents and
Settings\Administrator\NetHood\
Property(C): PersonalFolder = C:\Documents and Settings\Administrator\My
Documents\
Property(C): PrintHoodFolder = C:\Documents and
Settings\Administrator\PrintHood\
Property(C): RecentFolder = C:\Documents and Settings\Administrator\Recent\
Property(C): SendToFolder = C:\Documents and Settings\Administrator\SendTo\
Property(C): TemplateFolder = C:\Documents and Settings\All Users\Templates\
Property(C): CommonAppDataFolder = C:\Documents and Settings\All
Users\Application Data\
Property(C): LocalAppDataFolder = C:\Documents and
Settings\Administrator\Local Settings\Application Data\
Property(C): MyPicturesFolder = C:\Documents and Settings\Administrator\My
Documents\My Pictures\
Property(C): AdminToolsFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\Administrative Tools\
Property(C): StartupFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\Startup\
Property(C): ProgramMenuFolder = C:\Documents and Settings\All Users\Start
Menu\Programs\
Property(C): StartMenuFolder = C:\Documents and Settings\All Users\Start
Menu\
Property(C): DesktopFolder = C:\Documents and Settings\All Users\Desktop\
Property(C): FontsFolder = C:\WINDOWS\Fonts\
Property(C): GPTSupport = 1
Property(C): OLEAdvtSupport = 1
Property(C): ShellAdvtSupport = 1
Property(C): Intel = 15
Property(C): PhysicalMemory = 447
Property(C): VirtualMemory = 936
Property(C): AdminUser = 1
Property(C): LogonUser = Administrator
Property(C): UserSID = S-1-5-21-1202660629-1450960922-725345543-500
Property(C): UserLanguageID = 1033
Property(C): ComputerName = DISCOVSERVER
Property(C): SystemLanguageID = 1033
Property(C): ScreenX = 1280
Property(C): ScreenY = 1024
Property(C): CaptionHeight = 26
Property(C): BorderTop = 1
Property(C): BorderSide = 1
Property(C): TextHeight = 16
Property(C): ColorBits = 16
Property(C): TTCSupport = 1
Property(C): MsiWin32AssemblySupport = 5.1.2600.2180
Property(C): RedirectedDllSupport = 2
Property(C): Time = 17:46:21
Property(C): Date = 7/25/2007
Property(C): Privileged = 1
Property(C): USERNAME = Discovery
Property(C): COMPANYNAME = Discovery-uttuwah
Property(C): DATABASE = C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\2557a1.msi
Property(C): OriginalDatabase =
C:\ONSInstall\sql2ksp3\MSDE\Setup\SqlRun01.msi
Property(C): UILevel = 3
Property(C): ACTION = INSTALL
=== Logging stopped: 7/25/2007 17:46:21 ===
MSI (c) (10:C0) [17:46:21:531]: Note: 1: 1708
MSI (c) (10:C0) [17:46:21:531]: Product: Microsoft SQL Server Desktop
Engine -- Installation operation failed.
MSI (c) (10:C0) [17:46:21:531]: Grabbed execution mutex.
MSI (c) (10:C0) [17:46:21:531]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (10:C0) [17:46:21:546]: MainEngineThread is returning 1603
=== Verbose logging stopped: 7/25/2007 17:46:21 ===
2007-07-25 17:43:39.59 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)
2007-07-25 17:43:39.59 server Copyright (C) 1988-2002 Microsoft
Corporation.
2007-07-25 17:43:39.59 server All rights reserved.
2007-07-25 17:43:39.59 server Server Process ID is 1880.
2007-07-25 17:43:39.59 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$THINKHEALTH\LOG\ERRORLOG'.
2007-07-25 17:43:39.60 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2007-07-25 17:43:39.78 server SQL Server configured for thread mode
processing.
2007-07-25 17:43:39.79 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2007-07-25 17:43:39.92 spid3 Warning ******************
2007-07-25 17:43:39.92 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.
2007-07-25 17:43:39.93 spid3 Starting up database 'master'.
2007-07-25 17:43:40.40 server Using 'SSNETLIB.DLL' version '8.0.766'.
2007-07-25 17:43:40.40 spid5 Starting up database 'model'.
2007-07-25 17:43:40.49 spid3 Server name is 'DISCOVSERVER\THINKHEALTH'.
2007-07-25 17:43:40.49 spid3 Skipping startup of clean database id 5
2007-07-25 17:43:40.49 spid3 Skipping startup of clean database id 6
2007-07-25 17:43:40.49 spid3 Starting up database 'msdb'.
2007-07-25 17:43:40.67 server SQL server listening on Shared Memory.
2007-07-25 17:43:40.67 server SQL Server is ready for client connections
2007-07-25 17:43:40.74 spid5 Clearing tempdb database.
2007-07-25 17:43:41.29 spid5 Starting up database 'tempdb'.
2007-07-25 17:43:41.40 spid3 Recovery complete.
2007-07-25 17:43:41.40 spid3 SQL global counter collection task is
created.
2007-07-25 17:43:41.43 spid3 Warning: override, autoexec procedures
skipped.
2007-07-25 17:45:44.74 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
################################################## #############################
Starting Service ...
SQL_Latin1_General_CP1_CI_AS
-m -Q -T4022 -T3659
An error occurred while attempting to start the service (1460)
SQL Server configuration failed.
################################################## #############################
hi,
Microsoft News wrote:
> I have for the past 1.5 weeks been trying to get MSDE installed on a
> Windows XP computer. We are installing MSDE sp3 which we have
> installed on more than 20+ computers. Some computers Windows 2003
> Servers some Windows XP Pro. We have NEVER had a problem. So before
> anyone suggest it, I don't think going to MSDE sp4 will help with
> this problem. We have formatted the computer MANY times and started
> over. We have updated with ALL of the Windows update and it did not
> work. We formatted and install only SP2 on Windows XP. We have
> taken off all other software, virus scanners, office, etc. The
> computer is BLANK. It is on the network and I am remote desktopped
> in when I try to install. Now I have done this MANY time remote
> desktopped to a machine and no problem. We have made sure that
> network items like File and Print Sharing are on. I have tried to
> install as the administrator of the computer, as a user who have
> administrative priveleges, etc. This computer is a Windows XP
> computer, not on a domain, the software is XP Pro, and everything
> looks good. I am at a lost.
> When I install I have it dump out the logs, here is some of the log I
> get, it is
> to long to post all of it. I have also added the SQL
> Error logs that are left below this log. Then below that I have
> attached the cnfgsvr.out
> Any help is GREATLY appriecated, I can not blank out and install XP
> any more.
<-->
Setup failed to configure the server. Refer to the server error logs and
setup error logs for more information.
MSI (s) (00!F4) [17:46:12:140]: 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 17:46:12: InstallFinalize. Return value 3.
<-->
this exception is usually related to
http://support.microsoft.com/default.aspx?scid=kb;en-us;816499&Product=sql
is the "Server" service up and running as well?
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Andrea
Thank you for your response, as I said in my email this is a BLANK computer,
never had anything installed on it so the link does not help me with this
but I will try to install it in another directory just to see if there is
something wrong with trying to install it in the default location.
What do you mean by:
> is the "Server" service up and running as well?
Thank you
Clyde
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:5graglF37hkkqU1@.mid.individual.net...
> hi,
> Microsoft News wrote:
>
> <-->
> Setup failed to configure the server. Refer to the server error logs and
> setup error logs for more information.
> MSI (s) (00!F4) [17:46:12:140]: 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 17:46:12: InstallFinalize. Return value 3.
> <-->
> this exception is usually related to
> http://support.microsoft.com/default.aspx?scid=kb;en-us;816499&Product=sql
> is the "Server" service up and running as well?
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
|||hi,
> What do you mean by:
>
go in the Administrative Tools and select the Services Applet... scroll down
till you find a service called "Server" (Supports file, print, and
named-pipe sharing over the network for this computer. If this service is
stopped, these functions will be unavailable. If this service is disabled,
any services that explicitly depend on it will fail to start.)
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Andrea
You are a great help but that was not it. The service is up and running. I
even stopped it and started it, then checked the event log to make sure no
error occured. But everything worked fine. The server service is working
file.
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:5gsig1F3i3s7nU1@.mid.individual.net...
> hi,
> go in the Administrative Tools and select the Services Applet... scroll
> down till you find a service called "Server" (Supports file, print, and
> named-pipe sharing over the network for this computer. If this service is
> stopped, these functions will be unavailable. If this service is disabled,
> any services that explicitly depend on it will fail to start.)
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
|||hi,
Microsoft News wrote:
> Andrea
> You are a great help but that was not it. The service is up and
> running. I even stopped it and started it, then checked the event
> log to make sure no error occured. But everything worked fine. The
> server service is working file.
Sometimes you may need to delete this key:
HKLM\Software\Microsoft\Windows\CurrentVersion\Set up\ExceptionComponents,
then reinstall the SQL Server again.
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
-- remove DMO to reply
|||Andrea,
I tried removing the key after wiping out any registry settings and the
folder from the computer after the last install. I also tried installing in
a different folder since I read some where that might help. But getting rid
of the registry key you meantioned below along with changing the path did
not fix the problem. I still get the same error.
Thank you
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:5gtuueF3hi7apU1@.mid.individual.net...
> hi,
> Microsoft News wrote:
> Sometimes you may need to delete this key:
> HKLM\Software\Microsoft\Windows\CurrentVersion\Set up\ExceptionComponents,
> then reinstall the SQL Server again.
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz http://italy.mvps.org
> DbaMgr2k ver 0.21.0 - DbaMgr ver 0.65.0 and further SQL Tools
> -- remove DMO to reply
>
|||This is a long shot but you aren't trying to install this through a Terminal
Server connection are you? This will fail with a 1460 error similar to what
you're seeing. The log indicates SQL Server service installed and started
successfully and then shut down. You might try installing with different
options to see if that makes a difference. Since you messed around with the
registry, you may now get different failures related to the registry key
being partially there. SQL Server uses several thousand registry key so I'm
reasonably certain you didn't remove them all.
This posting is provided "AS IS" with no warranties, and confers no rights.
Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm
"Microsoft News" <Name@.coxinet.net> wrote in message
news:el2nANG0HHA.3768@.TK2MSFTNGP06.phx.gbl...
> Andrea,
> I tried removing the key after wiping out any registry settings and the
> folder from the computer after the last install. I also tried installing
> in a different folder since I read some where that might help. But
> getting rid of the registry key you meantioned below along with changing
> the path did not fix the problem. I still get the same error.
> Thank you
> "Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
> news:5gtuueF3hi7apU1@.mid.individual.net...
>
|||Roger,
Yes I am installing through a terminal server connection. I had read
another post were people pointed to that as a POSSIBLE problem but it was
not clear as to why. We have installed over 20+ MSDE systems through
Terminal Server connection and NEVER a problem. But tomorrow I will try to
install on a BLANK machine but this time I will have a local user run the
MSDE install.

> successfully and then shut down. You might try installing with different
> options to see if that makes a difference. Since you messed around with
> the
What different options are you referring to? I am installing with the
following command line:
setup instancename=<OurInstance> SECURITYMODE=SQL SAPWD=<SomePassword> /L*V
C:\msde.log

> options to see if that makes a difference. Since you messed around with
> the registry, you may now get different failures related to the registry
> key being partially there. SQL Server uses several thousand registry key
> so I'm reasonably certain you didn't remove them all.
Some time we try to install again after the install fails, what I do is go
into the registry and strip out everything that has SQL or MSSQL in the key,
that does not relate to ODBC. I figured that was cleaning up everything
because if you could look at the log file what you would see is that MSDE
rollback the install and remove all those thousands of registry keys. But
even if we do not get them all, as I said before we have tried MANY time to
format and re-install on a blank computer. I get the same error whether I
strip out keys or format. So your assumption of a different failures
related to registry key being partially there is incorrect.
Thanks for you help and advice, I will try to install locally and not
remoted, on a blank computer and see what happens. Any more suggestions
would be VERY helpful.
Clyde
"Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
news:48A8AC3E-F262-4875-BCCF-315DB9BDC51A@.microsoft.com...
> This is a long shot but you aren't trying to install this through a
> Terminal Server connection are you? This will fail with a 1460 error
> similar to what you're seeing. The log indicates SQL Server service
> installed and started successfully and then shut down. You might try
> installing with different options to see if that makes a difference.
> Since you messed around with the registry, you may now get different
> failures related to the registry key being partially there. SQL Server
> uses several thousand registry key so I'm reasonably certain you didn't
> remove them all.
> --
> This posting is provided "AS IS" with no warranties, and confers no
> rights.
> Use of included script samples are subject to the terms specified at
> http://www.microsoft.com/info/cpyright.htm
> "Microsoft News" <Name@.coxinet.net> wrote in message
> news:el2nANG0HHA.3768@.TK2MSFTNGP06.phx.gbl...
>
|||Roger,
Ok, we were able to install on a BLANK xp computer, we did nothing but
install XP, service pack 2, we did not install any hardware drivers (network
card or video card drivers, etc) we took all the windows defaults.
Plus, we did not remote in and try the installation, we just did the install
locally. The last thing we did was use MSDE sp4 not MSDE sp3 which I do not
think made a difference but I wanted to make sure anyone reading this would
know.
It all installed fine. I think the issue might have either been some other
driver or not installing remotely but we have installed remotely on a lot of
computers so I don't see the reason that would not work. The drivers are
the only other thing I can think of which might be the issue.
But thank to you and Andrea for all your help and I am glad this has been
solved.
Clyde W.
"Microsoft News" <Name@.coxinet.net> wrote in message
news:OzZdD2w0HHA.5380@.TK2MSFTNGP04.phx.gbl...
> Roger,
> Yes I am installing through a terminal server connection. I had read
> another post were people pointed to that as a POSSIBLE problem but it was
> not clear as to why. We have installed over 20+ MSDE systems through
> Terminal Server connection and NEVER a problem. But tomorrow I will try
> to install on a BLANK machine but this time I will have a local user run
> the MSDE install.
>
> What different options are you referring to? I am installing with the
> following command line:
> setup instancename=<OurInstance> SECURITYMODE=SQL SAPWD=<SomePassword>
> /L*V C:\msde.log
>
> Some time we try to install again after the install fails, what I do is go
> into the registry and strip out everything that has SQL or MSSQL in the
> key, that does not relate to ODBC. I figured that was cleaning up
> everything because if you could look at the log file what you would see is
> that MSDE rollback the install and remove all those thousands of registry
> keys. But even if we do not get them all, as I said before we have tried
> MANY time to format and re-install on a blank computer. I get the same
> error whether I strip out keys or format. So your assumption of a
> different failures related to registry key being partially there is
> incorrect.
> Thanks for you help and advice, I will try to install locally and not
> remoted, on a blank computer and see what happens. Any more suggestions
> would be VERY helpful.
> Clyde
> "Roger Wolter[MSFT]" <rwolter@.online.microsoft.com> wrote in message
> news:48A8AC3E-F262-4875-BCCF-315DB9BDC51A@.microsoft.com...
>

Install MSDE2000 failed

Hi,
I'm on Win2000 Pro Version 5.00.2195
I've installed succesfully Microsoft SQL Server 2000
Desktop Engine (MSDE 2000) Release A...
As I forgot to use the DISABLENETWORKPROTOCOLS=0
and SECURITYMODE=SQL
flags the first time I decided to uninstall MSDE.
Now, it won't install anymore. I use
setup SAPWD="mystrongpasswd" SECURITYMODE=SQL DISABLENETWORKPROTOCOLS=0 /L*v
C:/MSDELog.log
Here is my log file :
....
Starting custom action SetPropSQLMSDEInstalled
FindSet for ProductCode <{E09B48B5-E141-427A-AB0C-D3605127224A}> returned 1
MSI (s) (E0!5C) [19:01:19:368]: PROPERTY CHANGE: Adding SQLMSDEInstalled
property. Its value is '1'.
Setting SQLMSDEInstalled by MsiSetProperty returned 0
Setting SQLMSDESelected by MsiSetProperty returned 0
End SetPropSQLMSDEInstalled
Action ended 19:01:19:
SetPropSQLMSDEInstalled.2D02443E_7002_4C0B_ABC9_EA B2C064397B. Return value
1.
MSI (s) (E0:40) [19:01:19:368]: Doing action:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B
Action start 19:01:19:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B.
MSI (s) (E0:30) [19:01:19:378]: Invoking remote custom action. DLL:
C:\WINNT\Installer\MSI71.tmp, Entrypoint: RestoreSetupParams
SOFTWARE\Microsoft\Microsoft SQL Server
Setup.{E09B48B5-E141-427A-AB0C-D3605127224A}
Entering Function MyMsiEvaluateCondition
MsiEvaluateCondition for SQLMSDEInstalled returned TRUE
End Function MyMsiEvaluateCondition
Error reading setup parameters
Action ended 19:01:19:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value 3.
Action ended 19:01:19: INSTALL. Return value 3.
Property(S): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(S): SqlDataDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlProgramDir = C:\Program Files\Microsoft SQL Server\
Property(S): SqlSecurityMode = SQL
Property(S): SqlSa...
Property(S): VersionNT = 500
Property(S): ALLUSERS = 1
Property(S): ARPNOMODIFY = 1
Property(S): DefaultUIFont = Tahoma8
Property(S): INSTALLLEVEL = 3
Property(S): LIMITUI = 1
Property(S): Manufacturer = Microsoft Corporation
Property(S): ProductCode = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(S): ProductLanguage = 1033
Property(S): ProductName = Microsoft SQL Server Desktop Engine
Property(S): ProductVersion = 8.00.761
Property(S): MsiHiddenProperties = SqlSa...
...
Property(S): ColorBits = 32
Property(S): TTCSupport = 1
Property(S): Time = 19:01:19
Property(S): Date = 4/05/2005
Property(S): MsiNetAssemblySupport = 1.1.4322.2032
Property(S): RedirectedDllSupport = 1
Property(S): Privileged = 1
Property(S): DATABASE = C:\WINNT\Installer\85db8.msi
Property(S): OriginalDatabase = C:\MSDERelA\Setup\SqlRun01.msi
Property(S): UILevel = 3
MSI (s) (E0:40) [19:01:19:588]: MainEngineThread is returning 1603
MSI (s) (E0:F4) [19:01:19:588]: Destroying RemoteAPI object.
MSI (s) (E0:44) [19:01:19:588]: Custom Action Manager thread ending.
MSI (c) (24:28) [19:01:19:588]: Back from server. Return value: 1603
MSI (c) (24:28) [19:01:19:588]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
Action ended 19:01:19: INSTALL. Return value 3.
Property(C): UpgradeCode = {421A321C-2214-4713-B3EB-253F2FBCCE49}
Property(C): VersionNT = 500
Property(C): ALLUSERS = 1
Property(C): ARPNOMODIFY = 1
Property(C): DefaultUIFont = Tahoma8
Property(C): INSTALLLEVEL = 3
Property(C): LIMITUI = 1
Property(C): Manufacturer = Microsoft Corporation
Property(C): ProductCode = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(C): ProductLanguage = 1033
Property(C): ProductName = Microsoft SQL Server Desktop Engine
Property(C): ProductVersion = 8.00.761
Property(C): MsiHiddenProperties = SqlSa...
Property(C): SQLVersion.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 8.00.194
Property(C): SQLExitCode.2D02443E_7002_4C0B_ABC9_EAB2C064397B = 1603
.....
Property(C): DATABASE = C:\DOCUME~1\ADMINI~1\LOCALS~1\Temp\12f490.msi
Property(C): OriginalDatabase = C:\MSDERelA\Setup\SqlRun01.msi
Property(C): UILevel = 3
Property(C): ACTION = INSTALL
=== Logging stopped: 4/05/2005 19:01:19 ===
MSI (c) (24:28) [19:01:19:608]: Note: 1: 1708
MSI (c) (24:28) [19:01:19:608]: Product: Microsoft SQL Server Desktop
Engine -- Installation operation failed.
MSI (c) (24:28) [19:01:19:618]: Grabbed execution mutex.
MSI (c) (24:28) [19:01:19:618]: Cleaning up uninstalled install packages, if
any exist
MSI (c) (24:28) [19:01:19:618]: MainEngineThread is returning 1603
=== Verbose logging stopped: 4/05/2005 19:01:19 ===
What I have try so far :
- try to re-install without adding flags
- check server service and file and printer sharing
- HOW TO : remove manually instance Microsoft SQL Server 2000 (MSDE 2000)
Desktop Engine (MSDN)
- remove all files and folders under Program Files
- clean the registry
- msizap.exe T {E09B48B5-E141-427A-AB0C-D3605127224A} not sure how
to use this the right way... ?
- msizap.exe T {2D02443E_7002_4C0B_ABC9_EAB2C064397B}
- remove entry HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer
...
Thank for your help !!!
Martin
Hello,
I notice the following information in the verbose log:
Entering Function MyMsiEvaluateCondition
MsiEvaluateCondition for SQLMSDEInstalled returned TRUE
End Function MyMsiEvaluateCondition
Error reading setup parameters
Action ended 19:01:19:
RestoreSetupParams.2D02443E_7002_4C0B_ABC9_EAB2C06 4397B. Return value 3.
Action ended 19:01:19: INSTALL. Return value 3.
This problem occurs if the previous MSDE setup is not uninstalled
successfully. I recommend you refer to the following article to remove MSDE:
320873 HOW TO: Manually Remove a Microsoft SQL Server 2000 Desktop Engine
(MSDE
http://support.microsoft.com/?id=320873
You can perform the following steps to remove the MSDE 2000 installer
references:
Step 1: Download and install Msizap.exe.
Step 2: Determine the ProductCode for the MSDE instance that was installed.
You can find the ProductCode key value in the following registry key:
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\MSSQLServer\ Setup
The ProductCode key value may be {E09B48B5-E141-427A-AB0C-D3605127224A}
Step 3: Use Msizap.exe to remove all Windows Installer information for the
ProductCode of the MSDE 2000 instance.
1. Backup your registry file.
2. Click Start > Run, type CMD and press Enter.
3. Type the following line at the command prompt:
"C:\Program Files\MsiIntel.SDK\Tools\MSIZAP.EXE" T
{E09B48B5-E141-427A-AB0C-D3605127224A}
Note: you need to replace "C:\Program Files\MsiIntel.SDK\Tools" with the
folder which MSIZAP.EXE locates. You need to replace the
{E09B48B5-E141-427A-AB0C-D3605127224A} with your MSDE 2000 ProductCode.
Step 4: Follow the steps in the article 320873 to remove MSDE.
I hope the information is helpful.
Sophie Guo
Microsoft Online Partner Support
Get Secure! - www.microsoft.com/security
================================================== ===
When responding to posts, please "Reply to Group" via your newsreader so
that others may learn and benefit from your issue.
================================================== ===
This posting is provided "AS IS" with no warranties, and confers no rights.
|||Hi,
Thanks for your answer
but I've already followed these steps...
Something must be missing in that How To ?
My problem is now solved (restore a ghost image)
I couldn't wait...
Bye
Martin

Install MSDE2000 by InstallShield Professional 6.1

How can I include the MSDE2000 installation in an InstallShield Professional 6.1 project?
I have get a set of MSDE setup files including an MSI file, and how can I use it?
Thank you for any reply!Have you gotten this to work? I am looking at doing something similar.

Thanks.

Install MSDE without Microsoft .NET Framework

Hi
I want to include MSDE in my apps installation.
Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
Deployment Toolkit (Release Candidate) from
http://www.microsoft.com/downloads/d...DisplayLang=en
I have looked into the deployment toolkit which need Microsoft .NET
Framework.
But my client does not want to install the .NET Framework.
How can I do it?
Many thanks
Ken
You have two options if you can't use the loader:
1) Create your own loader using a non-managed language (C++, Delphi, VB6).
2) You can purchase a third party installation package
Cheers,
Brian A. Randell
MCW Technologies
"Ken" <kenchan@.fdlweb.com> wrote in message
news:uW7GAP7JEHA.208@.tk2msftngp13.phx.gbl...
> Hi
> I want to include MSDE in my apps installation.
> Microsoft SQL Server 2000 Desktop Engine (MSDE 2000)
> Deployment Toolkit (Release Candidate) from
>
http://www.microsoft.com/downloads/d...DisplayLang=en
> I have looked into the deployment toolkit which need Microsoft .NET
> Framework.
> But my client does not want to install the .NET Framework.
> How can I do it?
> Many thanks
> Ken
>
|||Thanks.
I have installshield version 9. How can I do it?
Thanks a lot
Ken
"Brian A. Randell" <brianr@.nospam.mcwtech.com> wrote in message
news:%23kSlIh7JEHA.2660@.TK2MSFTNGP09.phx.gbl...
> You have two options if you can't use the loader:
> 1) Create your own loader using a non-managed language (C++, Delphi, VB6).
> 2) You can purchase a third party installation package
>
> Cheers,
> Brian A. Randell
> MCW Technologies
> "Ken" <kenchan@.fdlweb.com> wrote in message
> news:uW7GAP7JEHA.208@.tk2msftngp13.phx.gbl...
>
http://www.microsoft.com/downloads/d...DisplayLang=en
>
|||Sorry Ken, I'm not familiar enough with InstallShield to provide qualified
advice. Maybe you can check with the InstallSheild folks to see what the
recommend.
Cheers,
Brian A. Randell
MCW Technologies
"Ken" <kenchan@.fdlweb.com> wrote in message
news:erU75xQKEHA.1156@.TK2MSFTNGP09.phx.gbl...[vbcol=seagreen]
> Thanks.
> I have installshield version 9. How can I do it?
> Thanks a lot
> Ken
>
> "Brian A. Randell" <brianr@.nospam.mcwtech.com> wrote in message
> news:%23kSlIh7JEHA.2660@.TK2MSFTNGP09.phx.gbl...
VB6).
>
http://www.microsoft.com/downloads/d...DisplayLang=en
>

Install MSDE with SP3 without User intervention

I have a 5 user app that uses MSDE as the database. It is run on a "SERVER"
any computer actually that they will use to use the same database.
I need an easy way for my low-tech users to stick in my install CD, select
Server installation , and I offer a named instance of SQL server using SQL
Security... Also needs to create a new copy of the database, offer them a
prompt for the DB password and more.
I need this to be as easy as possible.
What is the best route in doing this?
If it requires an DBA or high-tech user to install, then that will rule out
most of my clients, and make distributing this app and using MSDE not a very
wise choice.
Thanks for any help,
ShaneShane,
Your app sound very similar to ours and so do your users :> )
This is what I have just done and it works very well.
Our install software is InstallShield DevStudio 9.1 and it allows you to
conditionally install MSDE 2000. BTW it does not allow you to conditional
install MSDE 1.0. It also allows you to put in an instance name if you want
one.
So all I did was change the setup type screen that normally reads 'typical',
'minimum' and 'custom' to read 'server', 'client' and 'custom'. A Server
selection installs MSDE plus the client components and a Client selection
will not install MSDE.
As for the database itself I scripted all the schema, you can do that thru
EM, and enough table data to get the application going. ie Default Data.
You can run this either via a vbScript or batch file using the osql command.
We elected to script the data because some of our customers already have SQL
and they often want to use that, especially if there are large numbers of
users. It also gets over the problem of a customer having SQL, wanting to
use it, and their sort order is different to yours.
In the batch or vbscript you could offer prompts for sa password. Install
MSDE with a blank or known password, run the database scripts, ask for a new
password, change it and your done.
There's no easy way to do what you want, ie giving the user options like
passwords instance names etc., and I've tried them all. If you didn't want
to have the flexibility and wanted a set install then Installshield would do
it all. Just click on setup and it would install your app, msde, make the
instance, have a set sa password and attach or run a batch file to install
your databases. But, you have to make the decision.
Hope this helps.
Greg
--
greghines@.bigfoot.com.NOSPAM
Remove NOSPAM when replying
"SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:eCkwq$QEEHA.628@.TK2MSFTNGP10.phx.gbl...
> I have a 5 user app that uses MSDE as the database. It is run on a
"SERVER"
> any computer actually that they will use to use the same database.
> I need an easy way for my low-tech users to stick in my install CD, select
> Server installation , and I offer a named instance of SQL server using SQL
> Security... Also needs to create a new copy of the database, offer them a
> prompt for the DB password and more.
> I need this to be as easy as possible.
> What is the best route in doing this?
> If it requires an DBA or high-tech user to install, then that will rule
out
> most of my clients, and make distributing this app and using MSDE not a
very
> wise choice.
> Thanks for any help,
> Shane
>|||Thanks Greg.
Does the msde 2000 copy you are installing have SP3 already applied?
I installed on my dev machine using the one from VB.NET I think.
Also when you mention scripting with vbscript...is that from inside of
Install Shield or are you running that from wsh or something?
Since .NET comes with a decent installer I was thinking about making it with
that. Don't have a lot of funds to buy another installer.
But I could have two separate ones. One that installs the app, then another
that installs MSDE, and maybe have them both run from a webpage that starts
with autorun. Let them type sa password to use in the webpage and somehow
use javascript or something to run the actual MSDE with the appropriate
params. I don't know that might be hard. These are some things I have
thought of.
I know we are licensed to use MSDE for owning .NET Pro. There seem to be
several flavors of MSDE, and seems I saw one that would install with SP3
included. Guess I need to research some more.
At present, I have a new fire to put out. Did a restore on the database and
now ADO.NET fails to connect.
So can't do much else until I resolve this.
I am just gathering information on each area that I need or will need in
order to distribute the project easily.
Thanks for all your advice.
It is very helpful to hear from you,
Shane
"Greg Hines" <greghines@.bigfoot.com.NOSPAM> wrote in message
news:1080108879.380672@.gw-gos.nlc.net.au...
> Shane,
> Your app sound very similar to ours and so do your users :> )
> This is what I have just done and it works very well.
> Our install software is InstallShield DevStudio 9.1 and it allows you to
> conditionally install MSDE 2000. BTW it does not allow you to conditional
> install MSDE 1.0. It also allows you to put in an instance name if you
want
> one.
> So all I did was change the setup type screen that normally reads
'typical',
> 'minimum' and 'custom' to read 'server', 'client' and 'custom'. A Server
> selection installs MSDE plus the client components and a Client selection
> will not install MSDE.
> As for the database itself I scripted all the schema, you can do that thru
> EM, and enough table data to get the application going. ie Default Data.
> You can run this either via a vbScript or batch file using the osql
command.
> We elected to script the data because some of our customers already have
SQL
> and they often want to use that, especially if there are large numbers of
> users. It also gets over the problem of a customer having SQL, wanting to
> use it, and their sort order is different to yours.
> In the batch or vbscript you could offer prompts for sa password. Install
> MSDE with a blank or known password, run the database scripts, ask for a
new
> password, change it and your done.
> There's no easy way to do what you want, ie giving the user options like
> passwords instance names etc., and I've tried them all. If you didn't
want
> to have the flexibility and wanted a set install then Installshield would
do
> it all. Just click on setup and it would install your app, msde, make the
> instance, have a set sa password and attach or run a batch file to install
> your databases. But, you have to make the decision.
> Hope this helps.
> Greg
> --
> greghines@.bigfoot.com.NOSPAM
> Remove NOSPAM when replying
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:eCkwq$QEEHA.628@.TK2MSFTNGP10.phx.gbl...
> "SERVER"
select
SQL
a
> out
> very
>|||One Question, sp2kdesksp3.exe
I ran it to install to a local folder.
This says to have an install complete with SP3.
Is this the one I should use for install?
If so, then I just need a front end and to prompt for sa password and I am
set. Then using the scripting and such that you spoke of with OSQL to
install the database and such.
Thanks,
Shane
I downloaded a file called,
"Greg Hines" <greghines@.bigfoot.com.NOSPAM> wrote in message
news:1080108879.380672@.gw-gos.nlc.net.au...
> Shane,
> Your app sound very similar to ours and so do your users :> )
> This is what I have just done and it works very well.
> Our install software is InstallShield DevStudio 9.1 and it allows you to
> conditionally install MSDE 2000. BTW it does not allow you to conditional
> install MSDE 1.0. It also allows you to put in an instance name if you
want
> one.
> So all I did was change the setup type screen that normally reads
'typical',
> 'minimum' and 'custom' to read 'server', 'client' and 'custom'. A Server
> selection installs MSDE plus the client components and a Client selection
> will not install MSDE.
> As for the database itself I scripted all the schema, you can do that thru
> EM, and enough table data to get the application going. ie Default Data.
> You can run this either via a vbScript or batch file using the osql
command.
> We elected to script the data because some of our customers already have
SQL
> and they often want to use that, especially if there are large numbers of
> users. It also gets over the problem of a customer having SQL, wanting to
> use it, and their sort order is different to yours.
> In the batch or vbscript you could offer prompts for sa password. Install
> MSDE with a blank or known password, run the database scripts, ask for a
new
> password, change it and your done.
> There's no easy way to do what you want, ie giving the user options like
> passwords instance names etc., and I've tried them all. If you didn't
want
> to have the flexibility and wanted a set install then Installshield would
do
> it all. Just click on setup and it would install your app, msde, make the
> instance, have a set sa password and attach or run a batch file to install
> your databases. But, you have to make the decision.
> Hope this helps.
> Greg
> --
> greghines@.bigfoot.com.NOSPAM
> Remove NOSPAM when replying
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:eCkwq$QEEHA.628@.TK2MSFTNGP10.phx.gbl...
> "SERVER"
select
SQL
a
> out
> very
>|||Shane,
The MSDE 2000 Merge Module with DevStudio 9 does have SP3 already applied,
so you don't have to worry about applying it.
DevStudio allows either Installshield Scripting or a VBScript to be run from
inside Installshield. So you can do things like:-
a) Installer selects the type of setup. Typical, Min. Custom etc.
b) This opens your custom dialog with say some questions to answer. eg sa
password. Their responses are stored in variables.
c) They click on Next to proceed with the installation.
Or you could do:-
a) Install a default installation of MSDE 2000 SP3 with a blank sa password.
b) After setup finishes run either a vbScript or Installshield script that
asks for an sa password.
c) Within that script run an osql command to change the sa password.
If you want to go with MSDE 2000 then there is no reason to have 2 install
apps. DevStudio 9 will do all you want and more.
As I said earlier I've been installing MSDE 1.0 and more recently MSDE 2000
with our apps. for sometime now and the MSDE 2000 Merge Module with
DevStudio is by far the easiest as it can be conditionally installed. If
you want to go with MSDE 1.0 then it has to be script driven as MSDE 1.0
cannot be conditionally installed.
Hope I've been helpful.
Regards,
Greg
--
greghines@.bigfoot.com.NOSPAM
Remove NOSPAM when replying
"SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
news:epF$cacEEHA.3788@.TK2MSFTNGP10.phx.gbl...
> Thanks Greg.
> Does the msde 2000 copy you are installing have SP3 already applied?
> I installed on my dev machine using the one from VB.NET I think.
> Also when you mention scripting with vbscript...is that from inside of
> Install Shield or are you running that from wsh or something?
> Since .NET comes with a decent installer I was thinking about making it
with
> that. Don't have a lot of funds to buy another installer.
> But I could have two separate ones. One that installs the app, then
another
> that installs MSDE, and maybe have them both run from a webpage that
starts
> with autorun. Let them type sa password to use in the webpage and somehow
> use javascript or something to run the actual MSDE with the appropriate
> params. I don't know that might be hard. These are some things I have
> thought of.
> I know we are licensed to use MSDE for owning .NET Pro. There seem to be
> several flavors of MSDE, and seems I saw one that would install with SP3
> included. Guess I need to research some more.
> At present, I have a new fire to put out. Did a restore on the database
and
> now ADO.NET fails to connect.
> So can't do much else until I resolve this.
> I am just gathering information on each area that I need or will need in
> order to distribute the project easily.
> Thanks for all your advice.
> It is very helpful to hear from you,
> Shane
>
> "Greg Hines" <greghines@.bigfoot.com.NOSPAM> wrote in message
> news:1080108879.380672@.gw-gos.nlc.net.au...
conditional
> want
> 'typical',
selection
thru
Data.
> command.
> SQL
of
to
Install
> new
> want
would
> do
the
install
> select
> SQL
them
> a
rule
a
>|||Thanks Greg.
I appreciate the info.
Since I don't have a budget to buy additional setup software right now.
I chose to create a prompting VC++ app to do my server setup.
It prompts for all the needed info, creates the setup.ini file in a temp dir
and then calls the setup.exe program for MSDE passing the right parameters,
then it calls a batch file passing that info, so that I can create the
structure with calls to osql with scripts and then will copy the data as
soon as I learn how.
How can I copy data into the new database?
Is BCP the only option. Seems complicated. I was hoping for an easier way
to do that. The amount of data needing to be copied is less than 100 rows
in 8 tables.
Thanks,
Shane
"Greg Hines" <greghines@.bigfoot.com.NOSPAM> wrote in message
news:1080511923.196920@.gw-gos.nlc.net.au...
> Shane,
> The MSDE 2000 Merge Module with DevStudio 9 does have SP3 already applied,
> so you don't have to worry about applying it.
> DevStudio allows either Installshield Scripting or a VBScript to be run
from
> inside Installshield. So you can do things like:-
> a) Installer selects the type of setup. Typical, Min. Custom etc.
> b) This opens your custom dialog with say some questions to answer. eg sa
> password. Their responses are stored in variables.
> c) They click on Next to proceed with the installation.
> Or you could do:-
> a) Install a default installation of MSDE 2000 SP3 with a blank sa
password.
> b) After setup finishes run either a vbScript or Installshield script that
> asks for an sa password.
> c) Within that script run an osql command to change the sa password.
> If you want to go with MSDE 2000 then there is no reason to have 2 install
> apps. DevStudio 9 will do all you want and more.
> As I said earlier I've been installing MSDE 1.0 and more recently MSDE
2000
> with our apps. for sometime now and the MSDE 2000 Merge Module with
> DevStudio is by far the easiest as it can be conditionally installed. If
> you want to go with MSDE 1.0 then it has to be script driven as MSDE 1.0
> cannot be conditionally installed.
> Hope I've been helpful.
> Regards,
> Greg
> --
> greghines@.bigfoot.com.NOSPAM
> Remove NOSPAM when replying
> "SStory" <TheStorys@.TAKEOUTTHISSPAMBUSTERsofthome.net> wrote in message
> news:epF$cacEEHA.3788@.TK2MSFTNGP10.phx.gbl...
> with
> another
> starts
somehow
be
> and
to
> conditional
you
Server
> selection
> thru
> Data.
have
> of
wanting
> to
> Install
a
like
> would
> the
> install
message
using
> them
> rule
not
> a
>

Install msde with instancename on a W2003 cluster

How can i install the SQL MSDE (sp3a) with a instance name
on a windows 2003 cluster server.
A custumer has a windows 2003 cluster server. When i run
our setup, with parameters like intsance=myprogram, the
software installs normaly on the server. Our client
software louks voor
%Server%\%InstanceName% across the network.
The software don't see the instance name.
Thanks.
Sounds like it is installing correctly. There is nothing special about
installing MSDE on a node of a cluster. Can you use OSQL on the server you
installed MSDE on to connect to the SQL Server? Have you used svrnetcn.exe
to enable the protocols for MSDE? Have you applied SP3 to the MSDE
installation? TCP/IP is not available on Windows 2003 until SP3 is
installed on any version of SQL Server 2000.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Yes, the software installs correctly. (I don't see event
in the logs)
We used msde 2000 with sp3.
Yes i have used the svrnetcn.exe to configure the tcp/ip
protocol, set port to 1433.
I haven't used Osql to test the connection.
I test with the sql enterprice manager, to connect the
msde on the 2003 server. This don't work.
When i install the same msde software on a nomal Windows
2003 server everything works fine.
What else can i do?
What can there be wrong?
Thanks for your reply.
sql

Install MSDE questions

Hi everybody,
How can I install MSDE on drive <> C: ? Is this possible
at all ?
Best regards
eNWu
hi eNWu,
"eNWu" <enwu@.gazeta.pl> ha scritto nel messaggio
news:11ea01c47ba5$c020eca0$a301280a@.phx.gbl...
> Hi everybody,
> How can I install MSDE on drive <> C: ? Is this possible
> at all ?
by default, MSDE is installed on "Program Files" hosting disk... but you can
provide the DATADIR = '....' and TARGETDIR = '....' commandline parameter
in order to overrride theyr default settings...
part of the installation always require to be installed on x\Program Files\
in order to host binaries available and shared for all instances..
please have a look at
http://msdn.microsoft.com/library/de...stsql_84xl.asp
for MSDE setup.exe boostrap installer commandline parameters
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

Install MSDE on XP Home Ed. Unable connect DB from other PC

Hi,
I tried to Install MSDE (SQL Server free ed.) on XP Home Ed. It's running
but from other computer I could not connect to that database using sa
account. Unlike when installed on XP Professional which MSDE can perform
almost like SQLServer. Does it because XP Home Ed.?
Thanks,
Martin
hi Martin,
prof_martin wrote:
> Hi,
> I tried to Install MSDE (SQL Server free ed.) on XP Home Ed. It's
> running but from other computer I could not connect to that database
> using sa account. Unlike when installed on XP Professional which MSDE
> can perform almost like SQLServer. Does it because XP Home Ed.?
>
MSDE installs by default disabling network protocols for security reasons...
you can bypass this setting at install time, providing the
DISABLENETWORKPROTOCOLS=0
parameter to the setup.exe boostrap installer and/or later, at "run time",
running the Server Network Utility (svrnetcn.exe) and enabling the
desired/required protocol(s)...
additionally, WinXP sp2 installs and enables by default the Windows
Firewall, and you have handle and manage to allow incoming remote
connections, as reported in http://support.microsoft.com/kb/841249/en-us
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||Ahaa Andrea,
So you are the one the author DBAMgr2K, I'm using it ver 0.7.0. Quite useful
some more it's free. Only thing about your powerful software when database
structure need to be amended some field for datatype, its prompt something so
I was not able to do it. Anyway nearly perfect for free level.
Just confirmed with you, we got 5 PC all XP Home, PC1 I installed
MSDE2K+DBAMgr2K, the rest of PC contain application which consume Data from
PC1. Is this by right should works? And Is this smart enough for low cost
infrastructure for SME?
We have plan to upgrade PC1 using XP Professional, if necessary.
I really appreciate your answer.
Thanks you,
Martin A.N. (from Singapore)
"Andrea Montanari" wrote:

> hi Martin,
> prof_martin wrote:
> MSDE installs by default disabling network protocols for security reasons...
> you can bypass this setting at install time, providing the
> DISABLENETWORKPROTOCOLS=0
> parameter to the setup.exe boostrap installer and/or later, at "run time",
> running the Server Network Utility (svrnetcn.exe) and enabling the
> desired/required protocol(s)...
> additionally, WinXP sp2 installs and enables by default the Windows
> Firewall, and you have handle and manage to allow incoming remote
> connections, as reported in http://support.microsoft.com/kb/841249/en-us
> --
> Andrea Montanari (Microsoft MVP - SQL Server)
> http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
> DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
> (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
> interface)
> -- remove DMO to reply
>
>
|||prof_martin wrote:
> Ahaa Andrea,
> So you are the one the author DBAMgr2K, I'm using it ver 0.7.0. Quite
> useful some more it's free. Only thing about your powerful software
> when database structure need to be amended some field for datatype,
> its prompt something so I was not able to do it. Anyway nearly
> perfect for free level.
thank you for your interest in this prj of mine, and please feel free to
(privately) contact me for any question or concern, as long as for
suggestions and feedback...

> Just confirmed with you, we got 5 PC all XP Home, PC1 I installed
> MSDE2K+DBAMgr2K, the rest of PC contain application which consume
> Data from PC1. Is this by right should works? And Is this smart
> enough for low cost infrastructure for SME?
> We have plan to upgrade PC1 using XP Professional, if necessary.
> I really appreciate your answer.
it is ok on the client level... but I'd go for XP pro on the server for the
advanced net facilities it provides on XP home...
my $0.02
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||hi,
i installed msde in windows 2000 prof. its installed succes fully but i dont
know how to run it.becase there is no indication for installation
completion.a folder which i gave in seup file was created and some folders
like binn,data, were created . but there is no tool to run the msde.
do i have to down load any thing more.
i down loaded msde 2000 release A.
thanks
vinoth
|||hi,
vinoth wrote:
> hi,
> i installed msde in windows 2000 prof. its installed succes fully but
> i dont know how to run it.becase there is no indication for
> installation completion.a folder which i gave in seup file was
> created and some folders like binn,data, were created . but there is
> no tool to run the msde.
> do i have to down load any thing more.
> i down loaded msde 2000 release A.
> thanks
> vinoth
you are correct, the installer terminates it's work without any prompt.. if
you provided the
/L*v "c:\MsdeLog.txt"
additional parameter to the setup.exe boostrap installer you can inspect it
at it's end to verify MSDE has been succesfully installed...
you won't see anything in the tray area (the SQL Server Service Manager
icon) i f you do not restart your system, as all this requires a reboot to
register SQL Server services..
but you can connect to it using the only (command line) tool MSDE is
provided with, oSql.exe as reported in
http://support.microsoft.com/default...;EN-US;q325003
again... MSDE is not provided with graphical tools, but you can have a look
at a free prj of mine at the link followind my sign, which provides a user
interface similar to Enterprise Manager... further tools, bot commercial and
free are listed in http://www.microsoft.com/sql/msde/partners and/or
http://www.aspfaq.com/show.asp?id=2442
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.15.0 - DbaMgr ver 0.60.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

Install MSDE on New System

I currently have a WinXP system which has MSDE installed. I am replacing
that system with a new one and I want to install MSDE and then move a copy
of all my current DBs. I have MS Office 2003 and I plan to install MSDE from
those CDs. To move copies of the DBs I plan to Detach them at the old
system, copy the DB to the new system and attach it there (and attach it
back on the old system as well - just to be safe)
Is that a reasonable approach or is there a better way?
Wayne
hi Wayne,
Wayne Wengert wrote:
> I currently have a WinXP system which has MSDE installed. I am
> replacing that system with a new one and I want to install MSDE and
> then move a copy of all my current DBs. I have MS Office 2003 and I
> plan to install MSDE from those CDs. To move copies of the DBs I plan
> to Detach them at the old system, copy the DB to the new system and
> attach it there (and attach it back on the old system as well - just
> to be safe)
> Is that a reasonable approach or is there a better way?
> Wayne
it's a reasonable approach ... you can go on..
just a note... if you use SQL Server standard logins, please verify orphaned
user, that's to say users no longer in sync with their respective logins...
this sync is established on the sid column of database..sysusers and
master..syslogins, and where NULL is returned you have orhpaned users
problems.. so please check
http://msdn.microsoft.com/library/de...ca-cz_8qzy.asp
for sp_change_users_login system stored procedure synopsis and
http://www.sqlservercentral.com/colu...okenlogins.asp
Neil Boyle article for further info..
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
|||Thanks. Will do!
Wayne
"Andrea Montanari" <andrea.sqlDMO@.virgilio.it> wrote in message
news:3cdnj9F6l0itoU1@.individual.net...
> hi Wayne,
> Wayne Wengert wrote:
> it's a reasonable approach ... you can go on..
> just a note... if you use SQL Server standard logins, please verify
orphaned
> user, that's to say users no longer in sync with their respective
logins...
> this sync is established on the sid column of database..sysusers and
> master..syslogins, and where NULL is returned you have orhpaned users
> problems.. so please check
>
http://msdn.microsoft.com/library/de...ca-cz_8qzy.asp
> for sp_change_users_login system stored procedure synopsis and
> http://www.sqlservercentral.com/colu...okenlogins.asp
> Neil Boyle article for further info..
> --
> 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
>

Install MSDE on 2003 server cluster

I've two server 2003 configurated as cluster. How to
install MSDE2000A on nodes ?
hi Carlo,
Carlo Dolenz wrote:
> I've two server 2003 configurated as cluster. How to
> install MSDE2000A on nodes ?
AFAIK MSDE does not support cluster installation...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
|||You can install MSDE as an instance (default or named) on each node of the
cluster but MSDE is not cluster aware so if you're thinking of a
mini-failover cluster, that's not gonna happen with MSDE.
joe.
"Carlo Dolenz" <anonymous@.discussions.microsoft.com> wrote in message
news:282d01c514ea$7f039090$a501280a@.phx.gbl...
> I've two server 2003 configurated as cluster. How to
> install MSDE2000A on nodes ?

Install MSDE need XP disc

I have been installing MSDE2000 on several XP machines. Couple of them asked
for XP installation disc during the installation of MSDE. Others didn't.
Does anyone know why sometimes the installation of MSDE need the XP disc?
Thanks in advance.
Regards,
Otto
There might be requirements for things that weren't set up initially, like
TCP/IP/network support, MDAC, etc. I'm not sure of all the system
requirements for MSDE but if these installations are not all identical there
will likely be some required items missing...
http://www.aspfaq.com/
(Reverse address to reply.)
"Otto" <Otto@.discussions.microsoft.com> wrote in message
news:E7E21430-74ED-425B-B2CB-787D7DC6C66C@.microsoft.com...
> I have been installing MSDE2000 on several XP machines. Couple of them
asked
> for XP installation disc during the installation of MSDE. Others didn't.
> Does anyone know why sometimes the installation of MSDE need the XP disc?
> Thanks in advance.
> --
> Regards,
> Otto

Install MSDE need XP disc

I have been installing MSDE2000 on several XP machines. Couple of them asked
for XP installation disc during the installation of MSDE. Others didn't.
Does anyone know why sometimes the installation of MSDE need the XP disc?
Thanks in advance.
--
Regards,
OttoThere might be requirements for things that weren't set up initially, like
TCP/IP/network support, MDAC, etc. I'm not sure of all the system
requirements for MSDE but if these installations are not all identical there
will likely be some required items missing...
--
http://www.aspfaq.com/
(Reverse address to reply.)
"Otto" <Otto@.discussions.microsoft.com> wrote in message
news:E7E21430-74ED-425B-B2CB-787D7DC6C66C@.microsoft.com...
> I have been installing MSDE2000 on several XP machines. Couple of them
asked
> for XP installation disc during the installation of MSDE. Others didn't.
> Does anyone know why sometimes the installation of MSDE need the XP disc?
> Thanks in advance.
> --
> Regards,
> Otto

Install MSDE need XP disc

I have been installing MSDE2000 on several XP machines. Couple of them asked
for XP installation disc during the installation of MSDE. Others didn't.
Does anyone know why sometimes the installation of MSDE need the XP disc?
Thanks in advance.
Regards,
OttoThere might be requirements for things that weren't set up initially, like
TCP/IP/network support, MDAC, etc. I'm not sure of all the system
requirements for MSDE but if these installations are not all identical there
will likely be some required items missing...
http://www.aspfaq.com/
(Reverse address to reply.)
"Otto" <Otto@.discussions.microsoft.com> wrote in message
news:E7E21430-74ED-425B-B2CB-787D7DC6C66C@.microsoft.com...
> I have been installing MSDE2000 on several XP machines. Couple of them
asked
> for XP installation disc during the installation of MSDE. Others didn't.
> Does anyone know why sometimes the installation of MSDE need the XP disc?
> Thanks in advance.
> --
> Regards,
> Ottosql