Develop Reference

Azure Function with Node.js can't access SQL database: Entry point problem?

I am trying to connect an Azure Function to a SQL-Database that I also created in Azure. Sounds pretty simple and Microsoft even has a pretty good POC tutorial for it. However, in my case the Azure Function is dropping "entryPoint" errors that I am not able to resolve.
I checked some other stackoverflow discussions (Can't connect Node.js server to Azure SQL Database) and googled the hell out of it. Unfortunately it seems like none of this is helping. I updated the "function.json" to set my entryPoint as shown below.
{
"bindings": [
{
"authLevel": "function",
"type": "httpTrigger",
"direction": "in",
"access": "listen",
"name": "req",
"methods": [
"get",
"post"
]
},
{
"type": "http",
"entryPoint": "index",
"direction": "out",
"name": "res"
}
]
}
My index.js code is a very trivial try to connect to the database and tell me about the success.
var Connection = require('tedious').Connection;
var config = {
userName: 'XXXX',
password: 'XXXX!',
server: 'XXXX.database.windows.net',
// If you are on Microsoft Azure, you need this:
options: {encrypt: true, database: 'XXXXX'}
};
var connection = new Connection(config);
connection.on('connect', function(err) {
// If no error, then good to proceed.
console.log("Connected");
});
Normally this should connect to the database and print a "Connected" to the console but somehow it shows this error:
[Error] Executed 'Functions.TediousTest' (Failed, Id=XXXXXXX)
node exited with code 1
[error] Worker was unable to load function TediousTest: 'Unable to determine function entry point. If multiple functions are exported, you must indicate the entry point, either by naming it 'run' or 'index', or by naming it explicitly via the 'entryPoint' metadata property.',[error] Worker XXXXXX uncaught exception: ReferenceError: executeStatement is not defined
Hopefully this is enough information to understand my problem. The database has no special firewall etc. at the moment. Besides it seems like the code snippet isn't even able to get in touch with the firewall. Thanks in advance.

I believe you haven't exported your function properly based on the error message - basically missed the module.exports line.
I guess your code looks something like this
...
async function TediousTest() {
...
}
If so, just add this line to the end
module.exports = TediousTest;

Output bindings not picked up or present in Javascript Azure Functions

I'm having a bit of difficulty getting my simple Azure Function to dump a JSON payload into a CosmosDB. Here is the desired setup:
[HTTP TRIGGER] -> [JS FUNCTION] -> [INSERT JSON TO COSMOS DB]
I've added a cosmosDB output binding via Integrate in the web console
I know this part works because it will auto-create the collection upon running.
However, this is where my success ends.
I've included my code here. Maybe there is something obvious that I have missed:
function.json
{
"bindings": [
{
"authLevel": "function",
"type": "httpTrigger",
"direction": "in",
"name": "req"
},
{
"type": "http",
"direction": "out",
"name": "res"
},
{
"type": "documentDB",
"name": "outputDocument",
"databaseName": "outDatabase",
"collectionName": "MyCollection",
"createIfNotExists": true,
"connection": "mydocdb_DOCUMENTDB",
"direction": "out"
}
],
"disabled": false
}
index.js
module.exports = function (context, req) {
context.log('JavaScript HTTP trigger function processed a request.');
context.bindings.outputDocument = {test: "hello world"}
context.done();
};
snippet output of context.log(context)
I've also peeked into the context variables, and it seems that the outbund bindings not there. I would have expected to see outputDocument here:
bindings:
{ req:
{ originalUrl: 'https://log-ugly-url-here',
method: 'POST',
query: [Object],
headers: [Object],
body: [Object],
params: {},
rawBody: '{\n "name": "Azure"\n}' } },
bind: [Function],
Executing this function in the portal gets a 200 OK, but no values show up in my cosmosdb collections.
No errors are shown anywhere.
Can anyone see what I might have missed?
Updates
It was recommended that I try to use JSON.stringify() around the payload, per this document:
context.bindings.outputDocument = JSON.stringify({test: "hello world"});
However, this has not resolved the issue. I've noticed that the documentation under the binding config sections does not recommend this strategy.
Update - Nov. 8, 2017 (10:12 AM)
I was using the Data Explorer blade in azure to see if there were results in my collections. I decided to use Robo 3T Mongo client. Now, when I query the collection I get the following error:
Error: error: {
"_t" : "OKMongoResponse",
"ok" : 0,
"code" : 1,
"errmsg" : "Unknown server error occurred when processing this request.",
"$err" : "Unknown server error occurred when processing this request."
}
I tried to look at the logs for this cosmosdb, but no errors show up.

I ran into this as well. Kept banging my head until I saw this:
https://learn.microsoft.com/en-us/azure/azure-functions/functions-integrate-store-unstructured-data-cosmosdb
“At this time, the Azure Cosmos DB trigger, input bindings, and output bindings work with SQL API and Graph API accounts only“
Looks like there is a bug in Azure that accidentally corrupts the database.

Error while running Paypal API using node js

I am running the following code in a script called pp.js. And I am running this on my index.html on loading of the page for test. I am bundling every source files using the latest webpack module.
var paypal = require('paypal-rest-sdk');
var user_config ={
'mode': 'sandbox', //sandbox or live
'client_id': 'xxxxxxx',
'client_secret': 'xxxxxxx'
};
paypal.configure(user_config);
var create_payment_json = {
"intent": "sale",
"payer": {
"payment_method": "paypal"
},
"redirect_urls": {
"return_url": "http://return.url",
"cancel_url": "http://cancel.url"
},
"transactions": [{
"item_list": {
"items": [{
"name": "item",
"sku": "item",
"price": "1.00",
"currency": "USD",
"quantity": 1
}]
},
"amount": {
"currency": "USD",
"total": "1.00"
},
"description": "This is the payment description."
}]
};
// TILL HERE THERE IS NO ERROR
paypal.payment.create(create_payment_json, function (error, payment) {
if (error) {
console.log("There seems to be some error... I hope it can be corrected.");
throw error;
} else {
console.log("Create Payment Response");
console.log(payment);
}
});
When the last bit of the code is run i.e. paypal.payment.create(create_ ... I am getting the following error in the console of my browser.
How do I rectify this?

This code should be run server-side. The same issue in PayPal SDK tracker: https://github.com/paypal/PayPal-node-SDK/issues/220
Quote 1 (from the linked ticket)
Please see #149 (comment). It seems that you are trying to run this code in the browser which may be a security problem. If the user has access to your credentials or have an access token, they can do anything that you can do as a merchant (e.g. create more payments, refund people money, etc.).
Quote 2 (from the #149 ticket):
I did some more investigation. Apparently, this request.js:54 Uncaught Error: Invalid value for opts.mode. error comes from a version of stream-http/request.js. I'm guessing that you are trying to use browserify and using stream-http in the browser to simulate node.js's built-in http module.
Are you trying to run this SDK code in the browser (instead of in a server-side node.js process)?
This node.js SDK should only be used on a secured server. I have very limited experience using browserify. Unless I'm mistaken, you need to give this SDK access to your client ID and client secret to make this SDK work, and if your code runs in the browser, you will be exposing the credentials to any browser client. This will allow any customer to be able to do anything to your account (e.g. refund all of your payments).
If it's just that part of your code is intended to be run in the browser and another part is in the server but the code is all in one project, I recommend separating out the code into 2 different projects with different package.json files so you can have separate dependencies.

Firebase authentication error auth/internal-error

when using email/password authentication with firebase I am getting an error trying to log a user in
calling .signInWithEmailAndPassword(email, password)
it hits this endpoint https://www.googleapis.com/identitytoolkit/v3/relyingparty/verifyPassword? which returns a 400. The error contains:
{
"error": {
"errors": [
{
"domain": "usageLimits",
"reason": "keyExpired",
"message": "Bad Request"
}
],
"code": 400,
"message": "Bad Request"
}
}
This has only started happening in the last day, but it is hard to tell from the HTTP response if this is an error on my end or google's. It return a 400 but then says internal error.
There are not meant to be any usage limits or key expirations for firebase so I am lost as to what is going on here

what does opcode==0 signify?

I am using Kony studio for an app development. I have done the login validation using Eclipse to code for creating web services to connect to the oracle10g database. But on the front end I'm getting an error, when I'm trying to connect the front end to the web service.
The status==400 is getting validated but I'm not getting opcode as 0, instead its going in the else statement and giving an error alert. This is the Javascript code for connecting to the web service.
Please help. What does opstatus==0 signify?
function GetLogin()
{
var Userid =login.txtloginuname.text;
var Password = login.txtloginpass.text;
var inputParamsLogin={serviceID:"servicelogin",uname:Userid,pass:Password}
if (Userid!=null && Userid!="" && Password!="" && Password!=null)
{
appmiddlewareinvokerasync(inputParamsLogin,loginCallBackresponse);
}
else
{
var alert_seq5_act0 = kony.ui.Alert(
{
"message": "Please Enter User name and password",
"alertType": constants.ALERT_TYPE_ERROR,
"alertTitle": "",
"yesLabel": "OK",
"noLabel": "",
"alertIcon": "",
"alertHandler": null
}, {});
kony.application.dismissLoadingScreen();
}
function loginCallBackresponse(status,loginResults)
{
if(status==400)
{
alert("productResults");
if(loginResults.opstatus==0)
{
alert("inside opstatus");
else
{
var alert_seq5_act0 = kony.ui.Alert({"message": "Service Failed:"+loginResults.errmsg,
"alertType": constants.ALERT_TYPE_ERROR,
"alertTitle": "",
"yesLabel": "OK",
"noLabel": "",
"alertIcon": "",
"alertHandler": null}, {});
kony.application.dismissLoadingScreen();
}
}
}
}
I am getting the alert "product results" but unable to get the alert "inside opstatus".
Instead I'm getting "service failed alert.

If the opstatus is 0, it indicates that the service call is a success while a non-zero value indicates a failure.
Please read the following that gives you more info on network call in Kony
The following is the description of the parameters associated with network call in kony:
status - an integer value - indicating the status
The following are the various status returned:
100 - network call initiated successfully - resultset will not be available and it is nil.
200 - network is in progress (when you start receiving the 1st byte) - resultset will not be available and it is nil.
300 - network call canceled - resultset will not be available and it is nil.
400 - network call is finished (gets called in both success and failure scenarios - actual state can be queried using opstatus in the resultset.
Note: On Mobile Web, the callback function is always invoked with a status of 400. Other intermediate status codes are not applicable on Mobile Web.
resulttable - a Object with key-value pairs - follows the same structure (opstatus, errcode, errmsg along with the actual network returned data)
This represents the Object returned by the service. This Object contains three values:
opstatus
errcode
errmsg.
If the opstatus is 0, it indicates that the service call is a success while a non-zero value indicates a failure.
If the opstatus is a non-zero value, it is captured in errcode. The following are the possible error codes:
1000- Unknown Error while connecting (If the platform cannot differentiate between the various kinds of network errors, the platform reports this error code by default).
1011 - Device has no WIFI or mobile connectivity. Please try the operation after establishing connectivity.
1012 - Request Failed.
1013 - Middleware returned invalid JSON string.
1014 - Request timed out.
1015 - Cannot find host.
1016 - Cannot connect to host.
1200 - SSL - Certificate related error codes.
The error message corresponding to each error code is captured in the errmsg parameter.