Running TEM 8.1.617.0. Installed for Software Use Analysis V1.3.1 successfully as userid Administrator with:
Use NT authentication with user Administrator
http port 9080
…
The database BFInventory was successfully created with running of the configuration.
Service SQL Server Browser is started in addition to SQL Server. Also see services BigFix DSS Backend 0 to BigFix DSS Backend 5, BigFixDSSApache, BES Web Reports Server started. TEM Server Diagnostics Tool tests all pass.
…
Internet browser on TEM server with web URL http://localhost:9080 does show Tivoli Endpoint Manager for Software Usage Analysis and then fails with:
Connection failed. Connecting with the server has failed. Please check your network connection.
…
See Windows System event log message of:
The following fatal alert was generated: 10. The internal error state is 10.
with event 36888 and source of Schannel
…
http://localhost:8080 with the same IE 8 web browser on the same TEM server for the TEM Analytics works successfully for Security Compliance reporting.
…
Are there any further post installation steps to get Software Use Analysis V1.3.1 working with the web browser?
For event 36888 and source of Schannel from searching, turned off TLS and also SSL in IE8 advanced options. Turned off Windows firewall and set IE8 security and privacy to low. Rebooted TEMS Window 2008 R2 SP1 server.
…
Netstat -a -n -o shows:
Proto Local Address Foreign Address State PID
TCP 0.0.0.0:9080 0.0.0.0:0 LISTENING 1652
PID 1652 is only process using port 9080 which is httpd.exe for Apache HTTP Server.
nmap test below
nmap -sT localhost -P0 -p T:9080
Nmap scan report for localhost (127.0.0.1)
Host is up (0.00s latency).
rDNS record for 127.0.0.1: localhost.127.in-addr.arpa
PORT STATE SERVICE
9080/tcp open glrpc
Nmap done: 1 IP address (1 host up) scanned in 0.34 seconds
…
Do not see any error messsages in mongrel.log, development.log
Apache HTTP Server error.log at startup has:
Mon Aug 01 09:10:49 2011
notice
Child 1900: Starting thread to listen on port 9080.
Try restarting all the BigFix DSS services. It is typical for TEM-SUA to be unavailable after server restart until all the services have been restarted. At least, that’s been my professional experience.
This behavior occurs on both virtual and physical systems after a restart has occurred. I ended up using a vb script and scheduled task to manage this rather than manually restarting services. This solution has worked sufficiently.
All the VB script would do is automate restarting the 7 DSS services. Something like this:
Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
Set colListOfServices = objWMIService.ExecQuery ("Select * from Win32_Service Where Name like 'BigFix DSS Backend%' OR name = 'BigFixDSSApache'")
For Each objService in colListOfServices
objservice.stopservice()
Next
do until vFlag = 1
Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
Set colListOfServices = objWMIService.ExecQuery ("Select * from Win32_Service Where name = 'BigFixDSSApache'")
For Each objService in colListOfServices
If objservice.state = "Stopped" Then
vflag = 1
End if
Next
loop
wscript.sleep(2000)
Set objWMIService = GetObject("winmgmts:{impersonationLevel=impersonate}!\\.\root\cimv2")
Set colListOfServices = objWMIService.ExecQuery ("Select * from Win32_Service Where Name like 'BigFix DSS Backend%' OR name = 'BigFixDSSApache'")
For Each objService in colListOfServices
objservice.startservice()
Next