locked
Struggling with a specific application / Sequencer crash RRS feed

  • Question

  • Hello Community,

    I've to struggle with a specific application. The sequencing process itself seems to work fine, but always with the last step when I want to save the package, the sequencer crashes and the package is lost!

    Image

    I've tried to find the reason for the crash, but I've no plan.
    If I activate the debuging Log in the sequencer it shows me a entry like this:

    Error in ManagedFileNameInfoT::GetFileNameInfo(), FltGetFileNameInformation() ntstatus = The name requested was not found in Filter Manager's name cache and could not be retrieved from the file system.


    Does anyone know this error?
    Is there a way to trace back which file/s cause the error and brings the sequencer to crash?

    Here is the link to the setup binary that I use: http://deliver.cnc-keller.net/v600/SYM_ ... 0_R352.exe

    I've tried it with a sequencer based on APP-V 5.0 and APP-V 5.1. With both versions I get the same result.

    In another Forum where I've posted this case I got the Suggestion that the cause could be in relation with invalid ProgIDs (in the file type association) and Shortcuts (lnk files with a space at the end).

    Where can I check this?

    Maybe I should open a Microsoft support case for this, but first I'll try if it's possible to solve this with the help of the community.

    Thanks in advance for every Suggestion/help

    Wednesday, January 6, 2016 9:55 AM

Answers

  • Hi,

    I just downloaded the binary provided and tried sequencing, but as you said every tricks failed.

    However, I observed that the application extract a set of files and msi files for 32 bit and 64 bit architecture.

    I used the extracted source for installation and then stopped and disabled code meter service as this process keeps running even when you exit all the applications. Following this raw process, the sequencer did not crash and at least we got a package to work on. Service can be started through scripting if at all that is causing the issue.

    Thanks for uploading the source file.

    I hope this might help you.

    • Proposed as answer by znack Tuesday, March 22, 2016 3:32 PM
    • Marked as answer by CodyLambertModerator Tuesday, May 31, 2016 3:49 PM
    Monday, March 21, 2016 8:22 PM

All replies

  • Does the package contains .rels files? Kindly have a look in the below link.

    https://support.microsoft.com/en-us/kb/2843030


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

    app2pack.blogspot.com: app2pack.blogspot.com

    Wednesday, January 6, 2016 11:38 AM
  • Interessting article, thanks!

    I've never heard about .rels files before! But it seems that reason for the crash must be something else, because I couldn't find any .rels files in my package...

    Are there any logfiles with helpful informations to trace the crash...

    If I do a search with google I could find a similar case with a invalid manifest, but this also don't seem to be the Problem...

    http://packageology.com/2014/08/sometimes-fix-crashing-sequencer-imgburn-recipe/

    Wednesday, January 6, 2016 3:35 PM
  • You can check in event viewer for any logs.


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

    app2pack.blogspot.com: app2pack.blogspot.com

    Thursday, January 7, 2016 4:30 AM

  • Not sure if it might work for you. But I had similar problem wherein the sequencer used to crash at the last step. 

    I could not dig it deeper for the rootcause but enabling the PVAD and sequencing the software to the PVAD location instead of the default location did the trick for me. Well, we are using APPV Sequencer v 5.1.

    Worth a try may be!


    Thursday, January 7, 2016 6:15 PM
  • Thanks for the suggestion.

    I've tried it with enabling the PVAD mode. Installing the Software to the PVAD directory brings the same result. 

    Friday, January 8, 2016 3:14 PM
  • I've seen a similar issue before with OpenText Exceed and Miktex... in both situations there are lots of fonts installed. The App-V sequencer can only handle about 1000 fonts max. So if your application installes lots of fonts this could be your problem.
    I've solved mine by creating separate packages for the fons and merge them with a connectiongroup (so 500 fonts in the main package, and 600 font in a secondary package).
    Sunday, January 10, 2016 11:18 AM
  • Also, check to see if some of the file paths captured are extremely long. I've had that happen before a few times and had to adjust the installation path to get under the threshold.
    Monday, January 11, 2016 5:21 PM
    Moderator
  • You can check my blog where I have collected possible reasons for sequencer crash and their solutions from other App-V Techies. If I come across any new scenario, I will keep updating the blog.

    http://app2pack.blogspot.com/2016/01/possible-reasons-for-app-v-50-sequencer.html


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

    app2pack.blogspot.com: app2pack.blogspot.com

    Monday, January 18, 2016 9:35 AM
  • To be honest, if you open up a support case, there could be enough debugging to determine root cause and possibly adjust the sequencer in a future release.


    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.”

    Tuesday, February 16, 2016 4:34 AM
  • I can confirm this program causes the sequencer to crash when you are trying to 'save' the package.  It appears to be a german language program, I installed it on my EN-US sequencer box.  When I procmon'ed the 'save'  the last file it read before the crash was "C:\Program Files (x86)\KELLER\KELLERplusFD\CPMAIN.EXE".

    If I remove CPMAIN.EXE from the package then it finds another "CPMAIN.EXE" in a 'update' folder and crashes on that one.  If I remove all CPMAIN.EXE's then it crashes on VM_ACTIVEX.EXE.

    The common thread I see amongst these EXE's is they have German specified as a language on the details tab.

    Tuesday, February 16, 2016 7:45 AM
  • I can confirm that removing all the 'German'-only language applications resolves this crash.  I know this doesn't help get this software packaged for you but you can open a ticket with Microsoft on it.

    The .EXE's I removed to enable this to work:

    CPMain.exe
    VM_active.exe
    UpdateManager.exe

    Maybe installing a German language pack would resolve this issue?

    Tuesday, February 16, 2016 3:59 PM
  • Community, I thank you a lot for all of your suggestions! I'm amazed :)

    @Vigneshwaran

    Great to see that you've created a article on your blog to that topic!

    With help of the last Suggestion to exclude this three exe files I was able to find a Workaround to get the package to work! Tomorrow I'll update this thread and post my solution how I could finally solve it :)

    Thursday, February 18, 2016 4:59 PM
  • As I've promised,

    I've documented on my blog the final solution how I get the package to work!

    Thank you for all your answers, without your effort this wouldn't be possible :)


    • Edited by JFreak85 Friday, February 19, 2016 4:34 PM
    Friday, February 19, 2016 4:29 PM
  • As mentioned earlier, I'm going to post information on how you guys can start debugging these issues further.


    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.”

    Saturday, February 20, 2016 5:00 AM
  • Have updated my blog with your post too.

    http://app2pack.blogspot.in/2016/01/possible-reasons-for-app-v-50-sequencer.html

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

    app2pack.blogspot.com: app2pack.blogspot.com

    Saturday, February 20, 2016 10:09 AM
  • @Steve,

    Expecting part 2 soon :)


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

    app2pack.blogspot.com: app2pack.blogspot.com

    Saturday, February 20, 2016 10:09 AM
  • Expect about a dozen parts. A lot to cover.


    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.”

    Saturday, February 20, 2016 8:02 PM
  • I just want to let you know, that I did a post in the APP-V Uservoice related to that topic. For me it's the first time that I'm using this service and I'm really interessted if it's possible to find out the cause for the crash.

    If you're also interessted that this would be further analyzed, please give my topic a vote:

    https://appv.uservoice.com/forums/280448-microsoft-application-virtualization/suggestions/13060074-analyze-the-cause-of-a-sequencer-crash

    Thanks in advance   


    • Edited by JFreak85 Monday, March 21, 2016 5:27 PM
    Monday, March 21, 2016 5:26 PM
  • Hi,

    I just downloaded the binary provided and tried sequencing, but as you said every tricks failed.

    However, I observed that the application extract a set of files and msi files for 32 bit and 64 bit architecture.

    I used the extracted source for installation and then stopped and disabled code meter service as this process keeps running even when you exit all the applications. Following this raw process, the sequencer did not crash and at least we got a package to work on. Service can be started through scripting if at all that is causing the issue.

    Thanks for uploading the source file.

    I hope this might help you.

    • Proposed as answer by znack Tuesday, March 22, 2016 3:32 PM
    • Marked as answer by CodyLambertModerator Tuesday, May 31, 2016 3:49 PM
    Monday, March 21, 2016 8:22 PM
  • Nice find Nicke
    Tuesday, March 22, 2016 7:05 PM
    Moderator
  • @Karsjees

    Thank you very much for your help and analysis. I've tried it with the extracted files and disabled the codemeter runtime service as you've described, but the seqeuncer crashed again. Maybe I did soemthing wrong.

    I did extract the setup binary with 7-zip and got three folders:

    Dongle / KELLERplus / Updates

    That's the same structure when I execute the original setup binary and switch to the %temp% location.

    Inside the KELLERplus folder I can find the setup files which are based on Installshield, but I couldn't find any msi files or a difference between 32 bit and 64bit architecture. If I run the setup from there it's almost the same as I would execute the original setup binary directly.

    Did you do a further extraction of the installshield files? Can you guide me on that step what you did to get the extracted source files and which files you've used for the installation?

    Thanks in advance

    Wednesday, March 30, 2016 9:51 AM
  • Yes, you are right on further extraction or if you wait till end of the installation, you can find a set of files in %temp% location like this:

    

    it might or might not be complete installation but i guess it can be worked out this way. I will try to compare it when I have some time for sure. Let me know what you think.

    Wednesday, March 30, 2016 3:33 PM
  • @Karsjees

    After installing the codemeter runtime I could see the source files in the %temp% directory. I've copied them away and tried to sequence the application again.

    First I did install the CodeMeterRumtime64.msi and then after finishing this installation I did stop and disable the codemeter runtime service. Then I've used the setup binary from the extracted KELLERPlus folder for the rest of the installation. I've tried to finish the package --> Sequencer crash

    Then I did download the newest CodeMeterRuntime version and tried it again --> Sequncer crash

    After this two failure attempts I've tried to sequence the application completely without the codemeter runtime and the sequencer crashed again.

    Because of that I think the cause must be somewhere else in the application and is not to find in the codemeter runtime.

    If you get a working package I'm really interested in the detailed steps you did, but let you as much time as you need. I've a workaround as I've described above, but it would be great if we can solve this mystery :)


    • Edited by JFreak85 Thursday, March 31, 2016 2:08 PM
    Thursday, March 31, 2016 2:06 PM
  • Interesting!

    My initial assumption was that since the code meter runtime installs all the shortcuts, it might have

    most of the install files in it, and if some bit is remaining we can add it in the package files section to make the installation complete. But I guess that's not the case. I think I installed something prior to install but not so sure.

    I will work on it this weekend as now i am unable to find those saved files. I will have to start from scratch.

    Will let you know if I get some positive results.

    Thursday, March 31, 2016 2:19 PM
  • Karsjees,

    Any update on your results?

    Friday, April 8, 2016 5:09 PM
    Moderator
  • Hello all,

    We had this exact problem with a product called ENC Analyzer and while I appreciate you resolved your issue with AVE we took another free approach.

    We simply;

    • Renamed the .exe's In question to an arbitrary file format (I choose .enc)
    • Wrote a simple application in .NET (below; but FYI pInfo.UseShellExecute = False is the key!)
    • Modified the product shortcuts to launch the .NET application which subsequently launches the .enc files as binaries
    Module Module1
    
        Dim pInfo As New ProcessStartInfo
        Dim sRun As String
    
        Sub Main()
            ParseCommandLineArgs()
        End Sub
    
        Public Sub ParseCommandLineArgs()
            Try
                If Environment.GetCommandLineArgs.Count <> 2 Then
                    Console.WriteLine("Provide the file to run")
                Else
                    Try
                        RunCommand()
                    Catch ex As Exception
                    End Try
    
                End If
            Catch ex As Exception
            End Try
        End Sub
    
        Public Sub RunCommand()
    
            Dim pInfo As New ProcessStartInfo
            pInfo.FileName = Environment.GetCommandLineArgs(1)
            pInfo.UseShellExecute = False
            pInfo.WindowStyle = ProcessWindowStyle.Minimized
            Dim proc As Process = Process.Start(pInfo)
    
        End Sub
    
    End Module

    Hope this helps,

    Tuesday, April 12, 2016 9:53 PM