locked
SAP Crystal reports Viewer 2013 - Issue with APP-V 5.0 SP2/SP3 Package RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi,

    I am trying to create APP-V 5.0 package for SAP Crystal Reports Viewer 2013 application. I am using APP-V 5.0 SP2 sequencer. When I launch the application

    on a windows server 2008 R2 machine, I get the network failure error. ( Error Message : The application failed to launch. This may be due to network failure. ErrorCode:0x8F10252A-00000002 ). When the launch the application on a windows 7 machine, the

    application launches fine for the first time and in the subsequent launches, I get the JVM terminated.Exit code=13 error. ( see screenshot attached ).I tried 

    sequencing with APP-V 5.0 SP3 too, but it didn't work. I used promon to see what's happening when the application is launched. But, I am not able to gather much information on what's happening. If anyone has faced this issue, kindly

    help. 

    Thanks,

    Hariharan M

    Friday, October 9, 2015 2:38 PM

Answers

  • Question
    Sign in to vote
    0
    Sign in to vote
    Have a look here. Crystal Reports 13 installs to long paths which will give issues with Appv5. So try to shorten the patch described in that article. 
    Friday, October 9, 2015 3:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Exactly - try it again with the App-V 5.1 Sequencer and the App-V 5.1 client.

    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

    Sunday, October 18, 2015 4:40 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote
    Have a look here. Crystal Reports 13 installs to long paths which will give issues with Appv5. So try to shorten the patch described in that article. 
    Friday, October 9, 2015 3:45 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Is the issue resolved?

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

    Sunday, October 11, 2015 1:04 PM
  • Question
    Sign in to vote
    1
    Sign in to vote
    00002 is actually file not found windows error code. Try procmon to trace for File not found error again.

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

    app2pack.blogspot.com: app2pack.blogspot.com

    Sunday, October 11, 2015 2:17 PM
  • Question
    Sign in to vote
    0
    Sign in to vote
    probably a file not found because the path is too long.
    Monday, October 12, 2015 6:50 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Exactly - try it again with the App-V 5.1 Sequencer and the App-V 5.1 client.

    Steve Thomas, Senior Consultant, Microsoft

    App-V/MED-V/SCVMM/Server App-V/MDOP/AppCompat

    http://blogs.technet.com/gladiatormsft/
    The App-V Team blog: http://blogs.technet.com/appv/
    The MED-V Team Blog: http://blogs.technet.com/medv
    The SCVMM Team blog: http://blogs.technet.com/scvmm/

    “This posting is provided "AS IS" with no warranties, and confers no rights. User assumes all risks.”

    Sunday, October 18, 2015 4:40 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    Install the application in system context while monitoring phase. This was working for me for the appv4.6 version
    Thursday, September 27, 2018 8:23 AM