Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Wednesday, March 11, 2015 11:42 PM
Trying to use Database Compare capability of Office 2013 Professional Pro. Complete text of error message: follows
************** Exception Text **************
System.IO.FileNotFoundException: Could not load file or assembly 'Microsoft.ReportViewer.WinForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a' or one of its dependencies. The system cannot find the file specified.
File name: 'Microsoft.ReportViewer.WinForms, Version=9.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a'
at ProdianceAccessManager.CompareReport.InitializeComponent()
at ProdianceAccessManager.CompareReport..ctor(String rootFolder, ListView resultList, Boolean brief, String file1, String file2, Boolean compareTables, Boolean compareQueries, Boolean compareModules, Boolean compareMacros, Boolean compareForms, Boolean compareReports, Boolean comparePages, Dictionary`2 itemPathDictionary)
at ProdianceAccessManager.AccessCompare.btnCompare_Click(Object sender, EventArgs e)
at System.Windows.Forms.Control.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnClick(EventArgs e)
at System.Windows.Forms.Button.OnMouseUp(MouseEventArgs mevent)
at System.Windows.Forms.Control.WmMouseUp(Message& m, MouseButtons button, Int32 clicks)
at System.Windows.Forms.Control.WndProc(Message& m)
at System.Windows.Forms.ButtonBase.WndProc(Message& m)
at System.Windows.Forms.Button.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)
WRN: Assembly binding logging is turned OFF.
To enable assembly bind failure logging, set the registry value [HKLM\Software\Microsoft\Fusion!EnableLog] (DWORD) to 1.
Note: There is some performance penalty associated with assembly bind failure logging.
To turn this feature off, remove the registry value [HKLM\Software\Microsoft\Fusion!EnableLog].
************** Loaded Assemblies **************
mscorlib
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18444 built by: FX451RTMGDR
CodeBase: file:///C:/Windows/Microsoft.NET/Framework/v4.0.30319/mscorlib.dll
DatabaseCompare
Assembly Version: 5.5.0.5
Win32 Version: 5.5.0.5
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Office/Office15/DCF/DATABASECOMPARE.EXE
System.Windows.Forms
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Windows.Forms/v4.0_4.0.0.0__b77a5c561934e089/System.Windows.Forms.dll
System.Drawing
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Drawing/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Drawing.dll
System
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34238 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System/v4.0_4.0.0.0__b77a5c561934e089/System.dll
System.Configuration
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Configuration/v4.0_4.0.0.0__b03f5f7f11d50a3a/System.Configuration.dll
System.Xml
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.34234 built by: FX452RTMGDR
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/System.Xml/v4.0_4.0.0.0__b77a5c561934e089/System.Xml.dll
Accessibility
Assembly Version: 4.0.0.0
Win32 Version: 4.0.30319.18408 built by: FX451RTMGREL
CodeBase: file:///C:/Windows/Microsoft.Net/assembly/GAC_MSIL/Accessibility/v4.0_4.0.0.0__b03f5f7f11d50a3a/Accessibility.dll
Common.FileUtils
Assembly Version: 5.5.0.5
Win32 Version: 5.5.0.5
CodeBase: file:///C:/Program%20Files%20(x86)/Microsoft%20Office/Office15/DCF/Common.FileUtils.DLL
************** JIT Debugging **************
To enable just-in-time (JIT) debugging, the .config file for this
application or computer (machine.config) must have the
jitDebugging value set in the system.windows.forms section.
The application must also be compiled with debugging
enabled.
For example:
<configuration>
<system.windows.forms jitDebugging="true" />
</configuration>
When JIT debugging is enabled, any unhandled exception
will be sent to the JIT debugger registered on the computer
rather than be handled by this dialog box.
Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.
All replies (3)
Thursday, March 12, 2015 2:07 AM ✅Answered
Hi,
Please try to check the necessary components for Database Compare:
As a local administrator on the user’s computer, open a web browser, and visit Microsoft .NET Framework 2.0 Service Pack 2.
Download and install Microsoft .NET Framework 2.0 Service Pack 2.
Open a web browser, and visit Microsoft Report Viewer Redistributable 2008.
Download and install Microsoft Report Viewer Redistributable 2008.
Make sure that .NET Framework 4.0 is installed.
Restart the computer.
https://technet.microsoft.com/en-us/library/dn205149.aspx?f=255&MSPPError=-2147217396
Which Windows operation system do you use? If you are using Window 7/Windows 8/ Windows 8.1. We can install Microsoft .NET Framework 3.5 firstly ( Instead of install Microsoft .NET Framework 2.0 Service Pack 2) and then install the Microsoft Report Viewer Redistributable 2008.
Please see the same thread:
Regards,
George Zhao
TechNet Community Support
It's recommended to download and install Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office programs.
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Wednesday, March 18, 2015 3:30 PM
Thank you. No longer have the issue.
Steve
Wednesday, September 30, 2015 7:11 PM
I just built up a new machine with Windows 10 and Office Pro Plus 2016, and encountered the same error.
Installing Microsoft Report Viewer Redistributable 2008 (http://go.microsoft.com/fwlink/p/?LinkId=285725) resolved this error, but why does the latest version of Office still use this ancient Report Viewer, instead of the current Microsoft Report Viewer 2015 Runtime version (http://www.microsoft.com/en-us/download/details.aspx?id=45496)?