Application Virtualization Management Console Unexpected Error Occurred
One games Xbox 360 games PC games Windows games Windows phone games Entertainment All Entertainment Movies & TV Music Business & Education Business Students & educators Developers Sale Sale Find a store Gift cards Products Software & services Windows Office Free downloads & security Internet Explorer Microsoft Edge Skype OneNote OneDrive Microsoft Health MSN Bing Microsoft Groove Microsoft Movies & TV Devices & Xbox All Microsoft devices Microsoft Surface All Windows PCs & tablets PC accessories Xbox & games Microsoft Band Microsoft Lumia All Windows phones Microsoft HoloLens For business Cloud Platform Microsoft Azure Microsoft Dynamics Windows for business Office for business Skype for business Surface for business Enterprise solutions Small business solutions Find a solutions provider Volume Licensing For developers & IT pros Develop Windows apps Microsoft Azure MSDN TechNet Visual Studio For students & educators Office for students OneNote in classroom Shop PCs & tablets perfect for students Microsoft in Education Support Sign in Cart Cart Javascript is disabled Please enable javascript and refresh the page Cookies are disabled Please enable cookies and refresh the page CV: {{ getCv() }} English (United States) Terms of use Privacy & cookies Trademarks © 2016 Microsoft
Error code: 0000C800 when trying to import a package on the App-V Management server ★★★★★★★★★★★★★★★ J.C. HornbeckFebruary 3, 20113 0 0 0 Here's an issue we ran into the other day and since I didn't see it documented anywhere officially I thought I'd post it here. Symptoms When you try to import a Microsoft App-V (SoftGrid) package on the App-V Management Console, you receive the following error message: Unexpected error occurred. Please report https://support.microsoft.com/en-us/kb/930565 the following error code to your system administrator. Error code: 0000C800 Cause This can occur if the name of the SFT file is longer than 56 characters. Resolution Make sure that when you sequence you application, the name is 56 characters or less. More Information Microsoft App-V stores the name of the SFT file in the https://blogs.technet.microsoft.com/appv/2011/02/03/error-code-0000c800-when-trying-to-import-a-package-on-the-app-v-management-server/ DBO.Packages table in the SQL database. This Name Field is limited to 64 characters. It contains the name of the SFT File and automatically ads the _Package value, meaning that there is an effective maximum SFT file name length of 56 characters. ===== Thanks to Sebastian Gernert and Ben Fersenheim for their work on identifying this issue. J.C. Hornbeck | System Center Knowledge Engineer The App-V Team blog: http://blogs.technet.com/appv/ The WSUS Support Team blog: http://blogs.technet.com/sus/ The SCMDM Support Team blog: http://blogs.technet.com/mdm/ The ConfigMgr Support Team blog: http://blogs.technet.com/configurationmgr/ The SCOM 2007 Support Team blog: http://blogs.technet.com/operationsmgr/ The SCVMM Team blog: http://blogs.technet.com/scvmm/ The MED-V Team blog: http://blogs.technet.com/medv/ The DPM Team blog: http://blogs.technet.com/dpm/ The OOB Support Team blog: http://blogs.technet.com/oob/ The Opalis Team blog: http://blogs.technet.com/opalis The Service Manager Team blog: http: http://blogs.technet.com/b/servicemanager The AVIcode Team blog: http: http://blogs.technet.com/b/avicode Tags 0000C800 App-V Import Management Console Comments (3) Cancel reply Name * Email * Website CB says: February 3, 2011 at 5:02 pm Is this also an issue for System Center Configuration Manage
board cookies • All times are UTC + 1 hour [ DST ] Powered by phpBB Forum Software © phpBB Group phpBB Metro Theme by PixelGoose Studio
App-V 4.6, KB Article, Sequencer Here’s a new Knowledge Base article we published. This one explains how to allow applications running inside an App-V Virtual Environment to read from or write to the native registry on a client. ===== Summary The purpose of this document is to describe the support for registry pass-through functionality that exists in Microsoft Application Virtualization (App-V) version 4.6. Registry pass-through functionality is used when applications running inside a Virtual Environment (VE) need to read/write the contents of the native registry on a client. More Information The problem registry pass-through functionality addresses is when an application needs to write values to the native, non-virtual registry such that those values are created on the client system and are then visible to programs that have access to the native registry (e.g. natively installed applications). While the isolation provided by the VE is normally desired and is a cornerstone of the functionality delivered by App-V, there are cases where an application needs to have read/write access to the native system and update its state. Registry pass-through functionality provides the ability to write-through, or pass-through, registry operations from applications running inside the VE. Values that are written to pass-through locations from inside the VE can subsequently be used by other applications. Declaring a pass-through Pass-through keys are defined in the following location on the client system: HKLM\Software\[Wow6432Node\]Microsoft\Softgrid\4.5\SystemGuard\Overrides\VirtualRegistryPassThroughEx The VirtualRegistryPassThroughEx key should contain REG_MULTI_SZ type values identifying the registry keys on the client that should be accessed natively by an application in the VE. Examples: HKEY_LOCAL_MACHINE\Software\Microsoft\DirectDraw HKEY_CURRENT_USER\Software\Microsoft\ActiveMovie\devenum All registry values read or written at these levels, or anywhere in the tree underneath, will go to the native