400 Error when attempting to convert word files to PDF

[Casper23927037ehe1]

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'
}

[Guillaume28186326qs1t]

Hi, same problem here - I have a subscription bought from AWS Marketplace - was working until Jan 30 5PM GMT...

[Joel_Geraci]

I ran into that myself yesterday. Try updating to the latest SDKs. You shouldn't need to modify your code other than that.

[LAPS25810094s4dn]

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.

[Guillaume28186326qs1t]

updating the node sdk to the latest version fixed the issue (3.2.0)

Incredible that Adobe didn't handle that better, at least returning an explicit error about client being incompatible anymore...

[Raymond Camden]

By any chance do you remember which version you had before?

[LAPS25810094s4dn]

@Raymond Camden we were using pdfservices-node-sdk v2.2.3 and it was working for months up until today.

[Gabriel22165674l66w]

Facing the same issue! Migrated to version 3.2.0 and see another error popping up

OCR-Extraction/node_modules/@adobe/pdfservices-node-sdk/src/internal/http/http-client.js:80
|| (result.content.error?.details?.error_code && apiGatewaySubErrorCodesForStatus[result.content.error.details.error_code]))) {
^

SyntaxError: Unexpected token .
at Module._compile (internal/modules/cjs/loader.js:723:23)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)
at Module.load (internal/modules/cjs/loader.js:653:32)
at tryModuleLoad (internal/modules/cjs/loader.js:593:12)
at Function.Module._load (internal/modules/cjs/loader.js:585:3)
at Module.require (internal/modules/cjs/loader.js:692:17)
at require (internal/modules/cjs/helpers.js:25:18)
at Object.<anonymous> (/home/ubuntu/projects/OCR-Extraction/node_modules/@adobe/pdfservices-node-sdk/src/internal/http/http-request.js:12:18)
at Module._compile (internal/modules/cjs/loader.js:778:30)
at Object.Module._extensions..js (internal/modules/cjs/loader.js:789:10)

Anyone face the same?

[Raymond Camden]

We've been able to discover why the earlier SDKs stopped working and we're working on a fix asap. As to this issue, it may be something else. Do you mind sharing what you were trying to do (ie, what action), and your input?

[Gabriel22165674l66w]

Raymond, we are using functionality to split the pdf. Upon debugging, we found the issue arising at module import line below:

const PDFServicesSdk = require('@adobe/pdfservices-node-sdk');
The current version of the sdk being used is --> @adobe/pdfservices-node-sdk@3.2.0

FYI, the exact code was working with the older version

[Glenn263035267yqi]

Yes I was having the same problem then you. It happen because you use a version of Node < 14. 

So you have three possibilities to fix it:
- Upgrade your project to Node version >= 14
- Waiting Adobe's team fix this issue
- Make the new version working on Node < 14 by yourself

In my project, I choose the 3rd one. For that, you need:

- Copy the last version of the adobe librairy in your porject

- Replace in that librairy  all ".?" by "."
- Replace your require("@adobe/pdfservices-node-sdk") by require('<path to custom library>/pdfservices-sdk');

But it's really important to understand that this solution is just an unstable fix waiting for adobe's team to fix that more clean. Removing all the ".?" can create a lot of issues.

[Raymond Camden]

I'd highly recommend 1 myself, or even better, the LTS version.

[Glenn263035267yqi]

Totally agree, but not possible for a lot of legacy project.

I will really appreciate that the Adobe's team find a solution. I have that probleme using Node 11 and Adobe librairy 2.2.3.

@Raymond Camden Don't hesitate to contact me if you need some help to understand better our probleme.

[Gabriel22165674l66w]

Thanks @Glenn263035267yqi for the potential fix! Let me try and revert back!

[Gabriel22165674l66w]

Updated node to version 14.21.2 and it worked! Thanks for the support 🙂

[Raymond Camden]

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. 

[System22640200kiod]

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]

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

[System22640200kiod]

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]

I'm not sure what you want me to say here though. If the issue is corrected through an updated package... than that's the only recorse. In your dev environment, can you recreate and confirm you get the same issue, and then test there?

[System22640200kiod]

Looks like 500 error was intermittent. 

[System22640200kiod]

We are doing this upgrade and test in dev environment. Now, we need to figure how to create a patch and deploy to production as emergency patch. Not expecting company like Adobe to not see the impact this can have.