I install Oracle 11gR2 32 bit client on my Win7 64 bit machine. its Oracle.DataAccess.dll's version is 2.111.7.0. When I run my code, I got this error message:
Could not load file or assembly 'Oracle.DataAccess, Version=2.111.7.0, Culture=neutral, PublicKeyToken=89b483f429c47342' or one of its dependencies. The system cannot find the file specified.
What's the problem? Does it means, I cannot use this 32 bit on my Win7 64 bit machine, I have to install 64 bit version of it? Because 32 bit is our company policy to install on all my user's machine. It is hard to change it.
Thank you so much
Wes
If you run the application in 32 bit mode and link it against this specific version in the first place, it works and you can use the 32 bit version on a 64 bit system.
To force an application to run in 32 bit mode, you have several options (partially depending on whethere it's a stand-alone application or web application), which are outline in this article.
Related
I have a 32 bit Windows Operating System. But my system supports 64 bit architecture,i could say that because when i downloaded and ran VMWare Processor Check for 64 bit compatibility tool from the VMware website it shows 'This host is capable of running a 64-bit guest Operating System under this VMWare product'. So with this 64 bit architecture would i be able to install and use Cloudera VM and then hadoop?
Based on the comments, you can go ahead and use 64 bit without any issues and hadoop will be up and running. However, you can always go back and download 32 bit and import in your VMWare and have both 64 bit and 32 bit imported. If in case you get in to any issues with 64 bit, then you can stop using it and run 32 bit.
If cloudera is not supporting 32 bit, then check with hortonworks VM.
Hope this helps!
They both install node.exe into C:\Program Files (x86)... so I'm wondering what the actual difference is. I know that there is some because node-sqlserver module is failing on our machine and it does so in different ways for x86 and x64 versions of Node.
Can somebody explain the difference for me? Thanks.
The x64 installer installs the 64 bit version of node which is compiled against the 64 bit version of V8. The node-sqlserver package is a native module which means it needs to be compiled against the matching version of node. IE: It will fail if you are using a pre-compiled, 32 bit version of the module against the 64 bit version of node.
Other than the typical differences between 32 & 64 bit applications (larger address space, use of 8 bytes for addresses instead of 4 bytes), node doesn't differ between the two versions.
I have a vbscript, which connects to a .mdb file using 32 bit drivers and it works fine on a 32 bit system, but when i try to run the same on a 64 bit system( with 32 bit office),the connection doesnt work.
I cant install 64 bit drivers as the system has 32 bit office.
Is it possible to connect to .mdb file using 32 bit drivers on a 64 bit system?
For your scenario, just make sure that the process executing your script is running on 32 bit.
You could try to call your script from the x86 PowerShell prompt to test it on your x64 system.
I wrote a COM Dll for explorer that extends windows context menu, registration via regsvr32 works fine on 32 bit Windows, but on 64 bit it does not work without any clue. regsvr32 reports successful registration, although Dll is not working. I tried to call regsvr32 from SysWow64 directory aswell as from system32 and this is not the cause as far as I can guess. Checked the registry - everything was written to the registry to wow3264Node ofcourse (as installation was on 64 bit OS). Still nothing happens. Hard to provide any specific information for now. Can anyone suggest or point to other possible causes of such behavior. Thanks in advance.
You need to compile your DLL for 64 bit. The fact that the registration code writes to Wow6432Node indicates that your DLL is 32 bit. On a 64 bit OS, Explorer is a 64 bit process and so can only load 64 bit shell extensions.
Don't forget to register both 32 and 64 bit versions of the shell extension on a 64 bit machine so that any 32 bit programs can see your shell extension. You do that using C:\Windows\SysWOW64\regsvr32
I know that with Vista you can generate a dump file by goigg to task manager->processes-> right clicking on the process.
Is this option available in other versions of windows meaning Windows 7, Windows 2003, Windows 2008 etc?
It is available in Windows 7 and 2008, but I don't know about Windows 2003. One thing to keep in mind is that on a 64 bit version of Windows, there are actually two versions of Task Manager - one 32 bit and one 64 bit. If you use the 64 bit, you'll get a 64 bit dump, even if the process is 32 bit. I.e. you'll get all the Wow64 in the process as well. However, if you use the 32 bit version of Task Manager, you'll get a 32 bit dump without the Wow64 stuff. The latter is significantly easier to debug as the abstraction layer isn't present in the dump.
To collect a 32 bit dump, by opening a 32 bit task manager found at C:\Windows\SysWOW64\taskmgr.exe
Check in process explorer that it has a (32) to it