Calender Server Configuration Assistant failed

Question

Running on Red Hat Linux Enterprise edition 2.1.
Collaboration suite 9.0.4 (OCS R2).
Calender server configuration assistent failed with message:
Output generated from configuration assistant "Calendar Server Configuration
Assistant":
uniaddnode: Database initialization done
uniaddnode: node [2] has been successfully initialized
unistart: Oracle Calendar Server 9.0.4
unistart: Copyright (c) 1993, 2003, Oracle.
unistart: All rights reserved.
unistart:
unistart: unicheck working, please wait ...
unistart: Starting the Calendar Directory Access Server
**ERROR** unistart [error]: Error starting the Calendar Directory Access Server
unistart [error]: More details can be found in
unistart.log and in das.log.
**ERROR** Could not start the calendar server.
java.io.IOException: /home/oracle/midtier/ocal/bin/unistart: returned 1
Configuration assistant "Calendar Server Configuration Assistant" failed
Unistart.log and das.log does not provide any meaningful information on what is wrong.
------------------------------------------------------------------------------- DATE = Fri Aug 1 16:41:46 2003
PID = 20845; TID = 8192
ERROR CODE -> 0x40216
FUNCTION NAME -> Unistart::ProcessLocalStartServer()
Error starting the Calendar Directory Access Server.
All configuration assistants were successfully apart from the Calendar Server Configuration Assistent
Every prerequisite actions where taken according to Installations guide and
release notes.
All kernel parameters set.
The architecture is as follows:
Infrastructure and Storage RDBMS is installed on server A
and the middletier on server B.
All the components were successfully installed and configured on both servers apart for the Calendar server on middletier.
On server A the X-server was not running during the middletier installation.
We have tried the installation twice. The second time changing the
ip_local_port_range kernel from 61000 to 65000 as this parameter turned out not to have been correctly set in the first install.
Clues anyone?

Answer 1

I'm having a similar issue, and have opened a TAR for the problem. According to Oracle, it's the same error as the one received when the username is over 8 characters. Being that this is not the case in my environment, they are scratching their heads.
The only thing we can see as a possible user-name type issue is that the username and the group name are the same, though this is probably not the issue.
I'll post anything I find out.
Regards
Tait