400 Error when attempting to convert word files to PDF

Forum|Forum|3 years ago
January 31, 2023
5 replies
3177 views

Using the NodeJS sdk we keep getting 400 errors on files that previously worked to convert.

2023-01-31T08:43:16.574:[INFO]: All validations successfully done. Beginning PDF conversion
ServiceApiError:
    at rejectWithServiceApiError (/Users/casper/Projects/proj/backend/node_modules/@adobe/pdfservices-node-sdk/src/internal/http/http-client.js:31:17)
    at handleJsonResponse (/Users/casper/Projects/proj/backend/node_modules/@adobe/pdfservices-node-sdk/src/internal/http/http-client.js:55:3)
    at handleErrorResponse (/Users/casper/Projects/proj/backend/node_modules/@adobe/pdfservices-node-sdk/src/internal/http/http-client.js:117:2)
    at onEnd (/Users/casper/Projects/proj/backend/node_modules/@adobe/pdfservices-node-sdk/src/internal/http/http-client.js:176:3)
    at IncomingMessage.<anonymous> (/Users/casper/Projects/proj/backend/node_modules/@adobe/pdfservices-node-sdk/src/internal/http/http-client.js:216:5)
    at /Users/casper/Projects/proj/backend/node_modules/@opentelemetry/context-async-hooks/src/AbstractAsyncHooksContextManager.ts:74:49
    at AsyncLocalStorage.run (node:async_hooks:311:14)
    at AsyncLocalStorageContextManager.with (/Users/casper/Projects/proj/backend/node_modules/@opentelemetry/context-async-hooks/src/AsyncLocalStorageContextManager.ts:40:36)
    at IncomingMessage.contextWrapper (/Users/casper/Projects/proj/backend/node_modules/@opentelemetry/context-async-hooks/src/AbstractAsyncHooksContextManager.ts:74:26)
    at IncomingMessage.emit (node:events:532:35) {
  requestTrackingId: undefined,
  statusCode: 400,
  errorCode: 'UNKNOWN'
}

This topic has been closed for replies.

S

System22640200kiod

Participating Frequently

We are getting same issue all of a sudden with Node v12.x and

@adobe/pdfservices-node-sdk 2.1.0

We have solution deployed in production, so updating to latest is non-starter.

Raymond Camden

Community Manager

You can't update to 2.3.0? That's a minor update, not a major one.

S

System22640200kiod

Participating Frequently

This is not how it works. Our production site has been broken since yesterday because of this and we come to find out 12 hours later. I can't just upgrade package in production just like that regardless of whether its minor or major. Also, we are now getting 500 error code now. We were getting 400 earlier.

Raymond Camden

Community Manager

Update:

Today we released a new 2.x version of the SDK, 2.3.0. For folks who can't upgrade to 3.x, you can select this version, but we *highly* recommend migrating to 3.x as soon as possible. 2.X is EOL by September of 2023.

L

LAPS25810094s4dn

Participating Frequently

Anyone found the root cause of this issue? We also experienced the same behavior today. Our application is in production and can't update to the latest SDK version right away.