I have installed WebSphere portal in my local machine , it was running fine till now.Today i installed IBM HTTP server and suddenly my web sphere portal is not starting .
I have a WAS profile, web sphere portal server and ibm http server in my local machine which is running windows xp. All these are configured to run as windows service , now when i attempt to start the portal server i get below message:
WASService running at the same time for 'IBMWAS70Service -WebSphere_Portal_V$AIN' Service not started
Any input on this will be appreciated.
I restarted my machine and things worked fine :). Mostly likely there was some services created in windows services with same name or something of that sought which was rectified once i restarted my machine.
Related
I have Informatica 9.5 installed on a Windows 2008 server. I've recently had to restart the Informatica Service because I was unable to connect to the Informatica Integration Service. As a result of restarting the Informatica Service, the Admin Console does not come up. Sometimes, it hangs or I'll get, "The site can't be reached" error. I've tried going to the site on the server where Informatica application runs, and my pc. I get the same behavior on both machines. Also, on the server, I've tried http://localhost:port/administrator. Same behavior. Before restarting the Informatica Service, the Admin Console came up. Is there a service that did not start?
I have a IBM WebSphere 8.5.5.13 ND on Windows 2016 standard edition with JDK 1.7 enabled. I see that, node agent and server1 (application server) are getting stopped everyday but the deployment manager is still up and running (i.e. admin console can be accessed). So, I have to start nodeagent and the associated server manually everyday. Investigation done so far
Checked if the windows servers are getting restarted everyday? No they are not
Checked nodeagent start and stop server logs but there are no entries to see, some command was issued for stopping
Checked application server profile (server1) logs but nothing is there.
FYI, I don't have clustering done on WAS but it is planned for the future.
I don't no where else I can look for the reason the node agent and server1 is getting stopped everyday.
okay, this is what I found out. In my case I have
Dmgr01 - registered under windows service
Node agent - not registered under windows service
application server - no need or never register application server if you have deployment manager
Since my node agent was not registered under windows service, whenever I log-off or my session is killed due to in-activity, the default behavior is that, all running processes (jave.exe) associated with WebSphere will be crashed and there will not be any trace of it. This is why, I was unable to find the any logs.
I registered my node agent as windows service and everything worked.
I'm using windows 7, eclipse neon.3, liberty server 17.0.0.1, WebSphere® Application Server Liberty Tools 2016.0.0.v20170505_1729
I have a probem when starting the liberty server from eclipse. The server is actually starting fine, but eclipse is just showing the 'Starting'- status and never get confirmation that the server is actually started. After the predefined timeout, eclipse is giving up and stops the server.
If I start the server from command line, everythings works fine and eclipse confirmed that the server is running. Have tried both ibm sdk 8 and oracle.
What is actually the WDT (or eclipse) using for determing the server is started or not ?
WDT is looking for this message from the server: CWWKF0011I: The server is ready to run a smarter planet.
Please check the following link to make sure you have not changed something in the server configuration that is causing the tools to miss the message:
https://www.ibm.com/support/knowledgecenter/en/SSAW57_liberty/com.ibm.websphere.wlp.nd.multiplatform.doc/ae/r_limitations.html
I have TeamCity installed on a Windows Server 2012 machine. I installed teamCity default installation as service.
Later I added the Application Role and Web Server Role features to the Windows Server.
Now I can't access TeamCity's web interface (I got 404 error) although the TeamCity Server service is running, and the agents' service are running too.
Any ideas/directions on troubleshooting this ?
Credit to Ebeid Soliman El Sayed:
Ensure the following services are disabled as they conflict with port 80:
IIS / SQL Server Reporting Services (ReportServer)
Web Deployment Agent Service (MsDepSvc)
BranchCache (PeerDistSvc)
Sync Share Service (SyncShareSvc)
World Wide Web Publishing Service (W3SVC)
Internet Information Server (WAS, IISADMIN)
We install liferay6.2 in windows dedicated server 2008 r2. Liferay sever is working smoothly in the server but when we are trying to access it from browser then we are unable to access it. Error: server not found. In Liferay we have one portlet for video conference and it is also working fine. We can access the server through RDP(Remote Desktop) but whenever trying to access through browser fail to find the server in web.
May be this issue can be easily handle by the network admin or may be by any Liferay developer.
Does your dedicated server have a public (routed) IP address? Also, check firewalls that might block port 8080 if you have not changed the default port. As you say Liferay is running smoothly - you just can't access it - your problem is most likely rather related to the network configuration, not to Liferay itself