When trying to log into Strategy Web having the option "Log in, then show the projects accessible by the supplied login" set in Strategy Web Admin preferences, users might notice an slightly longer log in times to those compare when having "Show all the projects connected to the Web Server before the user logs in".
CAUSE:
When the option to log in first then display all projects is used for the project page, Strategy Web creates an internal Intelligence Server session, to retrieve the project list the user has access to, that we close immediately. This session has a distinguishing characteristic, it shows up in the IS_SESSION_STATS table in the Enterprise Manager Statistics Datawarehouse with the "client machine" field logged as "tempclient", so we can easily filter it out for the needs of Enterprise Manager reporting.
Since this is just a call to get the projects and the user has still not picked a project to login in, this session is not really a session that we want to keep track of in the Enterprise Manager statistics. To have an accurate count of actual user session activity, these sessions were tagged as tempclient so that they can be filtered out.
During the communication between the Intelligence Server and Strategy Web, there is a DNS Lookup based on the clientID. This lookup is typically very fast, the web server machine will try to resolve the IP address of the machine name "tempclient" which does not exist in the Network and normally the DNS server will return a "machine does not exist" response immediately, however Strategy Technical support has seen in some customer environments that it is taking a very long time to resolve this "tempclient" machine name on the customer's network.
The delay in the log in process is caused by this trying to resolve the IP address of for a non existent machine name tempclient.
ACTION:
To resolve the DNS tempclient machine ID lookup delay, the hosts file of the web server machine can be modified as follows:
Add an entry to the host file in the web server machine located under:
Windows NT, 2000, XP, 2003, Vista, 7 %SystemRoot%\system32\drivers\etc\
Most Unix and Unix-like OSes /etc/hosts
Enter:
127.0.0.1 tempclient
This way the web server machine will resolve the tempclient machine name to the IP address 127.0.0.1 and will not require a DNS lookup resolving the delay issue.
KB05511
