I am trying to upgrade a 5.1 (sp8) server to 6.5 (Sp5). I have tried the
in place upgrade and the migration methods.

I cannot install any licences on the new upgraded. When I try, I get a
response "that the object does not exist and that I should try
setupnls.exe". I have tried to load setupnls.nlm (I cannot find the exe
file anywhere) but the same result, no licences and thus not able to map
drives etc. (the licences are valid as if I set up a stand alone server
from "new" the licences are loaded correctly.

On running Pkidiag (which the inplace upgrade requested) it is clear that
the SSL certificateIP and SSL CertificateDNS cannot be created.

I am tempted to follow TID 10094253 which is trouble shooting steps for
SSL certificates but before I do I would like to know if this a step in
the right direction.

I have full working backups of my 5.1 server so it will not be a disaster
if it fails but I want to know if this TID will help in these
circumstances.

Here is the result of PKIdiag - For security I have changed the server's
name to xxx.


--------------------------------------------------------------------------
-
PKIDiag 2.78 -- (compiled Jul 18 2005 17:19:11).
(Check the end of the log for the last repair results)
Current Time: Wed Sep 20 09:21:04 2006
User logged-in as: admin.gm.
Fixing mode
Rename and create mode
Rename and create when necessary

--> Server Name = 'xxx'
--------------------------------------------------------------------------
-

Step 1 Verifying the Server's link to the SAS Service Object.
Server 'xxx.gm' points to SAS Service object 'SAS Service - xxx.gm'
Step 1 succeeded.

Step 2 Verifying the SAS Service Object
SAS Service object 'SAS Service - xxx.gm' is backlinked to
server 'xxx.gm'.
Step 2 succeeded.

Step 3 Verifying the links to the KMOs
Reading the links for SAS Service object 'SAS Service - xxx.gm'.
--> No KMOs are linked to Service object 'SAS Service - xxx.gm'.
Step 3 succeeded.

Step 4 Verifying the KMOs
---> Testing KMO 'SSL CertificateDNS - BORDERGW.gm'.
Rights check -- OK.
Back link -- Belongs to a different server -- Ignoring this KMO.

---> Testing KMO 'SSL CertificateIP - BORDERGW.gm'.
Rights check -- OK.
Back link -- Belongs to a different server -- Ignoring this KMO.

---> Testing KMO 'SSL CertificateDNS - xxx.gm'.
Rights check -- OK.
Back link -- OK.
Private Key -- Failed.

---> Testing KMO 'SSL CertificateIP - xxx.gm'.
Rights check -- OK.
Back link -- OK.
Private Key -- Failed.
Step 4 succeeded.

Step 5 Re-verifying the links to the KMOs
Reading the links for SAS Service object 'SAS Service - xxx.gm'.
--> No KMOs are linked to Service object 'SAS Service - xxx.gm'.
INFO: kmo SSL CertificateDNS - xxx.gm should probably be deleted.
INFO: kmo SSL CertificateIP - xxx.gm should probably be deleted.
Step 5 succeeded.

Step 6 Creating IP and DNS Certificates if necessary.
--> Number of Server IP addresses = 1
--> The default IP address is: 10.1.1.2
PROBLEM: A SSL CertificateIP does not exist
FIXING: Creating SSL CertificateIP (10.1.1.2)
Pausing for 5 seconds because of error -1418
ERROR -1418 creating SSL CertificateIP.
--> Number of Server DNS names for the IP address 10.1.1.2 = 1
--> The server's default DNS name is:
xxx
PROBLEM: A SSL CertificateDNS does not exist
FIXING: Creating SSL CertificateDNS (xxx)
Pausing for 5 seconds because of error -1418
ERROR -1418 creating SSL CertificateDNS.
Step 6 failed -1418.


Note: Occasionally multiple problems will be solved with a single fix.

Fixable problems found: 2
Problems fixed: 0
Un-fixable problems found: 0

====================================

Any help most welcome

Bernard