Error 0X8CE03102-0000050A Due to a Network Failure

All replies

• 

  

  0

  Sign in to vote

  So what does your evenlog say? Also check Subsystems-VFS in particular.

  • Marked as answer by Brandon RecordsModerator Monday, November 16, 2015 5:14 PM

  Friday, October 23, 2015 12:20 AM
• 

  

  0

  Sign in to vote

  Are you using any kind of folder redirection or SCS?

  ---

  (Please click on "Vote as Helpful" and/or "Mark as Answer", if it has helped you.)
  
  : app2pack.blogspot.com

  • Marked as answer by Brandon RecordsModerator Monday, November 16, 2015 5:15 PM

  Friday, October 23, 2015 4:08 AM
• 

  

  0

  Sign in to vote

  If you test it in a standalone environment, is it working?

  ---

  (Please click on "Vote as Helpful" and/or "Mark as Answer", if it has helped you.)
  
  : app2pack.blogspot.com

  • Marked as answer by Brandon RecordsModerator Monday, November 16, 2015 5:15 PM

  Friday, October 23, 2015 4:28 AM
• 

  

  0

  Sign in to vote

  What .exe is reported in eventvwr? I have seen this with a virtual office 2013 on msoia.exe which is the Telemetry Agent. Only solution: restart your PC.

  
  

  Friday, October 28, 2016 1:15 PM
• 

  

  0

  Sign in to vote

  Hi,

  Got a user who has reported this error when openning an app via AppV 5.1. Straight after login.

  Loading your applications was still in progress, but explore.exe has started already. So instead of waiting for AppVStreamingUX.exe to complete the loading app process, an app has been openned which has stopped loading app progress and presented the error:

  Microsoft application virtualization (App-V)

  The application failed to launch

  This may be due to a network failure

  Error code: 0X8CE03102-0000050A

  Procmon shows that when app is started AppVStreamingUX.exe stops executing whatever it was doing. 0.1 sec later app process starts

  The actual app process instead of injecting and executing methods from AppVEntSubsystems32.dll actualy injects and executes AppVTerminator32.dll (LOL) which kills app process.

  Just need to be more patience here and wait untill app loading process completes - unless there are sometricks to workaround this, feel free to let me know:)

  Jaro

  Wednesday, June 27, 2018 5:00 PM
• 

  

  0

  Sign in to vote

  The reason I usually get this error is when I create desktop shortcuts on the user desktop during sequencing, but then publish globally. If I'm publishing globally, I need to place the shortcuts on C:\users\Public\Desktop instead.

  • Proposed as answer by Walter_Bishop Thursday, June 28, 2018 1:55 PM

  Thursday, June 28, 2018 1:55 PM