I am running Visual Studio 2010 on a Win 7 - 64 bit machine. I created a WCF service project. I debugged it, and the WCF Test Client loaded, as expected. I ran the GetData operation, and upon doing so get this
Assembly Oracle.DataAccess was not found. Reinstall the assembly or Visual Studio
I never installed the Oracle adapter for dot net. So I search through the various machine.config files (both 32 and 64 bit versions of the framework, and multiple versions of the framework), and sure enough, there are entries for the Oracle data adapter. I removed them all, but am still getting the error.
Ideas???
Related
I have an ASP.NET Core web application which I'm trying to run in 32-bit with IIS Express. I followed other guides and tips to make IIS run in 32-bit, but every time i try to run the application it crashes with the error message:
System.BadImageFormatException: Could not load file or assembly. An
attempt was made to load a program with an incorrect format.
I have tried the following:
Set the build and debug to run x86
And unchecked the Use the 64 bit version of IIS Express for web sites and projects
But my project still closes almost immediately with the error mention above. Is there a setting that I am forgetting about or something else I need to do before the project can run in 32-bit.
I'm using visual studio 2017 on Windows 10 with IIS Express version 10.0.14393.0 and AspNetCore 2.1
I am getting this error when I bring up the website from within Visual Studio 2013. LibSass.x64.dll & libsassnet.dll are in the bin folder.
Could not load file or assembly 'LibSass.x64' or one of its dependencies
You can switch to 64 bit IIS Express in Visual Studio settings:
Tools > Options > Projects and Solutions > Web Projects > Use the 64 bit version of IIS Express for web sites and projects.
Update:
If you get this error on a clean Windows machine, you have to install Visual C++ Redistributable Packages for Visual Studio 2013.
I recommend to install both x86 and x64 packages.
It is a known issue with libsassnet. Basically you need correct library referenced, either 32 bit or 64 bit. In our project we reference 64 bit and thus project needs to be compiled and run in 64 bit environment. By default IIS Express runs in 32 bit (since VS.NET runs in 32) so that is why you get an exception.
Better create an IIS site and run it using it or you can modify nuget reference of libsassnet to 32 bit version.
PS: we resolved that automatically in azure deployment, but still working with libsassnet developers to resolve it when it is deployed locally.
Looks like the latest version requires the VC++ 2015 version: https://www.microsoft.com/en-us/download/details.aspx?id=48145
After successfully testing my MVC4 programs using this environment
I tried to publish it to 64-bit Windows 2008 Server with the IIS that disallows 32 bit apps, then I start getting stuck with the exception : the referenced dll's dependencies cannot be found!
I tried every advice the internet can give me including modifying web.config to reflect their dlls' on deploy-to server win 2008 using global cache cmd's on the prompt!
Yet nothing works. 32-bit is working but 64-bit is flat broke!
First, I stopped messing around the web.config. Then, I re-installed Oracle 11g 64 on my Windows 2008 server. Finally I placed ODAC on top of 11gx64's installation. The key to success is locating the correct ODAC to match the version of Oracle you have on your system.
http://www.oracle.com/technetwork/database/windows/downloads/index-090165.html
To VERIFY you have the right ODAC installed correctly over oracle 11 g you have to look into [asp.net] and [ODP.net] directories to make sure they BOTH have 2.x's and 4's dirs in each bin and their presence in global cache 64.
Ater solving the ODAC installation problem, I start experimenting with oracle client dll's. I copied the Oracle.DataAccess.dll(64-bit) from bin [2.x] to my app's compiled bin only to watch my program still crashed with the same complaint that it cannot find the dependent DLL's. Then I copied the Oracle.DataAccess.dll from bin [4], then everything WORKS fine!!
Now the remaining question is why 4.112.4 not found in register cache GAC_64 is working great but the set of dll's registered in GAC_64 broke the program? Can't help not being confused.
See the resulting view of the working dlls ==>
If you acquire all those screens I show in this case, your MVC4 apps should fly high with Oracle 11 g 64-bit client! Good luck! I'll share mine with you!
I would like to run a .exe file made with visual studio 2003 but I get an error every time I run it on a windows 7 machine, vista machine, and xp machine. The error on Windows 7 and vista says "application has stopped working" and then makes me close the error box.
In windows xp it's a little different error, "the application failed to operate (0xc0000135) Click on OK to terminate the application."
That error code seems to indicate the application failed to initialize correctly.
It is possible that the anticipated .NET version is not present.
As far as I know, VS 2003 by default compiles against the .NET 1.1 library. There is no straightforward way of installing this on a Windows 7 or Vista box. Do you need to compile it against the .NET 1.1 library, or can you load it in VS2005, change the output .net version to 2.0 or higher, and recompile the application?
If you have the source code to the application, try running the application in debug mode and stepping through line by line until you find the exception. If you do not have the source code, possibly try running the application in a couple different compatibility modes. Another option to try is to check the windows event log for anything more specific.
If you want to get really deep into it, you can use SysInternals ProcMon.exe and filter on the failing exe to view the WinAPI calls that are happening during the failure.
Also, a basic search of forums shows that error is usually accompanied with framework issues. Either recompile the application or check out what your required framework is in the VS2003 project settings.
My company has a VB6 application using Crystal Reports 7 which a client has asked to be installed on Windows 7 32 bit. It is currently installed on Windows XP 32bit SP2 machines at the client. Connection to the DB is done via ODBC to SQL Server 2000 instance on another server.
On Windows 7, the installation works fine, however when you try to open the application, the error is given.
I have looked at the following:
Registering all the dll's and ocx files using regsvr32. Some will not register as they either are registered already or the following message is given "Make sure that "[name].dll" is valid DLL or OCX file and then try again." I read this forum thread regarding this: http://social.msdn.microsoft.com/forums/en-US/vblanguage/thread/0653f685-4526-45d9-89f3-8c479a6b4c62
Monitored the opening of the application using a ProcessMonitor application to try and spot if there is a missing dll or ocx file - this does not seem to be the case.
Reviewed the application according to this list and nothing seems to be against these guidelines
I've noticed two items in the knowledge base that relate to this
http://support.microsoft.com/kb/281848 - the comdlg32.ocx bundled with the application is version 6.0.81.69 and the one in the system32 folder on the dev machine (WinXP 32 bit) is 6.1.97.82. However if this was the issue then surely it would not work currently?
http://support.microsoft.com/kb/184898 - I'm not sure how to confirm that this is the issue
Finally, due to complexities, I am not allowed to make code changes to this application. Even if I was, I'm not a VB6 programmer, just the guy who got the terribly support project! If code changes are required, then I'll have to investigate using WinXP mode.
Update: I get the same error in XP Mode. That's a Win XP with SP3 VM. This runs on a Win XP SP2 VM, is there potentially something in SP3 that would have caused this to occur? Or is it just a fact of it being XP Mode?
I got the same error but I solved by using regsvr32.exe in C:\Windows\SysWOW64.
Because we use x64 system. So if your machine is also x64, the ocx/dll must registered also with regsvr32 x64 version
The file msrdo20.dll is missing from the installation.
According to the Support Statement for Visual Basic 6.0 on Windows Vista, Windows Server 2008 and Windows 7 this file should be distributed with the application.
I'm not sure why it isn't, but my solution is to place the file somewhere on the machine, and register it using regsvr32 in the command line, eg:
regsvr32 c:\windows\system32\msrdo20.dll
In an ideal world you would package this up with the redistributable.
This download fixed my VB6 EXE and Access 2016 (using ACEDAO.DLL) run-time error 429. Took me 2 long days to get it resolved because there are so many causes of 429.
http://www.microsoft.com/en-ca/download/details.aspx?id=13255
QUOTE from link:
"This download will install a set of components that can be used to facilitate transfer of data between 2010 Microsoft Office System files and non-Microsoft Office applications"
You say it works once you install the VB6 IDE so the problem is likely to be that the components you are trying to use depend on the VB6 runtime being installed.
The VB6 runtime isn't installed on Windows by default.
Installing the IDE is one way to get the runtime. For non-developer machines, a "redistributable" installer package from Microsoft should be used instead.
Here is one VB6 runtime installer from Microsoft. I'm not sure if it will be the right version for your components:
http://www.microsoft.com/downloads/en/details.aspx?FamilyID=7b9ba261-7a9c-43e7-9117-f673077ffb3c