Kbase P105994: WebClient skips components during application upgrade.
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
5/4/2009 |
|
Status: Verified
SYMPTOM(s):
WebClient skips components during application upgrade.
A new application update has been placed onto the web server.
The client PC's existing application being updated is multiple versions behind.
Errors are produced on client PC's screen during upgrade.
Couldn't download application component: 3/diffs/Main1to3.cab from Web Server with URL: <url> Error code is 2.
Application update has been terminated.
FACT(s) (Environment):
Progress 9.1x
Windows
CAUSE:
Bug# OE00117467
CAUSE:
A problem exists when the Version used when generating the application update matches the WebClient internal version number. Internal version numbers are integers, so if you use integers for your version numbers. E.g. 1,2,3 instead of 1.0, 2.0, 3.0 then you could hit the problem.
FIX:
1. Upgrade to 10.1A or higher.
As a workaround:
1. Make a backup of the following files: WebClient Application project file ( .wcp), all files in the deployment directory including all previous versions
2. Open the WebClient application project file ( .wcp) using text editor
3. Locate the [Versions] section
That section will look like:
[Versions]
1=1 <--- notice the application version number matching the internal WebClient version number.
2=2
3=3
4. Rename the last application version to have name different than the internal version:
[Versions]
1=1
2=2
3=3a
5. Locate all version updates sections and modify the wrong diff cab file names,
including the last version directory name:
[1]
... There are a whole heap of fields here.
[1Updates]
TestApp=3/diffs/TestApp1to3.cab <--- change this to say TestApp1to2.cab, no updates should skip cabs, should be:
[1Updates]
TestApp=3a/diffs/TestApp1to2.cab <--- version directory changed from 3 to 3a and diff cab file name changed as well.
[2]
... There are a whole heap of fields here.
[2Updates]
TestApp=3a/diffs/TestApp2to3.cab
6. Rename the last version directory in the deployment directory to be the same as used
in the step 4 (i.e. from "3" to "3a").
7. Start the WebClient Application Assembler and generate a new version using version name
different than the internal version number e.g. "4a" .