Rick, Like you I thought that one would have to go through 7.1 because of the change with licensing in 7.1 that carries over into 7.5. ------Original Message------ From: Rick Cook To: Arslist ReplyTo: Arslist Subject: Re: Upgrading ARS 6.3 to 7.5 failed Sent: Sep 7, 2009 5:01 PM
Are you sure that going straight from 6.3 to 7.5 is allowed? Rick From: Miguel Suarez Gomez Date: Mon, 7 Sep 2009 22:57:34 +0200 To: <[email protected]> Subject: Re: Upgrading ARS 6.3 to 7.5 failed ** I've got more info about the issue: Finally, starting the ar server manually by the command line, I could connect to it using some of the clients (Developer, User, Data Import) with my Admin user. I could get an API log of the server inicialization and the result is this: <API > <TID: 0000000640> <RPC ID: 0000000000> <Queue: Main > <Client-RPC: 000000 > <USER: > /* lun sep 07 2009 12:49:32.6090 */Registro de seguimiento de API -- ACTIVADO (AR Server 7.5.00 Build 200812291922) <API > <TID: 0000004064> <RPC ID: 0000000000> <Queue: Fast > <Client-RPC: 390620 > <USER: 10.8.7.141 > /* lun sep 07 2009 12:51:01.7810 */+GEI ARGetEncryptInfo -- as user from Unidentified Client (protocol 14) at IP address <API > <TID: 0000004064> <RPC ID: 0000000000> <Queue: Fast > <Client-RPC: 390620 > <USER: 10.8.7.141 > /* lun sep 07 2009 12:51:01.7810 */-GEI OK <API > <TID: 0000001924> <RPC ID: 0000000001> <Queue: Fast > <Client-RPC: 390620 > <USER: Remedy Application Service > /* lun sep 07 2009 12:51:01.7960 */+GSI ARGetServerInfo -- as user Remedy Application Service from Application Command Dispatcher (protocol 14) at IP address 10.8.7.141 Dave ------------------------- [email protected] (Wireless)
