Repository navigation
[No QA] Add INT133 help article for inactive Sage Intacct web services user #104092
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,70 @@ | ||
| --- | ||
| title: INT133 Sync Error in Sage Intacct Integration | ||
| description: Learn what the INT133 sync error means in Sage Intacct and how to reactivate the web services user to restore your connection. | ||
| keywords: INT133, Sage Intacct inactive user, xmlgateway_expensify inactive, Sage Intacct web services user inactive, Expensify Sage Intacct sync error, PL04000076, Workspace Admin | ||
| internalScope: Audience is Workspace Admins using the Sage Intacct integration. Covers resolving the INT133 sync error caused by an inactive Sage Intacct web services user. Does not cover incorrect credentials or Sender ID errors (see INT122). | ||
| --- | ||
|
|
||
| # INT133 Sync Error in Sage Intacct Integration | ||
|
|
||
| If you see the error: | ||
|
|
||
| INT133 Sync Error: The Sage Intacct web services user is inactive. Please reactivate the user in Sage Intacct and attempt sync again. | ||
|
|
||
| This means Sage Intacct rejected the connection because the web services user is set to **Inactive**, preventing the sync from completing. | ||
|
|
||
| --- | ||
|
|
||
| ## Why the INT133 Sync Error Happens in Sage Intacct | ||
|
Contributor
There was a problem hiding this comment. Heading capitalization: Use sentence case for |
||
|
|
||
| The INT133 error typically indicates: | ||
|
|
||
| - The `xmlgateway_expensify` web services user was deactivated in Sage Intacct. | ||
| - An administrator changed the user's status to **Inactive** during a user cleanup or license review. | ||
| - The web services user that was used to connect the Workspace is no longer in use. | ||
|
|
||
| Reentering the same credentials will not fix this error. The user must be reactivated in Sage Intacct first. | ||
|
|
||
| --- | ||
|
|
||
| ## How to Fix the INT133 Sync Error | ||
|
|
||
| This issue must be resolved in Sage Intacct and then retried in Expensify. | ||
|
|
||
| ### Reactivate the Web Services User in Sage Intacct | ||
|
Contributor
There was a problem hiding this comment. Forbidden heading level: |
||
|
|
||
| 1. Log in to Sage Intacct as an administrator. | ||
| 2. Go to **Company > Admin > Web Services users**. | ||
| 3. Locate the **xmlgateway_expensify** web services user. | ||
| 4. Click **Edit**. | ||
|
Contributor
There was a problem hiding this comment. Action verb violation: Use select, not "click" (HELPSITE_NAMING_CONVENTIONS.md "Actions"): |
||
| 5. Change the **Status** to **Active**. | ||
| 6. Click **Save**. | ||
|
|
||
| If the web services user was deleted or can't be reactivated, create a new web services user and reconnect the Workspace with the new credentials. | ||
|
|
||
| --- | ||
|
|
||
| ### Retry the Sync in Expensify | ||
|
Contributor
There was a problem hiding this comment. Forbidden heading level: |
||
|
|
||
| 1. Go to **Settings > Workspaces**. | ||
| 2. Select your Workspace. | ||
|
Contributor
There was a problem hiding this comment. Terminology / navigation: Lowercase "workspace" in running text and use a bolded navigation path with select, e.g. |
||
| 3. Click **Accounting**. | ||
|
Contributor
There was a problem hiding this comment. Action verb violation: Use select, not "click": |
||
| 4. Click **Sync Now**. | ||
|
|
||
| Confirm the sync completes successfully. | ||
|
|
||
| --- | ||
|
|
||
| # FAQ | ||
|
|
||
| ## Do I Need Sage Intacct Admin Access? | ||
|
Contributor
There was a problem hiding this comment. Heading capitalization: FAQ |
||
|
|
||
| Yes. Changing the status of a web services user requires administrator permissions in Sage Intacct. | ||
|
|
||
| ## Do I Need to Reenter My Credentials? | ||
|
|
||
| Not usually. If you reactivate the same web services user, the existing credentials will work. If you create a new web services user, enter the new credentials in Expensify. | ||
|
|
||
| ## Does INT133 Mean the Integration Is Disconnected? | ||
|
|
||
| Not necessarily. The connection settings are kept, but Sage Intacct rejects every sync until the web services user is active again. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,70 @@ | ||
| --- | ||
| title: INT133 Sync Error in Sage Intacct Integration | ||
| description: Learn what the INT133 sync error means in Sage Intacct and how to reactivate the web services user to restore your connection. | ||
| keywords: INT133, Sage Intacct inactive user, xmlgateway_expensify inactive, Sage Intacct web services user inactive, Expensify Sage Intacct sync error, PL04000076, Workspace Admin | ||
| internalScope: Audience is Workspace Admins using the Sage Intacct integration. Covers resolving the INT133 sync error caused by an inactive Sage Intacct web services user. Does not cover incorrect credentials or Sender ID errors (see INT122). | ||
| --- | ||
|
|
||
| # INT133 Sync Error in Sage Intacct Integration | ||
|
|
||
| If you see the error: | ||
|
|
||
| INT133 Sync Error: The Sage Intacct web services user is inactive. Please reactivate the user in Sage Intacct and attempt sync again. | ||
|
|
||
| This means Sage Intacct rejected the connection because the web services user is set to **Inactive**, preventing the sync from completing. | ||
|
|
||
| --- | ||
|
|
||
| ## Why the INT133 Sync Error Happens in Sage Intacct | ||
|
Contributor
There was a problem hiding this comment. Heading capitalization: |
||
|
|
||
| The INT133 error typically indicates: | ||
|
|
||
| - The `xmlgateway_expensify` web services user was deactivated in Sage Intacct. | ||
| - An administrator changed the user's status to **Inactive** during a user cleanup or license review. | ||
| - The web services user that was used to connect the Workspace is no longer in use. | ||
|
Contributor
There was a problem hiding this comment. Terminology: Use lowercase "workspace" in running text (HELPSITE_NAMING_CONVENTIONS.md "Generic Terms"): "...used to connect the workspace is no longer in use." |
||
|
|
||
| Reentering the same credentials will not fix this error. The user must be reactivated in Sage Intacct first. | ||
|
|
||
| --- | ||
|
|
||
| ## How to Fix the INT133 Sync Error | ||
|
Contributor
There was a problem hiding this comment. Heading capitalization: Use sentence case for |
||
|
|
||
| This issue must be resolved in Sage Intacct and then retried in Expensify. | ||
|
|
||
| ### Reactivate the Web Services User in Sage Intacct | ||
|
Contributor
There was a problem hiding this comment. Forbidden heading level: |
||
|
|
||
| 1. Log in to Sage Intacct as an administrator. | ||
| 2. Go to **Company > Admin > Web Services users**. | ||
| 3. Locate the **xmlgateway_expensify** web services user. | ||
| 4. Click **Edit**. | ||
|
Contributor
There was a problem hiding this comment. Action verb violation: Use select, never "click" (HELPSITE_NAMING_CONVENTIONS.md "Actions"). Change to |
||
| 5. Change the **Status** to **Active**. | ||
| 6. Click **Save**. | ||
|
|
||
| If the web services user was deleted or can't be reactivated, create a new web services user and reconnect the Workspace with the new credentials. | ||
|
|
||
| --- | ||
|
|
||
| ### Retry the Sync in Expensify | ||
|
Contributor
There was a problem hiding this comment. Forbidden heading level: |
||
|
|
||
| 1. Go to **Settings > Workspaces**. | ||
| 2. Select your Workspace. | ||
|
Contributor
There was a problem hiding this comment. Terminology: Use lowercase "workspace" in running text unless quoting a UI label (HELPSITE_NAMING_CONVENTIONS.md "Generic Terms"). Also use a bolded navigation path and select rather than naming the Workspace generically, e.g. |
||
| 3. Click **Accounting**. | ||
|
Contributor
There was a problem hiding this comment. Action verb violation: Use select, not "click" (HELPSITE_NAMING_CONVENTIONS.md "Actions"). Change to |
||
| 4. Click **Sync Now**. | ||
|
|
||
| Confirm the sync completes successfully. | ||
|
|
||
| --- | ||
|
|
||
| # FAQ | ||
|
|
||
| ## Do I Need Sage Intacct Admin Access? | ||
|
Contributor
There was a problem hiding this comment. Heading capitalization: FAQ questions use |
||
|
|
||
| Yes. Changing the status of a web services user requires administrator permissions in Sage Intacct. | ||
|
|
||
| ## Do I Need to Reenter My Credentials? | ||
|
|
||
| Not usually. If you reactivate the same web services user, the existing credentials will work. If you create a new web services user, enter the new credentials in Expensify. | ||
|
|
||
| ## Does INT133 Mean the Integration Is Disconnected? | ||
|
|
||
| Not necessarily. The connection settings are kept, but Sage Intacct rejects every sync until the web services user is active again. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,75 @@ | ||
| --- | ||
| title: INT133 Sync Error in Sage Intacct Integration | ||
| description: Learn what the INT133 sync error means and how to reactivate the Sage Intacct web services user to restore the connection. | ||
| keywords: INT133, Sage Intacct inactive user, xmlgateway_expensify inactive, Sage Intacct web services user inactive, Sage Intacct sync authentication failure, PL04000076, Workspace Admin | ||
| internalScope: Audience is Workspace Admins managing the Sage Intacct integration. Covers resolving the INT133 sync error caused by an inactive Sage Intacct web services user. Does not cover incorrect credentials or Sender ID errors (see INT122). | ||
| --- | ||
|
|
||
| # INT133 Sync Error in Sage Intacct Integration | ||
|
Contributor
There was a problem hiding this comment. Duplicate article / scope: This file is identical to the new-expensify Sync-Errors/INT133-Sync-Error.md article. Publishing the same content in two folders dilutes retrieval precision (HELP_AUTHORING_GUIDELINES.md Sections 1 & 6). Keep one canonical article. |
||
|
|
||
| If you see the error: | ||
|
|
||
| INT133 Sync Error: The Sage Intacct web services user is inactive. Please reactivate the user in Sage Intacct and attempt sync again. | ||
|
|
||
| This means Sage Intacct rejected the connection because the web services user is set to **Inactive**. | ||
|
|
||
| When the web services user is inactive, syncing and exports will not work. | ||
|
|
||
| --- | ||
|
|
||
| ## Why the INT133 Sync Error Happens in Sage Intacct | ||
|
Contributor
There was a problem hiding this comment. Heading capitalization: Use sentence case for |
||
|
|
||
| The INT133 error typically occurs when: | ||
|
|
||
| - The **xmlgateway_expensify** web services user was deactivated in Sage Intacct. | ||
| - An administrator changed the user's status to **Inactive** during a user cleanup or license review. | ||
| - The web services user that was used to connect the Workspace is no longer in use. | ||
|
|
||
| Reentering the same credentials will not fix this error. The user must be reactivated in Sage Intacct first. | ||
|
|
||
| --- | ||
|
|
||
| ## How to Fix the INT133 Sync Error | ||
|
Contributor
There was a problem hiding this comment. Heading capitalization: Use sentence case: |
||
|
|
||
| Follow the steps below to reactivate the web services user and restore the connection. | ||
|
|
||
| --- | ||
|
|
||
| ## Reactivate the Web Services User in Sage Intacct | ||
|
Contributor
There was a problem hiding this comment. Heading rules: Use sentence case and a task-based phrase: |
||
|
|
||
| 1. Log in to Sage Intacct as an administrator. | ||
| 2. Go to **Company > Admin > Web Services users**. | ||
| 3. Locate the **xmlgateway_expensify** web services user. | ||
| 4. Click **Edit**. | ||
|
Contributor
There was a problem hiding this comment. Action verb violation: Use select, not "click" (HELPSITE_NAMING_CONVENTIONS.md "Actions"): |
||
| 5. Change the **Status** to **Active**. | ||
| 6. Click **Save**. | ||
|
|
||
| If the web services user was deleted or can't be reactivated, create a new web services user and reconnect the Workspace with the new credentials. | ||
|
|
||
| --- | ||
|
|
||
| ## Retry the Sync | ||
|
Contributor
There was a problem hiding this comment. Heading rules: |
||
|
|
||
| After reactivating the web services user: | ||
|
|
||
| 1. Go to **Workspaces > [Workspace Name] > Accounting**. | ||
|
Contributor
There was a problem hiding this comment. Navigation path placeholder: Placeholders must be lowercase and use select: |
||
| 2. Select **Sync Now**. | ||
| 3. Confirm the sync completes successfully. | ||
|
|
||
| If the web services user is active, the sync should complete without errors. | ||
|
|
||
| --- | ||
|
|
||
| # FAQ | ||
|
|
||
| ## Do I Need Sage Intacct Admin Access to Fix This? | ||
|
Contributor
There was a problem hiding this comment. Heading capitalization: FAQ |
||
|
|
||
| Yes. Changing the status of a web services user requires administrator permissions in Sage Intacct. | ||
|
|
||
| ## Do I Need to Reenter My Credentials? | ||
|
|
||
| Not usually. If you reactivate the same web services user, the existing credentials will work. If you create a new web services user, enter the new credentials in the Workspace. | ||
|
|
||
| ## Does This Error Affect Exports? | ||
|
|
||
| Yes. Exports and other integration features will not work until the web services user is active again. | ||
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,75 @@ | ||
| --- | ||
| title: INT133 Sync Error in Sage Intacct Integration | ||
| description: Learn what the INT133 sync error means and how to reactivate the Sage Intacct web services user to restore the connection. | ||
| keywords: INT133, Sage Intacct inactive user, xmlgateway_expensify inactive, Sage Intacct web services user inactive, Sage Intacct sync authentication failure, PL04000076, Workspace Admin | ||
| internalScope: Audience is Workspace Admins managing the Sage Intacct integration. Covers resolving the INT133 sync error caused by an inactive Sage Intacct web services user. Does not cover incorrect credentials or Sender ID errors (see INT122). | ||
| --- | ||
|
|
||
| # INT133 Sync Error in Sage Intacct Integration | ||
|
Contributor
There was a problem hiding this comment. Duplicate article / scope: This file is identical to the new-expensify Authentication-and-Login-errors/INT133-Sync-Error.md. Duplicate articles under two folders dilute retrieval precision (HELP_AUTHORING_GUIDELINES.md Sections 1 & 6). Keep one canonical article. |
||
|
|
||
| If you see the error: | ||
|
|
||
| INT133 Sync Error: The Sage Intacct web services user is inactive. Please reactivate the user in Sage Intacct and attempt sync again. | ||
|
|
||
| This means Sage Intacct rejected the connection because the web services user is set to **Inactive**. | ||
|
|
||
| When the web services user is inactive, syncing and exports will not work. | ||
|
|
||
| --- | ||
|
|
||
| ## Why the INT133 Sync Error Happens in Sage Intacct | ||
|
Contributor
There was a problem hiding this comment. Heading capitalization: Use sentence case for |
||
|
|
||
| The INT133 error typically occurs when: | ||
|
|
||
| - The **xmlgateway_expensify** web services user was deactivated in Sage Intacct. | ||
| - An administrator changed the user's status to **Inactive** during a user cleanup or license review. | ||
| - The web services user that was used to connect the Workspace is no longer in use. | ||
|
|
||
| Reentering the same credentials will not fix this error. The user must be reactivated in Sage Intacct first. | ||
|
|
||
| --- | ||
|
|
||
| ## How to Fix the INT133 Sync Error | ||
|
Contributor
There was a problem hiding this comment. Heading capitalization: Use sentence case: |
||
|
|
||
| Follow the steps below to reactivate the web services user and restore the connection. | ||
|
|
||
| --- | ||
|
|
||
| ## Reactivate the Web Services User in Sage Intacct | ||
|
Contributor
There was a problem hiding this comment. Heading rules: Use sentence case and start with an action verb/question word (HELP_AUTHORING_GUIDELINES.md Section 2): |
||
|
|
||
| 1. Log in to Sage Intacct as an administrator. | ||
| 2. Go to **Company > Admin > Web Services users**. | ||
| 3. Locate the **xmlgateway_expensify** web services user. | ||
| 4. Click **Edit**. | ||
|
Contributor
There was a problem hiding this comment. Action verb violation: Use select, not "click" (HELPSITE_NAMING_CONVENTIONS.md "Actions"): |
||
| 5. Change the **Status** to **Active**. | ||
| 6. Click **Save**. | ||
|
|
||
| If the web services user was deleted or can't be reactivated, create a new web services user and reconnect the Workspace with the new credentials. | ||
|
|
||
| --- | ||
|
|
||
| ## Retry the Sync | ||
|
Contributor
There was a problem hiding this comment. Heading rules: |
||
|
|
||
| After reactivating the web services user: | ||
|
|
||
| 1. Go to **Workspaces > [Workspace Name] > Accounting**. | ||
|
Contributor
There was a problem hiding this comment. Navigation path placeholder: Use a lowercase bracketed placeholder and select: |
||
| 2. Select **Sync Now**. | ||
| 3. Confirm the sync completes successfully. | ||
|
|
||
| If the web services user is active, the sync should complete without errors. | ||
|
|
||
| --- | ||
|
|
||
| # FAQ | ||
|
|
||
| ## Do I Need Sage Intacct Admin Access to Fix This? | ||
|
Contributor
There was a problem hiding this comment. Heading capitalization: FAQ |
||
|
|
||
| Yes. Changing the status of a web services user requires administrator permissions in Sage Intacct. | ||
|
|
||
| ## Do I Need to Reenter My Credentials? | ||
|
|
||
| Not usually. If you reactivate the same web services user, the existing credentials will work. If you create a new web services user, enter the new credentials in the Workspace. | ||
|
|
||
| ## Does This Error Affect Exports? | ||
|
|
||
| Yes. Exports and other integration features will not work until the web services user is active again. | ||
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Duplicate article / scope: This file is byte-identical to the Sync-Errors/INT133-Sync-Error.md article. Publishing the same INT133 content under two folders creates duplicate articles that dilute retrieval precision (HELP_AUTHORING_GUIDELINES.md Sections 1 & 6). Keep one canonical article and cross-link if needed.