tracker issue : CF-3367872

select a category, or use search below
(searches all categories and all time range)

Updater should leave the system how it found it

| View in Tracker

Status/Resolution/Reason: Closed/Fixed/

Reporter/Name(from Bugbase): Adam Cameron / Adam Cameron (Adam Cameron)

Created: 11/19/2012

Components: Hot Fix Installer, Installer

Versions: 10.0

Failure Type:

Found In Build/Fixed In Build: Final / 288574

Priority/Frequency: Major / Most users will encounter

Locale/System: English / Windows 7 64-bit

Vote Count: 0

Problem Description:
I generally have all my CF services set to manual start-up, and leave them OFF most of the time. When CF does an update, it starts everything (incl. all the helper services like .net integration, ODBC services etc). I understand how it might need to start these thigns as part of the update, but it should return them to the status it found them in once it's done. So if a service is OFF before the update needs to start it, it should return it to an OFF state once it's finished with it; if it's ON, it should ultimately leave it ON once it's done.

Steps to Reproduce:
Run an update with CF services off. 

Actual Result:
Note they're all ON once the update finishes.

Expected Result:
Leave things in order once you've finished.

Any Workarounds:

----------------------------- Additional Watson Details -----------------------------

Watson Bug ID:	3367872

External Customer Info:
External Company:  
External Customer Name: Adam Cameron.
External Customer Email:  
External Test Config: My Hardware and Environment details:



This issue is fixed in the next major release of ColdFusion.
Comment by Nimit S.
17176 | February 27, 2014 11:22:19 PM GMT
This has been closed as a duplicate of CF-3560667, which either doesn't exist, or is not publicly accessible. You do this fairly frequently. Can you pls stop cross-referencing public-facing bugs to "hidden" bugs by way of resolution? This is important because you also have a track record of being a bit trigger-happy in closing bugs as duplicates of other bugs, when they're not actually duplicates, so it's important for us to be able to see this. Can you pls make CF-3560667 public-facing? And pls adopt a policy of not cross-referencing client-raised tickets to internal tickets we can't see. -- Adam
Comment by External U.
17177 | February 27, 2014 11:39:42 PM GMT