Possible reasons for App-V 5.0 sequencer crash
Recently I came across a question in TechNet about App-V 5.0 Sequencer getting crashed when saving a package and its possible reasons. In this blog I am listing out the possible reasons for sequencer crash and its solutions provided from other App-V techies.
First and foremost it's always a good start to check in the event log when ever there is an issue. Check the screenshot as where to look for sequencer log entries. Always enable show analytic and debug logs from view menu.
1. rels files:
The App-V 5.0 sequencer fails to sequence if there is any .rels files present in the package.
You can identify a relationship part by the presence of a file with a ".rels" file extension in a folder named "_rels".
To know more check the link from Microsoft.
https://support.microsoft.com/en-us/kb/2843030
2. Invalid manifest detected:
Missing or invalid ProgId entries might also cause sequencer to crash with Invalid manifest detected error log.
Check the link from Dan Gough.
http://packageology.com/2014/08/sometimes-fix-crashing-sequencer-imgburn-recipe/
3.Backslash:
AppxManifest.xml schema does not allow backslashes in ProgId names. If found it leads to sequencer crash.
A manifest document failed validation against the schema(s).
DOM Error: 0xC00CE169
Reason: ‘Blackbaud.Ext\RE70\RE7’ violates pattern constraint of ‘[^\\]*’.
The element ‘{http://schemas.microsoft.com/appv/2014/manifest}ProgId’ with value ‘Blackbaud.Ext\RE70\RE7’ failed to parse.
Credit - Trentent & Dan Gough
4. Number of fonts:
There’s a limit of 700 fonts in a single AppV 5.0 SP3 package.
A manifest document failed validation against the schema(s).
DOM Error: -1072898028
Reason: Element ‘{http://schemas.microsoft.com/appv/2014/manifest}Font’ is unexpected according to content model of parent element ‘{http://schemas.microsoft.com/appv/2014/manifest}Fonts’.
Check Tim Mangan research paper for more details.
www.tmurgent.com/AppV/images/WhitePapers/Research_Fonts.pdf
5. Change from VFS to PVAD:
Try changing to PVAD during sequencing. This might some time resolve the issue.
6. Long paths:
Check for long paths in the package editor before saving.
7. Missing Language pack:
Sequencer might crash if there is any missing language pack. To know more check this link.
http://www.peppercrew.nl/index.php/2013/11/microsoft-app-v-5-0-sp1-sequencer-error-while-saving-package/
http://www.daniel85.ch/?p=1694
8. Shortcut names that end with a space:
Some times (not in all the cases) if there is a space in the shortcut at the end, it will lead to issues.
9.Manufacturer doesn't support App-V:
Some applications do not support App-V sequencing and causes sequencer to crash. In this case, there is no way to sequence it as manufacturer doesn't support App-V. It always a good approach to check with the manufacture in this scenario.
If you are not able to find any possible reason,then it is always recommended to raise a support ticket with Microsoft App-V team.
First and foremost it's always a good start to check in the event log when ever there is an issue. Check the screenshot as where to look for sequencer log entries. Always enable show analytic and debug logs from view menu.
1. rels files:
The App-V 5.0 sequencer fails to sequence if there is any .rels files present in the package.
You can identify a relationship part by the presence of a file with a ".rels" file extension in a folder named "_rels".
To know more check the link from Microsoft.
https://support.microsoft.com/en-us/kb/2843030
2. Invalid manifest detected:
Missing or invalid ProgId entries might also cause sequencer to crash with Invalid manifest detected error log.
Check the link from Dan Gough.
http://packageology.com/2014/08/sometimes-fix-crashing-sequencer-imgburn-recipe/
3.Backslash:
AppxManifest.xml schema does not allow backslashes in ProgId names. If found it leads to sequencer crash.
A manifest document failed validation against the schema(s).
DOM Error: 0xC00CE169
Reason: ‘Blackbaud.Ext\RE70\RE7’ violates pattern constraint of ‘[^\\]*’.
The element ‘{http://schemas.microsoft.com/appv/2014/manifest}ProgId’ with value ‘Blackbaud.Ext\RE70\RE7’ failed to parse.
Credit - Trentent & Dan Gough
4. Number of fonts:
There’s a limit of 700 fonts in a single AppV 5.0 SP3 package.
A manifest document failed validation against the schema(s).
DOM Error: -1072898028
Reason: Element ‘{http://schemas.microsoft.com/appv/2014/manifest}Font’ is unexpected according to content model of parent element ‘{http://schemas.microsoft.com/appv/2014/manifest}Fonts’.
Check Tim Mangan research paper for more details.
www.tmurgent.com/AppV/images/WhitePapers/Research_Fonts.pdf
5. Change from VFS to PVAD:
Try changing to PVAD during sequencing. This might some time resolve the issue.
6. Long paths:
Check for long paths in the package editor before saving.
7. Missing Language pack:
Sequencer might crash if there is any missing language pack. To know more check this link.
http://www.peppercrew.nl/index.php/2013/11/microsoft-app-v-5-0-sp1-sequencer-error-while-saving-package/
http://www.daniel85.ch/?p=1694
8. Shortcut names that end with a space:
Some times (not in all the cases) if there is a space in the shortcut at the end, it will lead to issues.
9.Manufacturer doesn't support App-V:
Some applications do not support App-V sequencing and causes sequencer to crash. In this case, there is no way to sequence it as manufacturer doesn't support App-V. It always a good approach to check with the manufacture in this scenario.
If you are not able to find any possible reason,then it is always recommended to raise a support ticket with Microsoft App-V team.
Comments
Post a Comment