Returns the Microsoft Word globally unique identifier (GUID) as a String. (Inherited from _Application.) PutFocusInMailHeader: Places the insertion point in the To line of the mail header if the document in the active window is an e-mail document. (Inherited from _Application.) Quit: Quits Microsoft Word and optionally saves or routes the open. Nov 12, 2018 - Office.Interop.Word, Version=13.0.0.0. The error that you get about missing interop files is usually the result of Office 2010.Net Programmability.
Important: If a Download/Install update prompt appears every time you open QSW or shows up after updating, select Cancel to open QSW. Solution 3: Change the Windows settings. Change user settings (for Windows 7 only):. Make sure you are not running QuickBooks or Excel as an Administrator. Right-click the version of QuickBooks and/or Excel you are using from the Programs menu, then select Properties.
Go to the Compatibility tab and make sure no boxes are checked. Solution 4: Make sure Excel is compatible QuickBooks Statement Writer 2014 and later versions are compatible with Microsoft Excel 2007, 2010 (32-bit), and 2013.
Check Microsoft article to know which version you have. Solution 5: Change the way you access the.QSM file. If you cannot open your QSW data file (.QSM) over a network, save the file locally.
If you are unsure whether the problem is with your QSW file or not, on the same computer, access the QSW file while using a different company file (.QBW). If the file opens, try some basic Solution 6: Refresh QSW's access permission.
From the Edit menu, choose Preferences. Select Integrated Applications on the left pane, then go to Company Preferences tab.
Choose QuickBooks Statement Writer, then select Remove. Close then relaunch your QuickBooks Desktop. Open the Statement Writer. Solution 7: Run the QuickBooks Statement Writer Diagnostics. From the Statement Writer Welcome Page, select Preferences & Formats. Select Run Diagnostics Now.
Follow the wizard to diagnose and fix any problems listed. Solution 8: Review the.log file.
Go to the location of the file: C: ProgramData Intuit Statement Writer. Note: You may need to if the folder is not appearing. Open the iswYYYY.log (where 'YYYY' is the year, such as isw2018.log).
This file shows user activity and errors that have occurred. Look at the very bottom of the.log file to determine what is causing the error, then refer to our to get detailed steps on how to resolve it. Solution 9: Edit the QBDSK.INI file This solution also resolves QuickBooks SDK invalid result error when creating a new report in QuickBooks Statement Writer.
Go to the location of the file C: ProgramData Intuit QuickBooks QBDSK.INI. Right-click the QBDSK.INI file, choose Open with then select Notepad.
Add the following: Log Level=verbose UnlimitedSize=Y Parser DumpRequestData=Y SdkAccelerator=N. Save the changes by going to File, then Save in Notepad. Restart QuickBooks.
Note: This step turns on logging and may affect performance the longer it is enabled. For specific issues.
Display issues If you are having problems with adjusting fonts and column widths when using two monitors, drag the Excel window to the primary monitor. Adjustment issues normally occur if the QSW is opened on a secondary monitor. StatementModel.DLL or FsdCommon.DLL could not be found This is caused by a problem with the QSW installation. Follow solutions 1-7 to fix this error. C: Program files (x86) Intuit Statement Writer 20XX microsoft.office.interop.word.dll did not succeed To determine if the problem is with QSW installation or with the QSW file itself, create a new report in QSW. If the report does not open, follow solutions above.
If the report opens, your existing file is damaged. You can just recreate the report.
Also if the StackTrace provides the name of the assembly it can not load then you can check the GAC to see if the assembly exists. However for Win10 it may be in a different location than on Win7 where I checked it. And file explorer will not work for displaying the GAC, at least not on Win7 even though I know the path for it. From this thread, which you may want to read also to see the answer, I was able to view the GAC on my Win7 system using the below procedure. ' Update: Also I found, for Windows 7, that if you in the start menu you select run (on the right under Help and Support) and paste in 'C: windows assembly GACMSIL' then it will display a Window showing the same path to GACMSIL and then you can select appropriate folders to view the actual.Dll 'C: windows assembly GACMSIL Microsoft.SqlServer.Types 10.0.0.089845dcd8080cc91' as I then selected Microsoft.SqlServer.Types which displayed three numbered folders (10.0. To 12.0.) and in each of those folders were the.Dlls.
See bottom image. Perhaps my Control Panel settings for viewing files and folders isn't set for viewing the GACMSIL folder such as hide certain protected files may be set.' La vida loca.