Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Copy link to clipboard
Copied
Sorry to hear you went through hoops with the updater. I can sympathize with your frustrations, we have had many or out own with all sorts of issues administratively as well as in development.
I think I found the cause of the problem you reported. I just applied the 8.0 to 8.0.1 UPDATER to a MULTI-INSTANCE server with 7 INSTANCES without incident. The update took all of approximately 10 minutes.
I couldn't agree with you more; you are so correct that ADOBE provides very little in the way of clearly defined instructions for the updater (and for that matter not very much on most other CF related topics). We found that there is nothing posted in the form or a step-by-step instruction as it regards instructions and in particular be careful as it regards the PATHS of a multiserver installation as it regards doing an upgrade.
To keep it as short as possible, there are several prompts that come up during the UPDATER, two of which fill in with a PATH during the update:
HERE'S WHY - Typically when CF 8 was installed on a server most users will take the defaults for the install and in doing so, the PATH is C:\Inetpub\wwwroot\CFIDE unless it was overidden to some other drive location. This is where the gotcha is during the updater process. If you don't change this path to the location of the CF ROOT CFIDE the only INSTANCE that will get updated to 8.0.1 will be the first INSTANCE that is in "Drive Letter\JRUN4\SERVERS\xxxxxxx". I believe this may explain why only the instance you targeted was updated and when you ran it again and picked another instance the next one updated, etc. After that, attempts to copy other CFIDE around to try to force it to work got it further twisted up until you resorted to the fix method you tried.
HERE'S MY GUESS ON WHY or HOW UPDATER BLOWS THE CONFIGS OUT OF THE WATER - I don't know the TECHNICAL specifics that the Adobe Wizards came up for the UPDATER behind the covers but it seems to me that the UPDATER needs to FIRST UPDATE the CF ROOT "CORE CFIDE" and as the process continues to run it then COPIES the UPDATED CORE CF ROOT CFIDE into each INSTANCE.
Hopefully my posting will help some poor unsuspecting CF ADMIN to an easy 8.0 - 8.0.1 UPDATE.
Good Luck
Copy link to clipboard
Copied
kensdw wrote:
HERE'S MY GUESS ON WHY or HOW UPDATER BLOWS THE CONFIGS OUT OF THE WATER -I don't know the TECHNICAL specifics that the Adobe Wizards came up for the UPDATER behind the covers but it seems to me that the UPDATER needs to FIRST UPDATE the CF ROOT "CORE CFIDE" and as the process continues to run it then COPIES the UPDATED CORE CF ROOT CFIDE into each INSTANCE.
Sounds like somebody had a very unpleasnt upgrade process. I just wanted to say that is is a very plosible theory. I do know that when one creates a new instance that the CFIDE of the new instance is a copy of the base instances CFIDE folder thus inheriting any configureations of the base instance at that time.