NW Compostion Environment 7.1 Trial Issue

[Former Member]

Hi,

I just recently download NW Composition Environment 7.1 and managed to install it in a VMWare machine. There were no errors in the installation but the WebAS is not switching on. The database instance is on but if I try to start the WebAS through the MMC, it just turns yellow for a minute or so and then goes back to grey (offline). This is a fresh installation on WinXP SP2 in VMWare 6 virtual machine. Odd part is that when the installation first finished the WebAS instance was on and I was able to link NWDS to it. But somehow by the time I ran the first sample app, WebAS was offline again. I repeated the install on another WinXP machine and the same problem happened.

Please help.

Regards,

Adeel Hashmi

[Former Member · Accepted solution]

There is no file named dev_disp in the work directory. I could find dev_jstart with the following error message

-

---

trc file: "dev_jstart", trc level: 1, release: "710"

-

---

*

• ACTIVE TRACE LEVEL 1

• ACTIVE TRACE COMPONENTS All, egi

*

F [Thr 2144] *** LOG => connected to Enqueue Server.

F [Thr 2144] *** WARNING => SfCMsClient::doAttach: Operation MS_CHANGE_IP failed (rc = 24 MSOP_EINVAL) [sfxxmsc.hpp 869]

F

F [Thr 2144] Fri Feb 19 00:30:42 2021

F [Thr 2144] *** WARNING => SfCMsClient::doAttach: Operation MS_CHANGE_IP failed (rc = 24 MSOP_EINVAL) [sfxxmsc.hpp 869]

F

F [Thr 2144] Fri Feb 19 00:30:47 2021

F [Thr 2144] *** WARNING => SfCMsClient::doAttach: Operation MS_CHANGE_IP failed (rc = 24 MSOP_EINVAL) [sfxxmsc.hpp 869]

F

F [Thr 2144] Fri Feb 19 00:30:52 2021

F [Thr 2144] *** WARNING => SfCMsClient::doAttach: Operation MS_CHANGE_IP failed (rc = 24 MSOP_EINVAL) [sfxxmsc.hpp 869]

F

F [Thr 2144] Fri Feb 19 00:30:57 2021

F [Thr 2144] *** WARNING => SfCMsClient::doAttach: Operation MS_CHANGE_IP failed (rc = 24 MSOP_EINVAL) [sfxxmsc.hpp 869]

F

F [Thr 2144] Fri Feb 19 00:31:02 2021

F [Thr 2144] *** WARNING => SfCMsClient::doAttach: Operation MS_CHANGE_IP failed (rc = 24 MSOP_EINVAL) [sfxxmsc.hpp 869]

F

F [Thr 2144] Fri Feb 19 00:31:07 2021

F [Thr 2144] *** WARNING => SfCMsClient::doAttach: Operation MS_CHANGE_IP failed (rc = 24 MSOP_EINVAL) [sfxxmsc.hpp 869]

F

F [Thr 2144] Fri Feb 19 00:31:12 2021

F [Thr 2144] *** WARNING => SfCMsClient::doAttach: Operation MS_CHANGE_IP failed (rc = 24 MSOP_EINVAL) [sfxxmsc.hpp 869]

F

F [Thr 2144] Fri Feb 19 00:31:17 2021

F [Thr 2144] *** WARNING => SfCMsClient::doAttach: Operation MS_CHANGE_IP failed (rc = 24 MSOP_EINVAL) [sfxxmsc.hpp 869]

F

F [Thr 2144] Fri Feb 19 00:31:22 2021

F [Thr 2144] *** WARNING => SfCMsClient::doAttach: Operation MS_CHANGE_IP failed (rc = 24 MSOP_EINVAL) [sfxxmsc.hpp 869]

F

F [Thr 2144] Fri Feb 19 00:31:27 2021

F [Thr 2144] *** WARNING => SfCMsClient::doAttach: Operation MS_CHANGE_IP failed (rc = 24 MSOP_EINVAL) [sfxxmsc.hpp 869]

F

F [Thr 2144] Fri Feb 19 00:31:32 2021

F [Thr 2144] *** WARNING => SfCMsClient::doAttach: Operation MS_CHANGE_IP failed (rc = 24 MSOP_EINVAL) [sfxxmsc.hpp 869]

F

F [Thr 2144] Fri Feb 19 00:31:37 2021

F [Thr 2144] *** ERROR => cannot connect to Message Server. [sfxxmsc.hpp 742]

F [Thr 2144] *** LOG => connecting to Message Server.

F [Thr 2144] *** LOG => Run level 0 completed.

F [Thr 2144] *** LOG => Instance state is "Instance terminated" (STOPPED @ 0, INACTIVE).

F [Thr 2144] *** LOG => exiting (exitcode 0, retcode 0).

[peter_dzurov · Accepted solution]

do you have firewall or anti virus sw running? Turn it off and try again.

[Former Member · Accepted solution]

Sorry. The darn WebAS server refuses to start. No change although I have turned off the firewall now.

Regards,

Adeel

[peter_dzurov · Accepted solution]

What about antivirus?

[Former Member · Accepted solution]

Have you checked TNS LIstener and also try to solve this by adding host entry in hosts file C:\WINDOWS\system32\drivers\etc\hosts

e.g. 172.31.1.40 dev.meezan.com

if your are working on standalone machine plz your system network loopback connector is working or network is working.

[peter_dzurov]

Hi, it is not possible to help you until you post at least some logs. You could start up with dev_disp from work directory.