It appears there's a problem when running the application in an RDC session. In my experimentation, it only happens when you configure the printer FROM an RDC session. If the application starts or is configured from the actual desktop, the errors don't occur. I'm still researching it, but at this point I'm suspecting it has something to do with Windows returning a printer name with the (redirected...) in it's name.
SComps
commented
1 year ago
It appears there's a problem when running the application in an RDC session. In my experimentation, it only happens when you configure the printer FROM an RDC session. If the application starts or is configured from the actual desktop, the errors don't occur. I'm still researching it, but at this point I'm suspecting it has something to do with Windows returning a printer name with the (redirected...) in it's name.
More later.