I guess this is the first I have ever tried this.
I don’t see any other chatter on this. Maybe it’s just my version that’s acting up?
Here, this should shed some light:
I wish I could help… but I just have to laugh about the ever so helpful error.
Cloud customers can’t look at any correlations… so… I feel your pain!
OK, so to that end, though, I have never understood what that GUID is “correlated” to. Where am I supposed to look for that? Event Viewer on app server?
Traces usually include a CorrelationID… but I don’t know if that would pinpoint anything or not.
From my understanding, this, I think, is supposed to be on the Server Logs, which Cloud customers don’t have access to. So, I’ve never been able to dig any deeper. I’m sure on-prem peeps should be able to answer that.
Did you ask support if you can have access? Or just ask for the message in the server log with that correlation Id?
Both event viewer and app server log
Is it possible to be more specific? Or is that actually the issue - it could be anywhere?
@Olga Yeah, I’ve requested from EpicCare in the past if I get completely stuck. But MAN what a pain (time suck) that effort is!
How more specific? Do you know what is server log for the App server?
For the event viewer you go to the server, open event viewer and in the Epicor App Server branch there will be the messages, one of them will contain the correlation id.
If it was a long past, then maybe something changed to the better. I cannot say more specific because it depends on many factors there in cloud. But you can try to ask if there is a way for you to know eror from correlation id now.
Well, I take that to mean the log IN the Event viewer. But I feel like I am missing something in what you are saying. Is there another?
So, this is where I look:
Indeed, this is the uBAQ that I was trying to paste-update. So, two questions:
[edit] The correlation ID for that moment is 10fcb3f0-9555-4391-8fd8-373e834f38d5 (I replicated the error after the OP)
Scroll to the bottom of the message
I’m missing something.
I copied the whole thing to notepad and then did a Ctrl+F and still see nothing matching.
Then maybe in your version correlation id was only in the server log.
I think it was added later at some point.
Now it looks like this:
Do you know what server log is and how it is switched on in Admin Console? Then you can go to the file named usually ServerLog.txt and search for correlation id there.
After some stabbing in the dark, it would seem that no, no I do not.
That will be wonderful when I am on that version. (No sarcasm; I know it sounds like it is. But that will be very helpful.)
@Olga Oh never mind, I had to go back to the first place I looked lol.
I just now checked the box; it’s not normally logging.
Is there perchance a guide to what all those options are?
You are a lucky user if you had not need to troubleshoot server with logs until now 
Leave all values empth then. exception will be written anyway.
I am just not sure if defalt folder is okay, it will create file right in the server folder, maybe some other disk with a lot of space is more reasonable.
Ha, I have used them but it has been a good while.
That worked as advertised - thank you @Olga !
There’s the correlation ID and the error message for it.
@utaylor @dcamlin If you are interested.
[edit from here…]
I see that now, it put it in C:\inetpub\wwwroot\Development\Server
Specifying the location is better advice.
