Skip to main content

ADMU3011E when deploying Cognos in Connections 4.5

I had a cognos for connections 4.5 to deploy, and I keep getting error. cognos_server was unable to start with WAS error into cognos-configure.log

ADMU0116I: Tool information is being logged in file
           /opt/IBM/WebSphere/AppServer/profiles/CognosProfile/logs/cognos_server/startServer.log
ADMU0128I: Starting tool with the CognosProfile profile
ADMU3100I: Reading configuration for server: cognos_server
ADMU3200I: Server launched. Waiting for initialization status.
ADMU3011E: Server launched but failed initialization. Server logs,
           startServer.log, and other log files under
           /opt/IBM/WebSphere/AppServer/profiles/CognosProfile/logs/cognos_server
           should contain failure information.
Waiting for Cognos services started.

I noticed that i left populated this variable also on linux

# The following property is only required for Windows systems.
# The fully qualified host name of this Application Server
# Example: host.example.com
was.fqdn.hostname=cognosnode.test.com

I changed the property to was.fqdn.hostname=

Then I cleansed everything
on linux this mean /opt/IBM/WebSphere/AppServer/profiles/CognosProfile/bin/removeNode.sh, ( if federated) then
/opt/IBM/CognosTR/bin/uninst -u -s
/opt/IBM/CognosBI/bin/uninst -u -s

then, after stopping all running servers

./manageprofiles.sh -delete -profileName CognosProfile

Then I cleaned the /tmp/folder  and the CognosProfile. Then I ran ./cognos-setup.sh, started cognos_server manually, ran ./cognos-configure and it worked correctly


Comments

Amirtha rao said…
Managing a business data is not an easy thing, it is very complex process to handle the corporate information both Hadoop and cognos doing this in a easy manner with help of business software suite, thanks for sharing this useful post….
Regards,
cognos Training in Chennai|cognos Training Chennai

Popular posts from this blog

Building bitcoin/litecoin on mac os x missing EC.h

For my own fun, I was playing around with bitcoin, to check how the parameters of the cryptocurrencies can be modified.

After recent upgrades to my OS, I could not build any longer the bitcoind. Seems like something changed on that side. Now this command

./configure --with-gui=qt5 --enable-debug
Was sistematically producing 
configure: error: OpenSSL ec header missing

EC is the file for elliptic curve cryptography. I had brew correctly configured, and the header files were all correctly present. After some time spent inspecting the issue, on github I was able to find the solution for this problem. I simply add to export the following
export LDFLAGS=-L/usr/local/opt/openssl/libexport CPPFLAGS=-I/usr/local/opt/openssl/include
There is aksi pull request on bitcoin for that, I hope I could save you some time https://github.com/bitcoin/bitcoin/pull/6885/files?diff=split&unchanged=expanded

Hybris setup issue: Unsupported major.minor version 52.0

While I was typing the final "ant all" command for hybris, it miserably failed with the following exception

hybris/bin/platform/resources/ant/antmacros.xml:123: java.lang.UnsupportedClassVersionError: de/hybris/ant/taskdefs/DbDriverValidator : Unsupported major.minor version 52.0 at java.lang.ClassLoader.defineClass1(Native Method)


Even though a "java -version" gave me back version 8, ant is still using $JAVA_HOME variable.
So you have to change it into the script. My suggestion is that you adapt the setantenv.bat script with the JAVA_HOME directly


@echo off
set ANT_OPTS=-Xmx512m -Dfile.encoding=UTF-8
set ANT_HOME=%~dp0apache-ant-1.9.1
set JAVA_HOME=C:/Program Files/Java/jdk1.8.0_101
set PATH=%ANT_HOME%\bin;%PATH%
rem deleting CLASSPATH as a workaround for PLA-8702
set CLASSPATH=
echo Setting ant home to: %ANT_HOME%
ant -version

SECJ0118E with form authentication and spnego enabled

Our deployment keeps getting an odd SECJ0118E  exception when authenticating with Form authentication with Mozilla or Chrome browser not configured for Active Directory Domain.

All instructions into WebSphere infocenter for enabling fallback to default authentication were correctly applied.  We noticed that standard WebSphere security tracing (*=info:com.ibm.ws.security.*=all:com.ibm.websphere.security.*=all:com.ibm.websphere.wim.*=all:com.ibm.wsspi.wim.*=all:com.ibm.ws.wim.*=all)  provided into trace a lot of Kerberos exceptions. 
[30/12/13 17.36.57:246 CET] 0000005e Krb5LoginModu < login() Exit javax.security.auth.login.FailedLoginException: Errore di login: com.ibm.security.krb5.KrbException, codice di stato: 68
messaggio: Nessuno at com.ibm.security.jgss.i18n.I18NException.throwFailedLoginException(I18NException.java:30) at com.ibm.security.auth.module.Krb5LoginModule.a(Krb5LoginModule.java:719) at com.ibm.security.auth.module.Krb5LoginModule.b(Krb5LoginModule.java:742)

Double chec…