Hi All

Need your help in resolving an issue with SAP Crystal Reports 2011 SP4

I had sequenced this app using AppV 5.0 SP3 as well as SP2 on a 32bit Windows 7, and haven't deleted any file after capturing the package, used the RAW .appv package and published it on  64bit Windows 7.

Later while launching the short cut "Crystal reports 2011" we are getting below error..iYASBF.png

> Provided full permissions to ROOT folder after publishing the package, still no go.
>Application has been sequenced with and without launching the shortcut during sequencing phase, still no go.
> Sequenced app on Appv SP2 and SP3, still no go.

Do you guys know if there are any known issues in sequencing this SAP Crystal Reports 2011 SP4
If So, please let me know.

Or is there anyone who worked on this application, if so please help me in resolution.

0 Comments   [ + ] Show Comments


  • This content is currently hidden from public view.
    Reason: Removed by member request
    For more information, visit our FAQ's.
Please log in to comment


Firstly, your 'Subject' doesn't match the problem you describe, as it seems you have sequenced the app. The problem described is that the sequenced app doesn't launch.

Secondly, it seems you're trying to take an app which was sequenced on a 32-bit OS and have it run on a 64-bit target OS. Why would you expect that to work properly, if at all?
Answered 11/09/2015 by: VBScab
Red Belt

  • @VBScab:

    Thanks for your response, as per client requirement we are performing Sequencing on 32bit and testing it on 64bit machine, however initial source analysis is performed on 64bit Windows7, by which we can say that Sequenced App should work on 64bit machine, until and unless there is some specific thing which saying 32bit sequenced apps do not work on 64bit Client.

    Let me know if you have any other suggestions.
Please log in to comment
0002 is file not found error. Use procmon to trace the issue. 
The issue would be CoW folder I think so.
Answered 11/09/2015 by: apptopack
Red Belt

  • @Vigneshwaran:

    Thanks for your reply, Procmon is not capturing any process when the shortcut is launched, so unable to check what is happening.

    Any other solutions...
    • I would say try to clear the CoW for the particular package in C:\Users\Administrator\AppData\Local\Microsoft\AppV\Client\VFS\<PackageID> and relaunch the shortcut again.
Please log in to comment
>client requirement
Your client needs educating. "Bring me The Packager's Baseball Bat Of Explanation!"

You need to include a shortcut to it in the sequence.
Answered 11/10/2015 by: VBScab
Red Belt

Please log in to comment
Answer this question or Comment on this question for clarity