locked
Word 2007 and Windows 7 RRS feed

  • Question

  • When opening a document from My Documents, first I am asked if I want to give MS Word permission to make changes on my computer. Then an error message, without a code, "There is a problem sending the commandto the program." To use Word I have to start the program and then open a file. I did not have this problem with Win 7 Beta.

    I have run the troubleshooter and checked for compatability. Each time it detects a problem but no fix has worked.

    I have uninstalled Office 2007, re-installed, repaired and have installed Office SP2 and nothing has worked.

    Any ideas???
    Wednesday, August 12, 2009 1:45 AM

Answers

  • Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry.

    SYMPTOMS

    When you use Dynamic Data Exchange (DDE) to send commands to Microsoft Office Word 2003, your custom program may not be able to come to the foreground. If you try to switch focus away from the Word 2003 window, Word 2003 will automatically come to the foreground again. You cannot switch from the Word 2003 document or minimize the Word 2003 window while the DDE commands are being sent to Word 2003.

    CAUSE

    This problem occurs because every time that Word 2003 obtains a WM_DDE_EXECUTE message from the calling program, it calls the SetForegroundWindow API to force itself into the foreground. As the DDE caller continues to automate Word 2003 through DDE, you will not be able to switch to another application because Word 2003 will come back into the foreground.

    RESOLUTION

    This problem was first fixed in a hotfix that is now contained in a service pack. If you installed the latest Office 2003 service pack, you do not have to install the hotfix.

     

    Service pack information

    This problem is corrected in Office 2003.

    To resolve this problem, obtain the latest service pack for Office 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:



    After you install the service pack, follow the steps that are listed in the "More Information" section to set the DontJumpForegroundInDDEExec registry key and to enable the hotfix.

    Hotfix information

    How to obtain the hotfix

    This issue is fixed in the Word 2003 Hotfix.For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

    Description of the Word 2003 post-Service Pack 1 hotfix package

    After you install this hotfix, follow the steps that are listed in the "More Information" section to set the DontJumpForegroundInDDEExec registry key and to enable the hotfix.

    STATUS

    Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Office 2003 Service Pack 2.

    MORE INFORMATION

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    To activate this hotfix, follow these steps:

    1.

    Quit Word 2003.

    2.

    Click Start, and then click Run.

    3.

    In the Open box, type regedit , and then click OK.

    4.

    Locate and then click to select the following registry key:

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

    5.

    After you select the key that is specified in step 4, point to New on the Edit menu, and then click DWORD.

    6.

    Type DontJumpForegroundInDDEExec, and then press ENTER.

    7.

    Right-click DontJumpForegroundInDDEExec, and then click Modify.

    8.

    In the Value data box, type 1 , and then click OK.

    9.

    On the File menu, click Exit to quit Registry Editor.

     

    Issues that this fix With package fixes

    This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

    When you try to open a Word 2007 document that has nested XML tags applied to the Word document's content, you may receive the following error message:

    XML has been disabled in the document as the system has become unstable. Close all programs and restart your computer

    In Word 2007, you open a document in a shared network location. Then, you use the Send to Exchange Folder command to send a copy of the document to an Exchange folder. However, when you view the document in the Exchange folder, you see that the document has a Temporary Internet file name instead of the document's original file name.

    Consider the following scenario:

    You save a Word Macro-Enabled Template (*.dotm) file in one of the following STARTUP folders:

    Drive :\Users\ user name \AppData\Roaming\Microsoft\Word\STARTUP

    Drive :\Program Files\Microsoft Office\Office12\STARTUP

    You start an instance of Word 2007.

    When you run the winword.exe /automation command to start a second instance of Word 2007, you may receive the following error message:


    File In Use
    file name is locked for editing by ' user name '. Do you want to:
    Open a Read Only Copy

    Create a local copy and merge your changes later
    Receive notification when the original copy is available

    Note In the error message, file name is the name of the Word Macro-Enabled Template (*.dotm) file that you saved in the STARTUP folder. BUG #:

    MORE INFORMATION

    Hotfix information

    A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

    If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.


    Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

    Prerequisites

    There are no prerequisites for installing this hotfix.

    Restart information

    You do not have to restart the computer after you apply this hotfix.

    Hot fix replacement information

    This hot fix does not replace a previously released hot fix.

    Registry information

    You do not have to make any changes to the registry to apply this hot fix.

     

    This hotfix is scheduled to be included with 2007 Microsoft Office Suite Service Pack 2.

    NOTE - Disclaimer

     

    By using the following materials or sample code you agree to be bound by the license terms below and the Microsoft Partner Program Agreement the terms of which are incorporated herein by this reference. These license terms are an agreement between Microsoft Corporation (or, if applicable based on where you are located, on of its affiliates) and you. Any materials (other than sample code) we provide to you are for your internal use only. Any sample code is provided for the purpose of illustration only and is not intended to be used in a production environment. We grant you a nonexclusive, royalty-free right to use and modify the sample code and to reproduce and distribute the object code form of the sample code, provided that you agree: (i) to not use Microsoft's name, logo, or trademarks to market your software produced in which the sample code is embedded; (ii) to include a valid copyright notice on your software product in which the sample code is embedded; (iii) to provide on behalf of and for the benefit of your subcontractors a disclaimer of warranties, exclusion of liability for indirect and consequential damages and a responsible limitation of liability; and (iv) to indemnify, hold harmless, and defend Microsoft, its affiliates and suppliers from and against any third party claims or lawsuits, including attorney's fees, that arise or result from the use or distribution of the sample code.

    -----

     

    • Edited by Anil Inampudi Thursday, August 13, 2009 5:12 PM
    • Proposed as answer by Anil Inampudi Monday, August 17, 2009 1:59 PM
    • Marked as answer by Andy Song Tuesday, August 18, 2009 11:17 AM
    Thursday, August 13, 2009 4:59 PM

All replies

  • Important This article contains information about modifying the registry. Before you modify the registry, make sure to back it up and make sure that you understand how to restore the registry if a problem occurs. For information about how to back up, restore, and edit the registry.

    SYMPTOMS

    When you use Dynamic Data Exchange (DDE) to send commands to Microsoft Office Word 2003, your custom program may not be able to come to the foreground. If you try to switch focus away from the Word 2003 window, Word 2003 will automatically come to the foreground again. You cannot switch from the Word 2003 document or minimize the Word 2003 window while the DDE commands are being sent to Word 2003.

    CAUSE

    This problem occurs because every time that Word 2003 obtains a WM_DDE_EXECUTE message from the calling program, it calls the SetForegroundWindow API to force itself into the foreground. As the DDE caller continues to automate Word 2003 through DDE, you will not be able to switch to another application because Word 2003 will come back into the foreground.

    RESOLUTION

    This problem was first fixed in a hotfix that is now contained in a service pack. If you installed the latest Office 2003 service pack, you do not have to install the hotfix.

     

    Service pack information

    This problem is corrected in Office 2003.

    To resolve this problem, obtain the latest service pack for Office 2003. For more information, click the following article number to view the article in the Microsoft Knowledge Base:



    After you install the service pack, follow the steps that are listed in the "More Information" section to set the DontJumpForegroundInDDEExec registry key and to enable the hotfix.

    Hotfix information

    How to obtain the hotfix

    This issue is fixed in the Word 2003 Hotfix.For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

    Description of the Word 2003 post-Service Pack 1 hotfix package

    After you install this hotfix, follow the steps that are listed in the "More Information" section to set the DontJumpForegroundInDDEExec registry key and to enable the hotfix.

    STATUS

    Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section. This problem was first corrected in Office 2003 Service Pack 2.

    MORE INFORMATION

    Warning If you use Registry Editor incorrectly, you may cause serious problems that may require you to reinstall your operating system. Microsoft cannot guarantee that you can solve problems that result from using Registry Editor incorrectly. Use Registry Editor at your own risk.

    To activate this hotfix, follow these steps:

    1.

    Quit Word 2003.

    2.

    Click Start, and then click Run.

    3.

    In the Open box, type regedit , and then click OK.

    4.

    Locate and then click to select the following registry key:

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

    5.

    After you select the key that is specified in step 4, point to New on the Edit menu, and then click DWORD.

    6.

    Type DontJumpForegroundInDDEExec, and then press ENTER.

    7.

    Right-click DontJumpForegroundInDDEExec, and then click Modify.

    8.

    In the Value data box, type 1 , and then click OK.

    9.

    On the File menu, click Exit to quit Registry Editor.

     

    Issues that this fix With package fixes

    This hotfix fixes the following issues that are not previously documented in a Microsoft Knowledge Base article:

    When you try to open a Word 2007 document that has nested XML tags applied to the Word document's content, you may receive the following error message:

    XML has been disabled in the document as the system has become unstable. Close all programs and restart your computer

    In Word 2007, you open a document in a shared network location. Then, you use the Send to Exchange Folder command to send a copy of the document to an Exchange folder. However, when you view the document in the Exchange folder, you see that the document has a Temporary Internet file name instead of the document's original file name.

    Consider the following scenario:

    You save a Word Macro-Enabled Template (*.dotm) file in one of the following STARTUP folders:

    Drive :\Users\ user name \AppData\Roaming\Microsoft\Word\STARTUP

    Drive :\Program Files\Microsoft Office\Office12\STARTUP

    You start an instance of Word 2007.

    When you run the winword.exe /automation command to start a second instance of Word 2007, you may receive the following error message:


    File In Use
    file name is locked for editing by ' user name '. Do you want to:
    Open a Read Only Copy

    Create a local copy and merge your changes later
    Receive notification when the original copy is available

    Note In the error message, file name is the name of the Word Macro-Enabled Template (*.dotm) file that you saved in the STARTUP folder. BUG #:

    MORE INFORMATION

    Hotfix information

    A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing this specific problem. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

    If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.


    Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

    Prerequisites

    There are no prerequisites for installing this hotfix.

    Restart information

    You do not have to restart the computer after you apply this hotfix.

    Hot fix replacement information

    This hot fix does not replace a previously released hot fix.

    Registry information

    You do not have to make any changes to the registry to apply this hot fix.

     

    This hotfix is scheduled to be included with 2007 Microsoft Office Suite Service Pack 2.

    NOTE - Disclaimer

     

    By using the following materials or sample code you agree to be bound by the license terms below and the Microsoft Partner Program Agreement the terms of which are incorporated herein by this reference. These license terms are an agreement between Microsoft Corporation (or, if applicable based on where you are located, on of its affiliates) and you. Any materials (other than sample code) we provide to you are for your internal use only. Any sample code is provided for the purpose of illustration only and is not intended to be used in a production environment. We grant you a nonexclusive, royalty-free right to use and modify the sample code and to reproduce and distribute the object code form of the sample code, provided that you agree: (i) to not use Microsoft's name, logo, or trademarks to market your software produced in which the sample code is embedded; (ii) to include a valid copyright notice on your software product in which the sample code is embedded; (iii) to provide on behalf of and for the benefit of your subcontractors a disclaimer of warranties, exclusion of liability for indirect and consequential damages and a responsible limitation of liability; and (iv) to indemnify, hold harmless, and defend Microsoft, its affiliates and suppliers from and against any third party claims or lawsuits, including attorney's fees, that arise or result from the use or distribution of the sample code.

    -----

     

    • Edited by Anil Inampudi Thursday, August 13, 2009 5:12 PM
    • Proposed as answer by Anil Inampudi Monday, August 17, 2009 1:59 PM
    • Marked as answer by Andy Song Tuesday, August 18, 2009 11:17 AM
    Thursday, August 13, 2009 4:59 PM
  • I downloaded Office 2007 SP2 and it had no effect. C ould this be a permissions issue? Each time you open a document from the file location you are asked if you want to allow the program to make changes to your computer. I have checked all the other Office 2007 programs and none of them ask for this permission.

    Thanks in advance.
    Friday, August 14, 2009 6:17 AM
  • Hi,

    Thank you for contacting the Microsoft site.

     

    Try the following:

     

    Method 1: Change File Type Association Directly from the File Properties

     

    1. Right click on a file with the type or extension that want to change its associated application program.
    2. Select Properties on right click context menu.
    3. In the General tab, click on Change button.
    4. An Open With window will appear. Choose a program to open the kind of file from the list of programs available. By default, Recommended Programs is automatically expanded. However, there is more detected programs in the section of Other Programs, which can be expanded to select by clicking on Down Arrow at the end of the separator line.
      If the program that want to used as the default program does not found, click
      Browse to select an executable file manually.
    5. Click OK button.

     

    Method 2: Change File Type Association Directly On The Fly

     

    Note that this method works if only several programs have been used to open and run a kind of file type extension previously.

     

    1. Right click on a file with the type or extension that want to change its associated application program.
    2. Point to Open With on right click context menu, and then select Choose Default Program.
    3. An Open With window will appear. Choose a program to open the kind of file from the list of programs available. By default, Recommended Programs is automatically expanded. However, there is more detected programs in the section of Other Programs, which can be expanded to select by clicking on Down Arrow at the end of the separator line.
      If the program that want to used as the default program does not found, click
      Browse to select an executable file manually.
    4. Check and tick the checkbox for Always use the selected program to open this kind of file option.
    5. Click OK button. The file association will be set, and the file or document will be opened using the new default program automatically.

     

    Method 3: Assign New File Association via Windows Vista Set Associations

     

    1. Open Control Panel. Then go to Programs and click Make a file type always open in a specific program.
      Alternatively, in the
      Classic View, open Default Programs and then click Associate a file type or protocol with a program.
    2. In the Set Associations folder, locate and highlight a file type by extension or protocol, and then click on Change Program button.
    3. An Open With window will appear. Choose a program to open the kind of file from the list of programs available. By default, Recommended Programs is automatically expanded. However, there is more detected programs in the section of Other Programs, which can be expanded to select by clicking on Down Arrow at the end of the separator line.
      If the program that want to used as the default program does not found, click
      Browse to select an executable file manually.
    4. Click OK button.

     

    I suggest we run a System File Checker which scans for and attempts to fix corrupted System files. - below are the instructions and have Vista Disc ready:

    Running the System File Checker

    1. Click Start, click All Programs, click Accessories, right-click Command Prompt, and select Run as Administrator.
    2. Click Continue or supply Administrator credentials if prompted.
    3.  In the Command Prompt window type the following, and press:  Enter:sfc /scannow
    4.  You should see the following on-screen messages:
      1. Beginning the system scan. This process will take some time.
      2. Beginning verification phase of system scan.
      3. Verification % complete
    5.   Once the scan has completed you will receive an onscreen message resembling one of the following:
      1. …found no integrity violations
      2. found corruption but repaired it
      3. found corruption that it could not repair
    6.  Please reply with the completion message that you received.

     

    This should resolve your problem.

     

    Let us know if these steps resolve your problem.  I hope the information is useful.

     

    Soluton 2:

    Please try to run Microsoft Office Diagnostics to in case this is caused by Office Client.

     

    To start the Microsoft Office Diagnostics program in Excel 2007, follow these steps:

     

    1.    Click the Office button.

    2.    Click the Excel Options button.

    3.    Click Resources.

    4.    Click the Diagnose button.

    5.    Click Continue, and then click Run Diagnostics.



     

    If this cannot solve your issue, could you please verify whether the two users have the same issue when logged on other machines?

     

    Hope the information can be helpful and you can find the more relavent information regarding Diagnostics.
    http://office.microsoft.com/en-us/help/HA012340761033.aspx.


    NOTE - Disclaimer

     

    By using the following materials or sample code you agree to be bound by the license terms below and the Microsoft Partner Program Agreement the terms of which are incorporated herein by this reference. These license terms are an agreement between Microsoft Corporation (or, if applicable based on where you are located, on of its affiliates) and you. Any materials (other than sample code) we provide to you are for your internal use only. Any sample code is provided for the purpose of illustration only and is not intended to be used in a production environment. We grant you a nonexclusive, royalty-free right to use and modify the sample code and to reproduce and distribute the object code form of the sample code, provided that you agree: (i) to not use Microsoft's name, logo, or trademarks to market your software produced in which the sample code is embedded; (ii) to include a valid copyright notice on your software product in which the sample code is embedded; (iii) to provide on behalf of and for the benefit of your subcontractors a disclaimer of warranties, exclusion of liability for indirect and consequential damages and a responsible limitation of liability; and (iv) to indemnify, hold harmless, and defend Microsoft, its affiliates and suppliers from and against any third party claims or lawsuits, including attorney's fees, that arise or result from the use or distribution of the sample code.

     

     

    Tuesday, August 18, 2009 12:50 PM
  • I ran into this problem and was befuddled for a couple years.

    I found the answer by switching excel into compatibility mode for XP, which caused the same symptoms.

    1. I get the warning "do you want to allow this program to make changes on this computer?" at each start-up

    2. clicking files opens MS word, but the file will not open. An error message stating "Windows encountered an error sending the file" or something similar.

    The cure: Right-click on the program from the start menu. Choose "properties" at the bottom.

    A number of tabs will appear, including: "Compatibility"

    Click on the compatibility  tab, un-click the "compatibility mode" dialog box, then click "apply" and then OK

    Everything returned to normal when I did that.

    Sunday, September 14, 2014 3:01 PM