I'm trying to run the "Analyze Now" on BHM50.exe (BizTalk Health Monitor) on BizTalk 2016.
I opened as Administrator, and I should have all the necessary privileges.
We have two BizTalk servers in a group, with SQL on a different machine.
It gives this error.
Launching "D:\Program Files (x86)\BizTalkHealthMonitor\BHMCOLLECT.EXE"
-PROFILE:C:\PROGRA~3\MICROS~1\BIZTAL~2\MBVSET~1.XML
Unhandled Exception: System.IO.FileLoadException: Could not load file
or assembly 'MYHC, Version=11.0.0.0, Culture=neutral,
PublicKeyToken=fa6906311f4bb5cd' or one of its dependencies. The
located assembly's manifest definition does not match the assembly
reference. (Exception from HRESULT: 0x80131040) at
MyHealthCheck.Class1.Init(String[] args)
There were no matches at all on Google for this error.
Sample screen shot:
It's complaining about MyHC - does it need to be put in the GAC?
Here it is in the same directory where I installed the utility.
You have this error when one of the BHM components is not "compatible" with the others. This issue can occur during a partial self-update of BHM.
When you update BHM using its self-update features, be sure that all the components proposed in the update were well downloaded; if only a part of them is downloaded in the BHM folder, you will have this kind of error at the BHM startup or collect start.
If you redownload and reinstall BHM, you should not meet this error but you will have to self-update BHM to have its latest components downloaded (queries/rules repository, collect engine, MMC snapin, etc...)
JP (BHM Dev team)
Try to update to the latest version. There is an option for that RC/BHM Update
Related
I've downloaded the open source edition of ncache and i've followed the instructions at http://www.alachisoft.com/resources/docs/ncache/help/aspnet-session-state-provider.html?mw=Mzk2&st=MQ==&sct=MTk4&ms=QwAAEAAAIAAAAQACATgIAhA=
to configure my website to put the session state in ncache.
However, i get this error hitting the site.
Configuration Error
Description: An error occurred during the processing of a configuration file required to service this request. Please review the specific error details below and modify your configuration file appropriately.
Parser Error Message: Could not load file or assembly 'protobuf-net, Version=1.0.0.282, Culture=neutral, PublicKeyToken=257b51d87d2e4d67' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
Source Error:
Line 136:
Line 137:
Source File: C:\inetpub\wwwroot\xxxx\web.config Line: 138
Assembly Load Trace: The following information can be helpful to determine why the assembly 'protobuf-net, Version=1.0.0.282, Culture=neutral, PublicKeyToken=257b51d87d2e4d67' could not be loaded
I'm not sure where to find that dll or why it can't be loaded? I tried using nuget to install protobuf-net but there is no 1.0.0 version and the recent version does not fix the problem when i copy it to the bin folder.
Randy
Turns out the issue was that you need NCache installed on the web servers too, in addition to the cache servers. This is a better page to follow if you are just starting out with NCache for sessionState.
http://www.alachisoft.com/resources/docs/ncache/ncache-session-guide.pdf
I am having a problem that many people have had before but none of the existing answers seem to work for me.
When I deploy my ASP.NET project I get an error in the event log saying
Could not load file or assembly 'Microsoft.SqlServer.Types, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The located assembly's manifest definition does not match the assembly reference. (Exception from HRESULT: 0x80131040)
To try to rectify this I installed the Nuget package:
PM> Install-Package Microsoft.SqlServer.Types
This didn't work and I get the same error. So then I followed the readme and used Loader.cs to load the files. Again, same problem. What is happening and why don't the usual solutions fix it?
One thing I did note is that my Microsoft.SqlServer.Types.dll is version 11 not 13? If it makes any difference our database is SqlServer 2016 and our machine is running Windows Server 2008
The way I solved this was to to set the SqlServerTypesAssemblyName in my app. I currently set it in my EntityContext constructor [that inherits off DbContext] to ensure its always set
SqlProviderServices.SqlServerTypesAssemblyName
= "Microsoft.SqlServer.Types, Version=13.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91";
Note your version may want to be different.
Make sure you are reference the correct version of assembly.
If not add manually.
Once the nuget package is installed you can ensure that the dll reference property is set to 'copy local = true'
I am getting the following error when I compile the release of my web application. The project ran fine previously on another machine the hard drive went out on. So I am thinking there is a problem with the configuration. I did some research and it made note of a Web Deploy issue but I am unable to verify what version was in use on the past machine.
Here is the error:
The "IsCleanMSDeployPackageNeeded" task failed unexpectedly.
System.InvalidCastException:
[A]Microsoft.Web.Deployment.DeploymentProviderOptions cannot be cast
to [B]Microsoft.Web.Deployment.DeploymentProviderOptions. Type A
originates from 'Microsoft.Web.Deployment, Version=9.0.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' in the context
'Default' at location
'C:\Windows\assembly\GAC_MSIL\Microsoft.Web.Deployment\9.0.0.0__31bf3856ad364e35\Microsoft.Web.Deployment.dll'.
Type B originates from 'Microsoft.Web.Deployment, Version=7.1.0.0,
Culture=neutral, PublicKeyToken=31bf3856ad364e35' in the context
'Default' at location
'C:\Windows\assembly\GAC_MSIL\Microsoft.Web.Deployment\7.1.0.0__31bf3856ad364e35\Microsoft.Web.Deployment.dll'.
at Microsoft.Web.Deployment.ArchiveElementHelper.get_ProviderContext()
at
Microsoft.Web.Deployment.ZipPackageProvider.d__0.MoveNext()
at
Microsoft.Web.Deployment.DeploymentObject.d__9.MoveNext()
at
Microsoft.Web.Deployment.DeploymentObject.d__0.MoveNext()
at
Microsoft.Web.Publishing.Tasks.IsCleanMSDeployPackageNeeded.CheckMSDeployDumpContainIisSetting(DeploymentObject
deploymentObject, String& iisMSDeployProviderName) at
Microsoft.Web.Publishing.Tasks.IsCleanMSDeployPackageNeeded.Execute()
at
Microsoft.Build.BackEnd.TaskExecutionHost.Microsoft.Build.BackEnd.ITaskExecutionHost.Execute()
at
Microsoft.Build.BackEnd.TaskBuilder.d__20.MoveNext() 0 0 PKL_QMW
Apparently this can happen if you install the Web Deployment package without the UI Components.
Try going into add remove programs and doing a Change install on 'Microsoft Web Deploy' and ensure that the UI components are selected to install.
I'm trying to add bundling to my Mvc4 web project. The steps I took:
Added a reference to my project to System.Web.Optimization
Added #Styles.Render("~/Content/css") within <head> of my _Layout.cshtml
Added BundleConfig.RegisterBundles(BundleTable.Bundles); to Global.asax.cs
Added BundleConfig.cs to my App_Start folder with bundles.Add(new StyleBundle("~/Content/css").Include("~/Content/site.css")); within RegisterBundles(...) method
Added a simple site.css within my Content folder.
The error that I get on the line from step #2 above is Could not load file or assembly 'WebGrease, Version=1.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies. The system cannot find the file specified.
Am I missing a DLL reference or something? Note that I started originally from a blank Mvc4 project.
Over the last day or so I was having this issue too but I figured out a solution. Basically you need to just update "webgrease".
Here's what I did to update webgrease:
right click your project solution in your solution explorer.
Click "Manage NuGet Packages for Solution"
Go to the updates section on the left
Search "WebGrease"
Then update "WebGrease"
This worked for me when I built my solution.
I had the same problem after having added ASP.NET MVC 5 to my old ASP.NET web application, running WebForms. I want to add new features and build them on the MVC platform, so it is important that I get MVC and the traditional web application to run side by side. I'm writing this answer here because all the solutions I have found on stackoverflow and other places, including the solution selected to the topic you're reading now, didn't help me. Maybe my findings will help someone out there...
When I added MVC 5 to the web application project, it installed a bunch of references, for example System.Web.Mvc, System.Web.Razor, etc. The NuGet package called Microsoft.AspNet.Web.Optimization was also installed, which has a reference to WebGrease; the reference you and I had problems with.
The version of the Optimization dll that was installed in my web project, is Microsoft.AspNet.Web.Optimization 1.1.3, which is the latest version as of right now. WebGrease version 1.5.2 comes with it.
The funny thing is that the error message I got when executing the #Styles.Render("~/Content/css") statement in _Layout.cs, referred to WebGrease version 1.5.1. I have no idea where it got the 1.5.1 version from, because 1.5.2 was installed in my web project. I tried uninstalling WebGrease and reinstalling, tried upgrading WebGrease to the latest version (1.6.5135). I made certain that none of these dlls were installed in the GAC (which they weren't). I deleted all temporary files in "C:\Windows\Microsoft.NET\Framework\v4.0.30319\Temporary ASP.NET Files\", but all to no avail.
I used the program called Fuslogvw.exe to log all binding information when I ran my web application, in the hope that I would spot a logical reason for why my application insisted on trying to load an old, non-existing version of WebGrease when running my application. Interestingly, the log's output showed me what the application was doing, but unfortunately didn't tell me why. The log told me that despite me having installed Microsoft.AspNet.Web.Optimization version 1.1.3 with WebGrease version 1.5.2, it tried to load Microsoft.AspNet.Web.Optimization version 1.1.0.0, which also comes with an older version of WebGrease. Why it did this? I have no idea, as I've never added Optimization to any project on my PC before.
My solution was to remove both Microsoft.AspNet.Web.Optimization and WebGrease (in that order), and then run the following command in Package Manager Console to install Microsoft.AspNet.Web.Optimization version 1.1.0:
Install-Package Microsoft.AspNet.Web.Optimization -Version 1.1.0
This resulted in WebGrease version 1.3.0 being installed, which didn't cause any problems when loading my MVC razor view which uses the _Layout.cshtml page.
For those of you who are interested: below you can see the output from the log produced by Fuslogvw.exe, where it clearly states that it tried to load the non-existing 1.1.0 version of Optimization:
*** Assembly Binder Log Entry (26.11.2018 # 13:19:59) ***
The operation failed.
Bind result: hr = 0x80131040. No description available.
Assembly manager loaded from: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\clr.dll
Running under executable c:\windows\system32\inetsrv\w3wp.exe
--- A detailed error log follows.
=== Pre-bind state information ===
LOG: DisplayName = WebGrease, Version=1.5.1.25624, Culture=neutral, PublicKeyToken=31bf3856ad364e35
(Fully-specified)
LOG: Appbase = file:///C:/Projects/MyProject/Web/
LOG: Initial PrivatePath = C:\Projects\MyProject\Web\bin
LOG: Dynamic Base = C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\myproject\1db399c5
LOG: Cache Base = C:\Windows\Microsoft.NET\Framework64\v4.0.30319\Temporary ASP.NET Files\myproject\1db399c5
LOG: AppName = 3f7f1cb1
Calling assembly : System.Web.Optimization, Version=1.1.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35.
===
LOG: This bind starts in default load context.
LOG: Using application configuration file: C:\Projects\MyProject\Web\web.config
LOG: Using host configuration file: C:\Windows\Microsoft.NET\Framework64\v4.0.30319\aspnet.config
LOG: Using machine configuration file from C:\Windows\Microsoft.NET\Framework64\v4.0.30319\config\machine.config.
LOG: Post-policy reference: WebGrease, Version=1.5.1.25624, Culture=neutral, PublicKeyToken=31bf3856ad364e35
LOG: GAC Lookup was unsuccessful.
LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/ipmvcang/1db399c5/3f7f1cb1/WebGrease.DLL.
LOG: Attempting download of new URL file:///C:/Windows/Microsoft.NET/Framework64/v4.0.30319/Temporary ASP.NET Files/ipmvcang/1db399c5/3f7f1cb1/WebGrease/WebGrease.DLL.
LOG: Attempting download of new URL file:///C:/Projects/MyProject/Web/bin/WebGrease.DLL.
LOG: Assembly download was successful. Attempting setup of file: C:\Projcets\MyProject\Web\bin\WebGrease.dll
LOG: Entering download cache setup phase.
LOG: Assembly Name is: WebGrease, Version=1.6.5135.21930, Culture=neutral, PublicKeyToken=31bf3856ad364e35
WRN: Comparing the assembly name resulted in the mismatch: Minor Version
ERR: The assembly reference did not match the assembly definition found.
ERR: Setup failed with hr = 0x80131040.
ERR: Failed to complete setup of assembly (hr = 0x80131040). Probing terminated.
Unable to Install Quality Center Client Side on the client's machine.
Operating System: Windows Vista
IE Version:9
We tried all the basic trouble shooting steps like deleting TD_80 folder from %temp% and performing a fresh installation.
Deleting Mercury Intercative folder from
C:\program files\common files
Running the internet explorer as Administrator.
None of the above solved the problem
we are recieving the below error message:::::
HP Quality Center: Unrecoverable Error Occured.
Reason: Could not load file or assembly 'interop.OTAClient, Version=10.0.02469,Culture=neutral, PublicKeyToken=792843134cf0407a' or Contact your site administrator.
Details::::
System.IO.FileNotFoundException: Could not load file or assembly 'interop.OTAClient, Version=10.0.0.2469, Culture=neutral, PublicKeyToken=792843134cf0407a' or one of its dependencies. The system cannot find the file specified.
File name: 'interop.OTAClient, Version=10.0.0.2469, Culture=neutral, PublicKeyToken=792843134cf0407a'
at Mercury.TD.Client.Ota.Core.Application.SSPREnabled(String serverUrl)
at Mercury.TD.Client.UI.Core.Services.ConnectionManagementService.Initialize()
at Mercury.TD.Client.UI.Core.Services.BaseService.Initialize(IServiceManager serviceManager)
at Mercury.TD.Client.UI.Core.ServiceFactory1.CreateService()
at Mercury.TD.Client.UI.Core.ServiceManager.ServiceCache1.b__0()
at Mercury.TD.Client.UI.Core.ServiceManager.ServiceCache1.CreateService(ServiceConstructorDelegate1 serviceConstructor, T& service)
at Mercury.TD.Client.UI.Core.ServiceManager.ServiceCache1.GetServiceEx(ServiceConstructorDelegate1 serviceConstructor)
at Mercury.TD.Client.UI.Core.ServiceManager.ServiceCache1.GetService()
at Mercury.TD.Client.UI.Core.ServiceManager.ServiceCache1.GetBaseService()
at Mercury.TD.Client.UI.Core.ServiceManager.DoPublish[T](IServiceFactory1 factory, Boolean activate)
at Mercury.TD.Client.UI.Core.ServiceManager.PublishAndActivate[T,C]()
at Mercury.TD.Client.UI.Core.ApplicationServicesPlugin.PublishServices(IServiceManager serviceManager)
at Mercury.TD.Client.UI.Core.Services.ApplicationService.InitializePlugins()
at Mercury.TD.Client.UI.Core.Services.ApplicationService.Start(Application application)
at Mercury.TD.Client.UI.Core.Application.Start()
at Mercury.TD.Client.UI.Core.Application.Initialize(String url, String configFilePath, IDictionary2 properties)
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].
Use the Quality Center Explorer Add-In rather than the one tied to the browser:
ALM Explorer 11
QCExplorer 10
QCExplorer 9
QC Forums