Issues with installing Central
Have issues installing Central. During the installation, the "start central" stage will fail after a time out. I can install by disabling Central Start, but when I try to access http://localhost:8080/oo, the browser get stuck displaying “you are about to be redirected to HPE Operations Orchestration web application.
In the WRAPPER log from TOMCAT, get strange SEVERE logs:
SEVERE: Exception sending context initialized event to listener instance of class liquibase.integration.servlet.LiquibaseServletListener
Tried several install with same issue.
- Windows 2012 R2 Datacenter (on azure)
- MySQL 5.7 x64
- MySQL Java connector 6.0.3
Database was created manually. Install script MYSQL.SQL just gone fine.
My.ini was adapted as follow from the standard mysql file, according to install doc and other MySQL issues.
transaction-isolation = READ-COMMITTED
default-storage-engine = INNODB
character-set-server = utf8
max_allowed_packet = 250M
innodb_log_file_size = 256M
max_connections = 1000
user = myusername
password = "mypassword" # <----------------------- VERY IMPORTANT (quotes)
host = localhost
Seems to be an issue with MySQL
Hi readers (and myself as well 🙂
The issue seems to be related with MySQL, since I could get it installed with MSSQL Express 2016. It seems that this version is not supported but it works and what is supported, not.
I faced an other issue with the Installer that won't recognize the named instances. The interface will not accept \ unless you brute paste the full server\instance string. Unfortunately the validator is smart and will not accept the MS naming convention. So workaround, install a new instance with no name, aka default instance, wich is not the default setting when you install mssql.
Re: Issues with installing Central
Install resumé that worked for me:
2012 R2 Datacenter (working on azure)
disabled firewall (should not be an prerequisite)
installed mssql 2016 express edition with admin studio
- mixed mode (sa account enabled)
- no named instance (NAMED INSTANCES will fail)
- enable tcp/ip on the instance
created user DB
USE master GO CREATE DATABASE OODB; ALTER DATABASE OODB SET ALLOW_SNAPSHOT_ISOLATION ON; ALTER DATABASE OODB SET READ_COMMITTED_SNAPSHOT ON; ALTER DATABASE OODB SET AUTO_SHRINK OFF; ALTER DATABASE OODB SET AUTO_CREATE_STATISTICS ON; ALTER DATABASE OODB COLLATE SQL_Latin1_General_CP1_CS_AS; GO CREATE LOGIN OOUSER WITH PASSWORD = 'change-me-soon-of-a-geek'; GO USE OODB IF NOT EXISTS (SELECT * FROM sys.database_principals WHERE name = N'OOUSER') BEGIN CREATE USER [OOUSER] FOR LOGIN [OOUSER]; EXEC sp_addrolemember N'db_owner', N'OOUSER'; END; GO
lauch community-installer-win64 WITH ADMIN ELEVATION otherwise fails
- install central only
- enable HTTP, self signed certs
then I finally get the central console.