I'm doing a callback when the TElSFTPServer raises a CloseHandle event to perform some handling after the file has successfully been uploaded to the server. Whenever some error occurs in the callback I want the uploader to be notified that the file transfer has somehow failed.

I have tried to do so by setting the errorCode in the event handler parameters but the server doesn't seem to display the error to the user (the errorCode works for other events though). The message from user's SFTP client shows as though as the file upload was successfully completed.

Could you guys advise me how I can display an error message to the user when something exceptional happens within the CloseHandle event?

That sounds cool but I come across another thread saying that it is not possible to implement error reporting in CloseHandle. I'm not sure if this applies also to my case since it is a different product. The thread link is https://www.eldos.com/forum/read.php?FID=13&TID=5423&MID=30280#message30280.

From my current understanding of SBB the user session is maintained until the end of CloseHandle event. In other words it is still possible to notify users about any errors that may happen during the closing of the handle but the thread link above suggests otherwise. Could you let me know if it is indeed possible to have error reporting in close handle event?

The thread you referenced concerns a different product, Callback File System, and is only applicable to the same. In fact, there is nothing common between the two CloseHandle() methods here and there except their names.

Quote

From my current understanding of SBB the user session is maintained until the end of CloseHandle event.

Not exactly. The client issues a CloseHandle() command whenever it decides to close a virtual file opened on the server. The session remains active; the client can proceed with the interaction by opening other files and eventually closing them with subsequent CloseHandle() calls.

I've just upgraded my system to use the latest release (28th Oct) and it seems that the issue is still existing. Has it been fixed or is there anything additional I should do to display an error message should an exception is thrown within the CloseHandle event?

We use cookies to help provide you with the best possible online experience. By using this site, you agree that we may store and access cookies on your device. You can find out more about and set your own preferences here.