This is the error I receive when trying to run the incremental installer to v6.0.1 on a Win2000 box. I tried rebooting the box before install to be sure no Domino services were still running; however, still same error.
Using Notes program directory X:\NOTES
Using Notes data directory X:\NOTES\DATA
X:\NOTES\nstrings.dll
Identified Release 6.0|September 26, 2002.
The file js32.dll is missing or in use by another process. Skipping
Subject: Incremental Installer v6.0.1 for Win2000 Error
I’m having the same problem. Upgraded a server from 4.6.7 to 4.6.7a to 6.0. Then the incremental installer wouldn’t let me go to 6.0.1 because of this same error message (“The file js32.dll is missing or in use by another process.”).
I tried deleting js32.dll, reinstalling the server. The reinstall failed with a -115 error, but got far enough to reinstall js32.dll. Then the incremental upgrade was failing with a new error: “The file nxmlcommon.dll is missing or in use by another process.”
I copied nxmlcommon.dll from the Notes folder on the same machine. The Incremental Installer worked!
The suggested “fix” is to start the machine in safe boot mode. In fact, just renaming js32.dll and nxmlcommon.dll allowed the upgrade to work for my server.
Here’s the suggested Lotus workaround, to save you the trouble of looking it up:
======================================
In this case the workaround was to invoke the Safe Mode during booting the operating system. This process of booting loads a minimal set of device drivers and services invoked by pressing F8 when prompted during booting to enter Safe Mode. Once Safe Mode is invoked, a Windows Advanced Options menu will display a listing of different Safe Mode options available.
The option you select depends on where the Domino install media is located. If a CD-ROM is being used, choose Safe Mode. If installing from a network share, choose Safe Mode with Networking. Behind the scenes, Windows 2000 dynamically adds switches to the boot.ini arc path such as “/safeboot: minimal” for basic Safe Mode or “/safeboot: network” for the networked Safe Mode option.
This also works if there is an error with the js32.dll file. The benefit of upgrading Domino with this method is that js32.dll is no longer a locked file, and the installation will run to completion as designed. Once the upgrade is finished, reboot the server and allow the Windows 2000 operating system to start normally. The Domino server then starts up without error.
Alternatively, renaming js32.dll to oldjs32.dll seems to allow the upgrade to finish as well.
Subject: Incremental Installer v6.0.1 for Win2000 Error
Your problem sounds like a similar one we had at the office (upgrading to R5.0.9a) and I could not get a straight answer out of the guys that support the OS, but they did come up with a work around.For us the file was always in use (???) so we couldn’t delete or upgrade it, but we were able to drag it to the root of the drive it was currently installed on and then upgrade our server code. A big difference is that we used the complete install and not the incremental. I’ve seen other posts where problems with individual files not passing their checksum tests can be deleted (or moved) and the incremental installer can then be run again to completion.
After a successful upgrade, we were then able to delete the file in the root of the drive.
Subject: RE: Incremental Installer v6.0.1 for Win2000 Error
My results were very similiar. I tried installing the full version of 6.0.1 and still the same errors messages (or at least very similiar). I ended up booting the OS in safe mode and trying the incremental installer, same error … I then tried installing the full version … no errors. Oh well, at least it’s in and working now. Not the easiest upgrade processes …
Subject: RE: Incremental Installer v6.0.1 for Win2000 Error
When I installed the full version of 6.0.1 on W2K it would not install without the W2K disk being inserted due to some “Windows file protection” warning. When I tried to ignore it, it backed out of the install. After trying again and this time inserting the W2K disk the install completed.