We recently had a client refresh their Sandbox account. We are trying to re-establish the website; however, using 2023.2, we cannot get past the error message below when deploying/fetching in the Sandbox account. However, we can still deploy/fetch from production. • 2023.2 developer tools, nodejs 14.19.0 • Set up the required Integration and TBA credentials and added the TBA entry to the .nstba/.env file. • Using the default SCDeployer role • I tried using a different DNS server for our internet, as I know this has been an issue.

Error in task gulp extension:fetch
Error Message
  Unexpected Error

We have also been able to create a new TBA token using the "new" option, but we encountered the following error.

An unexpected error has occurred. Please go back and try again.

With the URL

<https://system.netsuite.com/app/login/secure/authorizetoken.nl?oauth_token=undefined>

Any suggestions? Is it possible for the Sandbox account to have an issue?

You probably need a new integration record. 1. Go to Setup > Integration > Manage Integrations > New 2. Create an integration record. (For more information, see Create Integration Records for Applications to Use TBA.) a. In the Name field, enter a name for the integration record. b. In the State field, select Enabled. c. Check the Token-Based Authentication box. d. Check the TBA: Authorization Flow box. e. In the Callback URL field, enter: http://localhost:7777/tba. f. Clear the Authorization Code Grant box. g. Check the User Credentials box. 3. Save the integration. Be sure to save the consumer key/secret before closing the page. 4. Copy and paste the consumer key/secret in the .env file. ALSO IMPORTANT: the key/secret information you put in the .env file must be for the integration record that you’ve just created AND NOT FOR THE ACCESS TOKEN FOR YOUR ACCOUNT. If you attempt to use your the key/secret that you have manually created through the NetSuite UI (using the Manage Access Tokens link), then this will also cause this error.

Thanks Steve... I have done that step 4 times now. Same outcome.

OK, and have you updated your .nstba file?

Yes

😞

Total head scratcher

The fact that the oauth token in the request URL is undefined generally means that it isn’t fetching it from your machine

We have been logging the files in the ns-deploy folder.

@Christopher Dembek it should not be happening for that specific SCA version but try the following: If you get the oauth_token=undefined, try the following solution: Look for: ns_npm_repository\oauth1\index.js

const hostnameStep1 = this.vm ? hostName : `rest${molecule}.<http://netsuite.com|netsuite.com>`;

and change it for:

const hostnameStep1 = this.vm ? hostName : `system${molecule}.<http://netsuite.com|netsuite.com>`;

In some old version you must look for:

var hostnameStep1 = this.vm ? hostName : "rest" + molecule + ".<http://netsuite.com|netsuite.com>";

and change it for:

var hostnameStep1 = this.vm ? hostName : "system" + molecule + ".<http://netsuite.com|netsuite.com>";

@Christopher Dembek did that work for you?

Per @eminero suggestion, I searched for "rest$" and replaced it with "system$" but it was a different location.

Do you mind sharing where you updated it? I have not face the issue in other versions but it would be good knowing it

First, this only worked with my Extension 2022.1 dev tools, which have the production integration record key and secret values entered. Next, I will try setting up the 2023.2 Extension environment.

_setUrls() {
        const molecule = this.molecule ? `.${this.molecule}` : '';
        const hostName = this.vm && this.vm.replace(/https?:\/\//, '');

        let hostnameStep1;
        if (this.vm) {
            hostnameStep1 = hostName;
        } else if (this.account) {
            hostnameStep1 = `${this.account}.restlets.api${molecule}.<http://netsuite.com|netsuite.com>`;
        } else {
            hostnameStep1 = `system${molecule}.<http://netsuite.com|netsuite.com>`;
        }

Thanks for sharing! @Christopher Dembek

@Christopher Dembek I'd try 2023.2.1 SCEM