Internal Error: failed to convert date

Post questions here relative to DataStage Server Edition for such areas as Server job design, DS Basic, Routines, Job Sequences, etc.

Moderators: chulett, rschirm, roy

ascen
Premium Member
Premium Member
Posts: 67
Joined: Wed Apr 12, 2006 6:47 am
Contact:

Internal Error: failed to convert date

Post by ascen »

Hello,

During new installation of DS 7.5.3 on HP-UX 11.23 I got the following error:

Code: Select all

[DataStage 7.5 - Installation and Maintenance Utility]

SERVER LICENSE

Please enter your authorization details exactly as found on
the Product Authorization Code Details.

(* = previously licensed)


   1) Serial Number          : 407599
   2) CPU Count              : 16
   3) Expiration Date        : 01/01/2500

   4) Enterprise Edition Code: 
   5) Server Code            : ***********
   6) MVS Edition Code       : 


Enter (c)hange, (n)ext, (b)ack or (q)uit n


Internal Error: failed to convert date

Press <cr> to continue
The authorization codes where previously used on earlier version of HP-UX, DS 7.5 and works fine.
Do you know what causes the problem? How to solve it?
Thanks in advance.

Best regards,
Piotr Palka
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

What is your system's default date format? Perhaps it is yyyy-mm-dd and you might try entering the date in that format, i.e. 2500-01-01
ascen
Premium Member
Premium Member
Posts: 67
Joined: Wed Apr 12, 2006 6:47 am
Contact:

Post by ascen »

I've tried to type the date in various format, but nothing worked. Do you know how to check what is the default OS date format on HP-UX?
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

I would have expected the "date" command to display in the NLS format, but am not at a machine where I can check that.

I seem to recall we always had to type in the same formatted date regardless of NLS settings, so that is probably not the issue after all.

Do you get a different error if you try "01/01/2008"?
ascen
Premium Member
Premium Member
Posts: 67
Joined: Wed Apr 12, 2006 6:47 am
Contact:

Post by ascen »

ArndW wrote: Do you get a different error if you try "01/01/2008"?


Yes, the same error for different date values. But after applying some new patches to OS I got "authorization failed" error.
ray.wurlod
Participant
Posts: 54607
Joined: Wed Oct 23, 2002 10:52 pm
Location: Sydney, Australia
Contact:

Post by ray.wurlod »

The rule is that the date format must match exactly the format on the advice of the authorization code.

Check that your expiry date is, in fact, 01/01/2500 on the documentation.
IBM Software Services Group
Any contribution to this forum is my own opinion and does not necessarily reflect any position that IBM may hold.
ascen
Premium Member
Premium Member
Posts: 67
Joined: Wed Apr 12, 2006 6:47 am
Contact:

Post by ascen »

ray.wurlod wrote:The rule is that the date format must match exactly the format on the advice of the authorization code.

Check that your expiry date is, in fact, 01/01/2500 on the documentation.
Yes, it definitelly is.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

There's more going on than just the format of the date, it seems. Is this a PA-RISC or Itanium machine? I assume you pulled down the proper version of DataStage, yes?
-craig

"You can never have too many knives" -- Logan Nine Fingers
ascen
Premium Member
Premium Member
Posts: 67
Joined: Wed Apr 12, 2006 6:47 am
Contact:

Post by ascen »

chulett wrote:There's more going on than just the format of the date, it seems. Is this a PA-RISC or Itanium machine? I assume you pulled down the proper version of DataStage, yes?
It is an Itanium machine. I have downloaded it from Passport Advantage site for my ICN number so it should be the proper version.
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

It *should be* or *is*? I'd suggest you double-check, as from what I recall I could download either version for HP-UX.
-craig

"You can never have too many knives" -- Logan Nine Fingers
ascen
Premium Member
Premium Member
Posts: 67
Joined: Wed Apr 12, 2006 6:47 am
Contact:

Post by ascen »

chulett wrote:It *should be* or *is*? I'd suggest you double-check, as from what I recall I could download either version for HP-UX.
I checked the download page and there is only one version to download for HP-UX. So as I undestand there are only one installation program for both itanium and PA_RISC architecture.
ArndW
Participant
Posts: 16318
Joined: Tue Nov 16, 2004 9:08 am
Location: Germany
Contact:

Post by ArndW »

ascen - after applying the patch, is your error for the 01/01/2500 date still the same, while that for 01/01/2008 results in "authorization failed" or is that the error for both dates?
ascen
Premium Member
Premium Member
Posts: 67
Joined: Wed Apr 12, 2006 6:47 am
Contact:

Post by ascen »

The same error for any date: "authorization failed"
Does version 7.5.3 require any new authorization codes?
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

ascen wrote:
chulett wrote:It *should be* or *is*? I'd suggest you double-check, as from what I recall I could download either version for HP-UX.
I checked the download page and there is only one version to download for HP-UX. So as I undestand there are only one installation program for both itanium and PA_RISC architecture.
No, there isn't. Hopefully, however, they "know" which one to offer to you.
-craig

"You can never have too many knives" -- Logan Nine Fingers
chulett
Charter Member
Charter Member
Posts: 43085
Joined: Tue Nov 12, 2002 4:34 pm
Location: Denver, CO

Post by chulett »

ascen wrote:The same error for any date: "authorization failed"
Does version 7.5.3 require any new authorization codes?
Yes, of course. Did you not receive them when you ordered the upgrade or new license?
-craig

"You can never have too many knives" -- Logan Nine Fingers
Post Reply