/build/static/layout/Breadcrumb_cap_w.png

Help with MSI 2765

Help with MSI (Microsoft Installer) error 2765: Assembly name missing from AssemblyName table : Component: [4].

2 Comments   [ + ] Show comments
  • Another butt-saving on your part. Thank you. - Head_Scratcher 5 years ago
  • have same error but cant fix with this method. Internal Error 2765. File317.

    any suggestions? - jay25oct 5 years ago
    • Find the file in the WiseSourcePath table and change the attribute to 16. Then find the file in the MsiAssembly table and delete the row. That is an alternate way to do the same thing. It works - kboneill 5 years ago

Answers (2)

Posted by: Chiun 13 years ago
Yellow Belt
4
Cause The attributes in the WiseSourcePath table indicate that the [problem] files are .NET assemblies. Resolution Summary 1. Go to the Setup Editor > Tables > WiseSourcePath table 2. The Attributes column for the [problem] files should currently be 8. Change the attributes column for these three entries to 16 3. Go to the Files page 4. Double-click on each of the [problem] files, go to the Assembly tab and change the Assembly Type to None. 5. Compile the installation. This time when you compile, the Assembly Type should remain None even if the Rescan Com interop registry keys on compile option is selected

Comments:
  • Excellent post. Exactly right. Thank you!!! You saved me a LOT of time chasing that one. - kboneill 7 years ago
  • Very useful. Thanks - maros141 7 years ago
  • Thank you. This helped me. - jnoxon1 7 years ago
  • Sweet! Time saver! - Head_Scratcher 5 years ago
Posted by: Basvv85 4 years ago
White Belt
1

I have found a faster way.

Delete the whole table WiseSourcePath, or at least the files with attribute 8.

Then delete the whole table MSIassembly, you don't have to change the files themselves.


Comments:
  • I just ran into this error when attempting to repackage Aginity Workbench for Netezza (also called something like PureData System for Analytics). Tried running the MSI but got error 2765. Then I found this page and wound up deleting all the rows in the WiseSourcePath table that had an attribute of 8, and deleted the entire MSIassembly table.
    After that the MSI installed correctly without error.
    Glad I found this. Big time saver! - RonW 2 years ago
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Don't be a Stranger!

Sign up today to participate, stay informed, earn points and establish a reputation for yourself!

Sign up! or login

Share

 
This website uses cookies. By continuing to use this site and/or clicking the "Accept" button you are providing consent Quest Software and its affiliates do NOT sell the Personal Data you provide to us either when you register on our websites or when you do business with us. For more information about our Privacy Policy and our data protection efforts, please visit GDPR-HQ