13. Troubleshooting

13.1 A Button Is Disabled

Possible causes:

• Required input files have not been uploaded.
• An Application Profile has not been selected.
• A Location or context has not been selected.
• A prior step, such as mapping extraction or config validation, has not been completed.
• The current license does not include the module.
• A required config review has warnings or blockers.

What to do:

1. Review required inputs in the current step.
2. Check whether a previous button must be run first.
3. Confirm the license status.
4. Review warning or error panels.

13.2 A File Cannot Be Parsed

Possible causes:

• Unsupported file type.
• Incorrect workbook sheet names.
• CSV encoding or delimiter issues.
• Snapshot package structure does not match the selected provider.
• File is locked by another application.

What to do:

1. Confirm the supported file type for the module.
2. Close the file in Excel or other tools.
3. Use Run File Diagnostics where available.
4. Check the Snapshot Reader warning panel for snapshot issues.
5. Reproduce the issue with a sanitized sample.

13.3 Config Validation Fails

Possible causes:

• Missing required sheets.
• Incorrect dimension mapping.
• Invalid member mapping rules.
• Output settings do not match the selected mode.
• Required validation rules are incomplete.

What to do:

1. Open the validation result.
2. Review failed sheets and failed rows.
3. Return to Configure Wizard if the config was generated there.
4. Use Config Compare to compare with a previous working config.
5. Regenerate or correct the config, then rerun validation.

13.4 Conversion Output Is Not As Expected

Possible causes:

• Wrong conversion mode.
• Target grid or template is not the intended version.
• Clear-before-write setting was not selected when needed.
• Member mapping or dimension mapping is incomplete.
• Post-conversion audit was not enabled.

What to do:

1. Confirm the selected conversion mode.
2. Review the source file, target template, and config.
3. Run Validation before conversion if needed.
4. Enable post-conversion audit.
5. Open the run folder from Run History and compare inputs, outputs, and summary files.

13.5 License Or Module Is Not Available

Possible causes:

• License file has not been activated.
• License is for a different machine.
• License has expired.
• Module is not included in the license.

What to do:

1. Open Tools > License Activation.
2. Generate a new machine request if the machine changed.
3. Confirm that the license includes the module.
4. Contact support@epmvitals.com with the non-sensitive activation error and screenshot.

13.6 Oracle EPM Pull Cannot Connect Or Export

Possible causes:

• The Base URL is not the Oracle EPM environment URL.
• The username or password is incorrect.
• The user can log in to the browser but does not have permission to list or export migration artifacts.
• The environment blocks Basic Authentication for the account.
• A previous temporary snapshot with the same name already exists in Oracle EPM.
• The Oracle EPM export job failed or timed out.

What to do:

1. Confirm that the Base URL opens the intended Oracle EPM environment.
2. Confirm that the username format matches the Oracle EPM login requirement for the environment.
3. Re-enter the password. EPM Vitals does not store it.
4. Click Test Connection / Build Export Plan again.
5. Review the export plan and confirm that Essbase Data is excluded.
6. If the pull still fails, capture the non-sensitive error message and contact support.