I have a receive location working on a 64bit host with a schema located in an assembly built in visual studio 2013 (let's call it NameOfMyAssembly). This works fine so far.
Now I need to make it run under a 32bit host (to use an SQL adapter).
When I create the same receive location but on a 32 bit host, I get the following error :
The document specification NameOfMySchema from assembly NameOfMyAssembly failed to load. Verify the schema for this document specification is deployed and is in the Global Assembly Cache.
Do I need to make another schema for my SQL adapter? Or is there a way to deploy my assembly to make it visible to 32 bits hosts?
Related
I have just installed Visual Studio 2010 and I can not make a simple database using Visual Studio. I use the following method to create the database:
The problem is when I tried to create it, I see this error:
I also see the following error when I want to access to the Asp configuration section in my Visual Studio:
An error occurred during the execution of the SQL file 'InstallCommon.sql'. The SQL error number is 5110 and the SqlException message is: The file "\MAC\HOME\DOCUMENTS\VISUAL STUDIO 2010\WEBSITES\ULTIMATEGOLDENSTUDIO1\APP_DATA\ASPNETDB_TMP.MDF" is on a network path that is not supported for database files. CREATE DATABASE failed. Some file names listed could not be created. Check related errors. Creating the ASPNETDB_3cde4c4c17f74bb991c3d4fd2714db62 database...
Please let me know how to fix this problem.
It looks like you're running Visual Studio inside of a Parallels VM w/ your Windows User drive mapped to your host machine's shared Home folder.
Windows treats that as a network folder and, as the error message says, that isn't supported in this case.
The easiest solution would be to change the location of your Windows Profile directory so that it points to a location inside of your VM rather than a shared folder between the guest and host OSes.
tried looking at other examples on this and am a bit confused. I have 2 web servers that are load balanced and a sql server box (sql 2012). my cube is created on the sql server box (i see it in management studio). when i try to access via my asp.net page i receive the above error.
now, i see the msolap110.dll in C:\Program Files (x86)\Microsoft Analysis Services\AS OLEDB\110 on the sql box. do i need to do something permission wise with the dll or something? do i need to install analysis services on the web server? is there a specific port or something (doubtful as sql is running fine).
connection string is as follows:
"Provider=msolap;Data Source=;Initial Catalog=AutoOLAPAW;Cube Name=SampleCube;"
going to try to force to use MSOLAP.5 but waiting on a republish from our security/deployment group.
this all works fine in dev but my (more secured/stripped down) prod/qa is where i'm seeing the issue. using iis7 on both.
If you are using ADOMD.NET then either set CopyLocal=True on that reference on your ASP.NET source code so Microsoft.AnalysisServices.AdomdClient is deployed with the web app... Or install SQL_AS_ADOMD.msi from:
https://www.microsoft.com/en-us/download/details.aspx?id=49999
If you are using OLEDB then install SQL_AS_OLEDB.msi from that same link.
If you don’t want the SQL2012 version but want the latest then install from here and use Provider=MSOLAP in the connection string (instead of a number like MSOLAP.5).
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
Receiving below error message in Visual Studio 2008 while creating a connection for database.
could not load file or assembly
'microsoft.sqlserver.management.sdk.sfc ,Version=10.0.0.0,
Culture=neutral,PublicKeyToken=89845dcd8080cc91' or one of its dependencies.
The system cannot find the file specified.
I am trying to create database internally i.e. .mdf file and store it in the App_data folder.
But I'm not able to create the connection.
Please help me to sort out the issue quickly.
You can download these files from Microsoft website.
1.Microsoft SQL Server System CLR Types
2.Microsoft SQL Server 2008 Management Objects
3.Microsoft SQL Server 2008 Native Client.
After installing the above three files try to connect your application with sql server database and if still you got the same error message then don't worry and close your application then start it again and you will be able to connect it.
I have BizTalk orchestration where it reads xml file calls .net class from expression shape and send file to send location but it doesn't work always. It only works like 3 out of 5 times. When it doesn't process my orchestration, I am getting "Could not load file or assembly 'XXXX, Version=1.0.0.3, Culture=neutral, PublicKeyToken=xxxxxx' or one of its dependencies. The system cannot find the file specified."
Please help. Thank you.
On each BizTalk server with a BizTalk host instance, you need to verify that the assembly is in the Global Assembly Cache (GAC). If you can load a Visual Studio or Windows SDK command prompt on each, then run gacutil /l > c:/gac.txt and it will output everything in the GAC to a text file called gac.txt on your C: drive. Look in that file to verify that the assembly (and the right version of that assembly) is deployed on EACH BizTalk server that could be running a BizTalk host instance.
Whenever you make changes to an application, and deploy those changes, I find it helpful to restart the host instance your application is running on.
Also, if you are using an external assembly, perhaps in an orchestration or a map, you need to make sure that assembly is in the GAC (global assembly cache).