login vsi company logo login vsi company logo 250x40
header-01.jpg

Log on time too long - Login VSI Fatal error

  • mulcas
  • mulcas's Avatar Topic Author
02 Feb 2016 08:40 #2700 by mulcas
Login VSI Version: 4.1.4
Test system: VMware view
Operating system version target: Windows 8.1
Operating system version launcher(s): Server 2012 R2
Office version target: Office 2010

Hello Support Team,

I am having the following issue:

Horizon View Client takes more than 70 sec to log on, plus 60 sec more during the OS preparation where the session become active (It can be notice from the management console) and when the OS is ready, Login VSI had already started but it doesn’t execute the scrip, about after 2 minutes, it shows:
VSI Timer: Timeout reached Pressing file open. Login VSI will stop executing.

I was running a 25 desktops test, the session only became truly active for 5 desktops, the rest all expose the error message mentioned. If I access directly via Horizon View Client, the log on time is only 6 sec.

I have checked already documentation related to Horizon View and GPO and everything seems fine, I created the users on the domain using the PS1 file from the management console so I believe all the policies are right.

Seems this is similar/same issue, but I don't see any solution.
www.loginvsi.com/forum/login-vsi-v4/876-...s-long-time-to-login

Please advise.
Mulcas
Attachments:

Please Log in to join the conversation.

More
02 Feb 2016 10:19 #2701 by j.volkers
Hello Mulcas,

Sorry to here that, to help you further can you provide us with the following information?

* How long is the launch window you have setup?
* How many launchers do you have configured?
* Do you run into this issue if you just launch like 3 session with Login VSI?
* Could you send us your log file from this test? (to support@loginvsi.com)

Please Log in to join the conversation.

  • mulcas
  • mulcas's Avatar Topic Author
03 Feb 2016 01:51 #2702 by mulcas
Hello Jordi,

Thanks for your reply.

* How long is the launch window you have setup?
Default, 2880.

* How many launchers do you have configured?
For this specific test only one. I had tired with 4 before.

* Do you run into this issue if you just launch like 3 session with Login VSI?
No, I will check this.

I running a different test now using RDP connection, I deleted the all the VMs, so I will try again and update.

Thank you!
Mulcas

Please Log in to join the conversation.

  • mulcas
  • mulcas's Avatar Topic Author
05 Feb 2016 10:01 #2703 by mulcas
Hi Jordi,

This issue seems because of storage latency.

After running another test with 100 VMs, it was OK, but the in the results from the analyzer shows that all (the 100 VMs) were stuck, but I never saw that, all the VMs were logged off successfully without error messages on the sessions. What could be the reason for this kind of result?

Thanks,
Juan

Please Log in to join the conversation.

More
05 Feb 2016 12:47 #2704 by j.volkers
Hello Mulcas,

If you have enabled the engine debugging settings you should have error screenshots in the log files folder.

If not, you can Enable engine debugging and workload debugging in the management console under settings and then run the test again. This will give you error screenshots and additional log files in the log files folder.

If you can't figure out what happened we can help you troubleshoot the issue if you will send us the logfiles.

Please Log in to join the conversation.

Start Delivering the Best End User Experience Today

Request a Demo

Login VSI, Inc.

3945 Freedom Circle
Suite 670
Santa Clara, CA 95054

Phone: +1 408 899 7418

300 Tradecenter
Suite 3460
Woburn, MA 01801

Phone: +1 408 899 7418

Login VSI B.V.

De Entree 85
1101 BH Amsterdam
The Netherlands

Phone: +31 20 705 1200