locked
Crystal Reports Runtime 13 not found in sequence on App-V 5.0 SP2 Hotfix 5 client RRS feed

 > 

  • Question

  • Question
    Sign in to vote
    0
    Sign in to vote

    My application uses a VFS installation of Crystal Reports Runtime 13. (i.e., the path to CR13 isn't specified as the Primary directory during sequencing, as my app uses that particular path)

    On a test VM with an old App-V client (5.0.285.0) the application launches and can locate CR components successfully.

    However, when we upgrade to the latest App-V client (SP2 HF5) the application fails to find CR.

    The original application was sequenced with App-V 5.0 RTM (5.0.285.0). I've re-sequenced the app with the latest sequencer (SP2 HF4) but the error persists.

    There is literally nothing in the Event Log and the app doesn't appear to report the error to Windows (it pops up a UI message saying CR 13 can't be located).

    Procmon doesn't show anything meaningful, although I could have missed something whilst trawling through 16,000 lines of processes.

    I enabled all App-V logs and nothing relating to an error can be found there.

    I tried disabling DEP and following other advice in this earlier thread: virtualizing-business-objects-crystal-reports-pro-110

    OS: Windows 7 SP1, patched up to date.
    App-V client: 5.0.3404 (SP2 Hotfix 5)

    Anyone seen an issue like this?

    I'm about to open a case with Microsoft Support, just thought I'd ask here first.

    Regards.

    Tuesday, September 16, 2014 2:47 PM

Answers

  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi.

    We raised a support ticket with Microsoft and with their help, found that the path length to the VFS installation of Crystal Reports was the issue.

    I created an MST (btw, Crystal Reports MSI has numerous directory and registry entries that don't use best practice, so this took a while..) to reduce the path lengths.

    As to why the RTM version of the client works (from our Microsoft support engineer):

    "Regarding the “why”, between RTM and the next versions, lots of issues were corrected.
    In this particular situation, the issue was related with the fact that the application stopped extending the buffer. Probably what happened was that a COM or Object Bug was corrected between RTM and SP2 and this had a negative effect on the application. What this means is that, in fact, the application was not supposed to work in RTM as well, due to buffer being extended."

    So in summary, if you have an application with a particularly long path structure, you may need to re-sequence for the SP2 version of the client.


    • Marked as answer by TenBob Wednesday, September 24, 2014 11:56 AM
    • Edited by TenBob Wednesday, September 24, 2014 1:08 PM smelling pistakes
    Wednesday, September 24, 2014 11:56 AM

All replies

  • Question
    Sign in to vote
    0
    Sign in to vote

    Hello,

    I would raise a support ticket with Microsoft regarding the topic.

    ProcMon would of course where it searches for files (and since it works with an older version of the App-V client you can Always compare the two scenarios with ProcMon) and would potentially offer a workaround.

    Nicke Källén | The Knack| Twitter: @Znackattack

    Tuesday, September 16, 2014 6:49 PM
  • Question
    Sign in to vote
    1
    Sign in to vote

    Hi.

    We raised a support ticket with Microsoft and with their help, found that the path length to the VFS installation of Crystal Reports was the issue.

    I created an MST (btw, Crystal Reports MSI has numerous directory and registry entries that don't use best practice, so this took a while..) to reduce the path lengths.

    As to why the RTM version of the client works (from our Microsoft support engineer):

    "Regarding the “why”, between RTM and the next versions, lots of issues were corrected.
    In this particular situation, the issue was related with the fact that the application stopped extending the buffer. Probably what happened was that a COM or Object Bug was corrected between RTM and SP2 and this had a negative effect on the application. What this means is that, in fact, the application was not supposed to work in RTM as well, due to buffer being extended."

    So in summary, if you have an application with a particularly long path structure, you may need to re-sequence for the SP2 version of the client.


    • Marked as answer by TenBob Wednesday, September 24, 2014 11:56 AM
    • Edited by TenBob Wednesday, September 24, 2014 1:08 PM smelling pistakes
    Wednesday, September 24, 2014 11:56 AM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi TenBob,

    We are having an issue where an App-V application uses CR Runtime 13 but cannot find the path, and I think it may be down to the long path, is it possible to have a copy of the mst ?

    Tuesday, July 28, 2015 10:53 AM
  • Question
    Sign in to vote
    2
    Sign in to vote

    Hi Foxxi,

    I detailed how to create the MST here:

    http://trentent.blogspot.ca/2015/06/crystalreports-13-and-appv-5-have-issues_26.html

    • Proposed as answer by Vigneshwaran (MCTS)MVP Wednesday, July 29, 2015 5:08 AM
    • Unproposed as answer by TenBob Wednesday, July 29, 2015 8:04 AM
    Tuesday, July 28, 2015 7:16 PM
  • Question
    Sign in to vote
    0
    Sign in to vote

    Hi Foxxi

    Try this:

    Crystal Reports 13 Short Paths MST



    • Edited by TenBob Wednesday, July 29, 2015 9:13 AM
    Wednesday, July 29, 2015 8:18 AM
  • Question
    Sign in to vote
    0
    Sign in to vote
    I've found that I have a much better success rate for applications that have Crystal Reports runtime elements, when I designate the PVAD to the location that the runtime installs to (even if its outside the main application package).
    Wednesday, August 26, 2015 6:42 PM
    Moderator