View Issue Details

IDProjectCategoryView StatusLast Update
0004958SUMoBugpublic2018-08-08 19:58
ReporterFHAssigned ToKyle_Katarn 
PrioritynormalSeveritycrashReproducibilitysometimes
Status closedResolutionno change required 
PlatformWindows PCOSWindows 7OS VersionProfessional
Product Version5.6.6 
Target VersionFixed in Version 
Summary0004958: SUMo crashes during auto-update
DescriptionDuring auto-update the program crashes and the existing SUMo executable file gets deleted but is not replaced with the newer version.

This requires a manual download and software re-installation.

During the update process an error code appears indicating that "An error occurred while trying to rename a file in the destination directory: MoveFile failed code 183. Cannot create a file when that file already exists."

Selecting the "Retry" button fails to resolve the issue. Selecting the "Ignore" button results in a second error message indicating "Unable to execute file". "ShellExexecuteEx failed; code 5. Access is denied"
Steps To ReproduceThis is hard to reproduce as it only happens when a newer software version becomes available. I check for updates once a week and this has happened for several weeks. I didn't previously report the problem, hoping it would be resolved in the newer version.
Additional InformationThis might be a conflict between my anti-virus software and the program installation process. I will try adding a directory exclusion and see if this resolves the problem.

Still, if the update process fails, at the very least it should leave in place the existing version.

Perhaps the auto-update software can store the existing version as a temp file and only delete it if the update successfully completes. If the update doesn't successfully complete, the original file can then be restored with an appropriate explanatory message.
TagsNo tags attached.

Relationships

related to 0004942 resolvedKyle_Katarn Movefile Error code 183 during automatic update of SUMo PRO 

Activities

Kyle_Katarn

2018-08-08 19:57

administrator   ~0003021

Fixed. See 0004942

Issue History

Date Modified Username Field Change
2018-06-15 16:29 FH New Issue
2018-06-15 21:19 Kyle_Katarn Relationship added related to 0004942
2018-06-15 21:19 Kyle_Katarn Target Version => 5.7.x
2018-06-15 21:19 Kyle_Katarn Assigned To => Kyle_Katarn
2018-06-15 21:19 Kyle_Katarn Status new => acknowledged
2018-08-08 19:57 Kyle_Katarn Note Added: 0003021
2018-08-08 19:58 Kyle_Katarn Target Version 5.7.x =>
2018-08-08 19:58 Kyle_Katarn Status acknowledged => closed
2018-08-08 19:58 Kyle_Katarn Resolution open => no change required