000011669 - Upgrade issue from RCM 6.7 on Solaris to RCM 6.8 on Windows

Document created by RSA Customer Support Employee on Jun 14, 2016Last modified by RSA Customer Support Employee on Apr 22, 2017
Version 2Show Document
  • View in full screen mode

Article Content

Article Number000011669
Applies ToRSA Certificate Manager 6.8
Windows Server 2003 SP2
Sun Solaris
IssueUpgrade issue from RCM 6.7 on Solaris to RCM 6.8 on Windows
Customer has RCM 6.7 running on Solaris and want to upgrade and over to Windows.

The Windows 2003 R2 SP2 Install failed.
Got ...\iws\bin\apache-setup.exe -d2 -f iws.log iws.conf return code 48
XrcBADRESOURCE a req resource was not usable
Unable to retrieve or create CA for signing

had a successfully new install of RSA CM 6.8 Build 520 on a physical Windows 2003 R2 EE SP2 (32-bit) server.
Enrollment and Admin Console fully functional.
uninstalled the build.

Then using the package.tar from the Solaris server was able to upgrade on the Windows server.

Now the DOS Window states that the database is being indexed.
It has been over 2 hours.

NEXTID file = 1279

It finally displayed an error dialog after 3 hours: confirmXudadStartup: failed to confirm Xudad startup.
Also found "Caught XDK Exception" in Upgrader log.

RSA CM 6.8 (Secure Directory) is the only service created.

I did manage to reindex the DB on Solaris

I recreate the scenario again.

What I did do was migrate/upgrade form Solaris to Linux RSA 6.8 successfully again
And the DB was reindexed.

Windows still will not migrate.

Observed the log events missing issue for the below scenarios,

When we upgrade from RCM 6.7 build419 to RCM 6.8 build520 on same as well as cross platforms (Solaris to Solaris) or (solaris to windows), the log events are missing.
but upgrade with RCM 6.7 build419 to previous RCM 6.8 build519 release, there are no any missing log events.

There is an issue with xu_ldbmcat utility in RCM 6.8 build 520 for Solaris
This problem has been fixed in RCM 6.8 build 522.  Contact RSA Support to obtain RCM 6.8 build 522 or later, and run the upgrader again to generate a new package.tar and complete the upgrade.
Legacy Article IDa56575