Login failed (401) Internal error: Horizon Service call GetApplications failed

[freythman]

One of my users forwarded me a screenshot of this error message in a bubble notification from the system tray application. I collected diagnostic info from their machine and found the following repeating several times in the Service.log file. (Username is redacted)

[2013-09-20 06:54:27] CAgentSettings::CAgentSettings: [INFO] Polling interval='3600'; localExpirationWindow='2592000'.

[2013-09-20 06:54:27] CAgentSettings::CAgentSettings: [INFO] Polling enabled='1'; shortcutLocation='+USERPROFILE\Desktop\VMware Horizon Applications'.

[2013-09-20 06:54:28] HorizonUserSession::GetApplications: [ERROR] [.\horizonClient.cpp:1866] HZNGetApplications failed, Error = 401 err=401

[2013-09-20 06:54:28] HorizonClient::updateAppsLeaseFromCloud: [ERROR] [.\horizonClient.cpp:232] Error getting Applications err=12124561

[2013-09-20 06:54:28] ThinAgentRefreshUser: [ERROR] [.\userleases.c:164] HorizonClient::updateAppsLeaseFromCloud('USERNAME') failed. err=12124561

[2013-09-20 06:54:28] RpcThinAgentRefreshUser: [ERROR] [.\rpcserv.c:620] (null) err=12124561

[2013-09-20 06:54:28] CAgentSettings::CAgentSettings: [INFO] Polling interval='3600'; localExpirationWindow='2592000'.

[2013-09-20 06:54:28] CAgentSettings::CAgentSettings: [INFO] Polling enabled='1'; shortcutLocation='+USERPROFILE\Desktop\VMware Horizon Applications'.

[2013-09-20 06:54:28] HorizonClient::updateAppsLeaseFromCloud: [INFO] (K) Retrieved 4 apps for user USERNAME

This has been happening since we upgrade to Workspace 1.5. I've attached a screenshot from the client, as well as the redacted Service.log file. I had to trim it down below 50mb, and remove the username and application names.

[Jag_S]

Hi,

Did you manage to resolve this error? If so could you please let me know how?

Thanks

[freythman]

No it has not been resolved. The error still occurs sporadically.

[Jag_S]

Doesn't this stop you from accessing the apps whilst it errors. If so do you have a work around on that?

Thanks.

[freythman]

It does stop while it errors. Unfortunately I don't have a work around. We're not using 1.5 in production, so this hasn't been a priority for us.