-
Notifications
You must be signed in to change notification settings - Fork 30
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
install issue #39
Comments
Are you on a 32 bit Windows? If so, we haven’t published a prebuilt image for the driver. Thanks, Raymond Feng StrongLoop http://strongloop.com/ makes it easy to develop APIs http://strongloop.com/mobile-application-development/loopback/ in Node, plus get DevOps capabilities http://strongloop.com/node-js-performance/strongops/ like monitoring, debugging and clustering.
|
I have 64 bit WIndows 7 Enterprise Edition. However the Node JS i have is 32 bit. The loopback-connector-oracle is only for 64-bit versions? |
You should install the 64 bit Node. We start to deprecate the 32 bit support as iojs doesn't ship 32 bit version for Windows. |
Thanks! I was able to do a install with 64 bit version of Node. However now when I do a simple project using strongloop, it looks like it ws not properly installed, even though it said it did. Oops! Something is wrong Connector "oracle" is not installed. Add the connector to your project, configure the environment variables, restart Arc and try again. See docs: Installing the Oracle connector for more information. Show/hide details Name: InvocationError |
so if I do "slc run", i get the error. I have tried installing the loopback-connector-oracle quite a few times. taken the steps for Windows at following link: WARNING: LoopBack connector "oracle" is not installed as any of the following modules: ./connectors/oracle To fix, run:
events.js:72 ./connectors/oracle To fix, run:
|
Can you dump out the env vars for PATH to check if the Oracle instant client DLLs are on the path? |
yes i can see the instant client on my PATH installed by loopback-connector-oracle The following the the path (echo %PATH%) on my windows (x64) machine C:\Users\Redirection\AppData\npm; |
just trying to make sure around the versions i have installed Node (v0.10.38) is there any plce where i can verify if this versions are a correct match to be working in sync with each other. |
Anyone has inputs to have this connector working... |
What VisualStudio version do you have? |
I have Visual Studio 2013 |
Express 2013 for Windows Desktop https://www.visualstudio.com/en-us/products/visual-studio-express-vs.aspx |
I have VS 2012. It might be the case that VS 2013 is not compatible with Oracle Instant Client. |
Thanks! Works good now with VS 2012. |
Hi,
While trying to install the connector with Node (v0.12.0) and npm (v2.9.1), i am getting the following error
C:\TD\USTS\NodeWorkspaces\DBConnect>npm install loopback-connector-oracle --save
\
Downloading/Extracting http://7e9918db41dd01dbf98e-ec15952f71452bc0809d79c86f575
1b6.r22.cf1.rackcdn.com/loopback-oracle-Windows-x86-abi14-1.5.0.tar.gz
events.js:85
throw er; // Unhandled 'error' event
^
Error: incorrect header check
at Zlib._handle.onerror (zlib.js:366:17)
npm ERR! Windows_NT 6.1.7601
npm ERR! argv "node" "C:\Users\Redirection\arathor\AppData\npm\node_module
s\npm\bin\npm-cli.js" "install" "loopback-connector-oracle" "--save"
npm ERR! node v0.12.0
npm ERR! npm v2.9.1
npm ERR! code ELIFECYCLE
npm ERR! loopback-oracle-installer@1.4.0 install:
node pkginstall.js
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the loopback-oracle-installer@1.4.0 install script 'node pkgi
nstall.js'.
npm ERR! This is most likely a problem with the loopback-oracle-installer packag
e,
npm ERR! not with npm itself.
npm ERR! Tell the author that this fails on your system:
npm ERR! node pkginstall.js
npm ERR! You can get their info via:
npm ERR! npm owner ls loopback-oracle-installer
npm ERR! There is likely additional logging output above.
npm ERR! Please include the following file with any support request:
npm ERR! C:\TD\USTS\NodeWorkspaces\DBConnect\npm-debug.log
The text was updated successfully, but these errors were encountered: