Error fixIFS CloudPlatform / Aurena / Projection

Internal Server Error in IFS Cloud: How to Diagnose It

Error
internal server error ifs cloud

Also searched as

  • ifs cloud 500 internal server error aurena
  • ifs cloud projection returns 500
  • ifs cloud something went wrong server error

Short answer

An internal server error (HTTP 500) in IFS Cloud means a request reached the middleware but something behind it failed: a projection, a PL/SQL call, the database, or a pod that was restarting. The fastest route is to capture the failing request in the browser, read the error body, then match it to the middleware and database logs.

Applies to: IFS Cloud (Aurena client, OData projections) on IFS Managed Cloud, customer-hosted Kubernetes/OpenShift and on-prem installs. Log access differs by hosting model.

How to diagnose an IFS Cloud internal server error

  1. 1Reproduce the error with the browser developer tools open (Network tab) and note the failing URL, HTTP status and the response body. Aurena pages call projections under /main/ifsapplications/projection/v1/.
  2. 2Read the response body. Application errors normally return a JSON error with a message from the PL/SQL layer; a bare 500 or an HTML page points to infrastructure rather than business logic.
  3. 3Decide the scope: one user, one page, one projection, or everything. If every page fails, check platform health first (pods, database, ingress) before touching application data.
  4. 4Self-hosted: check that the middleware pods are Running and not in CrashLoopBackOff or OOMKilled, then read their logs around the timestamp of the error.
  5. 5Look for an ORA- error in the logs. A package state error, an invalid object after an upgrade or deployment, or a locked or missing row is the most common root cause.
  6. 6Check for invalid database objects and recent deployments or customisation (custom fields, event actions, projections extended with a customisation) that touch the failing page.
  7. 7Test the same record or call as another user. If it works, the problem is permission-set or user data specific, not the platform.
  8. 8If you cannot see the logs (managed cloud), raise a support case with the URL, UTC timestamp, user, projection name and full response body.

Where the 500 can come from

An IFS Cloud request passes through the ingress, the identity layer, the client or projection middleware, and finally the Oracle database where the business logic lives in PL/SQL. A 500 can be raised at any of those layers, which is why the response body matters more than the status code.

Business errors that the logic layer raises on purpose are usually returned as readable messages, sometimes with a 400-class status. A true 500 tends to mean an unhandled exception, a timeout, an unavailable dependency or a defect.

Typical causes in practice

After an upgrade or deployment, invalid database objects or a mismatch between the deployed client and the deployed middleware produce errors on pages that worked yesterday. Compare behaviour across pages: if only pages that use one component fail, suspect that component's deployment.

Customisations are the next suspect. A custom event action, a custom field with bad configuration, or a Lobby information source with a broken query can fail only for certain users or data. Disable the customisation in a test environment and retry to confirm.

Resource problems appear as intermittent 500s or 502/504 on long operations. Large exports, heavy reports and slow queries hit timeouts, and pods under memory pressure get restarted mid-request.

What to collect before escalating

A useful support case contains the exact URL, the UTC time, the user, the IFS Cloud version and update, the response body and any trace or request identifier shown in the error. Add whether it reproduces for other users and whether anything was deployed or changed recently.

Do not paste tokens or session cookies into tickets. Redact the Authorization header from any HAR file you attach.

# Self-hosted Kubernetes: find and read the pods (names vary by release)
kubectl get pods -n <ifs-namespace>
kubectl logs <pod-name> -n <ifs-namespace> --since=30m | grep -i -E "error|ORA-|exception"

Try it here, free

IFS Cloud Projection OData URL Builder

Open full tool

Fill in host, realm, projection and entity set to generate the token request and a ready OData GET URL for IFS Cloud projections.

Common pitfalls

  • !Restarting everything before capturing logs destroys the evidence you need to find the real cause.
  • !Assuming the platform is at fault when a recent customisation touches the failing page.
  • !Testing only as an administrator; permission-set issues and user-specific data issues will not show up.
  • !Treating a timeout on a heavy report as an application bug instead of a query or resource problem.
  • !Sending support a screenshot of the error banner only, without the response body and timestamp.

How an ERP-grounded AI assistant handles this

An assistant grounded in IFS Cloud logs and documentation can take the pasted response body, extract the ORA- code, projection name and timestamp, and propose the matching log lines and likely cause, so the first triage takes minutes. Netray runs this kind of assistant on private models next to the IFS installation, so logs and data never leave your network. It is a triage aid, not a replacement for IFS support on defects.

See ERPray

Frequently asked questions

Does an HTTP 500 in IFS Cloud always mean a bug?

No. It means an unhandled failure somewhere behind the request. Causes include a bad customisation, invalid database objects after a deployment, a timeout, or resource pressure on the middleware. Read the response body and logs before deciding whether it is a defect.

Where are the IFS Cloud logs?

On self-hosted Kubernetes or OpenShift, the logs are in the middleware pod logs and the Oracle alert and trace files. On IFS Managed Cloud you typically do not have direct access and request them through support.

Why does the error only happen for one user?

Usually a permission-set difference, a user-specific default, or data that only that user touches. Reproduce as another user on the same record to separate user issues from platform issues.

Can a customisation cause an internal server error?

Yes. Event actions, custom fields, custom projections and information sources all run code or queries in the request path. Disable the customisation in a test environment and retry.

Related

Error fix

IFS Cloud Background Job Stuck in Posted or Executing

A background job that stays Posted is waiting for a batch queue processor that is not picking it up, while one that stays Executing is either genuinely long-running or orphaned after a crash or restart. Check the Background Jobs page for the job state and error text, confirm the batch queue is active with capacity, then requeue or cancel the job.

Error fix

IFS Cloud OData Projection API: Fixing 401 and 403 Errors

IFS Cloud exposes its data through OData v4 projections under /main/ifsapplications/projection/v1/, secured by OAuth2 tokens from IFS IAM. A 401 almost always means the token is missing, expired or issued by the wrong realm; a 403 means the identity is authenticated but its permission sets do not grant that projection or its entity actions.

How-to

How to Add a Custom Field to an IFS Cloud Page

In IFS Cloud you add a custom field by opening the page in configuration mode, choosing to add a field, defining its name, type and placement, and publishing the configuration. The field is stored by the platform as configuration, not as a code change, which is why it normally survives upgrades.

Error fix

IFS Cloud: Unable to Save, Internal Server Error and Quick Report Problems

In IFS Cloud a save failure or internal server error is almost always a server-side exception returned through the projection the page calls. Read the error detail, reproduce it in the browser network tab, then check the middleware and database logs for the real cause, which is typically a business rule, a missing permission, a bad customization or a stale cache. Quick Report problems are usually a missing permission grant or mismatched bind parameters.

How-to

IFS Cloud Workflow Example, External File Templates, Update Analyzer and PO Status

Treat IFS Cloud configuration as a set of building blocks: workflows or business events to react to changes, external file templates to load or send flat files, an update analysis step to check what a release will touch in your customizations, and the supported database views for reading data such as purchase order status. This page shows how each fits together with a worked approval example.

How-to

IFS Cloud Report Designer, Quick Reports and Crystal Reports: Which to Use

IFS Cloud has several reporting routes. Use Quick Reports for fast read-only lists of data, the report designer route for formatted operational documents such as order confirmations and pick lists, legacy Crystal-based layouts only where you already have them, and the analytical tools for dashboards. Report rules then control when and how a report is produced and sent.

AI for ERP

AI for IFS Cloud in aerospace and defense manufacturing

Add AI to IFS Cloud for aerospace and defense: projections, Aurena UX, Lobby, and engineer-to-order data, deployed on-prem or in your private cloud.

AI for ERP

AI for IFS Cloud Maintenance: Work Orders, PM Plans and Spares Answered in Plain English

Private AI on IFS Cloud maintenance: ask questions across work orders, equipment objects, PM plans, spares and fault history, read-only, on your own servers.

Stuck on IFS Cloud?

Talk to engineers who work inside IFS Cloud every week, and who build private AI that answers these questions from your own ERP data.

Talk to an ERP engineerBrowse ERP Help
All ERP Help articles

Keep exploring

Free tools

ERP fixes and how-tos

Guides

AI on your ERP

Integrations

Comparisons

Software