RE: fwk 4.1 - RESOLVED - maybe

When I said resolved - maybe a little hasty..

The Endpoint now seems to install ok - the code arrives and the service starts -
 lcfd.log on the proxy looks ok.
However, winstlcf errors that the endpoint does not login to the gateway so 
can't be configured.
When I check the last.cfg it doesn't contain the contents of my -g switch which 
is (myserver+29494) or the -L switch which includes a 
lcs.login_interfaces=myserver+29494/tcp option.  The gateway_port in last.cfg 
is set to the standard port of 9494 so it will never login in my environment.  
I also get stuck with an lcs.machine_name=myhost-29495, although I'd expect I 
could override that with the label switch on winstlcf?  The Endpoint port is 
correct though (29495) so it is getting some of the config from winstlcf.  I 
don't think it matters, but the proxy endpoint uses the same gateway and 
endpoint ports as the switches in winstlcf.

Is there a reason why the config isn't going down to the endpoint?  I'm not 
sure at which stage all of the config is supposed to be sent - by this I'm 
thinking back to the winstlcf error message saying the endpoint didn't login to 
the gateway so can't be configured - what config is it expecting to apply after 
login?


Many thanks

K


Quoting Karl Prinelle <Karl.Prinelle-k8DSj05WqF8qdlJmJB21zg@xxxxxxxxxxxxxxxx>:

> Sigh!
> 
> Ok, I cleaned it all up & got the logging working fine (thanks Gary -
> didn't realise it would log to the proxy) - still failed.
> 
> I then decided to re-install the proxy endpoint (on the tmr) & realised
> my error.  The TMR was running a 41100 Endpoint, but the TMR itself is
> fwk 4.1+fp1+lcf23.  Once I put the proxy endpoint version down to the
> same as the TMR lcf_bundle's, all is (just about) ok.  I noticed the
> lcs.machine_name got set to <hostname>-<epport>, but I think I can deal
> with that somehow.
> 
> The cause....?  Way back I had (unsolved) problems getting the customers
> server to work with the odbc connection to MS/SQL under 4.1.1 or
> 4.1+TMF40 (my machines all worked fine, but their hardened machines
> refused to go).  In the end I gave up & regressed (re-installed) the TMR
> down to 4.1 + patches.  Of course I forgot to re-install the lcfd, I
> just edited last.cfg - everything else worked fine so I never thought to
> change it.
> 
> Anyway, thanks again
> 
> K
> 
> 
> 
> -----Original Message-----
> From: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx 
> [mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx]
> On Behalf Of David M. Funk
> Sent: 28 April 2004 19:03
> To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
> Subject: RE: [tme10] fwk 4.1
> 
> 
> 
> Run "net user" to see if the user "tmersrvd" account has been removed
> Run "net localgroup" to see if group "Tivoli_Admin_Privileges" has been
> removed. Run "net start" to see if any lcfd services are running Tivoli
> Endpoint Tivoli Endpoint-1 If so, then run:
> net stop "Tivoli Endpoint"   And/or
> net stop "Tivoli Endpoint-1"
> To stop those services
> Check to see if c:\[winnt|windows]\system32\TivoliAP.dll has been
> removed. If not delete it then reboot server.
> 
> If everything is clean, then try to re-install
> 
> HTH,
> David M. Funk
> 
> 
> 
> -----Original Message-----
> From: owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx 
> [mailto:owner-tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx]
> On Behalf Of karl.prinelle-k8DSj05WqF8qdlJmJB21zg@xxxxxxxxxxxxxxxx
> Sent: Wednesday, April 28, 2004 12:29 PM
> To: tme10-XtjxT7Vmt5b1ENwx4SLHqw@xxxxxxxxxxxxxxxx
> Subject: [tme10] fwk 4.1
> 
> 
> Hi list,
> 
> fwk 4.1+FP1+41LCF23
> 
> I'm having a problem with winstlcf installing from a Windows 2000 TMR to
> either 
> an NT4 machine or a WinXP machine.  Both machines have previously been 
> endpoints in their respective TMR's (both TMRs are built the same & are
> w2k at 
> the above patch level), but have had the uninstaller ran on them, files
> deleted 
> and registry cleaned & rebooted.  
> 
> I run this;
> 
> perl %BINDIR%\bin\winstlcf -d "c:/program files/tivoli/lcf-uk" -g 
> <mytmr>+<mygwport> -L "lcs.login_interfaces=<mytmr>+<mygwport>/tcp 
> bcast_disable=1 address_notif_interval=21600 
> lcfd_alternate_port=<myaltepport>" -l <myepport> -D  -N <mytmr> -a -v -Y
> "host1 
> domain\account password"
> 
> I get this in response;
> 
> "<list of files>
> 
> Error creaing lcfd service. See lcfd.log
> ->
> Debug Log:
> 
> LCF Installed failed for the following macghines: (see lcfhost.err)
> host1"
> 
> I've checked the archives, docs & remaining brain cells & tried the
> following;
> - The files have arrived in the specified directory on the endpoint
> Oddly, there isn't a c:\[winnt|windows]\Tivoli directory created on the 
> endpoint.
> 
> - There is no last.cfg created
> 
> - The service has been created in the machine registry & "looks" ok.  If
> I run 
> winstlcf again it errors due to the files already being on disk - good
> this 
> means it can see the c$ share.  If I delete the files & re-run winstlcf
> then it 
> creates a new service lcfd-1 which is what I'd expect & seems to show it
> can 
> access the machine registry.
> 
> - A reboot doesn't help as then the lcfd service attempts to start &
> hangs.  At 
> one point the NT4 machine was complaining it couldn't find libguid60.dll
> but 
> that file isn't in the list displayed to be sent by winstlcf nor is it
> present 
> on the TMRs (it's now stopped generating that error for some reason!)
> 
> - I've checked that the machines have the C$ default share in place.
> 
> - I've checked the perl version is v 4
> 
> - There are no firewalls between the machines
> 
> - I've run wchkdb -ux, wep sync_gateways
> 
> - Irritatingly I've used this many times before at fwk 4.1 (but lower
> patch 
> levels) & it's worked fine.
> 
> 
> 
> Anyone got any ideas about what to look for next??
> 
> Thanks in advance
> 
> K
> 
> 
> 
> 
> 
> 
>