Problems that you may experience when you try to use Microsoft App-V (SoftGrid) to sequence Microsoft Office programs in Microsoft Windows 2000, Windows XP, or Windows Server 2003

Article translations Article translations
Article ID: 931914 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

When you try to use Microsoft App-V (SoftGrid) to sequence Microsoft Office programs on a computer that is running Microsoft Windows 2000, Windows XP, or Windows Server 2003, you may experience one or more of the following problems:
  • Problem 1: When the administrator tries to start a Microsoft Office program by using the Launch Application screen of the Sequencing Wizard, the Office program crashes. When Office applications are launced in the sequencer and on the App-V (SoftGrid) client. you receive the following events in the event log:

    Event Type: Error
    Event Source: Application Error
    Error Event Category: None
    Event ID: 1000
    Description: Faulting application powerpnt.exe, version 11.0.6564.0, faulting module kernel32.dll, version 5.1.2600.3119, fault address 0x00012a5b. For more information, see Help and Support Center at <http://go.microsoft.com/fwlink/events.asp>.
    Data:
    0000: 41 70 70 6c 69 63 61 74 Applicat
    0008: 69 6f 6e 20 46 61 69 6c ion Fail
    0010: 75 72 65 20 20 70 6f 77 ure pow
    0018: 65 72 70 6e 74 2e 65 78 erpnt.ex
    0020: 65 20 31 31 2e 30 2e 36 e 11.0.6
    0028: 35 36 34 2e 30 20 69 6e 564.0 in
    0030: 20 6b 65 72 6e 65 6c 33 kernel3
    0038: 32 2e 64 6c 6c 20 35 2e 2.dll 5.
    0040: 31 2e 32 36 30 30 2e 33 1.2600.3
    0048: 31 31 39 20 61 74 20 6f 119 at o
    0050: 66 66 73 65 74 20 30 30 ffset 00
    0058: 30 31 32 61 35 62 0d 0a 012a5b..

  • Problem 2: When you start a Microsoft Office program on the App-V (SoftGrid) client, the Activation Wizard appears
  • Problem 3: When you start a Microsoft Office program on the App-V (SoftGrid) client, you receive the following error message:
    This application is not configured for this operating system
  • Problem 4: When you start a Microsoft Office program on the App-V (SoftGrid) client, the Windows Installer dialog box appears
  • Problem 5: When you start a Microsoft Office program on the App-V (SoftGrid) client, you receive a "0x000000C2" error on a blue screen or the client consumes all the open file handles to a network-redirected Application Data directory
  • Problem 6: When you start a Microsoft Office program on the App-V (SoftGrid) client for the first time, you are not prompted to type your name and initials
  • Problem 7: When you start Outlook on the App-V (SoftGrid) client, the following Outlook performance counter messages are logged in the event log:

    Event ID: 3003
    Type: Error
    Source: LoadPerf
    Description: The SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib key could not be opened or accessed in order to install counter strings. The Win32 status returned by the call is the first DWORD in Data section.

    Event ID: 3009
    Type: Error
    Source: LoadPerf
    Description: Installing the performance counter strings for service Outlook (Outlook) failed. The Error code is the first DWORD in Data section.

    Event ID: 1000
    Type: Information
    Source: LoadPerf
    Description: Performance counters for the Outlook (Outlook) service were loaded successfully. The Record Data contains the new index values assigned to this service.

  • Problem 8: You try to exit a Microsoft Office program on the App-V (SoftGrid) client. However, the program does not completely exit.
  • Problem 9: After you save the Softricity file from the App-V (SoftGrid) Sequencer, this file is several hundred megabytes larger than expected.
  • Problem 10: When starting Word on the App-V (SoftGrid) client, users may see a Windows Installer pop-up and/or the following error:

    Word has detected a problem with some of the current preferences

RESOLUTION

Important This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
322756 How to back up and restore the registry in Windows

Resolution for Problem 1

To resolve this problem, set two registry values before you start the sequencer. To do this, follow these steps:
  1. Exit the Sequencer.
  2. Start Registry Editor.
  3. Open the following registry subkey:
    HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer
  4. Right-click
  5. Right-click Installer, point to New, and then click DWORD Value.
  6. Type DisableRollback, and then press ENTER.
  7. Right-click DisableRollback, and then click Modify.
  8. In the Value Data box, type 1, and then click OK.
  9. Right-click Installer, point to New, and then click DWORD Value.
  10. Type MaxPatchCacheSize, and then press ENTER.
  11. Exit Registry Editor.
  12. Start the Sequencer.
  13. Open the sequence, and then perform the upgrade as usual.
After you follow these steps, the upgrade may fail, and you may receive the following error message:
Error 25090. Office Setup encountered a problem with the Office Source Engine, system error: -2147023836. Please open SETUP.CHM and look for "Office Source Engine" for information on how to resolve this problem.
If you receive this error message, follow these steps:
  1. When you run the Installation Wizard, during the Monitoring stage, start Setup by using the original installation media.
  2. After the Setup window appears, cancel Setup, and then respond to the prompts to exit Setup.
  3. Perform the upgrade as usual.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
827467 "Error 25090" error message when you start an Office program

Resolution to Problem 2

To resolve this problem, the administrator should use a product key that disables activation when you install (sequence) Microsoft Office by using the App-V (SoftGrid) Sequencer.

Resolution to Problem 3

To resolve this problem, upgrade the App-V (SoftGrid) client to version 3.2.0.311 or a later version. If you cannot upgrade, work around this problem by creating the following directories locally on the App-V (SoftGrid) client:
  • %CommonProgramFiles%\Microsoft Shared\Office11
  • %CommonProgramFiles%\System\MSMAPI\1033
Do this manually or by using the PRE LAUNCH script in the .osd file.

Note To create the directories, you must have the correct file permissions.

To do this, follow these steps:
  1. Open the .osd file in a text editor.
  2. Make the following changes to the <SCRIPT> element and to the child elements within the <DEPENDENCY> element:
    <DEPENDENCY>
      <SCRIPT TIMING="PRE" EVENT="LAUNCH" PROTECT="FALSE" WAIT="TRUE">
        <HREF>%SystemRoot%\system32\cmd.exe /c md "%CommonProgramFiles%\Microsoft Shared\Office11"</HREF>
      </SCRIPT>
      <SCRIPT TIMING="PRE" EVENT="LAUNCH" PROTECT="FALSE" WAIT="TRUE">
        <HREF>%SystemRoot%\system32\cmd.exe /c md "%CommonProgramFiles%\System\MSMAPI\1033"</HREF>
      </SCRIPT>
    </DEPENDENCY>
  3. Save the .osd file, and then exit the text editor.

Resolution to Problem 4

To resolve this problem, follow these steps:
  1. On the Customize Office Configuration screen of Microsoft Office Setup, make one of the following selections for each available feature:
    • Run from My Computer
    • Not Available
    Important Do not select Install on First Use.
  2. In the Installation Wizard, during the monitoring phase, copy the CD\Pro11.msi file to the Package Root Directory\Path\Office11 folder.

    Note Do not sequence to drive O or drive X.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
930995 Some applications fail to sequence to specific drive letters

Resolution to Problem 5

When the Application Data folder is redirected to a network location, the client can consume all open file handles for the file server. This occurs when Office 2003 creates temporary .dta files in the Application Data directory. To resolve this problem, configure the Sequencer to exclude the %Csidl_Windows%\Debug directory before you create the sequence.
  1. On the Tools menu, click Options.
  2. Click the Exclusion Items tab.
  3. Click New.
  4. In the Exclude Path box, type %Csidl_Windows%\Debug.
  5. In the Mapping Type list, select VFS, and then click OK.
  6. Click Save As Default, click Yes, and then click OK.

Resolution to Problem 6

During sequencing, Office obtains the name and initials from the user who performs the sequence. To configure Office to prompt the user for this information the first time that they start the program, the Registry values that contain this information must be removed from the Virtual Registry.
  1. Click the Virtual Registry tab.
  2. Expand REGISTRY, expand User, expand %SFT_SID%, expand Software, expand Microsoft Office 11.0, expand Common, and then expand UserInfo.
  3. Right-click and delete the following values:

    Company
    UserInfo
    UserInitials
    UserName

Resolution to Problem 7

To resolve this problem, follow these steps:
  1. Click the Virtual Registry tab.
  2. Expand REGISTRY, expand Machine, expand System, expand CurrentControlSet, and then expand Services.
  3. Right-click Outlook, and then click Delete.

Resolution to Problem 8

Ctfmon.exe provides text services and input languages. If the operating system and Office sequence both contain Ctfmon.exe, two instances of Ctfmon.exe will run. This may confuse the user. We recommended that you remove Ctfmon.exe from the sequence. However, this is not required. To remove Ctfmon.exe from the sequense, you must make some install features unavailable. From the Set Feature Installation Status screen of the Office installation, configure the following install features as Not Available, as Not Available, or as Hidden, Locked.
Collapse this tableExpand this table
ProductInstall feature
Microsoft Office AccessDatabase Replication
Calendar Control
Microsoft Office ExcelText to Speech
Microsoft Office OutlookCollaboration Data Objects
Schedule Plus
Microsoft Office PowerPointPackage for CD and PowerPoint Viewer
Microsoft Office WordRepair Broken Text
Office Shared FeaturesAlternative User Input
Digital Certificate for VBA Projects
Microsoft Handwriting Component
International Support
all Office Assistants except Logo
New and Open Office Document Shortcuts
Office 2003 Web Components
Spanish Proofing Tools
French Proofing Tools
Microsoft Office Download Control
Office ToolsMicrosoft Forms 2.0 .NET Programmability Support
Smart Tag .NET Programmability Support
Microsoft Office Picture Manager
Language Settings Tools
Microsoft Office Binder Support
Windows SharePoint Services Support
Research Explorer Bar
Smart Tag Plugins
System Information
For more information about Ctfmon.exe, click the following article number to view the article in the Microsoft Knowledge Base:
282599 Frequently asked questions about Ctfmon.exe

Resolution to Problem 9

To resolve this problem, we recommend that you remove the Local Install Source from the package. Doing this reduces the size of the .sft file. To remove the Local Install Source, do one of the following:
  • During the Office installation, from the Setup Completed screen, click to select the Delete installation files check box, and then click Finish.
  • When you create an .mst file, when the Modify Setup Properties screen appears, add a Property Name that is named Removecacheonly. Give it a value of 1.
  • Before you install Office, modify the Setup.ini file. Add REMOVECACHEONLY=1 to the Cache section.
For more information about the Local Installation Source (Msocache), click the following article numbers to view the articles in the Microsoft Knowledge Base:

825933 - Local Install Source (Msocache)

830168 - Frequently asked questions about the Local Install Source feature in Office 2003


Resolution for Problem 10

To resolve this problem, during sequencing, after the Office 2003 installation completes, open the registry and locate the following key:

HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\Word\Options

Add a DWORD value named NoRereg and set it to 1, then stop monitoring and launch winword.

MORE INFORMATION

You can create a Windows Installer transform (.mst) file to guide the Office installation. You can create this file by using the Custom Installation Wizard that is in the Microsoft Office 2003 Resource Kit. To download this kit, visit the Microsoft Download Center.

You can apply the .mst file to the installation as shown in the following example:
%SystemRoot%\system32\msiexec.exe /i <CDROM>\pro11.msi TRANSFORMS=PATH\FILENAME.mst /qb+

Properties

Article ID: 931914 - Last Review: June 22, 2011 - Revision: 7.0
APPLIES TO
  • Microsoft Application Virtualization for Terminal Services
  • Microsoft Application Virtualization for Windows Desktops
  • Microsoft Application Virtualization 4.6 for Terminal Services
  • Microsoft Application Virtualization 4.6 for Windows Desktops
  • Microsoft Application Virtualization 4.5 for Terminal Services
  • Microsoft Application Virtualization 4.5 for Windows Desktops
Keywords: 
kbtshoot kbexpertiseinter KB931914

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com