I'm not sure I'm familiar with this particular error message.

Have you tried OEINV04 or OEINV05? These report directly off the tables, not a datapipe.

that makes sense but oeinv01 and oeinv02 are the only ones to show up with no ability to browse but oeinv04 and 05 are in the \oe64\eng directory. Do you know where it gets the files so I can place oeinv04 and 05 to try them?

They will be wherever you installed Sage 300 to. If you go to Help > System Information it will tell you the Program Directory. For example:

C:\Sage\Sage 300 ERP\OE64A\ENG

If you use customization directories, you should check their too. You can see the path (if any) under Administrative Service > Customization Directories.

yeah that is what is so weird and i don't understand. I see all 4 choices there when I browse in the traditional client but in the web client i only see 01 and 02. if i go the location as you outline i see all 4 there also. It' s like the web client is filtering them out. i tried renaming the oeinv04 to oeinv01 and choosing it but i got the same error. I am not convinced it is reading it from the same directory so I still believe your fix may work if I could figure out a way to ensure is it using a .rpt file that is form db's.

I am having the same issue at one of my clients. Have you found anything that resolves this??

no i haven't. Frankly it makes the product kinda useless. they idea is the to have the people who are facing the clients be able to get to it thinly and those are the people printing crystal report forms. The back office people working in the traditional client is not really a problem i am extremely disappointed that so far no one has an answer to this.

I would call Sage support on this one.

i just opened a call so I will see what happens.

if you are experiencing these issues i can recommend the following after working with support to eventually get my issues resolves. KB article 75623 and 73028 - I was running 2017 and I installed SP2 and i rebooted the server. Hope this can help others out there it's a nasty issue.

Glad to hear it is working. Thanks for sharing the solution!

just wanted to update this with the solution that support helped me find it is documented that you have to renmae your customized form to one of the two displayed names oeinv01 or 02 for you to be able to use your customized invoice. Once I renmae my invoice it all worked fine. all my customization's worked. help.sage300.com/.../index.htm custom forms and reports supported"

Interesting. We were using the standard form and got the error. Looking at first suggestions made to see if that makes any difference.

look at my post april 10 4:39 and the 2 kb articles. You must first get printing working before it even matters what form you use. I suspect right now your AR aged trial balance won't print either.