"Could not load file or assembly 'Microsoft.SqlServer.Replication.dll' or one of its dependencies. The specified module could not be found." - iis-7

I am trying to deploy a web application built in VS 2012 on IIS7. Getting the error "Could not load file or assembly 'Microsoft.SqlServer.Replication.dll' or one of its dependencies. The specified module could not be found."
I have checked, I have this DLL in the following locations -
1 - My project location bin directory
2 - C:\Program Files (x86)\Microsoft SQL Server\100\SDK\Assemblies
But I find that the DLLs are of different size at different places, at one place it is 1.53 MB where as other is 1.68 MB.
This machine is 64 bit. And I have installed SQL Server 2008 Express and SQL Server 2008 Express Management Studio.

I have just found the answer for this problem. It started working as soon as I replaced the replication dll in my bin folder. The problem was with the version of this DLL.

Related

Crystal Reports - Could not load file or assembly 'CrystalDecisions.ReportAppServer.Controllers'

I recently switched to a new computer and can no longer use Crystal Reports when I publish to a server location, it works fine locally.
The exact error I get is: Could not load file or assembly 'CrystalDecisions.ReportAppServer.Controllers, Version=13.0.3500.0, Culture=neutral, PublicKeyToken=692fbea5521e1304' or one of its dependencies. The system cannot find the file specified.
I have tried/verified:
SAP Crystal Reports version 13.0.24.2970 is installed along with SAP Crystal Reports runtime engine for .NET Framework (32 & 64 bit) version 13.0.25.3158 are installed on my local machine.
Server has SAP Crystal Reports runtime engine for .NET Framework (32 & 64 bit) version 13.0.6.1027 and 13.0.21.2533 respectively.
Checked the C:\Windows\assembly\GAC_MSIL\CrystalDecisions.ReportAppServer.Controllers file and verified that the listed version on the internal file matches the 13.0.3500.0 version in the config file as well as checking that the .dll file is included in the file.
Checked the server's C:\Windows\assembly folder and verified that the CrystalDecisions.ReportAppServer.Controllers.dll includes version 13.0.3500.0 with a file version of 13.0.21.2533.
Checked that the .NET Framework Version 4_0_30319 and ASP.NET Framework Version 4_7_3429_0 is included in the aspnet_client folder both locally and on the server.
Checked that the local references (CrystalDecisions.CrystalReports.Engine; .ReportSource; .Shared; and .Web) are all included locally, set to copy local, and have a version that matches the config file and .dll versions (13.0.3500.0).
Checked that the target framework in VS 2010 is set to 4.0.
Tried to change version to 13.0.2000.0 in config file but received debugging error that CrystalReportViewer is ambiguous to CrystalDecisions.Web.
Tried other aspnet_client folder versions
Tried to include specific code config file to look for aspnet_client folder
<businessObjects>
<crystalReports>
<crystalReportViewer>
<add key="UseBrowserLocale" value="true" />
<add key="resourceURI" value="/aspnet_client/system_web/4_0_30319/crystalreportviewers13" />
</crystalReportViewer>
</crystalReports>
</businessObjects>
Tried removing all Crystal Report assemblies from the config file but still received an error after publishing.
The only thing I have not tried is uninstalling Crystal Reports and installing the latest version. My coworker and I both received new laptops and he was able to get his working just fine and had installed the same version of CR as I did. Our code matches as well.
The one thing I can think of that may be causing an issue is that the file version on the .dll in question is newer than the file version that is on the server. Could this be causing the issue? If not, can someone help me figure this out?
Hit the same problem myself deploying to Windows Server 2016
if installing the MS c++ runtime doesn't help you, this is what I did:
On DEV Machine
Uninstall Crystal for Visual Studio
uninstall Crystal x64 runtime
Reboot
Install dot net 4.7.2
Install Microsoft Windows Update KB2999226
Install Crystal for Visual Studio (includes x64 Runtime) (V26)
Fix Crystal References (13.0.4000.0) in reports and calling pages
Rebuild app and publish
On Webserver
Install Crystal x32 runtime (V26)
Install Crystal x64 runtime (V26)
Install the MS c++ runtime
Push New published site to Web Sever
Remove Crystal Report assembly references from Web.config <-- responsible for the " The system cannot find the file specified." error
Reboot Azure Server

OutOfMemoryException from aspnet_merge when trying to publish WebSite as single DLL

I thought this was going to be a simple thing to fix, but after trying several solutions I found on Google (clearing temp for the system, running build through 64-bit IIS Express, and building in release mode instead of debug), I'm still getting the following error:
The command that is being run:
C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\aspnet_merge.exe C:\Users\jmckinnon\AppData\Local\Temp\WebSitePublish\cv_net_2008--650083730\obj\Debug\AspnetCompileMerge\TempBuildDir -o xxxxx -copyattrs C:\Users\jmckinnon\AppData\Local\Temp\WebSitePublish\cv_net_2008--650083730\obj\Debug\AssemblyInfo\AssemblyInfo.dll -a -debug
I'm getting this error by running a publish to a zip with the following precompile settings:
A few things to note:
The WebSite is NOT a WebApplication!
The site has over 9100 files
Running .Net 4.5
Trying to build on a Windows 7 Professional 64 bit machine with 16GB of RAM
Only reason I'm trying to build into a single DLL is because I need to version the output of the package. I found out I can version the App_Code using an AssemblyInfo.vb file but the only way I can version all of the other DLLs (default no merging publish generates a DLL for each page) is to add a version directive in each page which is too much to maintain with over 1000 pages.
aspnet_merge is a 32-bit process and seems to crash when it gets to close to 2GB memory usage, which happened to our project. We fixed that by making aspnet_merge.exe large address aware using editbin.exe (included with VS2015, but not with VS2017 it seems...).
editbin /LARGEADDRESSAWARE "C:\Program Files (x86)\Microsoft SDKs\Windows\v10.0A\bin\NETFX 4.6.1 Tools\aspnet_merge.exe"

SSIS 2016 VS 2015 Error 0xC001700A Version number in the package is not valid. he version number cannot be greater than current version number

I upgraded an SSIS 2008R2 package to SSIS 2016 using the upgrade wizard. It upgraded successfully. I do have both 2008R2 and 2016 SQL Server loaded on my server. I am executing a batch file that calls the upgraded package. The batch file is calling DTEXEC.exe from "C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\". I receive these errors:
0xC001700A The version number in the package is not valid. The version number cannot be greater than current version number.
0xC0016020 Package migration from version 8 to version 6 failed with error 0xC001700A.
0xC0010018 Error loading value ",DTS:Property xmlns:DTS="www.microsoft.com/SqlServer/Dts" DTS:Name="PackageFormatVersion">8" from node "DTS:Property".
Any suggestions on what I can try next?
Try changing the path to DTEXEC.exe in your batch file to the following
C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\
Detailed Explanation
The error is likely from you running the DTEXEC.exe from the SSIS 2008 installation folder i.e. from C:\Program Files (x86)\Microsoft SQL Server\110\DTS.
The equivalent folder for SSIS 2016, if you had done the default installation, is as follows
32-bit SSIS: C:\Program Files (x86)\Microsoft SQL Server\110\DTS\Binn\
64-bit SSIS: C:\Program Files\Microsoft SQL Server\110\DTS\Binn\
From your question, it looks like you are trying to execute the 32-bit version of DTEXEC.exe, so the right path to call it from, in your batch file is
C:\Program Files (x86)\Microsoft SQL Server\130\DTS\Binn\
References:
File Locations for Default and Named Instances of SQL Server
dtexec Utility - Considerations on Computers with Side-by-Side Installations

BizTalk 2013 R2: Error in receive pipeline

Facing an issue after deployment of BizTalk solution on another server.
Error is highlighted below:-
There was a failure executing the receive pipeline:
"BTAHL72XPipelines.BTAHL72XReceivePipeline, BTAHL72XPipelines,
Version=1.3.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35"
Source: "BTAHL7 2.X Disassembler" Receive Port:
"HL7_25_ADT_A02_ReceivePort" URI: "******Some Location*******"
Reason: Field not found:
'Microsoft.Solutions.BTAHL7.Pipelines.MessageUtils.VersionforAck24'.
PS: I have already installed BizTalk 2013 R2 with HL7 Accelerator R2 two times on server.
It looks to me a installation issue, I have been running BizTalk 2013 R2 with HL7 Accelerator without any issues. Some suggestions
Most likely you have an old version of Microsoft.Solutions.BTAHL7.PipelineCommon.dll (possibly 2010 version). Make sure its version is 3.11.158.0. This assembly can be found in "\Program Files (x86)\Microsoft BizTalk 2013 R2 Accelerator for HL7\Bin" folder.
Uninstall HL7 Accelerator and Install it again, make sure you use 2013 R2 iso file
Is the assembly Microsoft.Solutions.BTAHL7.PipelineMessageCore deployed? Check under All Artifacts->Resources. Try redeploying it if it's in there.
Also take a look at the schema from that assembly under All Artifacts->Schemas and make sure it has the node. If it doesn't, you definitely have to redeploy from the original installation version, or at least undo any modifications that hav ebeen made to rename/remove that node.
Earlier we were using window server 2012.
In order to fix this issue, we did installation for window server 2012 R2,
Sql server 2014, VS 2013 and Framework 4.5.
Thanks all for helping out to resolve this issue.
I don't clearlyunderstand if it is a custom pipeline but if it is then you should copy your custom pipeline component to path
C:\Program Files (x86)\Microsoft BizTalk Server 2013 R2\Pipeline Components
if you are on development environment and tired of copying dll then a good way is:
Your dll mus must be deployed in GAC. Then a simpler way to do that is using gacutil.exe to deploy it. By the help of Visual Studio you can achieve this by post build event
"C:\Program Files (x86)\Microsoft SDKs\Windows\v8.0A\bin\NETFX 4.0 Tools\gacutil.exe" /i $(TargetPath)
After that you don't have to copy any dll but in production this may leads you forgetting to copy be careful.

Change launch path of Visual Studio 2010 Web Server

How I can tell Visual Studio 2010 to launch built in web server from a different location. Is there a registry settings somewhere that I can modify or some how change the Debug -> Start Debugging menu item command?
From
C:\Program Files (x86)\Common Files\microsoft shared\DevServer\10.0\WebDev.WebServer20.exe
To
C:\Program Files\Common Files\microsoft shared\DevServer\10.0\WebDev.WebServer20.exe
If you've facing the problem in connection with Oracle integration with ASP.NET in Windows 7 64 bits, then relax... XD
That's the solution (I'm using Visual Studio 2010 32 bits):
First of all, follow the steps here:
System.Data.OracleClient requires Oracle client software version 8.1.7
Then apply these steps:
Copy the directory of your webserver (typically in "C:\Program Files (x86)\Common Files\Microsoft Shared\DevServer\10.0") to "C:\Program Files\Common Files\Microsoft Shared\DevServer\10.0";
Open cmd, navigate to directory pasted in step 1 and start the web server (in my case "WebDev.WebServer40") pointing to the directory of your project (be careful, because this path cannot contain parenthesis, that causes the Oracle Bug 'ORA-06413: connection not open' as can be see described here);
If you want to debug your application, change the default URL to the URL of your started server in Visual Studio. In Solution Explorer go to your project > right click > properties > web > in "Servers" section select "Use Custom Web Server" and place the URL that your server are running on. After this, start debug and be happy =D
For those who are still facing this issue in 2016 like me,
you can change step1 of Caique Lemos's answer to:
mklink /J c:\ProgramsX86 "C:\Program Files (x86)"
And use c:\ProgramsX86\... for step2
Also, run as administrator can skip setting the folder permissions in the link above.

Resources