Management console generates “Could not load file or assembly Newtonsoft.Json” error - App-V 5.1 Support Tip

After upgrading the App-V 5.0 Service Pack 1 Database and Management Server, the following error is generated when loading the App-V management console:


Could not load file or assembly 'Newtonsoft.Json, Version=4.5.0.0, Culture=neutral, PublicKeyToken=30ad4fe6b2a6aeed' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)


To know more about resolving this issue click on the below official Microsoft TechNet link:


http://blogs.technet.com/b/appv/archive/2015/10/22/app-v-5-1-support-tip-management-console-generates-could-not-load-file-or-assembly-newtonsoft-json-error.aspx

Comments

Post a Comment

Popular posts from this blog

How to write to 64bit registry path from a 32bit MSI using a MST using ORCA tool

Image
In my earlier blog, I posted about how to create a transforms file to install a registry to 64 bit location in 64 bit OS using transforms in a 32 bit vendor MSI using Installshield tool. So, in this current post I will explain how to achieve this using a simple ORCA tool. 1) Open the MSI using ORCA tool. Select Tansforms from the menu bar and click on New Transforms. This will create a new transforms where you can do the modifications. 2) Add a new row in Component table and create a new component and set the Attribute field to 256 as shown below. Component attribute 256 - Set this bit to mark the component as a 64-bit component. ( https://msdn.microsoft.com/en-us/library/aa368007(v=vs.85).aspx ) 3) Add a row in FeatureComponents table and map the newly created component to an existing Feature. 4) Go to Registry table and select the registry for which needs to be installed to 64-bit path and set the Component field to the newly created obove component. 5) After doing the changes, s...
Read more

Solution for Error 17002 when uninstalling Office 365 (2016) when apps like word, excel, outlook are open

Image
When uninstalling office 365 silently, it is failing only when any applications like word, excel are kept open. This is because during uninstall, office checks for any running applications and prompts the user to close it which is not happening in silent uninstall. When uninstalling in UI mode, it prompts to close when any office apps are open. Since in silent mode office is not able to do this, it fails with an error code 17002. You can check in the log file for the error code 17002. To overcome this just add the property FORCEAPPSHUTDOWN with Value="True" in the uninstall config.xml file. This property will force shutdown any running office apps. Example: <Configuration>  <Remove>  <Product ID="O365ProPlusRetail" >  <Language ID="en-us" />   </Product>  </Remove> <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" /> <Display Level="None"/> <Logging Path="c:\temp\" Name...
Read more

Decrypting how Microsoft Teams new MSI works

Image
Microsoft has released a windows Installer MSI for Microsoft Teams for deployment through SCCM.You can download it here As per Microsoft Statement: "The Teams MSI will place an installer in Program Files. Whenever a user signs into a new Windows User Profile, the installer will be launched and a copy of Teams application will be installed in that user's appdata folder. If a user already has the Teams app installed in the appdata folder, the MSI installer will skip the process for that user." NOTE: Don't change the install location as it will break the process. In this blog, I will explain how this happens by opening MSI using Installshield. 1. To Install Microsoft Teams, it first requires .net 4.5 or later to be installed in the machine. This check happens using Launch condition which also does a system search for .net registry to be present in the machine. 2. The MSI has only one file which is Teams.exe that gets installed to [ProgramFilesFolder]Teams Installer locat...
Read more