Hi,
I facing problem while installing WmEnterprise Sever 4.1 on Win2000 machine which is connected to our company network. On stand-alone machine it is working fine but when you give host name as
domain-name/machine-name it is saying
“AdapterMonitor is not running…and all”
On examing we found that Win2000 Service Pack 2
might have giving problem but after updating machine to Service Pack 3 also the problem persitss.

In log following details are entered.

####################

STARTING INSTALL

####################
Opening service DLL
Loading C:\webMethodsEnterprise\windows\domestic\aisvc10.dll
Checking if SC Database is locked
Is Database locked ? 0 (No Error)
Looking for installed brokers

Running external command C:\webMethodsEnterprise\windows\domestic\runprog.exe C:\webMethodsEnterprise\windows\domestic\brokconf.exe -f C:\WINNT\TEMP_ISTMP2.DIR\comout.log -e AW_C_LOCALE -v TRUE -a list, output:

Warning: Cannot make a connection to the Enterprise server monitor on “domainname-machinename”:
Broker Not Running
(101-1020): The host ‘domainname-machinename’ was found, but no Enterprise Server is running on port 6850 on that host.
Warning: Could not contact Enterprise server monitor for list of Enterprise servers.
Listing local configuration:
Error: Could not read Enterprise server monitor configuration file “C:\WINNT\activesw\awbrokermon.cfg”: No such file or directory
User entered install key(s): ####### (Key is their which is removed from this place for the purpose of privacy )
User entered in 1 distinct keys
Key:####### (Key is their which is removed from this place for the purpose of privacy )
Regular install keys:####### (Key is their which is removed from this place for the purpose of privacy )

Running external command C:webMethodsEnterprise\windows\domestic\runprog.exe C:webMethodsEnterprise\windows\domestic\chkinst.exe -f C:\WINNT\TEMP_ISTMP2.DIR\comout.log -a -f C:\WINNT\TEMP_ISTMP2.DIR\chkinst.dat AHZK839 , output:

…
…

Can anyone please put suggest what might be the problem.

Regards
Hari

Windows 2000 SP3 changed some internal security mechanisms - and this causes the Broker Server (ver 4.x) to not start.

This was fixed in SP17 - http://advantage.webmethods.com/servicepacks/svc_pack-20021106-172836/BrokerCore_4-1-1_SP17_WIN.txt
Apply this service pack and see how it goes.

We’re running a Enterprise broker 4.1.1 (with Service Pack 17) on Windows 2000 system with Service Pack 3 (for Windows).
Broker starts up fine. However, we can’t get SSL security enabled on the system. Certificates were re-generated, but it didn’t make any difference. Is there a fix for this?

thanks.
jelena