When I run Tomcat configuration I get the error below.
Unable to open service BOEX140Tomcat.
Here is the error I get when I run SAP Crystal Server management
Here are the installed components of Crystal Report Server:
I would like to know what other software and components I need to install or what configuration changes I need to make .
apache tomcat for bi 4 automatically stop it self
[enter image description here][3]
and changed the config file inside tomcat to below
the apacha bi for tomcat services automatically get stopped in Central Configuration manager.
From your first screenshot, it appears that IIS is active on port 8080. If Tomcat has been installed along with Crystal Reports server and you've used the default port settings during the installation, then Tomcat will be configured to use port 8080 as well.
Only one process can bind to a given port. So as port 8080 is taken by IIS, Tomcat will stop and exit with an error. You can probably find the error message in one of the log files (check the log subfolder in the Tomcat installation folder).
Here's what you can do. Either:
Change the port Tomcat is using (as described here).
Change the port IIS is using (as described here).
Stop the IIS service if you don't need it (as described here)..
Related
Need some help...
I have jasperserver 4.1 installed on my ubuntu. It runs via bundled tomcat server on 8080 port.
I've installed jasperserver 4.5 on the same host in different folder, and want them to run together. Second tomcat instance is listening on 8081 port.
The problem is when I log in (with the same credentials) via jasperserver web-interface at localhost:8080/jasperserver i am throwed out at localhost:8081/jasperserver and vice versa.
Repositories are different for sure.
Maybe jasperserver use some single auth mechanism?
I think it has something to sessions/cookie mechanism, because if i open them (localhost:8080/jasperserver, localhost:8081/jasperserver) in different browsers everything works ok.
I have looked at lots of forms and threads on this site.
First I installed MySQL using msi installer.
Configuration settings:
- detailed configuration
- developer machine
- multifunctional database
- initial path
- decision support
- enable tcp/icp networking, port 3306, add firewall exception for this port.
- enable strict mode
- best support for multilangualism
- install as windows service, include bin directory
- entered root password.
Then when I clicked execute it freezes after writing the configuration file.
- I closed that window.
Then when I opened MySQL Command Line Client and typed in the root password i get this..
ERROR 2003: Can't connect to to MySQL server (10060)
I then opened up command prompt and typed.
C:\Program Files\MySQL\MySQL Server 5.5\bin\mysqld --install
got message:
Install/remove of this service denied.
I ran the initial configuration as administrator and I have checked that port 3306 is open.
Hope this is detailed enough.
Thanks.
I would suggesting uninstalling them all and reinstalling them with a package such as LAMP (for linux) or XAMPP (for windows). Much easier to install and set up, tutorials everywhere.
Can you get to the MySQL server instance config wizard in start menu
Is the MySQL service running?
whats the conf file look like?
I'm installing teamcity on a windows server 2008 box running iis7. I'm using the windows installer supplied by jetbrains. I've configured the servers to run under a domain account which has been given full control of the build & config directories. The services are configured to use unused ports (tomcat 14142 & build agent: 9090). whenever I connect to the tomcat instance from a machine other than the server I am prompted for credentials. None of the credentials I would expect work. How can I make this prompt for credentials go away?
This was resolved by changing the port number.
I have just installed SQL Server 2008 including Reporting Services on Windows Server 2003. I'm having a problem though accessing the Report Manager. When the Reporting Service is first started I can access it fine but after maybe an hour when I try and access it I get an error saying: Unable to connect to the remote server.
The reporting service is still running at this point. I can connect to it through Reporting Services Configuration Manager and clicking on the Web Service URL gives a directory listing (I assume that is correct behaviour). If I stop and start the service through Reporting Services Configuration Manager then I can access Report Manager once again (although in maybe an hour I will get the same error once again).
I've installed the latest SP1 service pack. I'm using the same domain account to run all the SQL services. The report server is set to use the default ReportServer virtual directory, is set to IP address All Assigned, TCP Port 80 and no SSL certificate. The report manager is set to use the default Reports virtual directory, IP address All Assigned, TCP Port 80 and no SSL certificates.
In the log file I get an error:
Unable to connect to remote server
HTTP status code 500
An attempt was made to access a socket in a way forbidden by its access permissions.
Does anyone have any idea why this is happening? I've searched the net but haven't been able to find a solution.
It was the anti-virus software on the server that was causing the problem. After adding the pagefile.sys as an exclusion it worked fine.
configure your rs like below link :
http://technet.microsoft.com/en-us/library/bb839480(SQL.90).aspx
maybe it solve your problem.
I installed TeamCity and got it working against my project. However, I have since realized that I don't want it the administration page to be configured on port 80. I'm going to have other websites on that server that I want on the default port. How do I change the configured port?
I wandered around the configurations a bit and looked through the administration settings but couldn't figure it out.
The port number can be edited in the <TeamCity home>/conf/server.xml file, line <Connector port="8111" protocol="HTTP/1.1".
from Installing and Configuring the TeamCity server
To add to the answer provided by #sfussenegger you will also need to make sure that your build agents can still connect to the TeamCity server instance on the new port, or else your builds won't run.
To do this, you'll need to change the build agent configuration files to reflect the new serverUrl value. You can find this setting in the C:\TeamCity\buildAgent\conf\buildAgent.properties file.