Re: Unable to save PDF and RTF file in Redirected Drive

[Amarjeet Singh]

Would I file a BUG in guacamle and steps to reproduce the above issue as
there is no response on the above ?

On Sun, Feb 10, 2019 at 3:36 PM Amarjeet Singh  wrote:

> I have tested with FreeRDP rdpdr channel and it is working fine.
>
> It is not working only with Guacamole.
>
> Any suggestions on the above ?
>
> Please guide me to look into it or debug it to get to any conclusion.
>
> Thanks
>
>

Re: Unable to save PDF and RTF file in Redirected Drive

[Amarjeet Singh]

I have tested with FreeRDP rdpdr channel and it is working fine.

It is not working only with Guacamole.

Any suggestions on the above ?

Please guide me to look into it or debug it to get to any conclusion.

Thanks

Re: Unable to save PDF and RTF file in Redirected Drive

[Amarjeet Singh]

Hi Team,

If target system is not windows then SharedAccess=0 which imeans there is
no need to implement it.

#ifndef WIN32
> file->SharedAccess = 0;
> #endif
> file->file_handle = CreateFileW(file->fullpath,
> file->DesiredAccess,
> file->SharedAccess, NULL,
> CreateDisposition,
> file->FileAttributes,
> NULL);


Any thoughts on the above ?
If that is not the case then what is it that I am missing?

Thanks

On Thu, Feb 7, 2019 at 11:13 PM Amarjeet Singh  wrote:

> Hi Team,
>
> Findings on the below issue is as follows :-
>
> I went ahead read about the shared access from *File System Behavior in
> the Microsoft Windows Environment* DOCS
> in which there is description of OPLOCK SEMANTICS.
>
> Oplock Semantics
>> 2.1 Overview
>>
>>> Opportunistic locks, or oplocks, provide a mechanism that allows file
>>> server clients (such as those utilizing the SMB and SMB2 protocols) to
>>> dynamically alter buffering strategy for a given file or stream in a
>>> consistent manner to increase performance and to reduce network use. To
>>> increase the network performance for remote file operations, a client can
>>> locally buffer file data, which reduces or eliminates the need to send and
>>> receive network packets. For example, a client may not have to write
>>> information into a file on a remote server if the client knows that no
>>> other process is accessing the data. Likewise, the client may buffer
>>> read-ahead data from the remote file if the client knows that no other
>>> process is writing data to the remote file. Applications and drivers can
>>> also use oplocks to transparently access files without affecting other
>>> applications that might need to use those files.
>>> Oplocks are granted on stream handles, meaning that the operations apply
>>> to the given open stream of a file and, in general, operations on one
>>> stream do not affect oplocks on a different stream. There are exceptions to
>>> this, which are explicitly listed below.
>>> There are currently eight different types of oplocks:
>>>
 1. A Level 2 (or shared) oplock indicates that there are multiple
 readers of a stream and no writers. This supports client read caching.
 2. A Level 1 (or exclusive) oplock allows a client to open a stream for
 exclusive access and allows the client to perform arbitrary buffering. This
 supports client read caching and write caching.
 3. A Batch oplock (also exclusive) allows a client to keep a stream
 open on the server even though the local accessor on the client machine has
 closed the stream. This supports scenarios where the client needs to
 repeatedly open and close the same file, such as during batch script
 execution. This supports client read caching, write caching, and handle
 caching.
 4. A Filter oplock (also exclusive) allows applications and file system
 filters (including minifilters), which open and read stream data, a way to
 “back out” when other applications, clients, or both try to access the same
 stream. This supports client read caching and write caching.
 5. A Read (R) oplock (shared) indicates that there are multiple readers
 of a stream and no writers. This supports client read caching.
 6. A Read-Handle (RH) oplock (shared) indicates that there are multiple
 readers of a stream, no writers, and that a client can keep a stream open
 on the server even though the local accessor on the client machine has
 closed the stream. This supports client read caching and handle caching.
 7. A Read-Write (RW) oplock (exclusive) allows a client to open a
 stream for exclusive access and allows the client to perform arbitrary
 buffering. This supports client read caching and write caching.
 8. A Read-Write-Handle (RWH) oplock (exclusive) allows a client to keep
 a stream open on the server even though the local accessor on the client
 machine has closed the stream. This supports client read caching, write
 caching, and handle caching.
 Level 1, Level 2, and Batch oplocks were implemented in Windows NT 3.1.
 The Filter oplock was added in Windows 2000. R, RH, RW, and RWH oplocks
 have been added in Windows 7.
>>>
>>>
> Please find the attached document of the above.
>
> Guacamole VIRTUAL FILE DRIVE REDIRECTION hasn't implented it whereas
> FreeRDP 2.0.0 has implemented it.
>
> *Guacamole Code :*
>
>> void guac_rdpdr_fs_process_create(guac_rdpdr_device* device,
>> wStream* input_stream, int completion_id) {
>> wStream* output_stream;
>> int file_id;
>> int desired_access, file_attributes, sharedAccess;
>> int create_disposition, create_options, path_length;
>> char path[GUAC_RDP_FS_MAX_PATH];
>> /* Read "create" information */
>> Stream_Read_UINT32(input_stream); /* Desired Access */
>> 

Re: Unable to save PDF and RTF file in Redirected Drive

[Amarjeet Singh]

Hi Team,

Findings on the below issue is as follows :-

I went ahead read about the shared access from *File System Behavior in the
Microsoft Windows Environment* DOCS
in which there is description of OPLOCK SEMANTICS.

Oplock Semantics
> 2.1 Overview
>
>> Opportunistic locks, or oplocks, provide a mechanism that allows file
>> server clients (such as those utilizing the SMB and SMB2 protocols) to
>> dynamically alter buffering strategy for a given file or stream in a
>> consistent manner to increase performance and to reduce network use. To
>> increase the network performance for remote file operations, a client can
>> locally buffer file data, which reduces or eliminates the need to send and
>> receive network packets. For example, a client may not have to write
>> information into a file on a remote server if the client knows that no
>> other process is accessing the data. Likewise, the client may buffer
>> read-ahead data from the remote file if the client knows that no other
>> process is writing data to the remote file. Applications and drivers can
>> also use oplocks to transparently access files without affecting other
>> applications that might need to use those files.
>> Oplocks are granted on stream handles, meaning that the operations apply
>> to the given open stream of a file and, in general, operations on one
>> stream do not affect oplocks on a different stream. There are exceptions to
>> this, which are explicitly listed below.
>> There are currently eight different types of oplocks:
>>
>>> 1. A Level 2 (or shared) oplock indicates that there are multiple
>>> readers of a stream and no writers. This supports client read caching.
>>> 2. A Level 1 (or exclusive) oplock allows a client to open a stream for
>>> exclusive access and allows the client to perform arbitrary buffering. This
>>> supports client read caching and write caching.
>>> 3. A Batch oplock (also exclusive) allows a client to keep a stream
>>> open on the server even though the local accessor on the client machine has
>>> closed the stream. This supports scenarios where the client needs to
>>> repeatedly open and close the same file, such as during batch script
>>> execution. This supports client read caching, write caching, and handle
>>> caching.
>>> 4. A Filter oplock (also exclusive) allows applications and file system
>>> filters (including minifilters), which open and read stream data, a way to
>>> “back out” when other applications, clients, or both try to access the same
>>> stream. This supports client read caching and write caching.
>>> 5. A Read (R) oplock (shared) indicates that there are multiple readers
>>> of a stream and no writers. This supports client read caching.
>>> 6. A Read-Handle (RH) oplock (shared) indicates that there are multiple
>>> readers of a stream, no writers, and that a client can keep a stream open
>>> on the server even though the local accessor on the client machine has
>>> closed the stream. This supports client read caching and handle caching.
>>> 7. A Read-Write (RW) oplock (exclusive) allows a client to open a stream
>>> for exclusive access and allows the client to perform arbitrary buffering.
>>> This supports client read caching and write caching.
>>> 8. A Read-Write-Handle (RWH) oplock (exclusive) allows a client to keep
>>> a stream open on the server even though the local accessor on the client
>>> machine has closed the stream. This supports client read caching, write
>>> caching, and handle caching.
>>> Level 1, Level 2, and Batch oplocks were implemented in Windows NT 3.1.
>>> The Filter oplock was added in Windows 2000. R, RH, RW, and RWH oplocks
>>> have been added in Windows 7.
>>
>>
Link of the above doc :
*http://download.microsoft.com/download/4/3/8/43889780-8d45-4b2e-9d3a-c696a890309f/file%20system%20behavior%20overview.pdf
*

Guacamole VIRTUAL FILE DRIVE REDIRECTION hasn't implented it whereas
FreeRDP 2.0.0 has implemented it.

*Guacamole Code :*

> void guac_rdpdr_fs_process_create(guac_rdpdr_device* device,
> wStream* input_stream, int completion_id) {
> wStream* output_stream;
> int file_id;
> int desired_access, file_attributes, sharedAccess;
> int create_disposition, create_options, path_length;
> char path[GUAC_RDP_FS_MAX_PATH];
> /* Read "create" information */
> Stream_Read_UINT32(input_stream); /* Desired Access */
> Stream_Seek_UINT64(input_stream); /* allocation size */
> Stream_Read_UINT32(input_stream, file_attributes);
> Stream_Read_UINT32(input_stream, sharedAccess); /* shared access */
> Stream_Read_UINT32(input_stream, create_disposition);
> Stream_Read_UINT32(input_stream, create_options);
> Stream_Read_UINT32(input_stream, path_length);
> }

*FreeRDP 2.0.0 Code while creating or opening a file:-*

>
> if (dwShareMode & FILE_SHARE_READ)
> 

Re: Unable to save PDF and RTF file in Redirected Drive

[Amarjeet Singh]

>
> If you are attempting to save the file directly into the "Download" folder,
> it is likely that the application is repeatedly closing and reopening the
> file over the course of saving things. As Guacamole will automatically
> delete the file and begin downloading once the file is closed, an
> application which behaves in this way will not work correctly. You will
> need to save the file elsewhere and then move it to the "Download"
> folder.


Thanks Mike for helping me out with this.

I have tried to save the file instead of downloading in the Download folder
and got the same error.

Thanks,
Amarjeet Singh



On Wed, Feb 6, 2019 at 12:11 AM Mike Jumper  wrote:

> On Tue, Feb 5, 2019 at 9:50 AM Amarjeet Singh 
> wrote:
>
> > ...
> > While trying to download pdf and rtf files in the local operating system
> [
> > Windows 10 ], I am getting the below error :-
> >
> > Report Builder *REP-0081* error during file i/o operation scaba 16
> >
> >
> > ... It is only writing *10 bytes* and corrupted pdf file is downloaded.
> >
>
> If you are attempting to save the file directly into the "Download" folder,
> it is likely that the application is repeatedly closing and reopening the
> file over the course of saving things. As Guacamole will automatically
> delete the file and begin downloading once the file is closed, an
> application which behaves in this way will not work correctly. You will
> need to save the file elsewhere and then move it to the "Download" folder.
>
> - Mike
>

Re: Unable to save PDF and RTF file in Redirected Drive

[Mike Jumper]

On Tue, Feb 5, 2019 at 9:50 AM Amarjeet Singh  wrote:

> ...
> While trying to download pdf and rtf files in the local operating system [
> Windows 10 ], I am getting the below error :-
>
> Report Builder *REP-0081* error during file i/o operation scaba 16
>
>
> ... It is only writing *10 bytes* and corrupted pdf file is downloaded.
>

If you are attempting to save the file directly into the "Download" folder,
it is likely that the application is repeatedly closing and reopening the
file over the course of saving things. As Guacamole will automatically
delete the file and begin downloading once the file is closed, an
application which behaves in this way will not work correctly. You will
need to save the file elsewhere and then move it to the "Download" folder.

- Mike

Unable to save PDF and RTF file in Redirected Drive

[Amarjeet Singh]

Hi Team,

I am using guacamole-server version 1.0.0 and guacamole-client version
1.0.0.

Server : Centos 7  [ Guacamole -Server ]
> Remote OS : Windows Server 2008


We are using  *Oracle Report Builder* application in remote desktop to
generate pdf and rtf files.

While trying to download pdf and rtf files in the local operating system [
Windows 10 ], I am getting the below error :-

Report Builder *REP-0081* error during file i/o operation scaba 16


 I have added as many as logs as possible which are as follows :-

>
> pid:24707(-348199168) 05-Feb-2019 23:00:05
> guac_rdpdr_new_io_completion:Completion id [10] of Status 0 at Size 4
> pid:24707(-348199168) 05-Feb-2019 23:00:06 Major_Func and Minor_Func: 0
> and 0
> pid:24707(-348199168) 05-Feb-2019 23:00:06 guac_rdp_fs_open:
> path="\Download\DELEV_EFF_REP.pdf", access=0x12019f, file_attributes=0x80,
> create_disposition=0x5, create_options=0x60
> pid:24707(-348199168) 05-Feb-2019 23:00:06 guac_rdp_fs_open: Normalized
> path "\Download\DELEV_EFF_REP.pdf" to "\Download\DELEV_EFF_REP.pdf".
> pid:24707(-348199168) 05-Feb-2019 23:00:06 guac_rdp_fs_open: Translated
> path "\Download\DELEV_EFF_REP.pdf" to
> "/home/admin/public/rdp/gaJ7SWmDE7/Download/DELEV_EFF_REP.pdf".

pid:24707(-348199168) 05-Feb-2019 23:00:06 guac_rdp_fs_open: native open:
> real_path="/home/admin/public/rdp/gaJ7SWmDE7/Download/DELEV_EFF_REP.pdf",
> flags=0x242
> pid:24707(-348199168) 05-Feb-2019 23:00:06 guac_rdp_fs_open: Opened
> "\Download\DELEV_EFF_REP.pdf" as file_id=8
> pid:24707(-348199168) 05-Feb-2019 23:00:06 guac_rdpdr_fs_process_create:
> [file_id=8] desired_access=0x12019f, file_attributes=0x80,
> create_disposition=0x5, create_options=0x60,
> path="\Download\DELEV_EFF_REP.pdf"
> pid:24707(-348199168) 05-Feb-2019 23:00:06
> guac_rdpdr_new_io_completion:Completion id [10] of Status 0 at Size 5
> pid:24707(-348199168) 05-Feb-2019 23:00:06 Major_Func and Minor_Func: 5
> and 0
> pid:24707(-348199168) 05-Feb-2019 23:00:06
> guac_rdpdr_fs_process_query_standard_info: [file_id=8]
> pid:24707(-348199168) 05-Feb-2019 23:00:06
> guac_rdpdr_new_io_completion:Completion id [10] of Status 0 at Size 26
> pid:24707(-348199168) 05-Feb-2019 23:00:06 Major_Func and Minor_Func: 4
> and 0
> pid:24707(-348199168) 05-Feb-2019 23:00:06 guac_rdpdr_fs_process_write:
> [file_id=8] length=10, offset=0
> pid:24707(-348199168) 05-Feb-2019 23:00:06 Wrote 10 bytes in file id [8]
> of length 10 at offset 0
> pid:24707(-348199168) 05-Feb-2019 23:00:06
> guac_rdpdr_new_io_completion:Completion id [10] of Status 0 at Size 5
> pid:24707(-348199168) 05-Feb-2019 23:00:06 Major_Func and Minor_Func: 10
> and 0
> pid:24707(-348199168) 05-Feb-2019 23:00:06 
> *guac_rdpdr_new_io_completion:Completion
> id [10] of Status 0 at Size 33*
> pid:24707(-348199168) 05-Feb-2019 23:00:06
> guac_rdpdr_fs_process_query_volume_info: [file_id=8]
> pid:24707(-348199168) 05-Feb-2019 23:00:06 Major_Func and Minor_Func: 5
> and 0
> pid:24707(-348199168) 05-Feb-2019 23:00:06
> guac_rdpdr_fs_process_query_basic_info: [file_id=8]
> pid:24707(-348199168) 05-Feb-2019 23:00:06
> guac_rdpdr_new_io_completion:Completion id [10] of Status 0 at Size 40
> pid:24707(-348199168) 05-Feb-2019 23:00:06 Major_Func and Minor_Func: 5
> and 0
> pid:24707(-348199168) 05-Feb-2019 23:00:06
> guac_rdpdr_fs_process_query_standard_info: [file_id=8]
> pid:24707(-348199168) 05-Feb-2019 23:00:06
> guac_rdpdr_new_io_completion:Completion id [10] of Status 0



When I click ok the error, I get the below error :-

[image: image.png]

>
> pid:24707(-348199168) 05-Feb-2019 23:02:03 guac_rdp_fs_open: path="
> *\Download\DELEV_EFF_REP.pdf*", access=0x1, file_attributes=0x0,
> create_disposition=0x1, create_options=0x0
> pid:24707(-348199168) 05-Feb-2019 23:02:03 guac_rdp_fs_open: Normalized
> path "\Download\DELEV_EFF_REP.pdf" to "\Download\DELEV_EFF_REP.pdf".
> pid:24707(-348199168) 05-Feb-2019 23:02:03 guac_rdp_fs_open: Translated
> path "\Download\DELEV_EFF_REP.pdf" to
> "/home/admin/public/rdp/gaJ7SWmDE7/Download/DELEV_EFF_REP.pdf".
> pid:24707(-348199168) 05-Feb-2019 23:02:03 guac_rdp_fs_open: native open:
> real_path="/home/admin/public/rdp/gaJ7SWmDE7/Download/DELEV_EFF_REP.pdf",
> flags=0x0

pid:24707(-348199168) 05-Feb-2019 23:02:03 guac_rdp_fs_open: Opened
> "\Download\DELEV_EFF_REP.pdf" as file_id=4
> pid:24707(-348199168) 05-Feb-2019 23:02:03 guac_rdpdr_download_to_owner:
> Initiating download of "\Download\DELEV_EFF_REP.pdf"
> pid:24707(-348199168) 05-Feb-2019 23:02:03 guac_rdp_fs_close: Closed
> "\Download\DELEV_EFF_REP.pdf" (file_id=8)
> pid:24707(-348199168) 05-Feb-2019 23:02:03
> guac_rdpdr_new_io_completion:Completion id [10] of Status 0 at Size 4



It is only writing *10 bytes* and corrupted pdf file is downloaded.

I also went through MS-RDPEFS and it seems that everything is fine from
guacamole-server side.

*Any idea how may I debug the above issue?*

While downloading the rtf file it is writing  4271 bytes and then it shows
the above error:-