T23:06:33.619Z - : Updated file-hasher based on watched changes, recomputing project graph. T23:06:33.319Z - : js/ts-packages/create-ts-app/bin/create-ts-app was modified T22:54:57.710Z - Error detected when recomputing project file map: ENOENT: no such file or directory, open Daemon Server] - T22:55:01.667Z - Time taken for 'init hashing' 3956.459025ms T22:54:54.560Z - Error detected when recomputing project file map: ENOENT: no such file or directory, open Daemon Server] - T22:54:57.389Z - : 1 file(s) created or restored, 0 file(s) modified, 1 file(s) deleted In order to associate localhost with your WebLogic AdminServer using port 7001 again, you will need to restart the AdminServer.Īfter applying the steps above, you should be able to use the localhost address with your WebLogic server environment running port 7001.- T22:54:54.560Z - Time taken for 'incremental hashing' 0.008351ms Now that the service has been restarted, the agent will no longer be using port 7001. Restart the service so the port number changes from 7001 to the port number you set.Ħ.
Nomachine server not running windows#
Open up the Windows Services and locate the service “NoMachine Display Monitor”.
NOTE: Make sure the value is NOT commented!ĥ. In this example, I changed the DisplayBase to 2001 (DisplayBase + 6000 = the port number used for the NX Agent) so that the NX Agent uses port 8001, a port which nothing with WebLogic will use. Set the number to a value which does not conflict with other running ports. Locate the parameter DisplayBase (may be commented out initially). Open the file server.cfg using a text editor (NOTE: Make a backup first!).ģ. Go to the file directory where NoMachine is installed (in Windows, it should be C:\Program Files (x86)\NoMachine by default) and go into the etc folder.Ģ. To fix this problem, you can change the port which NoMachine uses for the NX Agent using these steps below:ġ.
NOTE: Although the AdminServer starts up successfully, it is not possible to run anything with port 7001 for anything WebLogic-related using the localhost address (using your actual hostname instead of localhost works fine however):
Port conflict exists due to NoMachine agent using port 7001 on localhost:
As the agent is using port 7001, it can potentially cause a conflict with the AdminServer for any WebLogic environments using port 7001 primarily if using localhost to access the WebLogic Admin Console or anything WebLogic-related running on port 7001.Įrror in starting the AdminServer using port 7001: By default, the NX Agent will use port 7001 (the value of the DisplayBase set for NoMachine + 6000) running on localhost. NoMachine is a great example of a remote desktop client which can be used to connect from a Windows, Mac, or Linux box to another Windows, Mac, or Linux machine which has NoMachine also installed. There are many remote desktop applications available in the Internet.
0 kommentar(er)
