Advanced troubleshooting in SWS
Hallo guys and girls
Do any of you ppl have some information on troubleshootings, some guides on which logfiles are good to know and which aren't that relevant.
And perhaps in what situations you need to look in specific files.
The reason i ask is because i have 2 customers who are experiencing some problems.
Of course it would be ideal to contact customer support, but my problems are periodic which doesn't help much, and doing some digging on my own would also be very nice (before contacting them i mean).
1. problem is i from time to time experience authentication errors, there seem to be no good eplenation on why they appear but when they appear a logoff and logon again isn't enough to solve the problem, the cache on the client needs to be cleared and we once again need to logoff and on again.
In this setup we are running windows 7, with 2008 R2 as backend/frontend servers.
2. problem is i from time to time experience logon/logoff problems, this one may be a bit more trickier to find a solution.
This customer we have here are very thorough and have made a script which restarts the client, and have in the past done testing on logging on and off, and have never seen problems with it.
Now we installed sws, and the virtualization agent, and now we from time to time have clients which are hanging in the logon/logoff process.
We have about 30 virtual applications installed on the client at the moment.
In this setup we are using 2003 R2 and windows xp sp3.
in both environements we have 6.1 SP1 MR1 (or what it is it's called :P)
Kind Regards
Morten Leth
Comments
RE: Advanced Troubleshooting
Hello Morten,
There are various log files that we use to troubelshoot variety of issues. Each one of them has it's own use.
For instance:
So it is by nature of the issue we look into appropriate log files.
For issue 1, check if the customer uses LDAP authentication, make sure that all machines using SWS components can communicate to the LDAP server (ping to LDAP host an IP are simple tests). Also ensure that all the machines are in same domain and that "Enable Automatic Domain Authentication" (Streaming Console->Configuration->Launch Server->Basic) is checked. If this is not checked please check and restart the FE Services.
For issue 2, the slow logons/logoffs may be due n-variables: conflict with other apps on the base (Antivirus, hard drive integrity applications, compression software, application whitelisting softwares, VPN client, UPHClean.....e.t.c.). Please add more details of what applications are installed on the base. Also is there a business reason they scripted the restart?
The version you are referring is may be SWS_6_1_SP6_MP1. Please specify the build numbers (take a quick look in Control Panel).
Regards,
Balachandar.M
This is good information, can
This is good information, can you tell me where these log files are located?
Log files locations
For the client, the default log file location is "C:\_AC\Logs" usually MgrLog*.txt. The driver logs are in the same directory usually named KMLog_AppStream*.log.
The launchserver (Portal) logs are in "C:\Program Files\Symantec\Workspace Streaming\Server\launchserv\log" (not "[...]\logs").
The streaming server logs are in "C:\Program Files\Symantec\Workspace Streaming\Server\server\Logs". The AdministratorLog*.txt files are the audit logs for streaming session lifetime events, the log*.txt files are the error logs.
The streamlet engine logs are in "C:\Program Files\Symantec\Workspace Streaming\Server\streamletEngine\dci\log". With standalone DA's look in "[...]\da\log".
The management agent logs (server component for controlling the servers, not the client!) are in "C:\Program Files\Symantec\Workspace Streaming\Server\agent\log".
The Streaming Console logs are in "C:\Program Files\Symantec\Workspace Streaming\Server\console\log". The audit log of who issued server control commands, changed provisions, uploaded packages, etc. is in audit.log, the error log is console.log.
Nice feedback
Hallo balachandar
Thank you for that nice feedback, it gave me the quick overview i just need over the logfiles and their content.
I was referring to SWS_6_1_SP6_MP1, and i just finished upgrading the customer to SP7, since i have heard that the logon issues perhaps are fixed in the new release of the SVS agent.
Actually the reason they made the script in the first place was due to the fact they had a complaint stating there was logon issues (not releated to this in any way, this was before we introduced sws) and they wanted to prove that there was no issue with logon. So they made a script which was put into "start" of the users profile, which did after 2 minuts restarted the computer.
If the computer where to hang a some point, they where correct in assuming there was a problem, but it never did, it did over 200 logon/restarts in a row and they stopped the script, (of course there was a problem but it was only related to 3 profiles or so).
That means that before we started this we actually did have a baseline, and now we can only do about 30 logons, and at some point the computer will hang on logon, removing the sws client means we go back to things not hanging again.
I have now created a support call on the problem nr. 2, problem nr. 1 is still under investigation by my collegue, and i think we will start by upgrading this customer to the latest release too.
If we find out things are still hanging i will write to the support and let them know which applications are in the base os.
Kind Regards
Morten Leth
Thanks
Hello Morten,
Thanks for writing.
To verify if there are further logon issues (in case caused byour agents), the first thing to try is to isolate by doing a single agent install.
So what can be tested is install a standalone instance of SWV and add all virtual layers that they have used for testing. Set the "Activate at startup" on each layer one at a time and keep doing logon/log off and restarts as needed and check for locked logons. If the problem recurs with a certain layer active you might have found the solution.
As an additional step try creating an empty layer and set activate at startup and test logoff/logons and see if you can reproduce the issue. Compare and contrast the results between SWV_6_1_SP6_MP1 and SP7 and let us know.
Regards,
Balachandar.M
Would you like to reply?
Login or Register to post your comment.