Windows Server 2012, running Terminal Services has a client application installed. The server part is located on another Windows Server 2012.
The client application is an old one, based on dBase.
The problem is, said application cannot create emails using extended MAPI from the client computer.
When you try to create an email; a temporary file is saved in a shared folder, located on the server host. When Outlook (or any other email-client) tries to attach the PDF the application gives the error message "An error has occured during file access". So the message originates from the application, not the email client.
So naturally, we expect this to be a permissions issue and fire up process monitor from sysinternals. Problem is. You can now send emails. The second you disable logging in procmon, you get the error message back upon your next attempt to send an email.
This works in other enviroments, Say XP/Vista/Win7 -> Server2003/2008 It only occurs with Server 2012 -> Server 2012 I suspect SMB3 being involved with this somehow.
But the question is, what actually happens when you enable logging with procmon? Because whatever procmon does - that's what I want to use as a workaround.
EDIT: Oh, also happens with Win8 -> Server2012