Weblogic Console not coming to login page - weblogic-10.x

When I try to launch the weblogic console page in my browser after starting weblogic using command prompt, the login page isn't coming up for a long time.
I see the "Deploying application for /console" message followed by a long sequence of "." (dot/period). This is going on for a long time.
I observed this message printed on the command prompt from where I launched the startWebLogic.cmd file
<Warning> <Socket> <BEA-000449> <Closing socket as
no data read from it during the configured idle timeout of 5 secs>"
Is this the reason for the console not coming up? If yes, how to resolve it?

If the console app is deploying extremely slow, you can change to following setting:
Login to the WebLogic admin console
Click your domain name link on the left hand side
Open Configuration tab and General sub-tab
Uncheck the box labeled Enable on-demand deployment of internal applications
Save
Activate changes

Related

Disabling the admin port without using Weblogic console

I enabled the 'admin port' in the WebLogic Admin Console and now can't get back into the console to change it since I can't start the server.
When I try to start the server, I get this message in Eclipse:
[Stopped, User'principals=[weblogic, Administrators]' has administration role. All tasks by administrator administrators must go through an Administration Port.
When trying to access the console via browser, I get this message:
Console/Management requests or requests with specified to 'true' can >only be made through an administration channel.
This previous solution to this problem suggested modifying the <administration-port-enabled> element in the DOMAIN-HOME\config directory, but this element does not exist in my config.xml. Should I add it?
I have tried creating a new workspace and a new domain, but the problem persists.
Is there another way to disable the 'admin port' without using the WebLogic Admin Console or editing the config.xml file?
MW_HOME/oracle_common/common/bin
./wlst.sh
connect()
And Navigate to AdminServer and find the required Mbean
If not possible to connect, try with Offline Mode.

Websphere admin console restart

Recently I ecountered situation where my WebSphere's admin console stop responding (tired to open it and got timeout). It happened after I've made some changes and saved them.
All the WebSphere application server and nodeAgent was working (checked in serverStatus.sh -all). I could still access my Web Application.
Is there a way to restart just admin console with a script or do I have to restart everything?
In my case the WebSphere works on linux.
I found a solution if someone will be interested. My dmgr process couldn't stop so I have to kill it manualy. Then I had to run startManager.sh script in IBM websphere dmgr location. It's done without restart the whole server.

IIS w3svc error

I am trying to start my website in IIS, whenever I try to start my website I get the following error
Cannot start service w3svc on computer
I tried to start "World wide web publishing service", but I was unable to start it as it said:
Error 1068: The dependency service or group failed to start
Meanwhile when I checked my log I found this error,
The World Wide Web Publishing Service service depends on the HTTP service which failed to start because of the following error:
The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.
Please help me, I am badly caught with this error, I have spent a week researching this error but haven't found a solution yet.
Confirm that "Windows Management Instrumentation" is started and its start up type is set to automatic.
Also make sure the following dependency services are started for World Wide Web Publishing Service:
Windows Process Activation Service
Remote Procedure Call (RPC)
DCOM Server Process Launcher
RPC Endpoint Mapper.
Open regedit, navigate to [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\HTTP]:
a) Double click on Start and change value data from 4(disabled) to 3(automatically).
b) Delete "NoRun" key if this key exists.
(warning: backup any IIS website configuration first). UN-install "Internet information Service" and "Windows process activation service(if it is already installed)" from "Turn windows feature on or off" and Restart your PC.
Type the below command in CMD and press enter:
net start http
Now it will notify you that service is already running.
Re-install Internet information Service from "Turn windows feature on or off".
Start IIS and my websites are started now, no more "w3svc service is not running error."
As for me - I just restarted the computer.
Make sure these 2 services running and their startup type is automatic.If they disabled and not running right click on them and go to properties and change from there.
Windows process activation service
Worldwide web publishing service.
Run cmd as administrator. Type iisreset. That's it.
Go to Task Manager --> Processes and manually stop the W3SVC process. After doing this the process should start normally when restarting IIS
In my case it was C:\Windows\System32\inetsrv\config\applicationHost.config which had an issue.
I had a "system.web" section in this file which was causing the problem. Removed the section and everything started working
I have got same issue on my server. Follow below steps -
Open command prompt (run as administrator)
type IISReset and enter.
It works and solved my problem.
I have had this problem after a windows update. Windows Process Activation Service is dependent service for W3SVC. First, make sure that Windows Process Activation Service is running. In my case, it was not running and when I tried to run it manually, I got below error.
Windows Process Activation Service Error 2: The system cannot find the file specified
The issue seems to be, that windows adds an incorrect parameter to the WAS service startup parameters. I fixed the issue using the following steps:
Start regedit (just type it into start) Navigate to
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\WAS\Parameters
Delete the NanoSetup variable. This variable is preventing WAS from starting
Start the WAS service using task manager
Now start the W3SVC service
You can now start your website in IIS again
I found above WPA service solution in this stack overflow thread.
In my case, IIS suddenly stopped working, and after that Windows process activation service was unable to restart.
The solution to fix this was:
Find WAS service in the services tab of windows task manager
In context menu choose Go to process
Kill process (its name will be svchost.exe)
Restart Windows process activation service
My Net.Tcp Port Sharing Service was disabled. I changed its startup to manual, started the service, and then IISRESET worked.
I also verified that the following dependent services were started in Services ([windows]+[r] services.msc):
World Wide Web Publishing Service
Windows Process Activation Service
Remote Procedure Call (RPC)
DCOM Server Process Launcher
RPC Endpoint Mapper
Net.Msmq Listener Adapter
Net.Pipe Listener Adapter
Net.Tcp Listener Adapter
Net.Tcp Port Sharing Service
I found this solution by going through all dependencies and child dependencies of the World Wide Web Publishing Service and making sure that each service was enabled and started.
To verify all services for yourself, do the following:
Open up Services (just search for it from the start menu in Windows 10)
Find the World Wide Web Publishing Service
Right click on the service and then click "Properties"
Click on the Dependencies tab
Go through each system component in the two boxes and verify that each service is started (in Services).
Repeat steps 3-5 for each of the dependencies' dependencies until you run out of child dependencies
Service Properties - Dependencies Tab
This is probably a rarer case, but...
If you are using a custom AppPool Identity configuration be sure to check the AppPool is running. It may be turned off because credentials are invalid (usually due to an expired password). Update your credentials and start the AppPool.
I am able to resolve this by simply executing the below command in PowerShell to kill/stop service and restart the IIS server
taskkill /F /FI "SERVICES eq w3svc"
I managed to solve after:
Ctrl+Shift+Esc = To open Task Manager
In the "Processes" tab locate the "IIS Worker Process" and
finish it!
Run on cmd as an administrator. Type iisreset.
I was getting this error. It turns out World Wide Web Publishing Service was disabled.
Click Start, type Services in the Search box, and then click Services.
Scroll until you find the World Wide Web Publishing Service that is stopped or disabled.
right-click the service, and then click Properties.
Click the Startup type list, and then click Automatic.
Click Apply, and then click OK.

how to connect to WebSphere 7 admin console, or how to view error logs if it's not starting?

I have IBM RAD / WebSphere 7 installed locally. My web application I'm developing runs fine.
I'm trying to log into the WAS admin console.
In the "Servers" view, I right-click the server > Administration > Run Administration Console ... but I get a "webpage cannot be found" error page.
In Firefox, I attempt to browse to the admin console URL, I tried each of the following but no luck:
http://localhost:9091/ibm/console/logon.jsp
http://localhost:9091/ibm/console/
http://localhost:9060/ibm/console/
http://localhost:9060/admin
Any ideas what the URL is?
Or, alternately, if the admin console is not starting due to some error, is there a log file somewhere where I can find the error?
Any help is greatly appreciated!
Rob
The third of those would normally be the correct one, but the port number depends on what happened during the profile creation process. Find the profile directory and then look in the properties directory for the portdefs.props file. That will tell you what the correct port number should be.
It is possible to create a profile without the admin console application, in which case it will obviously never work. You could also try running wsadmin from the profile bin directory to see whether you can connect to the admin service that way.
Any errors from the admin console application will be reported in the normal log files in the profiles/profilename/logs/servername directory.

How an application can start its own service after it closes in Delphi?

I have an application that the user can start in two different ways, as a normal application or as a Windows service. When the service is already running (there's a icon of it in the system tray) and the user tries to start the application (not just open by clicking on the tray icon, but start again clicking in Start>Applications>Blah blah), it says: "The application is already running as a Service, do you want to close the service and start the App?" When the user clicks 'Yes' the application closes the service and starts itself as a normal application.
When that occurs I put a flag indicating that the user had once stopped the service and when they close the application the software sees the flag and the service has to start running again, because it was closed before to start as a normal app.
I tried to put:
WinExec(PChar('NET START MyApplicationName'),SW_shownormal);
in the OnClose event, before this line:
ExitProcess(0);
but it says that the service is already running and closes the application without starting the service, and if I put it after that line it doesn't do anything at all.
Is there any way to do this?
When I put the line before the ExitProcess(0); it opens a cmd window with the message:
"The service is not responding to the control function"
then it closes the application, closes the cmd window and it doesn't start the service.
In my view you are over-complicating the problem. Starting and stopping services is a complicated action and indeed it is forbidden by default for non-admin users. This very fact will make your application very annoying to use. You will limit its use to admin users, and also pepper them with UAC dialogs. Nobody likes apps like that.
The alternative is to simply leave your service running the whole time, but make it inactive whilst the standard desktop app is running. When the desktop app starts it strikes up communication with the service using some form of IPC and asks the service to stop work. The service does this and then the desktop app proceeds. When the desktop app closes, the service is asked to resume work. You would want to keep a communication channel open the whole time to guard against the desktop app terminating abnormally – if that happened the service would simply start up again.
Now, if you really wanted to do a good job you could let all the processing of work always happen in the service. The desktop app would merely be a front end for the service. That would seem to me to be the most efficient and logical design for this app.
Write a simple Batch file like that
#ECHO OFF
ping 1.1.1.1 -n 1 -w 10000 > NUL
NET START MyApplicationName
Then run execute this batch file before close your program.
ShellExecute(0, 'Open', YourBatchFile, nil, nil, SW_HIDE)

Resources