Inserting Null Value: failed

Showing posts with label failed. Show all posts

Friday, March 30, 2012

Install roll back

Hi Guys,
During install of msde2000a, at the last few second of
install on a 2000 server box, installation failed and
rollback. Could anyone can help to solve the problem,
below copied from msde log file.
Thanks,
Ted
Action 14:58:50:
DisableNetAccess.2D02443E_7002_4C0B_ABC9_EAB2C0643 97B.
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-
E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\C2KUSE~1.CLA\LOCALS~1
\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library C:\DOCUME~1
\C2KUSE~1.CLA\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-
D3605127224A}\sqlcax.dll
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-
E141-427A-AB0C-D3605127224A}
Starting custom action DisableNetAccess()
Ending custom action DisableNetAccess()
Action 14:58:50: WriteEnvironmentStrings. Updating
environment strings
WriteEnvironmentStrings: Name: PATH, Value: C:\Program
Files\Microsoft SQL Server\80\Tools\Binn\, Action
1610612738
Action 14:58:50: RegisterTypeLibraries. Registering type
libraries
RegisterTypeLibraries: LibID: {10010001-E260-11CF-AE68-
00AA004A34D5}
RegisterTypeLibraries: LibID: {10010001-EB1C-11CF-AE6E-
00AA004A34D5}
RegisterTypeLibraries: LibID: {10010200-740B-11D0-AE7B-
00AA004A34D5}
Action 14:58:51: InstallServices. Installing new services
Action 14:58:51:
InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B.
SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-
E141-427A-AB0C-D3605127224A}
TempFolder is C:\DOCUME~1\C2KUSE~1.CLA\LOCALS~1
\Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
Loading extended custom action library C:\DOCUME~1
\C2KUSE~1.CLA\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
PerfmonLoad routine returned error code 6
Action ended 14:58:52: InstallFinalize. Return value 3.
Action 14:58:52: Rollback. Rolling back action:
If more of the log will help let me know.
Hi Ted,
Is your 2000 server part of a domain or standalone?
bigp
"Ted" <anonymous@.discussions.microsoft.com> wrote in message news:<355701c4c34c$ce848a60$a401280a@.phx.gbl>...
> Hi Guys,
> During install of msde2000a, at the last few second of
> install on a 2000 server box, installation failed and
> rollback. Could anyone can help to solve the problem,
> below copied from msde log file.
> Thanks,
> Ted
>
> Action 14:58:50:
> DisableNetAccess.2D02443E_7002_4C0B_ABC9_EAB2C0643 97B.
> SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-
> E141-427A-AB0C-D3605127224A}
> TempFolder is C:\DOCUME~1\C2KUSE~1.CLA\LOCALS~1
> \Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library C:\DOCUME~1
> \C2KUSE~1.CLA\LOCALS~1\Temp\{E09B48B5-E141-427A-AB0C-
> D3605127224A}\sqlcax.dll
> SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-
> E141-427A-AB0C-D3605127224A}
> Starting custom action DisableNetAccess()
> Ending custom action DisableNetAccess()
> Action 14:58:50: WriteEnvironmentStrings. Updating
> environment strings
> WriteEnvironmentStrings: Name: PATH, Value: C:\Program
> Files\Microsoft SQL Server\80\Tools\Binn\, Action
> 1610612738
> Action 14:58:50: RegisterTypeLibraries. Registering type
> libraries
> RegisterTypeLibraries: LibID: {10010001-E260-11CF-AE68-
> 00AA004A34D5}
> RegisterTypeLibraries: LibID: {10010001-EB1C-11CF-AE6E-
> 00AA004A34D5}
> RegisterTypeLibraries: LibID: {10010200-740B-11D0-AE7B-
> 00AA004A34D5}
> Action 14:58:51: InstallServices. Installing new services
> Action 14:58:51:
> InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B.
> SOFTWARE\Microsoft\Microsoft SQL Server Setup.{E09B48B5-
> E141-427A-AB0C-D3605127224A}
> TempFolder is C:\DOCUME~1\C2KUSE~1.CLA\LOCALS~1
> \Temp\{E09B48B5-E141-427A-AB0C-D3605127224A}\
> Loading extended custom action library C:\DOCUME~1
> \C2KUSE~1.CLA\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
> PerfmonLoad routine returned error code 6
> Action ended 14:58:52: InstallFinalize. Return value 3.
> Action 14:58:52: Rollback. Rolling back action:
> If more of the log will help let me know.
|||I'm having the same problem he describes. It is a standalone server. I have found several web pages that detail this problem, but have yet to find a solution to it for Windows 2000 professional.
This page outlines the specific problem I'm having:
http://www.crescentbloom.com/III/D/11.htm
But in it's workaround, step 4 is something that my computer doesn't have (a 'Server' item on my services list)
I have also found instructions from Microsoft's site on how to fix this in Win 2003, but they also do not work for Win 2000 Pro. Can anybody be of help? Thank you!
-Greg
*****************************************
* A copy of the whole thread can be found at:
* http://www.sqlmonster.com/Uwe/Forum...erver-msde/681
*
* Report spam or abuse by clicking the following URL:
* http://www.sqlmonster.com/Uwe/Abuse...a630a1edd2a9d2
*****************************************
|||The Server is part of a large domain, I have installed
MSDE on other servers on the same domain and they worked
fine.

>--Original Message--
>Hi Ted,
>Is your 2000 server part of a domain or standalone?
>bigp
>"Ted" <anonymous@.discussions.microsoft.com> wrote in
message news:<355701c4c34c$ce848a60$a401280a@.phx.gbl>...[vbcol=seagreen]
{E09B48B5-[vbcol=seagreen]
{E09B48B5-[vbcol=seagreen]
type[vbcol=seagreen]
services[vbcol=seagreen]
{E09B48B5-[vbcol=seagreen]
{E09B48B5-
>.
>
|||The server service is runing ok

>--Original Message--
>I'm having the same problem he describes. It is a
standalone server. I have found several web pages that
detail this problem, but have yet to find a solution to
it for Windows 2000 professional.
>This page outlines the specific problem I'm having:
>http://www.crescentbloom.com/III/D/11.htm
>But in it's workaround, step 4 is something that my
computer doesn't have (a 'Server' item on my services
list)
>I have also found instructions from Microsoft's site on
how to fix this in Win 2003, but they also do not work
for Win 2000 Pro. Can anybody be of help? Thank you!
>-Greg
>*****************************************
>* A copy of the whole thread can be found at:
>* http://www.sqlmonster.com/Uwe/Forum.aspx/sql-server-
msde/681
>*
>* Report spam or abuse by clicking the following URL:
>* http://www.sqlmonster.com/Uwe/Abuse.aspx?
aid=c471d6429e704a1082a630a1edd2a9d2
>*****************************************
>.
>
|||Can your server locate the PDC, the fsmocheck line of dcdiag?
<anonymous@.discussions.microsoft.com> wrote in message news:<43ee01c4c56d$de6b0800$a601280a@.phx.gbl>...[vbcol=seagreen]
> The Server is part of a large domain, I have installed
> MSDE on other servers on the same domain and they worked
> fine.
> message news:<355701c4c34c$ce848a60$a401280a@.phx.gbl>...
> {E09B48B5-
> {E09B48B5-
> type
> services
> {E09B48B5-
> {E09B48B5-
|||It is the pdc.
Do you think it my be rights?

>--Original Message--
>Can your server locate the PDC, the fsmocheck line of
dcdiag?
><anonymous@.discussions.microsoft.com> wrote in message
news:<43ee01c4c56d$de6b0800$a601280a@.phx.gbl>...[vbcol=seagreen]
worked[vbcol=seagreen]
$a401280a@.phx.gbl>...[vbcol=seagreen]
of[vbcol=seagreen]
and[vbcol=seagreen]
problem,[vbcol=seagreen]
DisableNetAccess.2D02443E_7002_4C0B_ABC9_EAB2C0643 97B.[vbcol=seagreen]
AB0C-[vbcol=seagreen]
C:\Program[vbcol=seagreen]
AE68-[vbcol=seagreen]
AE6E-[vbcol=seagreen]
AE7B-[vbcol=seagreen]
InstallPerfMon.2D02443E_7002_4C0B_ABC9_EAB2C064397 B.[vbcol=seagreen]
AB0C-[vbcol=seagreen]
value 3.
>.
>

Wednesday, March 28, 2012

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

Monday, March 26, 2012

Install MSDE2000 failed and auto rollback

Dear all,
I use a windows xp with sp1 installed
Then, i install SQL server client tools, this ok!
Then, i install msde2000 , but it auto rollback during installing process
and it does show any error or message...
Even , i try to use sql2ksp3 to install, it also like this, what is the
problem?
Is it the winxp sp1 make this occurs? or other problems?
hi Joe,
Joe wrote:
> Dear all,
> I use a windows xp with sp1 installed
> Then, i install SQL server client tools, this ok!
> Then, i install msde2000 , but it auto rollback during installing
> process and it does show any error or message...
> Even , i try to use sql2ksp3 to install, it also like this, what is
> the problem?
> Is it the winxp sp1 make this occurs? or other problems?
please add the
/L*v "C:\MsdeLog.Txt"
parameter to your command line call to the setup.exe boostrap installer...
this will enable verbose logging of the installation process (about 2mb text
file) you can inspect for
RETURN VALUE 3
entries... about 10/20 lines after or before each entry, some (sometime
cryptic) description of the problem will be listed...
just before running, please verify that File and Printer sharing is enabled
and the Server service is running..
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
sql

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 MSDE 2000 on WinXP home failed

Dear all,
During install MSDE 2000 on WINXP HOME edition, not complete and then
rollback, could anyone can help?
Thanks.
Below attached error.log content.
2004-12-23 16:47:36.38 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)
2004-12-23 16:47:36.38 server Copyright (C) 1988-2002 Microsoft
Corporation.
2004-12-23 16:47:36.38 server All rights reserved.
2004-12-23 16:47:36.38 server Server Process ID is 3808.
2004-12-23 16:47:36.38 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL$TL_MSDE\LOG\ERRORLOG'.
2004-12-23 16:47:36.42 server SQL Server is starting at priority class
'normal'(1 CPU detected).
2004-12-23 16:47:36.44 server SQL Server configured for thread mode
processing.
2004-12-23 16:47:36.44 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2004-12-23 16:47:36.45 spid3 Warning ******************
2004-12-23 16:47:36.45 spid3 SQL Server started in single user mode.
Updates allowed to system catalogs.
2004-12-23 16:47:36.46 spid3 Starting up database 'master'.
2004-12-23 16:47:36.61 server Using 'SSNETLIB.DLL' version '8.0.766'.
2004-12-23 16:47:36.64 spid5 Starting up database 'model'.
2004-12-23 16:47:36.91 spid3 Server name is 'DLINK\TL_MSDE'.
2004-12-23 16:47:36.91 spid3 Skipping startup of clean database id 5
2004-12-23 16:47:36.91 spid3 Skipping startup of clean database id 6
2004-12-23 16:47:36.91 spid3 Starting up database 'msdb'.
2004-12-23 16:47:36.92 server SQL server listening on 169.254.159.200:
1104.
2004-12-23 16:47:36.92 server SQL server listening on 219.76.249.145: 1104.
2004-12-23 16:47:36.92 server SQL server listening on 127.0.0.1: 1104.
2004-12-23 16:47:36.92 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2004-12-23 16:47:36.92 server SQL Server is ready for client connections
2004-12-23 16:47:37.11 spid5 Clearing tempdb database.
2004-12-23 16:47:38.16 spid5 Starting up database 'tempdb'.
2004-12-23 16:47:38.23 spid3 Warning ******************
2004-12-23 16:47:38.23 spid3 Attempting to change default collation to
Chinese_Taiwan_Stroke_CI_AS.
2004-12-23 16:47:41.78 spid3 Clustered index restored for
master.sysdatabases.
2004-12-23 16:47:41.93 spid3 Non-clustered index restored for
master.sysobjects.
2004-12-23 16:47:42.09 spid3 Non-clustered index restored for
master.sysobjects.
2004-12-23 16:47:42.13 spid3 index restored for master.syscolumns.
2004-12-23 16:47:42.23 spid3 index restored for master.systypes.
2004-12-23 16:47:42.25 spid3 index restored for master.sysusers.
2004-12-23 16:47:43.50 spid3 index restored for master.sysproperties.
2004-12-23 16:47:43.57 spid3 index restored for
master.sysfulltextcatalogs.
2004-12-23 16:47:43.76 spid3 index restored for master.sysxlogins.
2004-12-23 16:47:43.79 spid3 index restored for master.sysdevices.
2004-12-23 16:47:44.19 spid3 index restored for master.sysservers.
2004-12-23 16:47:45.66 spid3 index restored for master.syslanguages.
2004-12-23 16:47:45.71 spid3 index restored for master.syscharsets.
2004-12-23 16:47:45.75 spid3 index restored for master.sysfilegroups.
2004-12-23 16:47:46.05 spid3 index restored for master.spt_values.
2004-12-23 16:47:46.06 spid3 index restored for
master.MSreplication_options.
2004-12-23 16:47:46.08 spid3 index restored for
master.spt_datatype_info_ext.
2004-12-23 16:47:46.09 spid3 index restored for master.spt_datatype_info.
2004-12-23 16:47:46.15 spid3 Non-clustered index restored for
tempdb.sysobjects.
2004-12-23 16:47:46.15 spid3 Non-clustered index restored for
tempdb.sysobjects.
2004-12-23 16:47:46.15 spid3 index restored for tempdb.syscolumns.
2004-12-23 16:47:46.15 spid3 index restored for tempdb.systypes.
2004-12-23 16:47:46.16 spid3 index restored for tempdb.sysusers.
2004-12-23 16:47:46.16 spid3 index restored for tempdb.sysproperties.
2004-12-23 16:47:46.16 spid3 index restored for
tempdb.sysfulltextcatalogs.
2004-12-23 16:47:46.18 spid3 index restored for tempdb.sysfilegroups.
2004-12-23 16:47:46.35 spid3 Non-clustered index restored for
model.sysobjects.
2004-12-23 16:47:46.35 spid3 Non-clustered index restored for
model.sysobjects.
2004-12-23 16:47:46.45 spid3 index restored for model.syscolumns.
2004-12-23 16:47:46.46 spid3 index restored for model.systypes.
2004-12-23 16:47:46.52 spid3 index restored for model.sysusers.
2004-12-23 16:47:46.52 spid3 index restored for model.sysproperties.
2004-12-23 16:47:46.52 spid3 index restored for
model.sysfulltextcatalogs.
2004-12-23 16:47:46.54 spid3 index restored for model.sysfilegroups.
2004-12-23 16:47:46.76 spid3 Non-clustered index restored for
msdb.sysobjects.
2004-12-23 16:47:46.77 spid3 Non-clustered index restored for
msdb.sysobjects.
2004-12-23 16:47:46.79 spid3 index restored for msdb.syscolumns.
2004-12-23 16:47:46.79 spid3 index restored for msdb.systypes.
2004-12-23 16:47:46.80 spid3 index restored for msdb.sysusers.
2004-12-23 16:47:46.80 spid3 index restored for msdb.sysproperties.
2004-12-23 16:47:46.80 spid3 index restored for msdb.sysfulltextcatalogs.
2004-12-23 16:47:46.80 spid3 index restored for msdb.sysfilegroups.
2004-12-23 16:47:46.83 spid3 index restored for msdb.sysjobschedules.
2004-12-23 16:47:46.84 spid3 index restored for msdb.syscategories.
2004-12-23 16:47:46.84 spid3 index restored for msdb.systargetservers.
2004-12-23 16:47:46.84 spid3 index restored for
msdb.systargetservergroups.
2004-12-23 16:47:47.96 spid3 index restored for msdb.sysalerts.
2004-12-23 16:47:47.96 spid3 index restored for msdb.sysoperators.
2004-12-23 16:47:47.97 spid3 index restored for
msdb.syscachedcredentials.
2004-12-23 16:47:47.97 spid3 index restored for msdb.logmarkhistory.
2004-12-23 16:47:48.00 spid3 index restored for msdb.sysdtscategories.
2004-12-23 16:47:48.00 spid3 index restored for
msdb.sysdbmaintplan_databases.
2004-12-23 16:47:48.01 spid3 index restored for msdb.mswebtasks.
2004-12-23 16:47:48.01 spid3 index restored for msdb.sysdownloadlist.
2004-12-23 16:47:48.01 spid3 index restored for msdb.sysjobs.
2004-12-23 16:47:48.02 spid3 index restored for msdb.sysjobsteps.
2004-12-23 16:47:48.57 spid3 Default collation successfully changed.
2004-12-23 16:47:49.07 spid3 Recovery complete.
2004-12-23 16:47:49.07 spid3 SQL global counter collection task is
created.
2004-12-23 16:47:49.10 spid3 Warning: override, autoexec procedures
skipped.
2004-12-23 16:47:56.63 spid3 SQL Server is terminating due to 'stop'
request from Service Control Manager.
Hi
Excuse my English
I've got this problème.
Carefull if several install/uninstall...
Carefull if several servers connected with two instances with same name...
See http://support.microsoft.com/default...en-us;320873#3
for a clean uninstallation.
JCH
kpler a écrit :
> Dear all,
> During install MSDE 2000 on WINXP HOME edition, not complete and then
> rollback, could anyone can help?
> Thanks.
> Below attached error.log content.
>
> 2004-12-23 16:47:36.38 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)
> 2004-12-23 16:47:36.38 server Copyright (C) 1988-2002 Microsoft
> Corporation.
> 2004-12-23 16:47:36.38 server All rights reserved.
> 2004-12-23 16:47:36.38 server Server Process ID is 3808.
> 2004-12-23 16:47:36.38 server Logging SQL Server messages in file
> 'C:\Program Files\Microsoft SQL Server\MSSQL$TL_MSDE\LOG\ERRORLOG'.
> 2004-12-23 16:47:36.42 server SQL Server is starting at priority class
> 'normal'(1 CPU detected).
> 2004-12-23 16:47:36.44 server SQL Server configured for thread mode
> processing.
> 2004-12-23 16:47:36.44 server Using dynamic lock allocation. [500] Lock
> Blocks, [1000] Lock Owner Blocks.
> 2004-12-23 16:47:36.45 spid3 Warning ******************
> 2004-12-23 16:47:36.45 spid3 SQL Server started in single user mode.
> Updates allowed to system catalogs.
> 2004-12-23 16:47:36.46 spid3 Starting up database 'master'.
> 2004-12-23 16:47:36.61 server Using 'SSNETLIB.DLL' version '8.0.766'.
> 2004-12-23 16:47:36.64 spid5 Starting up database 'model'.
> 2004-12-23 16:47:36.91 spid3 Server name is 'DLINK\TL_MSDE'.
> 2004-12-23 16:47:36.91 spid3 Skipping startup of clean database id 5
> 2004-12-23 16:47:36.91 spid3 Skipping startup of clean database id 6
> 2004-12-23 16:47:36.91 spid3 Starting up database 'msdb'.
> 2004-12-23 16:47:36.92 server SQL server listening on 169.254.159.200:
> 1104.
> 2004-12-23 16:47:36.92 server SQL server listening on 219.76.249.145: 1104.
> 2004-12-23 16:47:36.92 server SQL server listening on 127.0.0.1: 1104.
> 2004-12-23 16:47:36.92 server SQL server listening on TCP, Shared Memory,
> Named Pipes.
> 2004-12-23 16:47:36.92 server SQL Server is ready for client connections
> 2004-12-23 16:47:37.11 spid5 Clearing tempdb database.
> 2004-12-23 16:47:38.16 spid5 Starting up database 'tempdb'.
> 2004-12-23 16:47:38.23 spid3 Warning ******************
> 2004-12-23 16:47:38.23 spid3 Attempting to change default collation to
> Chinese_Taiwan_Stroke_CI_AS.
> 2004-12-23 16:47:41.78 spid3 Clustered index restored for
> master.sysdatabases.
> 2004-12-23 16:47:41.93 spid3 Non-clustered index restored for
> master.sysobjects.
> 2004-12-23 16:47:42.09 spid3 Non-clustered index restored for
> master.sysobjects.
> 2004-12-23 16:47:42.13 spid3 index restored for master.syscolumns.
> 2004-12-23 16:47:42.23 spid3 index restored for master.systypes.
> 2004-12-23 16:47:42.25 spid3 index restored for master.sysusers.
> 2004-12-23 16:47:43.50 spid3 index restored for master.sysproperties.
> 2004-12-23 16:47:43.57 spid3 index restored for
> master.sysfulltextcatalogs.
> 2004-12-23 16:47:43.76 spid3 index restored for master.sysxlogins.
> 2004-12-23 16:47:43.79 spid3 index restored for master.sysdevices.
> 2004-12-23 16:47:44.19 spid3 index restored for master.sysservers.
> 2004-12-23 16:47:45.66 spid3 index restored for master.syslanguages.
> 2004-12-23 16:47:45.71 spid3 index restored for master.syscharsets.
> 2004-12-23 16:47:45.75 spid3 index restored for master.sysfilegroups.
> 2004-12-23 16:47:46.05 spid3 index restored for master.spt_values.
> 2004-12-23 16:47:46.06 spid3 index restored for
> master.MSreplication_options.
> 2004-12-23 16:47:46.08 spid3 index restored for
> master.spt_datatype_info_ext.
> 2004-12-23 16:47:46.09 spid3 index restored for master.spt_datatype_info.
> 2004-12-23 16:47:46.15 spid3 Non-clustered index restored for
> tempdb.sysobjects.
> 2004-12-23 16:47:46.15 spid3 Non-clustered index restored for
> tempdb.sysobjects.
> 2004-12-23 16:47:46.15 spid3 index restored for tempdb.syscolumns.
> 2004-12-23 16:47:46.15 spid3 index restored for tempdb.systypes.
> 2004-12-23 16:47:46.16 spid3 index restored for tempdb.sysusers.
> 2004-12-23 16:47:46.16 spid3 index restored for tempdb.sysproperties.
> 2004-12-23 16:47:46.16 spid3 index restored for
> tempdb.sysfulltextcatalogs.
> 2004-12-23 16:47:46.18 spid3 index restored for tempdb.sysfilegroups.
> 2004-12-23 16:47:46.35 spid3 Non-clustered index restored for
> model.sysobjects.
> 2004-12-23 16:47:46.35 spid3 Non-clustered index restored for
> model.sysobjects.
> 2004-12-23 16:47:46.45 spid3 index restored for model.syscolumns.
> 2004-12-23 16:47:46.46 spid3 index restored for model.systypes.
> 2004-12-23 16:47:46.52 spid3 index restored for model.sysusers.
> 2004-12-23 16:47:46.52 spid3 index restored for model.sysproperties.
> 2004-12-23 16:47:46.52 spid3 index restored for
> model.sysfulltextcatalogs.
> 2004-12-23 16:47:46.54 spid3 index restored for model.sysfilegroups.
> 2004-12-23 16:47:46.76 spid3 Non-clustered index restored for
> msdb.sysobjects.
> 2004-12-23 16:47:46.77 spid3 Non-clustered index restored for
> msdb.sysobjects.
> 2004-12-23 16:47:46.79 spid3 index restored for msdb.syscolumns.
> 2004-12-23 16:47:46.79 spid3 index restored for msdb.systypes.
> 2004-12-23 16:47:46.80 spid3 index restored for msdb.sysusers.
> 2004-12-23 16:47:46.80 spid3 index restored for msdb.sysproperties.
> 2004-12-23 16:47:46.80 spid3 index restored for msdb.sysfulltextcatalogs.
> 2004-12-23 16:47:46.80 spid3 index restored for msdb.sysfilegroups.
> 2004-12-23 16:47:46.83 spid3 index restored for msdb.sysjobschedules.
> 2004-12-23 16:47:46.84 spid3 index restored for msdb.syscategories.
> 2004-12-23 16:47:46.84 spid3 index restored for msdb.systargetservers.
> 2004-12-23 16:47:46.84 spid3 index restored for
> msdb.systargetservergroups.
> 2004-12-23 16:47:47.96 spid3 index restored for msdb.sysalerts.
> 2004-12-23 16:47:47.96 spid3 index restored for msdb.sysoperators.
> 2004-12-23 16:47:47.97 spid3 index restored for
> msdb.syscachedcredentials.
> 2004-12-23 16:47:47.97 spid3 index restored for msdb.logmarkhistory.
> 2004-12-23 16:47:48.00 spid3 index restored for msdb.sysdtscategories.
> 2004-12-23 16:47:48.00 spid3 index restored for
> msdb.sysdbmaintplan_databases.
> 2004-12-23 16:47:48.01 spid3 index restored for msdb.mswebtasks.
> 2004-12-23 16:47:48.01 spid3 index restored for msdb.sysdownloadlist.
> 2004-12-23 16:47:48.01 spid3 index restored for msdb.sysjobs.
> 2004-12-23 16:47:48.02 spid3 index restored for msdb.sysjobsteps.
> 2004-12-23 16:47:48.57 spid3 Default collation successfully changed.
> 2004-12-23 16:47:49.07 spid3 Recovery complete.
> 2004-12-23 16:47:49.07 spid3 SQL global counter collection task is
> created.
> 2004-12-23 16:47:49.10 spid3 Warning: override, autoexec procedures
> skipped.
> 2004-12-23 16:47:56.63 spid3 SQL Server is terminating due to 'stop'
> request from Service Control Manager.

Friday, March 23, 2012

Install issue for Business Contact Manager for Outlook 2007 and SQL Express

Hi,

We try to install Business Contact Manager for Outlook 2007 and get installation failed without any error. It simply refers to the log file. I have posted below the last 40 lines of this huge log file. The information in there are not vary help full since it refers to error codes that nobody seem to be able to explain. Now this is happening on 3 brand new dell computers running XP Pro. I would be happy for any assistance to either explain the error coded (if any MS guy is monitoring this) or maybe someone had a similar problem and could let me know some options on what I could try to get this resolved and my program installed.

Thank you all very much for assisting me.

Thom

Log file last 40 lines (more on request)
Property(S): RemoteAdminTS = 1
Property(S): WindowsVolume = C:\
Property(S): MsiNTProductType = 1
Property(S): ServicePackLevelMinor = 0
Property(S): AdminUser = 1
Property(S): ServicePackLevel = 2
Property(S): WindowsBuild = 2600
Property(S): DigitalProductID = #xA40000000300000038393431302D3238312D323037393634372D3034383138000800000000000000000000000000000000000000003AD3F42CD592998379FDEF3D020300000000005C9495464B6CAB0D0000000000000000000000000000000000000000000000003236333037000000000000009B2D00008555946CBF070000EC3E0000000000000000000000000000000000000000000000000000000000003316ABDF
Property(S): VersionMsi = 3.01
Property(S): VersionDatabase = 200
Property(S): CLIENTPROCESSID = 200
Property(S): CLIENTUILEVEL = 3
Property(S): CURRENTDIRECTORY = C:\Documents and Settings\Justin Jong\My Documents\ShareFiles\Business Contact 2007
Property(S): BOOTSTRAPPED = 1
Property(S): REBOOT = ReallySuppress
Property(S): PackagecodeChanging = 1
Property(S): ProductState = -1
Property(S): PackageCode = {A8529450-48A4-4346-92F8-8A9634381267}
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): SOURCEDIR = C:\Documents and Settings\Justin Jong\My Documents\ShareFiles\Business Contact 2007\
Property(S): SourcedirProduct = {B32C4059-6E7A-41EF-AD20-56DF1872B923}
Property(S): ProductToBeRegistered = 1
MSI (s) (64:0C) [02:39:28:441]: Note: 1: 1708
MSI (s) (64:0C) [02:39:28:441]: Product: Business Contact Manager for Outlook 2007 -- Installation operation failed.

MSI (s) (64:0C) [02:39:28:441]: Cleaning up uninstalled install packages, if any exist
MSI (s) (64:0C) [02:39:28:441]: MainEngineThread is returning 1603
MSI (s) (64:04) [02:39:28:535]: Destroying RemoteAPI object.
MSI (s) (64:9C) [02:39:28:535]: Custom Action Manager thread ending.
=== Logging stopped: 7/12/2007 2:39:28 ===
MSI (c) (C8:50) [02:39:28:550]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (C8:50) [02:39:28:550]: MainEngineThread is returning 1603
=== Verbose logging stopped: 7/12/2007 2:39:28 ===

I have same issue, XP sp 2, bcm 2007.

Any one help, cant find any info on this issue.

Thanks

Steve

|||

Hi Thom

Did you fix the error? I also get the same arror on a dell notebook running Vista.

Any advice will be appreciated.

Barry-Dean

Install issue for Business Contact Manager for Outlook 2007 and SQL Express

Hi,

Thank you all very much for assisting me.

Thom

I have same issue, XP sp 2, bcm 2007.

Any one help, cant find any info on this issue.

Thanks

Steve

|||

Hi Thom

Did you fix the error? I also get the same arror on a dell notebook running Vista.

Any advice will be appreciated.

Barry-Dean

Install Failed... help

Folks:

Cannot install SQL 2005 Express, I've done some searching but to no avail, I appreciate any help

, I am administrator on this machine so I don't know why there would be a problem accessing a key...

Here is the log info:

Microsoft SQL Server 2005 9.00.1399.06
==============================
OS Version : Microsoft Windows XP Professional Service Pack 2 (Build 2600)
Time : Tue Oct 10 13:53:29 2006
Machine : VAIO
Product : Microsoft SQL Server Setup Support Files (English)
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_VAIO_Support.log
Last Action : InstallFinalize
Error String : Could not open key: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SQL Server\90\Bootstrap. System error 5. Verify that you have sufficient access to that key, or contact your support personnel.
Error Number : 1402
--
VAIO : There was an unexpected failure during the setup wizard. You may review the setup logs and/or click the help button for more information.

SQL Server Setup failed. For more information, review the Setup log file in %ProgramFiles%\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt.

Time : Tue Oct 10 13:53:44 2006

List of log files:
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_VAIO_Core.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_VAIO_Datastore.xml
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_VAIO_Support.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Files\SQLSetup0004_VAIO_.NET Framework 2.0.log
C:\Program Files\Microsoft SQL Server\90\Setup Bootstrap\LOG\Summary.txt

Have you confirmed that you do have permission to the Key in question? I know you should given you're administrative status, but this is a Windows Installer error that typically means what it says. Go ahead and check just to be sure.

In the mean time, I'm moving this to the setup forum since this is thier bag.

Mike

|||

Here's a Microsoft KB about this issue. This seems to happen with lots of software products when the registry gets out of line with the files on the box.

From the article:

CAUSE

This behavior may occur if there is incorrect, invalid, or corrupted information in the Windows registry. This behavior may occur if specific files or folders were previously removed or renamed on your hard disk. As a result, registry entries associated with the deleted files remain in the Windows registry.

http://support.microsoft.com/kb/303089

Take a look at the article and see if it applies to your situation.

Thanks,
Sam Lester (MSFT)

Install Failed

Sorry, but I am not overly knowledgabel about this topic. I am trying to
install MSDE on my Windows XP Pro machine at home so that I don't have to
commute so often. Alas, I keep getting failures. The part of the log where
"value 3" is is below but I can't see any information about why it failed.
Any help or guidance greatfully received.
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:\Temporary\MSDE\Setup\
Property(S): SourcedirProduct = {E09B48B5-E141-427A-AB0C-D3605127224A}
Property(S): ProductToBeRegistered = 1
MSI (s) (F4:68): MainEngineThread is returning 1603
MSI (c) (D4:C4): Back from server. Return value: 1603
MSI (c) (D4:C4): Decrementing counter to disable shutdown. If counter >= 0,
shutdown will be denied. Counter after decrement: -1
Action ended 17:53:04: INSTALL. Return value 3.
MSI (c) (D4:C4): Note: 1: 2262 2: Control 3: -2147287038
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
> Alas, I keep getting failures.
Can you be a bit more specific?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
|||Sorry, I thought it was in the log file extract.
I run the MSDE installation as per the instructions and it gets so far then
backs out with the error in the log file.
I'm not sure what else you need to know, I can't find a reason for the
failure in the area of the log the instructions indicate, "Within 10 lines
of the string" ("value 3"). Sorry for being so vague.
"Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
news:%2367wSSsMEHA.3012@.tk2msftngp13.phx.gbl...
> Can you be a bit more specific?
> --
> Aaron Bertrand
> SQL Server MVP
> http://www.aspfaq.com/
>
|||Instead of worrying about "within 10 lines of the string," have you
considered searching the log file for the words "error" or "failure"?
Aaron Bertrand
SQL Server MVP
http://www.aspfaq.com/
"news.microsoft.com" <jonathan_grant@.hotmail.com> wrote in message
news:#Eeg0EtMEHA.684@.TK2MSFTNGP09.phx.gbl...
> Sorry, I thought it was in the log file extract.
> I run the MSDE installation as per the instructions and it gets so far
then
> backs out with the error in the log file.
> I'm not sure what else you need to know, I can't find a reason for the
> failure in the area of the log the instructions indicate, "Within 10 lines
> of the string" ("value 3"). Sorry for being so vague.
>
> "Aaron Bertrand - MVP" <aaron@.TRASHaspfaq.com> wrote in message
> news:%2367wSSsMEHA.3012@.tk2msftngp13.phx.gbl...
>
|||If I knew what I was looking for I wouldn't be asking for help here!
There are no instances of the word failure in the log. The reason I quoted
10 lines is because that it what it says in the Microsoft documentation. If
you can't or won't assist please leave this thread for someone who will.
|||> If I knew what I was looking for I wouldn't be asking for help here!
I told you what to look for: the word "error" or the word "failure."

> you can't or won't assist please leave this thread for someone who will.
Oh, for Christ's sake, I'm trying to help. I can't help you if I don't know
what the problem is. I can't fix "broken" or "failed" but I can point you
somewhere if you figure out what error you are getting. See my point
above... if you use verbose logging, the reason for a botched install will
be there somewhere.
A
|||I have searched the log and there is no instance of the word "failure". There are 37 "error" but I cannot for the life of me see any clues as to why the install failed in them. A lot of them seem to be removing stuff from the registry, etc, as a result o
f the failure. I appreciate that you are looking at this for no reward but please understand that I do not know any more than what I have read in the limited MS documentation and have picked up from this news group.
I copy the error lines from the log below:
MSI (s) (F4:68): Executing op: RegAddValue(,Value=Microsoft SQL Distribution Error lookup,)
WriteRegistryValues: Key: HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{16D9A8E 2-C326-11d0-94E9-00C04FC2DB9C}\ExtendedErrors, Name: , Value: Microsoft SQL Distribution Error lookup
MSI (s) (F4:68): Executing op: RegAddValue(,Value=Error Lookup Service for Microsoft SQL Replication Distribution Provider,)
WriteRegistryValues: Key: HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{16D9A8E 2-C326-11d0-94E9-00C04FC2DB9C}\ExtendedErrors\{246CBC55-F3E8-11d0-9AEB-00C04FB6B6EF}, Name: , Value: Error Lookup Service for Microsoft SQL Replication Distribution Provider
MSI (s) (F4:68): Executing op: RegAddValue(,Value=Microsoft SQL Replication Distribution Provider-Error Lookup,)
WriteRegistryValues: Key: HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{246CBC5 5-F3E8-11d0-9AEB-00C04FB6B6EF}, Name: , Value: Microsoft SQL Replication Distribution Provider-Error Lookup
MSI (s) (F4:68): Executing op: RegAddValue(,Value=Microsoft SQL Replication Distribution Provider-Error Lookup,)
WriteRegistryValues: Key: HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{246CBC5 5-F3E8-11d0-9AEB-00C04FB6B6EF}\ProgID, Name: , Value: Microsoft SQL Replication Distribution Provider-Error Lookup
MSI (s) (F4:68): Executing op: RegAddValue(,Value=Microsoft SQL Replication Distribution Provider-Error Lookup,)
WriteRegistryValues: Key: HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{246CBC5 5-F3E8-11d0-9AEB-00C04FB6B6EF}\VersionIndependentProgID, Name: , Value: Microsoft SQL Replication Distribution Provider-Error Lookup
MSI (s) (F4:68): Executing op: RegAddValue(,Value=Microsoft SQL Replication Error Class,)
WriteRegistryValues: Key: HKEY_LOCAL_MACHINE\Software\Classes\SQLReplError.S QLReplError.2, Name: , Value: Microsoft SQL Replication Error Class
MSI (s) (F4:68): Executing op: RegAddValue(,Value=Microsoft SQL Replication Error Class,)
WriteRegistryValues: Key: HKEY_LOCAL_MACHINE\Software\Classes\SQLReplError.S QLReplError, Name: , Value: Microsoft SQL Replication Error Class
MSI (s) (F4:68): Executing op: RegAddValue(,Value=Microsoft SQL Replication Error Class,)
WriteRegistryValues: Key: HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{08b0b2e b-3fb3-11d3-a4de-00c04f610189}, Name: , Value: Microsoft SQL Replication Error Class
MSI (s) (F4:68): Executing op: RegAddValue(,Value=Microsoft OLE DB Bulk Import Provider 7.5 Extended Error Service,)
WriteRegistryValues: Key: HKEY_LOCAL_MACHINE\Software\Classes\MSQLImpProvErr orLookup75, Name: , Value: Microsoft OLE DB Bulk Import Provider 7.5 Extended Error Service
MSI (s) (F4:68): Executing op: RegAddValue(,Value=Microsoft OLE DB Bulk Import Provider Extended Error Service,)
WriteRegistryValues: Key: HKEY_LOCAL_MACHINE\Software\Classes\MSQLImpProvErr orLookup, Name: , Value: Microsoft OLE DB Bulk Import Provider Extended Error Service
MSI (s) (F4:68): Executing op: RegAddValue(,Value=Microsoft OLE DB Bulk Import Provider 7.5 Extended Error Service,)
WriteRegistryValues: Key: HKEY_LOCAL_MACHINE\Software\Classes\MSQLImpProvErr orLookup\CurVer, Name: , Value: Microsoft OLE DB Bulk Import Provider 7.5 Extended Error Service
MSI (s) (F4:68): Executing op: RegAddValue(,Value=Microsoft OLE DB Bulk Import Provider Extended Error Service,)
WriteRegistryValues: Key: HKEY_LOCAL_MACHINE\Software\Classes\CLSID\{CB0122A 6-60BC-11D3-B2A6-00C04F68CBB6}, Name: , Value: Microsoft OLE DB Bulk Import Provider Extended Error Service
MSI (s) (F4:68): Executing op: RegRemoveValue(,Value=Microsoft OLE DB Bulk Import Provider Extended Error Service,)
MSI (s) (F4:68): Executing op: RegRemoveValue(,Value=Microsoft OLE DB Bulk Import Provider 7.5 Extended Error Service,)
MSI (s) (F4:68): Executing op: RegRemoveValue(,Value=Microsoft OLE DB Bulk Import Provider Extended Error Service,)
MSI (s) (F4:68): Executing op: RegRemoveValue(,Value=Microsoft OLE DB Bulk Import Provider 7.5 Extended Error Service,)
MSI (s) (F4:68): Executing op: RegRemoveValue(,Value=Microsoft SQL Replication Error Class,)
MSI (s) (F4:68): Executing op: RegRemoveValue(,Value=Microsoft SQL Replication Error Class,)
MSI (s) (F4:68): Executing op: RegRemoveValue(,Value=Microsoft SQL Replication Error Class,)
MSI (s) (F4:68): Executing op: RegRemoveValue(,Value=Microsoft SQL Replication Distribution Provider-Error Lookup,)
MSI (s) (F4:68): Executing op: RegRemoveValue(,Value=Microsoft SQL Replication Distribution Provider-Error Lookup,)
MSI (s) (F4:68): Executing op: RegRemoveValue(,Value=Microsoft SQL Replication Distribution Provider-Error Lookup,)
MSI (s) (F4:68): Executing op: RegRemoveValue(,Value=Error Lookup Service for Microsoft SQL Replication Distribution Provider,)
MSI (s) (F4:68): Executing op: RegRemoveValue(,Value=Microsoft SQL Distribution Error lookup,)
MSI (s) (F4:68): Error in rollback skipped. Return: 5
|||Hi Jonothan,
I'm gitting the same error. Was wondering if you managed to sort it out?
Regards
G.

Wednesday, March 21, 2012

Install Error

Can anyone shed some light on this one?
<Func Name='PerformDetections'>
0
Failed to find property in cache: InstalledInstances
Failed to perform discovery on machine: DEV01
HRESULT: 2147749891
<EndFunc Name='PerformDetections' Return='2' GetLastError='183'>I am experiencing the same error when trying to install the report designer.
Does anyone know how to resolve this problem (short of reinstalling the
entire PC)?
Thanks
"TonyL" wrote:
> Can anyone shed some light on this one?
> <Func Name='PerformDetections'>
> 0
> Failed to find property in cache: InstalledInstances
> Failed to perform discovery on machine: DEV01
> HRESULT: 2147749891
> <EndFunc Name='PerformDetections' Return='2' GetLastError='183'>sql

Monday, March 12, 2012

Install 2005 Enterprise Edition on windows XP Home Edition has pro

My pc used to have 2000, and i tried to install 2005 once with the instance
as name instance but failed, so i uninstall 2000, but looks like it always
recognize the default instance there even though there is no more 2000 sever,
when i try to install 2005 with name instance again, i got the error failed
to install database engineer, i don't know what to look at the
SQLSetup0006_DDAI_SQL.log, can somebody advice? thank you
Machine : DDAI
Product : SQL Server Database Services
Error : The SQL Server service failed to start. For more
information, see the SQL Server Books Online topics, "How to: View SQL Server
2005 Setup Log Files" and "Starting SQL Server Manually.
----
Machine : DDAI
Product : Microsoft SQL Server 2005
Product Version : 9.00.1399.06
Install : Failed
Log File : C:\Program Files\Microsoft SQL Server\90\Setup
Bootstrap\LOG\Files\SQLSetup0006_DDAI_SQL.log
Last Action : InstallFinalize
Error String : The SQL Server service failed to start. For more
information, see the SQL Server Books Online topics, "How to: View SQL Server
2005 Setup Log Files" and "Starting SQL Server Manually."
The error is (1053) The service did not respond to the start or control
request in a timely fashion.
Error Number : 29503Hi
According to http://msdn2.microsoft.com/en-us/library/ms143506.aspx
Enterprise Edition is not supported on XP home.
You should be able to have an instance of SQL 2000 and a named instance of
SQL 2005 running on the same machine.
It sounds like SQL 2000 did not fully un-install.This may hekp you to remove
it http://support.microsoft.com/kb/290991
John
"tulip" wrote:
> My pc used to have 2000, and i tried to install 2005 once with the instance
> as name instance but failed, so i uninstall 2000, but looks like it always
> recognize the default instance there even though there is no more 2000 sever,
> when i try to install 2005 with name instance again, i got the error failed
> to install database engineer, i don't know what to look at the
> SQLSetup0006_DDAI_SQL.log, can somebody advice? thank you
> Machine : DDAI
> Product : SQL Server Database Services
> Error : The SQL Server service failed to start. For more
> information, see the SQL Server Books Online topics, "How to: View SQL Server
> 2005 Setup Log Files" and "Starting SQL Server Manually."
> ----
> Machine : DDAI
> Product : Microsoft SQL Server 2005
> Product Version : 9.00.1399.06
> Install : Failed
> Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> Bootstrap\LOG\Files\SQLSetup0006_DDAI_SQL.log
> Last Action : InstallFinalize
> Error String : The SQL Server service failed to start. For more
> information, see the SQL Server Books Online topics, "How to: View SQL Server
> 2005 Setup Log Files" and "Starting SQL Server Manually."
> The error is (1053) The service did not respond to the start or control
> request in a timely fashion.
> Error Number : 29503|||according to
http://www.microsoft.com/sql/downloads/trial-system-requirements.mspx,
I am installing the trial edition, so should work on windows xp home
edition, right?
"John Bell" wrote:
> Hi
> According to http://msdn2.microsoft.com/en-us/library/ms143506.aspx
> Enterprise Edition is not supported on XP home.
> You should be able to have an instance of SQL 2000 and a named instance of
> SQL 2005 running on the same machine.
> It sounds like SQL 2000 did not fully un-install.This may hekp you to remove
> it http://support.microsoft.com/kb/290991
>
> John
> "tulip" wrote:
> > My pc used to have 2000, and i tried to install 2005 once with the instance
> > as name instance but failed, so i uninstall 2000, but looks like it always
> > recognize the default instance there even though there is no more 2000 sever,
> > when i try to install 2005 with name instance again, i got the error failed
> > to install database engineer, i don't know what to look at the
> > SQLSetup0006_DDAI_SQL.log, can somebody advice? thank you
> >
> > Machine : DDAI
> > Product : SQL Server Database Services
> > Error : The SQL Server service failed to start. For more
> > information, see the SQL Server Books Online topics, "How to: View SQL Server
> > 2005 Setup Log Files" and "Starting SQL Server Manually."
> > ----
> > Machine : DDAI
> > Product : Microsoft SQL Server 2005
> > Product Version : 9.00.1399.06
> > Install : Failed
> > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > Bootstrap\LOG\Files\SQLSetup0006_DDAI_SQL.log
> > Last Action : InstallFinalize
> > Error String : The SQL Server service failed to start. For more
> > information, see the SQL Server Books Online topics, "How to: View SQL Server
> > 2005 Setup Log Files" and "Starting SQL Server Manually."
> > The error is (1053) The service did not respond to the start or control
> > request in a timely fashion.
> > Error Number : 29503|||Hi
It does say that is allowed, but loading a trial edition onto a XP machine
when you can not use the same machine or OS for production is not really
going to give you anything. If you just want to learn SQL Server you can use
SQL Express or buy a copy of Developer edition. If you are looking at testing
compatibility either use a server that you can trash or a virtual machine
with the server os.
John
"tulip" wrote:
> according to
> http://www.microsoft.com/sql/downloads/trial-system-requirements.mspx,
> I am installing the trial edition, so should work on windows xp home
> edition, right?
> "John Bell" wrote:
> > Hi
> >
> > According to http://msdn2.microsoft.com/en-us/library/ms143506.aspx
> > Enterprise Edition is not supported on XP home.
> >
> > You should be able to have an instance of SQL 2000 and a named instance of
> > SQL 2005 running on the same machine.
> >
> > It sounds like SQL 2000 did not fully un-install.This may hekp you to remove
> > it http://support.microsoft.com/kb/290991
> >
> >
> >
> > John
> >
> > "tulip" wrote:
> >
> > > My pc used to have 2000, and i tried to install 2005 once with the instance
> > > as name instance but failed, so i uninstall 2000, but looks like it always
> > > recognize the default instance there even though there is no more 2000 sever,
> > > when i try to install 2005 with name instance again, i got the error failed
> > > to install database engineer, i don't know what to look at the
> > > SQLSetup0006_DDAI_SQL.log, can somebody advice? thank you
> > >
> > > Machine : DDAI
> > > Product : SQL Server Database Services
> > > Error : The SQL Server service failed to start. For more
> > > information, see the SQL Server Books Online topics, "How to: View SQL Server
> > > 2005 Setup Log Files" and "Starting SQL Server Manually."
> > > ----
> > > Machine : DDAI
> > > Product : Microsoft SQL Server 2005
> > > Product Version : 9.00.1399.06
> > > Install : Failed
> > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > Bootstrap\LOG\Files\SQLSetup0006_DDAI_SQL.log
> > > Last Action : InstallFinalize
> > > Error String : The SQL Server service failed to start. For more
> > > information, see the SQL Server Books Online topics, "How to: View SQL Server
> > > 2005 Setup Log Files" and "Starting SQL Server Manually."
> > > The error is (1053) The service did not respond to the start or control
> > > request in a timely fashion.
> > > Error Number : 29503|||Hi
Re-reading this is only says Windows XP SP2 and not what variety of Windows
XP. As Windows 2000 was only professional then it could be that it the
information is not specific enough.
John
"tulip" wrote:
> according to
> http://www.microsoft.com/sql/downloads/trial-system-requirements.mspx,
> I am installing the trial edition, so should work on windows xp home
> edition, right?
> "John Bell" wrote:
> > Hi
> >
> > According to http://msdn2.microsoft.com/en-us/library/ms143506.aspx
> > Enterprise Edition is not supported on XP home.
> >
> > You should be able to have an instance of SQL 2000 and a named instance of
> > SQL 2005 running on the same machine.
> >
> > It sounds like SQL 2000 did not fully un-install.This may hekp you to remove
> > it http://support.microsoft.com/kb/290991
> >
> >
> >
> > John
> >
> > "tulip" wrote:
> >
> > > My pc used to have 2000, and i tried to install 2005 once with the instance
> > > as name instance but failed, so i uninstall 2000, but looks like it always
> > > recognize the default instance there even though there is no more 2000 sever,
> > > when i try to install 2005 with name instance again, i got the error failed
> > > to install database engineer, i don't know what to look at the
> > > SQLSetup0006_DDAI_SQL.log, can somebody advice? thank you
> > >
> > > Machine : DDAI
> > > Product : SQL Server Database Services
> > > Error : The SQL Server service failed to start. For more
> > > information, see the SQL Server Books Online topics, "How to: View SQL Server
> > > 2005 Setup Log Files" and "Starting SQL Server Manually."
> > > ----
> > > Machine : DDAI
> > > Product : Microsoft SQL Server 2005
> > > Product Version : 9.00.1399.06
> > > Install : Failed
> > > Log File : C:\Program Files\Microsoft SQL Server\90\Setup
> > > Bootstrap\LOG\Files\SQLSetup0006_DDAI_SQL.log
> > > Last Action : InstallFinalize
> > > Error String : The SQL Server service failed to start. For more
> > > information, see the SQL Server Books Online topics, "How to: View SQL Server
> > > 2005 Setup Log Files" and "Starting SQL Server Manually."
> > > The error is (1053) The service did not respond to the start or control
> > > request in a timely fashion.
> > > Error Number : 29503

Friday, March 30, 2012

Install roll back

Wednesday, March 28, 2012

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

Monday, March 26, 2012

Install MSDE2000 failed and auto rollback

Install MSDE2000 failed

Install MSDE 2000 on WinXP home failed

Friday, March 23, 2012

Install issue for Business Contact Manager for Outlook 2007 and SQL Express

Install issue for Business Contact Manager for Outlook 2007 and SQL Express

Install Failed... help

CAUSE

Install Failed

Wednesday, March 21, 2012

Install Error

Monday, March 12, 2012

Install 2005 Enterprise Edition on windows XP Home Edition has pro

Inserting Null Value

Blog Archive

About Me