Please can you help me for this problem.
I installed TIBCO EMS correctly but when I want to start, it shows this error below.
I used ./tibemsd.sh (like ./tibemsd64 -config ................)
TIBCO Enterprise Message Service.
Copyright 2003-2017 by TIBCO Software Inc.
All rights reserved.
Version 8.4.0 V14 7/20/2017
Parameter error: configuration file
'/home/tibco/TIBCO_HOME/tibco/cfgmgmt/ems/data/tibemsd.conf' not found
or not accessible
I tried to modify the authorization of this file configuration but without results.
I am also get the same problem to start EMS.
In my case, I installed in linux OS.
To start the EMS in GUI mode
go to the path: tib_dir/ems/8.4/bin
[tib_dir is your tibco directory where the ems installed]
Enter the following command
nohup ./tibemsd –config /home/tibco/TIBCO_HOME/tibco/cfgmgmt/ems/data/tibemsd.conf &
hope, it's work.
Related
I have Mirth Connect Version 2.2.3.6825 installed on RHL I want to access my Mirth my Local Machine which have Java 1.8(Java 1.7 it Work fine), I am not able to launch the Administrator tool of Mirth. When I clicked on the administrator button, It opened the window saying starting application after giving User name and Password it give error 'There was an error connecting to the server at the specified address. Please verify that the server is up and running'
http://www.mirthcorp.com/community/wiki/display/mirth/System+Requirements
Java 8 should work with version 2.2.3, but you must be using the Oracle JRE. OpenJDK only recently became supported with version 3.7.
You may also want to try using the new Administrator Launcher available on the mirth downloads page. It comes bundled with a Java 8 JVM so that you don't need to install one separately. It works with all versions of mirth from 2.x and up. See announcement here: https://www.mirthcorp.com/community/forums/showthread.php?t=218662
I just finished installing Tibco EMS on a server that is already running on the old version of tibco. Installation was successful ant it started up properly. But i am having a bit of issues trying to secure the EMS server. I am getting the error below after i entered the default user;
/prov_uat/npsdev1/test/prov/New_Tibco/tibco/ems/8.2/bin> ./tibemsadmin connect
TIBCO Enterprise Message Service Administration Tool.
Copyright 2003-2015 by TIBCO Software Inc.
All rights reserved.
Version 8.2.1 V4 2/1/2015
Login name (admin): admin
Password:
Failed connect to 'connect': error=17, message=Invalid hostname
Anyone with the idea on how to resolve this...
To connect to an EMS instance through the admin utility, you just have to call it. It does not need a separate "connect" operation.
$ ./tibemsadmin
TIBCO Enterprise Message Service Administration Tool.
Copyright 2003-2013 by TIBCO Software Inc.
All rights reserved.
Version 8.0.0 V9 6/7/2013
Type 'help' for commands help, 'exit' to exit:
If your server is not listening on the default port on localhost you can further specify the address with "-server".
./tibemsadmin -server "tcp://myhost:7222"
run tibemsadmin without arguments to be talking to the local EMS server.
'connect' is a command within tibemsadmin, not a command line option.
We are encountering a problem running the MobileFirst Enterprise Server on Windows Server 2012 R2. When we start using a batch file as Administrator, as long as we stay remote connected the server is working OK, we see the Runtime Environments. But when we log out, server is unreachable. We created a Windows Service that starts the server with same command:
*sc create WASLibertyV85 binPath= "C:\Program Files\IBM\WebSphere\Liberty\bin\server.bat start worklight" DisplayName="IBM WebSphere Liberty V8.5 Worklight" start=auto*
But the Runtime is not displayed, we only see:
No runtime environment deployed in this server.
Is there a way to enable MobileFirst Server seeing the Runtime Environments when was started as service?
Here's our complete solution:
1. Start CMD as administrator and run this:
sc create WASLibertyV85 binPath= "C:\Program Files\IBM\WebSphere\Liberty\bin\server.bat start worklight" DisplayName="IBM WebSphere Liberty V8.5 Worklight" start=delayed-auto
2. under Services.msc open the properties of the „IBM WebSphere Liberty V8.5 Worklight“ service and set this (if not already):
Tab GENERAL -> Startup type: Automatic (Delayed Start)
Tab LOG ON -> Log on as: Local System account + Allow service to interact with desktop
++ When the server restarts, it can take up to 2 minutes, until the runtimes are displayed in the Worklight Console!++
MFP is not being run as a service. MFP is simply a web app (a .war file, a .jar file and some artifacts) running on-top of WebSphere Liberty, in your case. So all of this is related only to Liberty and not to MFP.
As long as the Liberty instance is launched correctly, it should handle everything on its own, including the web apps that are deployed to it, MFP being one of them.
You could perhaps follow the instructions provided in this forum topic explaining how to use Apache Commons Daemon to run Liberty as a Windows service. There are other tools that can do this as well.
The problem was cause by starting the service with a log on account set as current windows user. When we've chaged to Local System Account and enabled Allow system to interact with desktop, the Runtime became visible on MobileFirst Server.
Installing the opshub migration tool while logged in as user 'Administrator' fails during setup with error message
ops-003: You are not running the installer with appropriate settings! Please verify the user running the installer is an Admin user.
I searched for this error message in google and looked in the Q&A Visual Studio Gallery site for the migration tool but found nothing concerning this error.
I am trying to install the utility on a virtual server logged in as Administrator.
Download version is:
OVSMU-V1.1.0.005
Operating system:
Windows 2008 R2 Datacenter with Service Pack 1 (This is the machine where TFS 2012 is installed).
Thanks for any help.
We are setting up Tridion 2011 SP1 CDS (.net based) on one of our servers.
We are sruck at point 'Installing Monitoring as a Wndows Service'.
Evern after running the batch file 'StartCDInstaller.bat' and following the procedure, we cannot locate the Tridion Monitoring Agent service in the windows services.
Are we missing something?
Also another question regarding CDS, can we change the location of config files (Deployer, Storage_conf etc) post Installation? Or do we need to re-run the installer?
Update:
The same error even after reinstalling the monitoring service.
"The Event log details: The description for Event ID 100 from source TCDmonitor cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted"
You can change the location of tridion folder structure by setting the System variable in environment variable(Control panel -> system and security -> System -> Advance -> Environment variables -> system variables) called "Tridion_Home" and value as "d:\tridion" (this is the path of the tridion folder ). You can test this after going to run and type %tridion_home% .
If for some reason the Tridion Monitoring Service was not installed by the installer, you can do it manually.
Locate the file cd_monitor.exe (it is on the installation CD in Content Delivery\roles\monitoring\windows).
Copy it to a location where you keep your executables (e.g. to the Tridion\bin folder)
Start a command prompt as administrator and type 'cd_monitor -install'
Go to the services console and start the monitoring service
Had a similar issue too, it was an x64 Content Delivery server with x64 Java installed. Manually installed the monitoring service but refused to start with:
The description for Event ID 100 from source TCDmonitor cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Could not load Java runtime libraries at
the message resource is present but the message is not found in the string/message table
The monitoring service requires 32bit Java, as soon as that is installed it started with no problem.
Hope that helps.
Scott