iisnode encountered an error when processing the request.

HRESULT: 0x6d
HTTP status: 500
HTTP subStatus: 1013
HTTP reason: Internal Server Error

You are receiving this HTTP 200 response because system.webServer/iisnode/@devErrorsEnabled configuration setting is 'true'.

In addition to the log of stdout and stderr of the node.exe process, consider using debugging and ETW traces to further diagnose the problem.

The last 64k of the output generated by the node.exe process to stderr is shown below:

(node:16084) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 6)
(node:16084) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 9)
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 12)
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 14)
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 22)
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 24)
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 28)
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 30)
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 35)
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 43)
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 51)
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 53)
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 56)
(node:16084) UnhandledPromiseRejectionWarning: Error: Transaction cannot be rolled back because it has been finished with state: commit
    at Transaction.rollback (C:\sites\cu-api\node_modules\sequelize\lib\transaction.js:86:29)
    at loginGoogleMeb (C:\sites\cu-api\utils\meb.js:996:44)
(node:16084) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 64)

คะแนนร้านค้า

Book info

Product details :

Review score from buyers