Got this error trying to setup a deployment. Using the latest version of BuildMaster Version 4.3.9 (Build 2) and Vault Standard V7. I've installed the Vault extension within BuildMaster.
ERROR: Assembly SourceGear was not found. The extension may be out of date, have been deleted, or could not be loaded.
Parameter name: assemblyName
Any ideas?
This error typically means that the service cannot load the SourceGear assembly; your best bet is to restart the service, and hope it works again. If it's continually a problem, then you can run the service interactively to see why the assembly can't be loaded.
Usually, it's an access/permission problem, or anti-virus.
Related
I have an ASP.NET web site targeting Framework 4.6.2 where I attempt to use a GRPC service from my controller. When I attempt to create the Channel, I get an exception:
"Error loading native library \"C:\\Users\\sstainba\\repos\\location-management-service\\src\\LocationManagement.Web\\bin\\grpc_csharp_ext.x86.dll\""}
My project already has a reference to the GRPC, GRPC.Core, GRPC.Auth and GRPC.Tools packages. And, in fact, the assembly DOES exist at that exact location. I am at a loss as to why it won't load. What other things can I try other than adding the reference?
Figure out the problem... Permissions on the bin folder. I temporarily set permissions to give everyone full control and it worked.
I'm getting this error message when I submit the input file (which BizTalk eats up as expected)...
There was a failure executing the receive pipeline:
"FileName.BizTalk.Pipelines.Receive_ResponsePipeline,
FileName.BizTalk.Pipelines,
Version=1.0.0.0,
Culture=neutral,
PublicKeyToken=040e2e09e19196ce"
Source: "Unknown "
Receive Port: "rcv_Response"
URI: "C:\Data\drops\in\*.txt"
Reason: Could not load file or assembly 'file:///C:\Program Files (x86)\Microsoft
BizTalk Server 2013 R2\Pipeline Components\FileName.BizTalk.Core.dll' or one of its
dependencies. The system cannot find the file specified.
I checked that directory and the DLL it's looking for is there. I even rebuilt it from the solution along with all its dependencies.
Could this simply be a case of a corrupt file/installation or could it be something else?
The BizTalk solution builds with no issues and I was able to deploy to the BizTalk Server without issues.
To deploy a BizTalk pipeline component, you need to:
Add the file to the "Pipeline Components" folder as the error suggest.
Add it to the Global Assembly Cache (GAC).
Make sure you restart the host instance(s) after deployment AND be sure to deploy it on all BizTalk servers within the BizTalk Group.
Here are the few check points that may be cause of issue:
Check if all the dependent assemblies(Required/imported in given assemby) are also present in GAC & wherever necessary. Any missing dependent assembly gives the same error.
Receive Location handler (check if it is 32 or 64 bit host)
Check if the receive handler is running on all nodes of the farm, if
yes check required dlls are in place
Does EDI component has been properly installed on production box
Check if your project is properly build from Visual Studio, probably
clean the solution and then rebuilt and deploy from VS on dev
environment and then move to prod
After deployment hosts are restarted
Check if receive handler is defined for the host instance Adapters-->File-->New-->Receive Handler and check if the HostInstance is added. Check Receive Location and updated the Receive Handler property.
Check the application pool to Integrated and targeted the v4.0 Framework. This clears the initial error, but then you can receive a new error from IIS that the svc handler was not correctly mapped. I then realized that I needed to run the "aspnet_regiis.exe -I" command against the correct version of aspnet_regiis (the v4.0 framework version).
Sources:
http://social.msdn.microsoft.com/Forums/en-US/246d306b-5a18-497d-a4f6-f8b3a9aacdb8/receive-pipeline-error-could-not-load-file-or-assembly?forum=biztalkgeneral
http://social.technet.microsoft.com/wiki/contents/articles/7204.biztalk-server-list-of-errors-and-warnings-causes-and-solutions.aspx
http://blogs.msdn.com/b/joscot/archive/2013/08/14/biztalk-2013-hosted-wcf-service-fails-because-it-could-not-load-microsoft-biztalk-interop-ssoclient.aspx?utm_source=buffer&utm_campaign=Buffer&utm_content=buffer52156&utm_medium=twitter
I'm trying to debug an error of the form
Could not load file or assembly '[assembly], Version=[version], Culture=[culture], PublicKeyToken=[publicKeyToken]' or one of its dependencies.
The error page tells me that assembly binding logging, which could help me debug my problem, is turned off:
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].
I navigated to HKLM\Software\Microsoft\Fusion in the registry, created a DWORD value called EnableLog, and set it to 1. I refreshed the web page, but I still got the same warning that Assembly binding logging was turned off. I rebooted the server, but assembly binding logging still wasn't turned on.
Then I tried setting some additional registry settings from this question. Still no assembly binding logging.
This is all on an Azure web role virtual machine by the way. Fuslogvw is not installed. In order to get it, I would have to install the Windows SDK on all of my web roles. And I don't want to use fuslogvw anyway; I just want assembly binding logs.
What else do I need to do to turn on assembly binding logging?
Edit: I installed the Windows SDK on both web roles, but it looks like fuslogvw is still not there. At least, I get a "command not found" error trying to run fuslogvw from the admin command prompt, and fuslogvw.exe is not in the location indicated by this question (which I realize is referring to a fuslogvw.exe installed through Visual Studio, and part of an older version of the Windows SDK than what I installed).
Edit: I installed an older Windows SDK, and then found fuslogvw.exe (I'll bet it actually came with the first SDK I installed, and I was just a fool and couldn't find it). I found it in D:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools.
Now I can debug the error I'm getting.
However, the original question is still open: what could I be missing trying to turn on assembly binding logging through registry settings?
(The reason I want to be able to use registry settings instead of fuslogvw from the Windows SDK is that I can configure my web roles to set registry settings automatically, but to use the Windows SDK I would have to manually log in to my web roles and run the graphical installer. It's not that much work to install the SDK, but it's the principle of the thing. The registry settings should work, and automation is better than manual tasks.)
I run ssis package from my asp.net application. When it's running on my local machine (32-bit OS), everything is working fine.
but when I published my site on remote computer (64-bit OS) I was getting run-time error:
Could not load file or assembly 'Microsoft.SqlServer.ManagedDTS, Version=10.0.0.0,
Culture=neutral, PublicKeyToken=89845dcd8080cc91' or one of its dependencies. The system cannot
find the file specified.
I put Microsoft.SqlServer.ManagedDTS.dll and Microsoft.SqlServer.DTSRuntimeWrap.dll into the bin folder of my web site.
After that I had the next error:
“An attempt was made to load a program with an incorrect format”
I turned on " Enable 32-Bit Applications" option on iis for application pool and changed platform target to x86 in the properties of a project.
And now I have the following error:
Retrieving the COM class factory for component with CLSID {BA785E28-3D7B-47AE-A4F9-4784F61B598A}
failed due to the following error: 80040154 Class not registered
(Exception from HRESULT: 0x80040154 (REGDB_E_CLASSNOTREG)).
Any ideas how to fix that?
OR may be I'm moving in wrong direction?
Any help is appreciated.
MSDN reference:
Read the topic Understanding the Differences between Local and Remote Execution on MSDN to understand the concept of running the packages remotely
You can only run a package outside the development environment on a
computer that has Integration Services installed
The server that hosts your package should have Integration Services installed. Please consult Microsoft document on how the licensing model works with respect to Integration Services. Copying only the DLLs to the server where the package should run will not resolve the issue.
You can remotely invoke the package execution but you still need Integration Services on the server hosting the package.
MSDN blog article:
Running SSIS package programmatically Read the point 1 in the article that describes about executing SSIS packages from ASP.NET
Quoted directly from the article:
Run package programmatically using SSIS Object Model. This is discussed in details in Books Online here: http://msdn2.microsoft.com/en-us/library/ms136090.aspx
Benefits: Everything runs in process, it is very easy to set variables or modify package before executing it. You can also get events about package progress or ask it to stop by setting CancelEvent.
Drawbacks: Obviously this is local execution - you need to install SSIS on same machine where your app runs. This method also can't be used from .NET 1.1 application, unless it is moved to .NET 2.0 (which should be very easy to do, and in my experience improves the performance as well).
ASP.NET specific: The impersonation context does not get passed to additional threads SSIS package creates, so the data source connections will not be impersonated. Also, ASP.NET can be configured to recycle the worker process in case it consumes too much memory to improve availability of ASP.NET application. Since SSIS is likely to consume a lot of memory if you have lots of data, it can trigger this recycling and lower reliability of your application.
Some Background
This works on your local machine because your SSIS package build version matches the Microsoft.SqlServer.ManagedDTS.dll version you have in ASP.NET project. Now, you need to match the library versions from your SSIS build package to your Microsoft.SqlServer.ManagedDTS.dll versions. The versions must match and the 32-bit versus 64-bit libraries must match as well.
Answer
An easy way to do this is: Add SSIS script task to your package (on your remote server) and click the 'Edit Script' button. Now, look in the SSIS library references and you should see the version that the SSIS package loaded. That is the one you need to compile with ASP.NET project. This Script tasks can be deleted afterwards.
Add service reference to Amazon service fails, saying
"Could not load file or assembly "System.Core, Version=3.5.0.0,...' or
one or more of it dependencies. The module was expected to contain an
assembly manifest."
This is in VS 2008, haven't installed SP1 on this machine yet.
Any ideas?
This can happen if ASP.NET isn't installed. Go to Add/Remove Windows Components and look under IIS; make sure that ASP.NET is checked (meaning that it's installed.) That should clear up your problem!