Upgrade 4.03 -] 4.12 Problem (OpenInsight 32-bit Specific)
At 03 DEC 2002 06:01:22PM Kevin Bolitho wrote:
On applying the 4.03 -]4.12 upgrade an error results. Setup starts and finds the OINSIGHT serial number in the directory that I point to. It then copyies the OS file without problem and gets to the point of loging into oinsight. I supply the SYSPROG password (I am sure this is correct) and OK to proceed. I then get an error message box. This has a title of "OpenInsight Communications" and a message of "Error! OpenInsight failed to start" . Nothing I do seem to help. I have tried different upgrades (eg 4.03 -] 4.1 etc). This is the first upgrade I have had any problems with
Thanks in advance
At 03 DEC 2002 06:48PM Kevin Bolitho wrote:
So much for being sure about the password !!!!!!!!!!! I'll just go and wipe egg of my face…….
At 04 DEC 2002 03:45AM Oystein Reigem wrote:
Kevin,
If it can be of any comfort: For many of the betas it didn't help to know the SYSPROG password. It seemed you had to turn off the password to get the installation to run.
- Oystein -
At 04 DEC 2002 04:28AM Oystein Reigem wrote:
Kevin,
I just said I had to turn off the SYSPROG password to get the 4.1.2 betas installed. But now I suspect the problem had to do with case sensitivity.
I didn't install the final 4.1.2 until right now. And I got the same problem we both had - you with the final 4.1.2 and I with the betas. The solution seemed to be to key in the password in uppercase. That's never necessary when logging on to SYSPROG in OpenInsight. I think the logon window in OI automatically converts the password you key in to uppercase while the logon window in the upgrade doesn't, furthermore that the password is stored as uppercase and comparison is case sensitive.
Silly.
- Oystein -
At 04 DEC 2002 03:44PM Kevin Bolitho wrote:
Oystein
Yes thats right - the password had to be uppercase. It was originally entered lowercase and lowercase seems to work elsewhere.
At 04 DEC 2002 04:27PM Oystein Reigem wrote:
Kevin,
It was originally entered lowercase
The place I enter new passwords (Database Manager - User Management) the password is converted to uppercase while I write. So I assume it's also stored as uppercase. (Encrypted, of course, but from the uppercase version.)
/i]and lowercase seems to work elsewhere.[/i]
I think it's also converted to uppercase when you log in to an OpenInsight application the normal way. But you can't see it of course. Then the uppercase password is compared with the stored version which is also uppercase, and the comparison succeeds.
But in the login window in the installation the password you key in is not converted to uppercase. So if you key it in in lowercase the comparison with the stored version fails.
The guy who made the login window for the installation forgot to set the password control to uppercase. That is my theory.
- Oystein -