S-071159 Full Solution

 

S-071159:: When I publish a report in the SOLIDWORKS® Simulation software, software, S-071159 why do I receive the error 'SolidWorks Simulation is unable to create a report because it failed to instantiate Microsoft Word’? The SOLIDWORKS® Simulation software is not able to communicate with the Microsoft® Word application on your system. Publication of SOLIDWORKS Simulation reports depends on the resource file 'MSWORD.OLB' and the associated registry entries. If there is an issue with this file or with the registry entries, programs such as SOLIDWORKS Simulation are unable to run Microsoft Office to send study data to the report. This issue can occur if you roll back to an older version of the Office software after installing a newer version. To resolve this issue, first determine if your version of the SOLIDWORKS software supports the version and software package type of your Microsoft Office installation. Contact your IT department to verify that you have a complete and valid installation. It might be possible to resolve this issue by uninstalling the Microsoft Office products. However, if you do not want to do this, try the t he following steps to correct your Microsoft Office environment without uninstalling the Microsoft Office software. CAUTION: Before attempting this procedure, be sure to consult your IT department. 1.  2.  3.  4.  5.  6. 

7.  8.  9.  10.  11. 

12. 

13.  14.  15.  16. 

To avoid potential problems with your system, create a full backup of the registry. Exit all Microsoft Office programs. Open Windows Task Manager and verify that t hat the 'winword.exe' process does not appear in process details. If it does, select each instance of that process and then click on 'End Task'. Open the Microsoft Word application. In Windows Task Manager, right-click on the 'winword.exe' process > 'Open File Location'. In the Windows Explorer dialog box of the Microsoft Word installation folder that appears, verify that the file 'MSWORD.OLB' exists. If you do not see this file, contact your IT department to verify the version, license, and installation integrity of your Microsoft Office installation. Be sure to check the current system requirements on the official SOLIDWORKS website. Copy the file path in the address bar of the Windows Explorer window. For example, the default file path for the Microsoft Office 2016 64-bit version is 'C:\Program Files\Microsoft Office\Office 16'. Run 'regedit' to open the Registry Editor. In the Registry Editor, browse to: 'HKEY_CLASSES_ROOT\TypeLib\{00020905-0000-0000-C000-000000000046}' Locate and expand the subfolder for the highest version number that is available. For example, '8.7' for the Microsoft Office 2016 64-bit version. If you see multiple subfolder entries, such as '8.7' and '8.6', you must select the '8.7' entry because it is highest version. Browse to the subfolder of the highest version subfolder that contains a registry string (REG_SZ) with the path to file 'MSWORD.OLB'. For example: 'HKEY_CLASSES_ROOT\TypeLib\{00020905-0000-0000-C000-000000000046}\8.7\0\win64' Modify the registry entry and paste the full path to the MSWORD.OLB file on your system. For example, 'C:\Program Files\Microsoft Office\Office 16\MSWORD.OLB' 16\MSWORD.OLB' for Microsoft Office 2016 64-bit. 64 -bit. Note that the exact file name and extension (MSWORD.OLB) must appear at the end of the path. In the Registry Editor, browse to: 'HKEY_LOCAL_MACHINE\SOFTWARE 'HKEY_LOCAL_MACHIN E\SOFTWARE\Classes\Typ \Classes\TypeLib\{00020905-0000-0000-C000-000000000046}' eLib\{00020905-0000-0000-C000-000000000046}' Repeat steps 10 through 12. Close the Microsoft Word application and then ensure that the t he 'winword.exe' process does not appear in Windows Task Manager. Try again to publish a SOLIDWORKS Simulation report.

Page 1 of 2

©2016 Dassault Systèmes SolidWorks Corporation 

 

  If the issue persists, follow these steps to provide additional information to your support representative: 1. 

Open the Microsoft Word application and go to ‘Account’ > ‘About Word’. Capture a screenshot that is similar to the attached image. 2.  Run 'regedit' to open the Registry Editor. 3.  In the Registry Editor, export the following registry keys. 'HKEY_LOCAL_MACHINE\SOFTWARE E\SOFTWARE\Classes\Type \Classes\TypeLib\{00020905-0000-0000-C000-000000000046}' Lib\{00020905-0000-0000-C000-000000000046}' •  'HKEY_LOCAL_MACHIN •  'HKEY_CLASSES_ROOT\TypeLib\{00020905-0000-0000-C000-000000000046}' 4.  Rename the file extensions to .txt. 5.  6.  7.  8. 

Provide the files to your support representative. State the last time that you successfully published a SOLIDWORKS Simulation Report on this system (if ever). Ask your IT department to investigate and list the installation history of Microsoft Office products and updates on your system. If possible, try to using a different computer at your location to publish a SOLIDWORKS Simulation Report. Create a SOLIDWORKS Rx Problem Capture with a video that depicts the issue.

Page 2 of 2

©2016 Dassault Systèmes SolidWorks Corporation