Search This Blog

Friday, September 7, 2018

(RESOLVED) Need help with installation of FP9/FP10: External VM is not valid - it must be a 1.5 or 1.6 Sun or IBM VM


Today I spent almost a whole day but couldn't install LN 9.0.1 FP10.
This is very embarrassing especially for the one working with Notes for more than 15 years.
Did I become too old?

The story:

1) I rolled out Hyper-V VM with x64 Windows 10 Enterprise (build 1803).
2) Installed standard 9.0.1 for multi users - all was good at this point.
3) Tried to install FP10 - failed with error "The wizard was interrupted before IBM Notes 9.0.1 FP10 could be completely installed.

I started googling by error text "The wizard was interrupted..." but all suggestions didn't work for me.
4) Eventually I didn't have any other options except looking into Installation.log.
I found there following error message:

Line 431: XPD: 9/7/2018 16:23:59 CActionsCommon/GetProperty: DEBUG - Retrieved property: RCP_INVALID_EXTERNAL_JVM_ERROR, Value: External VM is not valid - it must be a 1.5 or 1.6 Sun or IBM VM.

I started googling "External VM is not valid - it must be a 1.5 or 1.6 Sun or IBM VM" and found that FP6 had to fix that error.

So I cleand VM and did everything again, but this time I installed FP6 at first.
FP6 was installed successfully and I (feeling myself on the edge of a victory) started installation of FP10 but got the same dialog with "The wizard was interrupted...". However this time I spotted that error happened almost in the very beginning of FP10 installation - previously (without installation of FP6) it happened in the very end.

I checked installation log again and this time I found there something new:

Line 439: XPD: 9/7/2018 17:30:51 CActionsCommon/GetProperty: DEBUG - Retrieved property: RCP_INVALID_EXTERNAL_JVM_ERROR, Value: External VM is not valid - it must be a 1.5 or 1.6 Sun or IBM VM.
Line 613: 9/7/2018 17:31:06 2018-09-07T05:31:06.6--1:00 CCCUActionsApp/RenameDirectory: ERROR: Maximal retry time exceeded. Consider renaming failed.
Line 615: 9/7/2018 17:31:06 2018-09-07T05:31:06.6--1:00 UninstallJvmUpdate: ERROR: Failed to rename directory C:\Program Files (x86)\IBM\Notes\jvm to C:\Program Files (x86)\IBM\Notes\jvm_old: 5

I googled "Failed to rename directory jvm to jvm_old" - but I only found some posts where IBM confirmed the issue and included it into scope of following fixes but there wasn't any workaround suggested.

I discovered that FP8 worked OK the same as FP6 - the problems happened with FP9 and FP10 only.

That's all - I couldn't do anything eventually but trust me, I tried really a lot:
- I tried to disable Windows Defender, UAC, Firewall
- tried to change Notes folders permissions, owners;
- tried to install LN for a single user
- tried to use other path for installation
- I used some monitoring software trying to catch if any other processes works with Notes-folder during FP10 installation.
Nothing helped.

I would be grateful for any ideas please.

Update on 9.9.18
I managed to install FP10 IF4 - previously I tried to install FP10 IF2.

Still have issue with FP9 IF1 (SHF55).
I am going to try two things:
1) check if FP9 IF2 (SHF123) works OK.
2) try to use older build of Windows 10, for example 1709.
Update on 10.9.18

Installed FP9 as well.
The problem was with expired certificate in FP9 installation.
It is a bit shameful and strange in the same time: I had the problem with expired certificate in FP9 installation in past and even made a post about it but that time I clearly saw something about "expired signature" in installation logs. This time installation logs didn't have a word about certificate/signature error.
The difference in installation processes is that previously I used installation with Notes+Designer+Admin but this time I used Notes-only installation.
It's very sad that I forgot about this issue and wasted so much time.
Thank you very much to all who provided suggestions in comments to this post.


  1. Please check

    1. Installation log does not say anything about issues with certificates or signatures as it was described by your link. Thank you though.

    2. You were right!
      Though installation logs didn't have a word about expired signature the problem was exactly about it. Thank you very much, it's sad that I forgot about this problem and lost so much time...

  2. Use Notes 9.0.1 FP10 IF4 or IF3 installer. Download links at:

    1. Thank you. I will try. However I need to install VM with Notes 9.0.1 FP9 as well ( I am testing differences in work of OSGI plugins between Expeditor 3x (Notes with FP prior FP9) against Expeditor 4x (Notes FP10). I can't install FP9 as well on my VM so that FP10IF4 will not help.

    2. Thank you so much - FP10 IF4 WORKED!
      I think previously I tried FP10 IF2.
      Half of problem is resolved, thank you one more time.
      Now I am focusing on issue with FP9...

    3. For FP9 you should use IF2.

    4. Yes, I already got it. Thank you very much for your help.

  3. check your NTFS properties:
    From an Administrator cmd prompt: fsutil 8dot3name query
    check that 8dot3name creation is on. Installer is old, and new Filesystems default to 8dot3name OFF. Which cause problems if paths have spaces...
    You can see this if you follow where the temp files go using the update log and process explorer.
    See also response to Rainer Brandl post:

    1. Hi, thank you, it didn't help unfortunately, I worked with user "User" so there wasn't spaces in username. Just in case I tried fsutil 8dot3name query and it returned me status = "2".
      I tried to set it to "0" - no difference.

    2. just setting the property only changes the behaviour on create. It does not create the 8dot3name if it is missing. Forgot to mention that.

  4. Access rights may be a problem. I usually install to C:\IBM\Notes.

    1. It was a clean Windows. I used user with Admin rights. Installation of standard Notes worked OK, installation of FP6 and FP8 also worked OK. Only FP9 and FP10 failed. I tried to install to C:\IBM\Notes - still had the error.

  5. Hi.
    I had all the same errors with FP10, including the JVM error, w/o the expired certificate errors in the install log.
    I made these changes:

    in file \lotus\notes\framework\rcp\plugin_customization.ini

    in temporary FP10 install unpacked location (which will overwrite same setting above)
    in file \Users\XXX\AppData\Local\Temp\IBMNotes\deploy\plugin_customization.ini

    Then FP10 finally installed.

    1. Hi, thanks, I used this workaround also in past and even described it on my blog:
      The problem is that with time I forgot about this and wasted much time.
      The better thing is to download the latest FP, delete FP with problems and forget about this at all.

    2. Hi Yuri and also "Anonymous" above... It's a disgrace, than even after 2 years, when updating (HCL!)Notes 10.0.1 with newest FP5 this stupid error still exists... So thank you both, you saved my day :-)

  6. Hi Yuriy,

    I didn't expect to get on your blog when looking for my issue installing Notes 9.0.1 FP9. It was a pleasant surprise, and you saved my day !

  7. Hi Yuriy, thank you for this post - it helped me more than 1 time upgrading with a hotfix.
    Unfortunately while upgrading from "9.0.1 FP 10 IF8" to "9.0.1 FP 10 IF10" results in the same errors, although the settings in plugin_customization.ini are set to ALLOW.
    The plugin_customization.ini in the extracted upgrade package is empty, tried to add the values there also but no try helped.
    Does anyone have other ideas ?

    1. Hi, I do not think you had the same error.
      I used the trick with plugin_customization.ini for clean FP9 only (without any IF included).
      As far as I remember IBM fixed the problem with expired certificate in next FP9 with interim fixes included, maybe it was FP9 IF3, I do not remember.
      I doubt the problem existed in fixpacks released after FP9IF3 but I am not sure, of course. I personally would try again and use some clean Notes installation on a separate VM to test the scenario.

    2. Thanks for the quick answer.
      V9 is not under support anymore and I do not have a clean 9.0.1 installation package nor is the download available, I will try to convince the customer to upgrade to 10, 11 or 12...these installers all ran fine.