We are upgrading from E10 to Kinetic 2026.100.9. Conversion processes were fine for the most part. We are having an issue that gives an error “We apologize, but an unexpected internal problem occurred. Please provide your System Admin or Technical Support this Correlation ID for further details. Correlation ID: …” When I look at the server log and find that correlation ID, it shows:
Severity: Exception, Table: Part, RowID: 84bd0172-52bb-4548-bb33-4fed8176be2b, Text: VIEW SERVER PERFORMANCE STATE permission was denied on object ‘server’, database ‘master’. The user does not have permission to perform this action.
This error happens when attempting to update or create a Part, Customer, Sales Order or Job.
Each of these has UD fields, but the simpler programs like Customer Group and Supplier also have UD fields and they update fine.
I updated Pilot to 2026.104 wondering if it may do something to help, but same errors. And now I can’t access the Admin type in Server File Download, so can’t even confirm it is exactly the same error. The Admin option has disappeared. (I opened a case for this as well…)
I have opened a case for this and it has been passed on to Dev support. Just thought I would put it out there in case it is something that some else has seen or has any suggestions.
Are you testing the upgrade on a separate App and SQL Server? What SQL login are you using in Epicor Admin Console > App Server Config > Database? Does that login have the same permissions in the new SQL server as it does in the old SQL server?
The error indicates that the SQL login being used by Epicor doesn’t have all the permissions it needs. Our login is set up with the sysadmin server role since we use a dedicated SQL server for Epicor.
We are 2026 in the cloud, so no access to view SQL Server properties. This happens in the Pilot and Live instances, with Live being vanilla (no customizations but still has UD fields). I am thinking it is related to the UD tables, but it’s not every UD table, so hard to imagine that the permissions are that specific.
The database upgrade was done by Epicor in middle of July. They give you 2 instances - Pilot with all customizations to review and correct to build solutions to then move to Live, which is vanilla (no customizations). I was 80% through the customization uplifts before I noticed this error.
I thought if someone else experienced the same thing that if they gave support my case number then support would be able to find the resolution that was done for me. The fix was implemented by cloud support and I have no other reference to it.