This is where the log file shows an error which cascades into an endless
installation that never stops until the computer process is killed:
Action start 8:42:12: GetWebInfo.A95D0BB4_0582_442D_B456_D295EAEB7628.
MSI (s) (80:14): Creating MSIHANDLE (200) of type 790542 for thread 1556
Found 6 columns in table SeagateWebVirtualDir
Writing
SeagateWebVirtualDir="crystalreportviewers.98FD4916_3FB9_496F_A0FE_E757F169B2A7"
Writing Component_="ASPforDotNET.98FD4916_3FB9_496F_A0FE_E757F169B2A7"
Writing Path="C:\Program Files\Common Files\Crystal
Decisions\2.0\crystalreportviewers\"
Writing VirtualDir="crystalreportviewers"
Writing Attribute="513"
Writing ComponentAction="+-"
SaveTableToIniFile: Table SeagateWebMimeType doesn't exist
Couldn't get component state for component
"wcsdsapi.dll.413A0FA5_373A_11D4_91AE_009027A76C22".uReturn 1607
DEBUG: Error 2769: Custom Action
GetWebInfo.A95D0BB4_0582_442D_B456_D295EAEB7628 did not close 3 MSIHANDLEs.
The installer has encountered an unexpected error installing this package.
This may indicate a problem with this package. The error code is 2769. The
arguments are: GetWebInfo.A95D0BB4_0582_442D_B456_D295EAEB7628, 3,
Action ended 8:42:12: GetWebInfo.A95D0BB4_0582_442D_B456_D295EAEB7628.
Return value 1.
MSI (s) (80:14): Doing action: RemoveExistingProducts
Action start 8:42:12: RemoveExistingProducts.
MSI (s) (80:14): Skipping RemoveExistingProducts action: current
configuration is maintenance mode or an uninstall
Action ended 8:42:12: RemoveExistingProducts. Return value 0.
MSI (s) (80:14): Doing action:
AddProgressTime2.A95D0BB4_0582_442D_B456_D295EAEB7628
Action start 8:42:12: AddProgressTime2.A95D0BB4_0582_442D_B456_D295EAEB7628.
MSI (s) (80:14): Creating MSIHANDLE (222) of type 790542 for thread 1556
AddTimeToProgressBar: Adding 60 seconds
Action ended 8:42:12: AddProgressTime2.A95D0BB4_0582_442D_B456_D295EAEB7628.
Return value 1.
MSI (s) (80:14): Doing action:
CommitWindowsSettingsAction.A95D0BB4_0582_442D_B456_D295EAEB7628
Action start 8:42:12:
CommitWindowsSettingsAction.A95D0BB4_0582_442D_B456_D295EAEB7628.
MSI (s) (80:14): Creating MSIHANDLE (225) of type 790542 for thread 1556
Action ended 8:42:13:
CommitWindowsSettingsAction.A95D0BB4_0582_442D_B456_D295EAEB7628. Return
value 1.
MSI (s) (80:14): Skipping action: AllocateRegistrySpace (condition is false)
MSI (s) (80:14): Doing action: ProcessComponents
Action start 8:42:13: ProcessComponents.
MSI (s) (80:14): Using cached product context: User non-assigned for
product: 06B7A39BA26F7DE419484F8431EA084F
Action 8:42:13: GenerateScript. Generating script operations for action:
GenerateScript: Updating component registration
Action ended 8:42:13: ProcessComponents. Return value 1.
MSI (s) (80:14): Doing action:
AddProgressTime1.A95D0BB4_0582_442D_B456_D295EAEB7628
Action start 8:42:13: AddProgressTime1.A95D0BB4_0582_442D_B456_D295EAEB7628.
MSI (s) (80:14): Creating MSIHANDLE (226) of type 790542 for thread 1556
AddProgressTime1:Started
AddTimeToProgressBar: Adding 170 seconds
[quoted text, click to view] "thejamie" wrote:
> When I compile, in the release folder (or whatever the folder may be that the
> project is compiled into), the Studio setup first creates a CAB file and when
> the compile is complete the cab file is consumed by the msi. Or, at least it
> should be, but lately, the cab file remains, the computer freezes up and my
> best guess is that the two files are cross-linked. The only way out is to
> turn the computer off and then back on again. Then go to the folder where
> the two files exist, delete them, reboot, come back and - if lucky -
> recompile and hope the two won't cross-link again. To be sure, I have been
> compiling in Safe Mode as this seems to be the only method that keeps the
> files from cross-linking. Well, those are the symptoms. Anyone have an
> idea as to what causes this?
> --
> Regards,