Error 500 when attaching package.

[mmaus]

I have setup my first app to try and install Notepad++ on a test machine.  I am not 100% sure I have done this correctly, but everything looks to be right to me.

I setup the application, installed the package in my provision vm, everything said successful.  I have set my package to current and have assigned it to my test account.

When I login to the account...I get the following error.

I researched this and start giving me KB articles about AD issues.  I looked at the time sync, permissions, connectivity, deleted the clone and had it rebuild and I dont believe this is an AD issue.  I did find something interesting in my testing though...  If the package is assigned...I get the 500 error...as soon as I unassigned it...the error goes away.  I tested this on two different test accounts on two different laptops and got the same results. 

Am I missing a setup in my package creation or is this something else?

[vBritinUSA]

When you captured the package did you use a local account or Domain account? I've had an issue with capturing software using a local account and not work, but the domain account works. Just make sure the account you use doesn't have any assignments.

[mmaus]

I did originally create the package with a local account.  I recreated the package using a domain admin account and am getting the same results.  Assigned = 500 error.  Unassign = Error gone.

[vBritinUSA]

Is the cert you have on the AppVolumes Manager trusted?

Is it just this application or does something simple like Firefox work?

I created this Blog on Packaging when 4 came out, just for a sanity check welcome to check.

https://www.vbrit.net/appvolumes/appvolumes-4-packages​

Also, AppVolumes 4.1 is out but I didn't see anything in the release notes

[vBritinUSA]

Meant to ask do the logs show any errors?

C:\Program Files (x86)\CloudVolumes\Agent\Logs\svservice.log

[sjesse]

Did you edit that error message, it seems off as it usually says the name of the app volumes server in the error message

[mmaus]

Is the cert you have on the App Volumes Manager trusted?

     - I have not modified any of the certs so everything is self-signed.  I did have to make an adjustment to the registry to get App Volumes to connect initially as I was getting connection errors when I first started working with this.  I think reg change would prevent any non-trusted certificate error, but I could be wrong.  I just know the clean client finally stopped spitting out connection error screens when I made this change.

Is it just this application or does something simple like Firefox work?

     - I created a second package for Firefox using my domain admin account and assigned this as the only package to my test user.  Upon logging in with the test user

I did notice something strange when I created the Firefox package...after install you are asked to reboot the machine to finalize.  I rebooted my provision machine and it came back up.  I logged back in and got the "Package Successful - Please revert back to your clean image" popup window,

but I noticed that Firefox was no longer installed after the reboot. 

I went back into Horizon Manager and changed the "Refresh OS Disk After Logoff" option to Never as it was set to Always.  I then deleted both Notepad++ and Firefox packages and recreated them again.  When I got to the reboot section this time...once again Notepad++ and Firefox were both missing after the reboot of my provision VM during the package creation....is this normal?  I would think they should still be there...hence why you get the message to revert to an older snapshot. 

I reverted back to my clean snapshot of my provision machine and tried to install both these apps just normally without going the App Manager.  Once installed after rebooting the VM...they were still there.  There appears to be something in the package creation processes that is reverting my VM back to the snapshot upon completion.

I created this Blog on Packaging when 4 came out, just for a sanity check welcome to check.

https://www.vbrit.net/appvolumes/appvolumes-4-packages

     - I reviewed your blog and it appears I followed the same steps for both my Firefox and Notepad++ packages.

Meant to ask do the logs show any errors?

     - I deleted the log to get a fresh sample.  I collected the log with the apps assigned and then again with the apps unassigned, but there was not much info given.

Did you edit that error message, it seems off as it usually says the name of the app volumes server in the error message

     - I did not edit the error message.  That is how it shows on the screen.

[sjesse]

I pulled the nic on a clone in my lab(running 4.1)

Now look at yours

see how mine shows the url and your says HorizonServer). That seems off.

[mmaus]

I adjusted the registry to reference the FQDN and the IP Address of the server and got the following errors similar to yours.

If I type in the address into a browser I can get to a login page and successfully login as well.

[sjesse]

Why are you calling this horizon server, is there any other software on this, or is it dedicated to app volumes.

[mmaus]

I have two VMs running this test environment.  The HorizonServer that is running Horizon 7 and Apps Manager 4.  The other VM is an SQL server for the databases.

[sjesse]

I suggest at least for now split out the horizon and app volumes server into separate vms, its not designed to be installed on the same server. Then if it works look at collapsing them if you want to save resources. Honestly, when I tried this I think before getting a bigger lab, I put app volumes on the sql server since it didn't need to use port 443.

[mmaus]

Roger that...ill try splitting them up and see how that works out.

[mmaus]

Ok..so I created a new VM to host the AppManager services.  I got everything updated and connecting on my agent machines.  I and am getting a slightly different error message now.  The error message still does not display when there is no package assigned to the client, but does appear when either my Notepad++ or my Firefox package is assigned.

The error before I moved the server states "Connection Error"...now it is saying "Manager Error".  I do not know if this might be due to the fact that the old App Volume was ver 4.0 and I went ahead and installed 4.1 on the new server.

Looking in the error logs...this is what I see that appears to be relevant:

[2020-08-03 18:31:31.347 UTC] [svservice:P1624:T5068] [0] Connecting to horizonappmanager.[REDACTED].local:443 using HTTPS (attempt 1)

[2020-08-03 18:31:31.347 UTC] [svservice:P1624:T5068] WinHttpAddSessionCookies: successfully added Cookie header to HTTP request.

[2020-08-03 18:31:31.347 UTC] [svservice:P1624:T5068] WinHttpSendRequestWithSSLCertValidation: SSL certificate validation is disabled.

[2020-08-03 18:31:31.763 UTC] [svservice:P1624:T5068] WinHttpSendRequestWithSSLCertValidation: WinHttpSendRequest succeeded.

[2020-08-03 18:31:31.763 UTC] [svservice:P1624:T5068] HttpSendRequest: WinHttpQueryHeaders returned status code 401

[2020-08-03 18:31:31.763 UTC] [svservice:P1624:T5068] ProcessNTLMType1Buffer: -NTLM Type 1: domain: [], workstation: [] version (10.0.18362 ntlm ver 15)

[2020-08-03 18:31:31.763 UTC] [svservice:P1624:T5068] WinHttpAddSessionCookies: successfully added Cookie header to HTTP request.

[2020-08-03 18:31:31.763 UTC] [svservice:P1624:T5068] WinHttpSendRequestWithSSLCertValidation: SSL certificate validation is disabled.

[2020-08-03 18:31:32.243 UTC] [svservice:P1624:T5068] WinHttpSendRequestWithSSLCertValidation: WinHttpSendRequest succeeded.

[2020-08-03 18:31:32.243 UTC] [svservice:P1624:T5068] HttpSendRequest: WinHttpQueryHeaders returned status code 401

[2020-08-03 18:31:32.243 UTC] [svservice:P1624:T5068] ProcessNTLMType2Buffer: -NTLM Type 2: target -> name: [[REDACTED]], dnsdomainname: [[REDACTED].local], dnscomputername: [[REDACTED].[REDACTED].local]

[2020-08-03 18:31:32.243 UTC] [svservice:P1624:T5068] GenerateNTLMType3: ChannelBinding-Hash (32): 631dce6b80d9b5ea72a5d8d9736fc837f9b6f90db14f500b7eed3902b2f64ba5

[2020-08-03 18:31:32.243 UTC] [svservice:P1624:T5068] ProcessNTLMType3Buffer: -NTLM Type 3: target -> ntlmname: [LDAP/[REDACTED].[REDACTED].local], dnsdomainname: [[REDACTED].local], dnscomputername: [[REDACTED].[REDACTED].local]

[2020-08-03 18:31:32.243 UTC] [svservice:P1624:T5068] ProcessNTLMType3Buffer:   client -> username: [[REDACTED]], domainname: [[REDACTED]], workstationname: [WIN10-IC1], version -> 10.0.18362 ntlm ver 15

[2020-08-03 18:31:32.243 UTC] [svservice:P1624:T5068] ProcessNTLMType3Buffer:   channelbindings -> 9b1b11f9ca31e73f757fad5f84e16b10

[2020-08-03 18:31:33.483 UTC] [svservice:P1624:T5068] HttpSendRequest: WinHttpQueryHeaders returned status code 500

[2020-08-03 18:31:33.483 UTC] [svservice:P1624:T5068] HttpReadAllAvailableData: Error 0 in WinHttpQueryDataAvailable: dwSize 0

[2020-08-03 18:31:33.483 UTC] [svservice:P1624:T5068] LogManagerResponse: Manager status 500 response (50 bytes): Failed to mount volumes, no mount results returned

[2020-08-03 18:31:33.483 UTC] [svservice:P1624:T5068] HttpSendRequest: Already contacted all 1 Manager(s) and received status 500 (aborting)

[2020-08-03 18:31:33.483 UTC] [svservice:P1624:T5068] User login over HTTP failed

[2020-08-03 18:31:33.483 UTC] [svservice:P1624:T5068] HttpUserLogin: failed (user login)

[2020-08-03 18:31:33.483 UTC] [svservice:P1624:T5068] OnLogon: succeeded

[2020-08-03 18:31:35.566 UTC] [svservice:P1624:T2648] OnStartShell called (Session ID 1, Handle 000001F2D67D1000, Params 00000001005FE858, Context 0000000000000000)

[2020-08-03 18:31:35.566 UTC] [svservice:P1624:T2648] OnStartShell: [REDACTED]\[REDACTED] (NameSamCompatible)

[2020-08-03 18:31:35.566 UTC] [svservice:P1624:T2648] ExpandEnvironmentVariable: ExpandEnvironmentVariable  : %localappdata%

[2020-08-03 18:31:35.566 UTC] [svservice:P1624:T2648] ExpandEnvironmentVariable: ExpandEnvironmentVariable  Returning  : C:\Users\[REDACTED]\AppData\Local

[2020-08-03 18:31:35.621 UTC] [svservice:P1624:T2648] OnStartShell<<< exit

[2020-08-03 18:31:35.621 UTC] [svservice:P1624:T5456] DeferredShellStart: Deferred Shell Start - [1].

[2020-08-03 18:31:35.621 UTC] [svservice:P1624:T5456] LaunchDesktopMonitoringProcess: launching deskmon process for sessionid 1

[2020-08-03 18:31:35.621 UTC] [svservice:P1624:T5456] RunExecutableAsUser: CommandLine C:\Program Files (x86)\CloudVolumes\Agent\svservice.exe deskmon 1

[2020-08-03 18:31:36.047 UTC] [svservice:P1624:T5456] CreateProcessCheckResult: Successfully launched: "C:\Program Files (x86)\CloudVolumes\Agent\svservice.exe deskmon 1". WaitMilliseconds 0 ms, pid=5684 tid=5724

[2020-08-03 18:31:36.047 UTC] [svservice:P1624:T5456] Message: "Manager Error (Manager "horizonappmanager.[REDACTED].local" error code 500):

App Volumes Manager returned a service error.

Virtualization is disabled." (hToken 000000000000080C)

[2020-08-03 18:31:36.047 UTC] [svservice:P1624:T5456] RunExecutableAsUser: Path "C:\Program Files (x86)\CloudVolumes\Agent\svservice.exe"

[2020-08-03 18:31:36.047 UTC] [svservice:P1624:T5456] RunExecutableAsUser: CommandLine svservice.exe message "Manager Error (Manager "horizonappmanager.[REDACTED].local" error code 500):

App Volumes Manager returned a service error.

Virtualization is disabled."

[2020-08-03 18:31:36.052 UTC] [svservice:P1624:T5456] CreateProcessCheckResult: Successfully launched: "svservice.exe message "Manager Error (Manager "horizonappmanager.[REDACTED].local" error code 500):

App Volumes Manager returned a service error.

[VirtualSpence · Accepted solution]

I was able to reproduce the error and log entry "Manager status 500 response (50 bytes): Failed to mount volumes, no mount results returned". by connecting to a VM running on an EXSi host that didn't have access to the datastore where the package (VMDK) resides. Can you verify that the host where the desktop resides has access to that datastore?

[mmaus]

We are a small company and im doing my best to try and keep this proof of concept separate test enviroment from my production environment, but I dont have the hardware or licensing to do a proper lab environment.

It looks as if the clients did not have access to the datastore where the packages were being stored.  I tried to re-create the package on a datastore I knew they did have access to, but am getting an error saying the provision vm cant mount the drive for package creation...

I think I have some redesigning of this environment to do before I can try to move forward some more.

Thanks for the info so far.  Ill post back as soon as I have everything flowing again.

[mmaus]

Alright...got everything rebuilt and got the Notepad++ app to install.

I do have a followup question... Is there a way to notify the user that a new package has been issued to them and to logoff and log back on to get it like a desktop message pop up?

[VirtualSpence]

Nothing quite like that in App Volumes. However, if you're using Horizon you could use the "send message" ability in the Horizon console to send an immediate alert to a user. It would work well for one-off notifications, but probably less useful for large assignments.

[mmaus]

Excellent.  Thank you to everyone that has helped me on this adventure...in this thread and my many others Horizon posts. 

[sjesse]

What we do is run a script that automatically sends a message at the end of the month for people to logout and in again, if they don' we force restart the desktops, you can do all of this with the horizon api.