Msi Error 2765
PKI Service Identity Access Manager Shop Online Cyber Security Services Managed Security Services DeepSight Intelligence Incident Response Security Simulation Website Security SSL Certificates Complete Website Security Code Signing Certificates Norton Shopping Guarantee Buy SSL Products A-Z Services Services Home Business Critical Services Consulting Services Customer Success Services Cyber Security Services Education Services Solutions Solutions Home Topics Encryption Everywhere Internet of Things Next Generation Endpoint Office 365 Industries Automotive Cyber Insurance Education Financial Services Global Service Providers Industrial Control Systems Healthcare Retail Government Federal Government State & Local Support Center Technical Support Symantec Connect Buying Programs Upgrades Maintenance & Renewals Training Security Center Security Center Home Blogs ISTR Threats Virus Definitions and Security Updates Removal Tools Partner Find a Partner Become a Partner Login Required Login into Partner Portal Partner Licensing Partner Renewals Partner Training Margin Builder Opportunity Registration Financial Benefits English 中文(简体) 中文(繁體) Česká English Français Deutsch Magyar Italiano 日本語 한국어 Polski Português Pусский Español Site: Symantec Enterprise Small Business Norton United States Search Support Home Support Home MySymantec Licensing Products A-Z SYM16-015 Security Advisory Login Profile Subscriptions Logout Login Forgot Password? Don't have a SymAccount? Create a SymAccount now!' Internal error 2765 TECH12758 February 27th, 2008 http://www.symantec.com/docs/TECH12758 Support / Internal error 2765 Did this article resolve your issue? Thank you for your feedback! Provide feedback on this article Request Assistance Print Article Products Subscribe to this Article Manage your Subscriptions Search Again Situation I receive the following error: Internal error 2765: Assembly name missing fro
2008 by leereid In repackaging an internally developed application that requires .NET Framework 2.0 SP1 and 3.0, I came across this error 2765. Here's what I did and how I got around it: I installed .NET Framework 3.5 on the machine Performed a setup capture in Wise of the installation Completed that, then edited what I needed to in Wise, compiled the installation. Running the install gave Internal error 2765 : KO.dll (for example) This page suggested to remove items from the MsiAssembly table if they didn’t have entry in the MsiAssemblyName table. Doing this in https://support.symantec.com/en_US/article.TECH12758.html Wise didn't work as the entries were put back in on compilation, so I opened the msi in Orca and created a transform, then removed the rows from there. This installation then completed, although I'm not aware of any other consequences of removing these items. Like this:Like Loading... Related Posted in Packaging, Work | 2 Comments 2 Responses on April 3, 2013 at https://leereid.wordpress.com/2008/02/08/msi-internal-error-2765/ 5:41 pm | Reply Steph That's useful, thanks! (wow 5 years later) on June 3, 2015 at 12:49 am | Reply Rob Winslow Now 7 years later, still useful. Thanks! Comments RSS Leave a Reply Cancel reply Enter your comment here... Fill in your details below or click an icon to log in: Email (required) (Address never made public) Name (required) Website You are commenting using your WordPress.com account. (LogOut/Change) You are commenting using your Twitter account. (LogOut/Change) You are commenting using your Facebook account. (LogOut/Change) You are commenting using your Google+ account. (LogOut/Change) Cancel Connecting to %s Notify me of new comments via email. Recent Posts Citrix Studio PVS - Remove user from Delivery Group with activesession The specified Task does not exist - merging PVSvDisks Installing HP UFT and ALM PlatformLoader Adobe Acrobat Printer won'tinstall Top Posts How to run VBScript VBScript Current Directory (or Folder) VBScript edit line in file Everything about Adobe's cache.db (well, not quite) VBScript - get file version Uninstall Adobe Creative Suite 5 (CS5) silently - how to 1904 1905 Acrobat ActiveSetup Add new tag adobe backup BDD code CodePro
Studio 2015 products Visual Studio Team Services Visual Studio Code Visual Studio Dev Essentials Office Office Word/Excel/PowerPoint Microsoft Graph Outlook OneDrive/Sharepoint Skype Services Store Cortana Bing Application Insights Languages & platforms Xamarin ASP.NET https://msdn.microsoft.com/en-us/library/windows/desktop/aa372835(v=vs.85).aspx C++ TypeScript .NET - VB, C#, F# Server Windows Server SQL Server BizTalk http://www.aspnet-answers.com/microsoft/Windows-MSI/29453068/2765-error-question.aspx Server SharePoint Dynamics Programs & communities Students Startups Forums MSDN Subscriber downloads Sign in Search Microsoft Search Windows Dev Center Windows Dev Center Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI msi error Develop API reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Explore Why Windows What’s new for Windows 10 Intro to Universal Windows Platform Dev Center Benefits Develop for accessibility Build for enterprise Docs Windows apps Get started Design and UI Develop API msi error 2765 reference Publish Monetize Promote Games Get started UI design Develop Publish Desktop Get started Design Develop API reference Test and deploy Compatibility Windows IoT Microsoft Edge Windows Holographic Downloads Samples Support Dashboard Windows Installer Windows Installer Reference Errors Reference Errors Reference Windows Installer Error Messages Windows Installer Error Messages Windows Installer Error Messages Windows Installer Error Messages MsiExec.exe and InstMsi.exe Error Messages TOC Collapse the table of content Expand the table of content This documentation is archived and is not being maintained. This documentation is archived and is not being maintained. Windows Installer Error Messages The error codes detailed in this topic are returned by the Windows Installer, and have error codes of 1000 or greater. The error codes numbered 1000 to 1999 are ship errors and must be authored into the Error table. The error codes numbered greater than 2000 are internal errors and do not have authored strings, but these can occur if the installation package has been incorrectly authored. For error codes specific to the Windows Installer functions MsiExec.exe and InstMsi.exe, see MsiExec.exe and InstMsi.exe Error Messages. For a list of reserved error codes, see Error table. Note If you are a user experien
you can have MsiAssemblyName entries with no MsiAssembly counterpart. I have this situation in my .msi and it appears to be OK as there are no errors on install. Does anyone know if this is, in fact, OK? Superfreak3 replied on 09-Mar-07 09:48 AM Or, if there are MsiAssemblyName entries with no MsiAssembly counterpart, does Windows Installer simply ignore the MsiAssemblyName information in this case? Any information is greatly appreciated as we just upgraded our authoring tool and it has an issue in this area. I just want to feel about what we ship regarding the contents of these two tables. Phil Wilson replied on 09-Mar-07 10:40 AM Is there some reason why you can't just put the right things in MsiAssembly and MsiAssemblyName? They're designed to work together - why are you doing these unusual things? -- Phil Wilson [Microsoft MVP-Windows Installer] Superfreak3 replied on 09-Mar-07 01:44 PM It's not really me doing what I too call crazy things. Its the Wise product we use. My guess is that in their previous product, if a file was NOT set as an assembly within Wise, but had attributes, there was no record created for it in the MsiAssembly table, but the attributes were translated to the MsiAssemblyName table. Therefore, you had records (attributes) listed in the MsiAssemblyName table with no corresponding item in the MsiAssembly table. Now, with their new product, those assemblies we have set to 'None' are set to .NET, which creates a record in the MsiAssembly table. Some of these don't really have attributes so you end up with an MsiAssembly record with nothing matching in the MsiAssemblyName table, causing error 2765. I don't really want to monkey around too much, but I created a utility that, after the installation is compiled in Wise, will edit the MsiAssembly table and remove any records with no matching MsiAssemblyName records. I don't know if this will work or not. I guess what I was aiming for in my time crunch was to mimic whatever h