When trying to access the Extension Manager we're ...
# suitecommerces
Santiago
09/21/2023, 1:29 PMWhen trying to access the Extension Manager we're getting this error:
c
Chris
09/21/2023, 4:54 PMHey @Santiago, I'm getting this too.
f
Fran
09/21/2023, 5:02 PMSame issue here!
c
Chris
09/21/2023, 5:26 PMBoth SB and Prod. Hey @Flo, sorry to bother you, this seems to be a not-isolated event.
f
Flo
09/21/2023, 5:29 PMHey, I am not aware of any recent changes on our side so it may be related to something else. Do you have an issue number I can check?
Flo
09/21/2023, 5:31 PMCan you send me the steps to reproduce? Is this just by trying to access the EM through the UI?
c
Chris
09/21/2023, 5:32 PMYes, the EM page throws the error upon opening. We're still opening a ticket.
f
Flo
09/21/2023, 5:33 PMThanks, i will send it to the team
🙏🏻 1
c
Chris
09/21/2023, 5:45 PMCase #5383013 is open.
Chris
09/21/2023, 11:54 PMWe're still having the same issue. Anyone else still getting this?
p
pablod
09/22/2023, 2:13 PMyes, same thing
l
LC
09/22/2023, 2:13 PMWe’re experiencing the same issues since yesterday and still not working. Any idea if NS is currently working on this? @Flo
f
Flo
09/22/2023, 2:13 PMYes, there is an issue open for this.
đź‘Ť 1
Flo
09/22/2023, 2:14 PMThis has been posted as a workaround, though it has not worked for everyone
Flo
09/22/2023, 2:14 PMWORKAROUND to access Activation Records:
â–ş Accessing the Activation Record via URL
https://<ACCOUNT_ID>.app.netsuite.com/app/site/hosting/scriptlet.nl?script=<SCRIPT_ID>&deploy=1&compid=<ACCOUNT_ID>&service_name=STEP_2&website_id=<WEBSITE_ID>&domain_id=<CUSTOMER_DOMAIN>&subsidiary_id=&location_id=
NOTE:
- <ACCOUNT_ID>: Customer Account ID
- <SCRIPT_ID>: Script ID of “NS SC ExtMechanism Services” SuiteLet
- <CUSTOMER_DOMAIN>: This is the customer domain associated to a website record. (e.g. www.mywebstore.com)
- <WEBSITE_ID>: Website Record ID (Make sure to replace this with the exact website ID of the customer domain)
WORKAROUND to create new Activation Record:
â–ş If new activation is needed, then customer can access new Activation page thru this link:
https://<ACCOUNT_ID>.app.netsuite.com/app/site/hosting/scriptlet.nl?script=<SCRIPT_ID>&deploy=1&compid=<ACCOUNT_ID>&whence=&service_name=STEP_1
NOTE:
- <ACCOUNT_ID>: Customer Account ID
- <SCRIPT_ID>: Script ID of “NS SC ExtMechanism Services” SuiteLet
Flo
09/22/2023, 2:15 PMsome of the customers experienced an error after clicking on the activate but the activation was completed successfully
l
LC
09/22/2023, 2:19 PMOk, thanks I’ll try that on the clients we have experiencing this issue. I hope it works.
Any idea if there’s going to be an efix release soon to fix the issue?
f
Flo
09/22/2023, 2:20 PMI do not know about that as it’s not clear if it’s a bundle issue. The latest bundle e-fix was on July so it is more likely it was a core injection.
l
LC
09/22/2023, 2:22 PMThanks @Flo for the updates. Please let us know if you have any other update on the issue. Really appreciate it.
f
Flo
09/22/2023, 2:29 PMCan you let me know which NS version are you running on?
Flo
09/22/2023, 2:29 PMyou can check this by viewing the source code of your NS account and scrolling to the bottom of the page
c
Chris
09/22/2023, 2:39 PM<!-- Host [ a225.prod.iad.na13.core.ns.internal ] App Version [ 2023.2.12.30357 ] -->f
Flo
09/22/2023, 2:40 PMThanks Chris. 2023.2.12.30357 was NetSuite Core yesterday hot-fix, so that makes sense.
c
Chris
09/22/2023, 2:41 PMI replicated the issue in 3 different accounts.
Chris
09/22/2023, 2:43 PMI saw an error like this in a suitelet once when some logging stuff was being auto-appended to HTML output.
f
Flo
09/22/2023, 2:44 PMIt is very likely that the issue is related to yesterday NetSuite core hot-fix. I will update the issue record with my findings so this issue gets rooted to the correct team. Thanks for your help
l
LC
09/22/2023, 3:16 PMI think that most are running the latest version 2023.1.3
And yes the issues started yesterday so probably related to the hotfix released.
f
Flo
09/22/2023, 3:52 PMone more question, do you know if the account where you are experiencing the problem was recently move to OCI or to a different data center?
c
Chris
09/22/2023, 3:54 PMOCI move happened awhile back. DC move, not sure.
p
pablod
09/22/2023, 4:10 PMIs working again on one account, I was able to activate an extension
🤔 1
pablod
09/22/2023, 4:11 PMwe created a case yesterday, maybe support fixed it 🤷🏻
f
Flo
09/22/2023, 4:12 PMNo, the issue record is still open, there was no fix released
Flo
09/22/2023, 4:12 PMBut is interesting that you can no longer reproduce it
p
pablod
09/22/2023, 4:12 PMit started working again, I don’t know what to tell you 🙂
pablod
09/22/2023, 4:13 PM@Chris can you check if it’s working on your end?
f
Flo
09/22/2023, 4:13 PMI believe you, but that makes me think it was not related to yesterday hot-push but to a different thing
Flo
09/22/2023, 4:13 PMI will check on my accounts as well
c
Chris
09/22/2023, 4:13 PMWe're up again as well.
👍🏻 1
f
Flo
09/22/2023, 4:14 PMWoooow
f
Fran
09/22/2023, 4:16 PMIt is working fine here as well
f
Flo
09/22/2023, 4:18 PMI appreciate if you could update your support cases about the issue suddenly being fixed so it is reported that the issue is intermittent and is likely to be related to a temporary error.
đź‘Ť 1
👍🏻 1
s
Santiago
10/04/2023, 2:41 PMIt was fixed, but this issue is now back. The workaround works for accessing the extensions and attempting an activation, but we can't see any progress.
l
LC
10/04/2023, 6:54 PMWe’re experiencing this issue on a few of our demos accounts. I already submitted a NS case. I’ll update if they provide any feedback.
đź‘Ť 1
e
Emily Pascas
10/04/2023, 7:11 PMAlso experiencing this issue on our sandbox accounts, submitted a case
l
LC
10/04/2023, 7:26 PMI just finished a call with NS support, is a known defect, they are currently working on that. But they don’t have any estimate on when they’ll release the fix.
đź‘Ť 2
5 Views