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.
Related
I am running sqlpackage from commandline:
sqlpackage.exe /action:Extract /TargetFile:"C:\file.dacpac" /sourceDatabasename:dbsorgente /sourceservername:dummy.database.windows.net /p:ExtractAllTableData=True
and I get error:
[Windows logins are not supported in this version of SQL Server]
The db is on Azure and from Sql Management STudio I can successfully connect to it.
Can you help me ?
You need to specify also /SourceUser: and /SourcePassword: in your command, otherwise it will use Windows login to authenticate to source server.
So your command should look like:
sqlpackage.exe /action:Extract /TargetFile:"C:\file.dacpac" /sourceDatabasename:dbsorgente /sourceservername:dummy.database.windows.net /sourceuser=yourUser /sourcePassword=yourPassword /p:ExtractAllTableData=True
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.
When I try to integrate TFS 2017 U3 with SQL Server 2017 Reporting Services, from TFS Administration Console, an error appear. Please see screenshot.
In the event viewer of TFS server, I see registered this error:
DCOM was unable to communicate with the computer servername using any of the configured protocols; requested by PID
1080 (C:\Program Files\Microsoft Team Foundation Server 2018\Tools\TfsMgmt.exe).
Error Image
I have had checked the following:
Windows Firewall is not blocking port 80
Reporting service is started
User Account has required permissions
WMI is running on the report Server
TFS databases are in the same server than reporting services and the TFS service is running without any problem.
Please, any idea how to revolve this error will be very appreciated
I was wrong when placing the error text messaage. I had performed a test from TFS 2018 that's the reason why I wrote with that description eror, but the productive environment is with TFS 2017 U3 and the error message is the same thing; the difference is the path where TfsMgmt.exe is located.
Thanks for your attention.
Audberto
I have a personal laptop running Windows 10 Home edition.
I log into the laptop with my hotmail account.
I installed TFS 2017 locally and I have it woring in the browser. I can clone the repository and push to it.
Now when I try to setup the build I have to add an agent. I downloaded the agent and when I try to configure it I get this:
PS D:\TfsAgent> .\config.cmd
Connect:
Enter server URL > http://localhost:8080/tfs/
Enter authentication type (press enter for Integrated) >
Connecting to server ...
An error occurred while sending the request.
Failed to connect. Try again or ctrl-c to quit
Enter server URL >
Soo, for some reason an error happens when it tries to connect to the server.
I do not see any verbose parameter to the config.cmd or any logs for that matter.
Any reasons why?
Home edition of Windows does not support the full TCP stack nor does it have all of the tools expected by applications. You need Professional edition at a minimum.
I would recommend that you go to http://tfs.visualstudio.com and let Microsoft provision you a free TFS instance that you can use.
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.