The information below outlines steps to resolve common issues faced by SAP
ASPM users, including "Failed to Update," "Failed to Calculate," and "429 Too Many Requests" errors.
Step 1: Basic Troubleshooting:
1.0 Initially in case of "Failed to Update" & "Failed to Calculate":
Ensure sheet values adhere to industry standards.
Verify that all necessary and mandatory values, as per the template and for calculation purposes, are correctly entered and thoroughly checked via the API logbook.
1.1 Change the Browser
- If the
error occurs in one browser (e.g., Chrome), try using another (e.g., Edge
or Firefox).
- Ensure
your browser is updated to the latest version.
1.2 Use Private or Incognito Mode
- Open
your browser in private or incognito mode to bypass cached data.
- Chrome:
Press Ctrl + Shift + N
- Edge:
Press Ctrl + Shift + N
- Firefox:
Press Ctrl + Shift + P
1.3 Switch Network
- Try
switching from Wi-Fi to LAN for a stable connection.
- If
possible, connect to a different organization network to rule
out local network issues.
1.4 Restart Your Machine
- Reboot
your system to clear temporary glitches.
Step 2: Advanced Steps: Capturing Network Trace
2.1 Open Developer Tools
- Open
the browser where the issue occurs.
- Right-click
anywhere on the page and select Inspect, or press:
- Chrome/Edge:
Ctrl + Shift + I
- Firefox:
Ctrl + Shift + I
Screenshot Example:
2.2 Go to the Network Tab
- In the
Developer Tools window, navigate to the Network tab.
- Ensure
the page is being monitored for network activity.
Screenshot Example:
2.3 Reproduce the Issue
- Perform
the action that caused the error (e.g., clicking Calculate or Save).
- Look
for the API request(s) in the Network tab.
2.4 Identify the Error
- Select
the request that failed (marked in red).
- Right
click and under the Payload or Response section, check for
the specific error code or message and copy as object under payload and
response (normal copy) and paste both of them in a notepad file separately
and share with us over support channel.
Screenshot Example:
Step 3: Collect and Share Information
- Note
the following details:
- Error
message and code (e.g., "429 Too Many Requests").
- Timestamp
of the issue.
- Steps
taken before encountering the error.
- Share
the network trace or a screenshot of the failed API request with us over
support email.
Notes
1. Ensure your IT team has access to any additional
firewall settings or server logs if required.
2. Following the steps above, the AsInt Development
team will be able to further investigate the issue, delving into the technical
details.
3. Persistent errors may require escalation to the
SAP ASPM support team for server-side troubleshooting.