Archive

Archive for September, 2011

MED-V 1.0: Unhandled Exception when running the VM Prerequisite Wizard

September 20, 2011 Leave a comment

If you are still using MED-V v1, you may run into this issue when you are running the VM pre-requisites utility on the Windows XP image:

“Unhandled exception has occured in your application. If you click Continue, the application will ignore this error and attempt to continue. if you click Quit, the application will close immediately.”

“Critical error.”

Details will show the following:

************** Exception Text **************
System.Management.ManagementException: Critical error
   at System.Management.ThreadDispatch.Start()
   at System.Management.ManagementScope.Initialize()
   at System.Management.ManagementObject.Initialize(Boolean getObject)
   at System.Management.ManagementClass.GetInstances(EnumerationOptions options)
   at System.Management.ManagementClass.GetInstances()
   at Kidaro.VMPreparation.PreparationUtils.IsMasterDriveSCSI()
   at VMPreparationTool.VMPreparationToolActivator.Activate()
   at VMPreparationTool.VMPreparationToolForm.OnApplyClicked(Object sender, EventArgs e)
   at VMPreparationTool.VMPreparationToolControl.ApplyClickHandler(Object sender, EventArgs e)
   at System.Windows.Forms.Control.OnClick(EventArgs e)
   at DevExpress.XtraEditors.BaseButton.OnClick(EventArgs e)
   at DevExpress.XtraEditors.BaseButton.OnMouseUp(MouseEventArgs e)
   at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at DevExpress.XtraEditors.BaseControl.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.OnMessage(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(IntPtr hWnd, Int32 msg, IntPtr wparam, IntPtr lparam)

This is caused by a corrupt WMI repository.

You will also see the following in the event logs:

“WMI ADAP was unable to process the performance libraries: 0x80041001” and/or “WMI ADAP failed to connect to namespace \.rootcimv2 with the following error: 0x8004100a”

if this has happened, you will need to run the WMI Diagnosis utility for Windows XP to find out what may be wrong with the repository. You can download it here:

http://www.microsoft.com/downloads/en/details.aspx?familyid=d7ba3cd6-18d1-4d05-b11e-4c64192ae97d&displaylang=en

If necessary, you may need to rebuild the WMI repository although this should only be done as a last resort.

Click Start, Run and type the following command:

rundll32 wbemupgd, UpgradeRepository

This command is used to detect and repair a corrupted WMI Repository. The results are stored in the setup.log (%windir%system32wbemlogssetup.log) file.

 

Advertisements
Categories: Uncategorized Tags: , , , , ,

App-V: Error when you attempt to launch an application: xxxxxx-xxxxxx0a-00000124

September 20, 2011 Leave a comment

Scenario:

Users receive the following error message when attempting to launch an application virtualized by App-V:

The Application Virtualization Client could not launch APPLICATION_NAME”
This action cannot continue because the package must be upgraded. Shutdown all the application that are part of this package and try again.
 
Error code: xxxxxx-xxxxxx0a-00000124

This error can occur under one of the following conditions:

1. An application was left running during an App-V management server upgrade from a pre-4.5 version to 4.5 or later. During an App-V upgrade, the client will continue to operate in disconnected operations mode using cached authorizations. Susbsequent cached launches will resume in online mode post upgrade. It is at this point you may see the above error message.

2. A new version of the application is currently advertised via a ConfigMgr 2007 (SCCM) virtual advertisement that has not been downloaded/streamed yet.

In the case of #1 being the issue, rebooting the computer and/or restarting the App-V client service may clear up the problem.  If that does not work then running the following command should resolve the issue:

      SFTMIME UNLOAD APP:application

Unloading the application in the Client UI will also suffice.

In the case of #2 being the issue, verifying through configuration manager the status of the updated package advertisement is an important step. Bear in mind that if you are currently working on a Terminal Server/RDS Server running the App-V client managed by Config manager, any instances of the application currently launched and in use will need to be shut down first.

Check polling policies, CCM cache, maintenance window settings, etc. as well.

Also note that the error string differs from a similar error with the exact same code:

This application cannot be imported because it is in use.

Close all instances of this application and any others that use the same package, and then try again.

Error code: xxxxxx-xxxxxx0A-00000124

Categories: Uncategorized Tags: , , ,

App-V: Beyond Trust unable to Trigger SFTTRAY /REFRESHALL under different user context

September 15, 2011 Leave a comment

I recently dealt with an issue where a customer had several machines attempting to perform a non-interactive DC Refresh via a third-party program. This program called Beyond Trust was failing with the following error in the SFTLOG.TXT:

[03/23/2011 13:52:50:127 SRVC ERR] {tid=1654:usr=steveth}
Failed to open connecting process handle to track process termination (PID 7604, error 5).

NOTE: This does not have to happen with just this particular program. This could also occur with any program that attempts to process this command under the context of a user account (with or without UAC disabled.)

ALSO NOTE: This is not to be confused with the similar process termination error (997.)

Simple elevation to the user’s context will not suffice. The call to refresh against the server will still need to be called from the credentials of the targeted user account in which it must be able to also call SFTDCC at the same time.

The best resolution to this issue would likely be to use something such as the built-in Scheduled Tasks within Windows to achieve offline non-interactive refreshes against the App-V server. Then simply create and distribute the *.job file for this.

Specific information related to the SchTasks command is found here:

http://msdn.microsoft.com/en-us/library/bb736357(VS.85).aspx

SCVMM: Avoid STOP 07XB Issues Post-P2V Migration by Ensuring Registry Hooks to Physical Storage Filters are Removed

September 13, 2011 Leave a comment

Sometimes P2V migrations fail in SCVMM after the 70% completion phase. This is usually post copy/post virtualization fixup. This could also be a situation where it seems the job is hanging at 70% in the VMM console.  Another symptom that might be noticed would be that the P2V job has completed w/ Info. Often you will see this error:

Warning (13210)

Timeout occurred while waiting for VM integration services to be installed on virtual machine <name> residing on host <host>

Recommended Action

Ensure that the version of the VM integration services binaries matches the version of the guest operating system in the virtual machine and then try again.

The issue can be confirmed by starting the VM in Hyper-V. This will show it crashing upon bootup with a STOP 0x7B error. This may occur if certain registry entries that are added by 3rd-party storage providers or physical hardware providers when these were installed are not removed because the software was not uninstalled prior to P2V process, the software was installed but these settings were not removed prior to P2V, or these were not removed during the P2V fixup phase. These registry entries are preventing your computer from starting correctly.

When this happens, you can do one of two things. Prior to P2V on the source machine search your registries for “UpperFilters” and “LowerFilters.” You can usually track down culprits of post P2V STOP 0x7B’s this way.

For example, you may find the following:

HKLMSYSTEMCurrentControlSetControlClass{71A27CDD-812A-11D0-BEC7-08002BE2092F}

UpperFilters = snapman timounter

Or

HKLMSYSTEMCurrentControlSetControlCriticalDeviceDatabasegendisk

LowerFilters = ZetSFD

Simplay removing these values prior to running a P2V, will resolve the issue although this could be time consuming. You could also mount the VHD in another OS (such as Windows 7 or Windows Server 2008 R2) and load the hives. Then you can search and make the same changes. Bear in mind, you will need to make sure the right ControlSet hive is actually modified (check HKEY_LOCAL_MACHINESYSTEMSelect first) or modify all ControlSets.

App-V 4.6SP1: Issue with Sequencing the Dynamics NAV 2009 R2 Client

September 9, 2011 3 comments

There is an issue that currently being investigated by the App-V support team regarding virtualization of the Microsoft Dynamics NAV 2009 R2 client with the new App-V 4.6 SP1 sequencer. It appears the issue is tied to the Classic Client more and not the Role-Tailored client. In addition to the workflow being slightly different from the workflow outlined here:

http://msdn.microsoft.com/en-us/library/gg670188.aspx

The Role-Tailored client will also need to be sequenced using a VFS path rather than an SFT mount (MNT) path. You will need to change this part of your recipe:

Section: “To run Microsoft Dynamics NAV 2009 R2 Setup”

In Step 5: Do not specify the destination directory. Use the default directory.

It is also recommended to install the  Visual C++ 2008 SP1 run-time module on the Sequencer in advance.

Package Accelerators

There may be a maximum path limitation being hit preventing the creation of a package accelerator resulting from a VFS installation. This is caused by 3 factors: 1.) Lengthy paths created by the Dynamics installation. 2.) The package accelerator creation process adding additional 7 characters to the package root. 3.)  If the sequencing machine is a single volume machine where the Q: drive is actually a substitution.

You can work around this by creating a second partition for the Q: drive on the sequencing workstation.

Error when you Attempt to Delete a Package using the XenApp Connector for Configuration Manager 2007 R2

September 7, 2011 Leave a comment

The following issue may occur when you are using the XenApp Connector for Configuration Manager 2007. When you click to delete a package under the System Center Configuration Manager node – Site Database – Computer Management – Software Distribution – XenApp Publications, you get the following error:

ConfigMgr cannot delete the specified object. Please verify that you have delete access to the selected object and refresh the ConfigMgr Administrator console to verify that another administrator has not moved or deleted the object.

This error occurs in spite of the permissions being correct. In addition, the SmsAdminUI.log will show the following error:

  [3][8/31/2011 1:21:04 PM] :Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlQueryExceptionrnFailure deleting management objectrn   at Microsoft.ConfigurationManagement.ManagementProvider.WqlQueryEngine.WqlResultObject.Delete(ReportProgress progressReport)

   at Microsoft.ConfigurationManagement.AdminConsole.ConsoleView.ConsoleFormView.DeleteResultItems(Object sender, ActionDescription actionDescription, Status status, IResultObject selectedResultObject, PropertyDataUpdated dataUpdatedDelegate)rnConfigMgr Error Object:

instance of SMS_ExtendedStatus

{

      CauseInfo = “4”;

      Description = “CSspPkgProgram: Unknown offer error!”;

      ErrorCode = 2152205061;

      File = “c:\qfe\nts_sms_fre\sms\siteserver\sdk_provider\smsprov\ssppkgprogram.cpp”;

      Line = 541;

      Operation = “DeleteInstance”;

      ParameterInfo = “SMS_Program.PackageID=”SBT00153″,ProgramName=”Microsoft Office Professional 2007″”;

      ProviderName = “WinMgmt”;

      StatusCode = 2147749889;

This can happen if the assets related to this XenApp package are deleted but the database record has not been deleted. These packages are stored in the same manner as other packages and advertisements. You can connect to the SQL Configuration Manager database and  run a SQL statement to delete these records. You will need to know the Advertisement and Package ID’s.  You can find this information out for sure by running a SQL Profiler trace while reproducing the issue as shown in the following profiler trace output:

 

Once you know what needs to be removed, you will need to run the SQL scripts to remove the entries. If you only need to worry about the package, we can simply ignore the advertisement steps and use the package steps.

To remove the stale advertisements, run the following SQL statement:

Select * from programoffers where offerid = ‘advertismentID’

Delete from programoffers where offerid = ‘advertismentID’

 – where advertisementID refers to the ID you found in the above trace.

To remove the stale packages, run the following SQL statement:

Select * from smspackages where pkgid = ‘PackageID’

Delete from smspackages where pkgid = ‘PackageID’

 – where PackageID refers to the ID you found in the above trace.

Once these are deleted, additional SQL triggers will remove the other remaining references and entries related to these records in other tables.

Categories: Uncategorized Tags: , , , , ,