Jump to content
Welcome to our new Citrix community!
  • 0

XenMobile 10.3.6 Patch Experiences


Michael VanVliet

Question

Recommended Posts

  • 0

After major issues in 10.3.5 in a cluster setup, the 10.3.6 update solved some of the issues but new problems have come up. 

Sporadically HTTP error 417 when start to install the profiles for IOS; some users can´t even get past these errors and not been able to access WorxStore giving "unable to fetch the required assets to continue, please try again" error loop for both android and IOS.

 

Not good at all....  

  • Like 1
Link to comment
  • 0

After major issues in 10.3.5 in a cluster setup, the 10.3.6 update solved some of the issues but new problems have come up.

Sporadically HTTP error 417 when start to install the profiles for IOS; some users can´t even get past these errors and not been able to access WorxStore giving "unable to fetch the required assets to continue, please try again" error loop for both android and IOS.

 

Not good at all....

http://support.citrix.com/article/CTX205342

Link to comment
  • 0

Sorry, link still works for me, but I'll copy paste. We had the same problem, changing persistence fixed it.

 

HTTP 417 Error While Enrolling iOS Device on XenMobile

Article | Connectivity | Created: 08 Jul 2016 | Modified: 08 Jul 2016

Languages

 

Symptoms or Error

HTTP 417 error in Safari while enrolling an iOS device on XenMobile.

 

or

 

Second Profile Installation error: "Cannot establish connection to server.

 

Solution

Change the persistence method to Use Source IP at the MDM / XenMobile 8443 and 443 load balancer.

 

If XenMobile Servers are in a cluster, validate the Time/Date settings on the server.

Link to comment
  • 0

Just a word of caution that there appears to be an issue with clustering in 10.3.6.

 

We have random nodes leave the cluster and issues with high CPU making the nodes unresponsive.

 

We have to reboot our nodes a few times a week to keep the cluster healthy.

 

The short term fix has been to bump the CPU to 4 and RAM to 8 GB for now.

 

Citrix is working on a fix which is supposed to be release mid August.

Link to comment
  • 0

The actual upgrade went well for us but after we started seeing the HTTP 417 errors on iOS devices during enrolment.  The change to NetScaler persistence as detailed in CTX205342 appears to have resolved the issue.

 

We also run a cluster of 3 XM servers and have experienced the issues mentioned by Chris Starke in the previous post in relation to CPU and unresponsive nodes.  Because of this I have been forced to restart all nodes.

 

Curently we are experiencing issues with public app store and delivery group install on iOS which I have raised a support call with Citrix for.  I am not too sure whether this has been introduced by the upgrade but don't recall seeing the issue prior to 10.3.6.

Link to comment
  • 0

Curently we are experiencing issues with public app store and delivery group install on iOS which I have raised a support call with Citrix for.  I am not too sure whether this has been introduced by the upgrade but don't recall seeing the issue prior to 10.3.6.

 

I have my test environment on 10.3.6 and my prod on 10.3.5 and I am seeing the same thing noted above, issues with apps from either the public app store or VPP for iOS and delivery groups installs. If there is a device that has not been enrolled it will get all the items in that delivery group, however, if an app is added to that delivery group it never gets pushed to the device, even though it is set as required.

I am seeing this behavior on both environments.

Link to comment
  • 0

System ver: 10.3.6.310 now

 

Changing the persistence method to use source IP fixed the 417 issue.

Another issue which some users have (ios and android) is the error message "Unable to fetch required assets.." when accessing worxstore. From the device logs i can see that when accessing worxstore this error is common for both IOS and Androids:

 

"Received an unexpected HTTP 403 response" on android and 

"Request failed: forbidden (403) on IOS

 

I cant see any difference between these devices and other devices which are working fine. 

 

The above problem i´m having on my IOS device and the only way to fix this is to factory reset the device and set it up as new and not from a backup. That is confirmed by another user som it may be a device issue but i´m trying to find a pattern here...

If theres anybody out there with same issue please reply.

 

Thanks/Marius

Link to comment
  • 0

System ver: 10.3.6.310 now

Another issue which some users have (ios and android) is the error message "Unable to fetch required assets.." when accessing worxstore. From the device logs i can see that when accessing worxstore this error is common for both IOS and Androids:

 

"Received an unexpected HTTP 403 response" on android and 

"Request failed: forbidden (403) on IOS

 

I cant see any difference between these devices and other devices which are working fine. 

 

The above problem i´m having on my IOS device and the only way to fix this is to factory reset the device and set it up as new and not from a backup. That is confirmed by another user som it may be a device issue but i´m trying to find a pattern here...

If theres anybody out there with same issue please reply.

 

Thanks/Marius

 

Can confirm it affects users who restored their iPhone. Users now cannot access any Worx Applications and I cannot tell everyone to "just" reset their iPhone to factory settings. What a nightmare

 

Edit: Running XenMobile Server version 10.3.6.10014

Link to comment
  • 0

I´ve the same issue.

"Unable to fetch the reqiured assets to continue.

 

We use Toolkit 10.3.10.24 to wrapped the apps.

XenMobile Server 10.3.6.310.

 

Should the issue fix with 10.3.6 rp?

 

Do you have any experience with that?

 

Thanks!

Did you check the device logs from WorxHome? Could you see the 403 errors which i mentioned in my post? 

 

I did receive a possible solution from Citrix for a while back but i can´t confirm that is working as i did try it with my device but the issue was still there. The solution involves some SQL quieries (to be performed on the Xen-DB) and the xms´s needs to be restarted at least 2 times during the process which is not what i prefer in an production environment and a cluster setup... 

Link to comment
  • 0

we upgraded from 10.3.5 to 10.3.6.310 (no rolling patches yet) and instantly noticed our tech support team could not access the admin console and was redirected to SHP.  I plan to apply latest rolling patches (calling support to verify order of patches) to resolve the SHP issues.

 

Didn't experience that kind of issue. Have you made sure your admins are using accounts which are not tied to any device or enrollment?

Link to comment
  • 0

Regarding the "Unable to fetch the reqiured assets to continue." issue on iOS devices:

 

It seems the issue is fixed by upgrading to iOS 10.0.2, at least it immediately did for our affected devices. I cannot confirm currently however that this is any permanent fix for the underlying issue or just coincidence that the conflicting information is overwritten by the update and that the issue won't happen again when restoring an enrolled 10.0.2 iOS device.

Link to comment

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...