Client Drive Mapping Fails when File Size is Larger than 4GB

In XenApp and XenDesktop, very large files that have a file size greater than 4GB are not supported with Client Drive Mapping.

For Example, when viewing a file which is greater than 4GB using a published Windows Explorer instance in a XenApp Client Mapped Drive, file size will be incorrectly displayed.

The following error message might appear:

“The file <filename> is too large for the destination file system”

When copying a file with file size greater than 4GB using a CDM mapped drive, the file is partially copied, resulting in an incomplete target file being written.

Related:

Disarm Function cuts pdf attachment files with umlauts (special characters)

I need a solution

Since Version 10.7.0-5 the disarm function cuts pdf filename with special characters like äüö. The recipient can’t open the file. We need a solution for this big problem.

Regards Marcel

file.

SMG Protocol

0

Related:

Using REST API for getting suspicious files from endpoints

I need a solution

This is refering to https://www.symantec.com/connect/forums/using-rest…

As per https://apidocs.symantec.com/home/saep#_send_a_sus… I was able to issue a “/api/v1/command-queue/files” command successfully which then returned the commandID.

Based on this ID I found the [BINARY_RESULTS_ID] in the [COMMAND] table with the given [COMMAND_ID] to run the “/api/v1/command-queue/file/{file_id}/content” successfully, too.

After saving the output so a file I was able to open the “archive” and saw two files:

– binary file
– metadata.xml

<?xml version="1.0" encoding="UTF-8"?>
<MetaFile>
<File Key="128" OriginalFileName="\?C:WindowsSystem32notepad.exe" OriginalFilePath="\?C:WindowsSystem32" FileName="fa2258b2cc57610861ed1279079e2854cce6768178fe7b3e952a56a990403e66" FileSource="filesystem" FileXORed="true"/>
</MetaFile>

The only issue I’m facing now is that I’m unsure how to “convert” the binary file back to its original format (.exe)
I guess you would have to remove the XOR encryption.

0

Related:

Re: Recovery a file from a EMC networker saveset that has expired and no longer browsable

Let me first make these comments:

– A single save set that spans 15 tapes – not a good idea, in general

– Changing the browse (and retention) once the save set is not browsable any more will not repopulate the CFI info which

has been deleted when it changed state from browsable to recoverable/recyclable.

If you really need the CFI info, you must run “scanner -i” for that save set.

##################################

In general you have 3 options for a standard file system backup which start the save set as ‘browsable’:

1. Recover by rebuilding the file index info first

Of course the client file index must be available (the metadata must be retrievable within the data stream).

If you have deleted the client in the meantime, you must first

– ensure that you can resolve the hostname (worst case by an entry in the local hosts file)

– recreate a client resource (the exact parameters do not matter because you don’t want to run backups)

– I do not remember exactly any more but you might need to set the browse and retention dates for the save set high

enough so that the current policies would not automatically delete the metadata immediately again.

– rebuild the CFI with “scanner -i”

– recover the file(s)

2. Recover the whole save set to a temp directory and get the file(s) from there.

3. Run a subset recovery like

recover -iR -R <dest_client> -d <dest_directory> -S <ssid> -a “exact_pathname_what_to_recover”

– This of course implies that you know the exact pathname (directory- or file name)

– Be aware that NW will read the whole save set … which may take a while … but only recovers what you want

You better familarize with the command on a small (sub) save set 😉 .

Related:

ShareFile Error “The folder structure that you tried to download is too deep to be supported by most operating systems….. your folders and files.”

The Microsoft Windows API defines the maximum file path limit as 260 characters for a fully specific path-and-filename. This includes the beginning of the directory to the file extension. While there are some exceptions to this limit, ShareFile typically enforces a file path limit on files upload or downloaded via our various apps and tools.

File Path errors refer to the length of the file path and file name rather than the size of the file. If you encounter this error when attempting to upload or download a file using one of our apps, you may need to navigate to a deeper folder within the structure you are trying to download. By downloading at a level of 1 or 2 folders deeper than the root folder, you may be able to still download the majority of your data without having to recreate the folder structure on your own computer.

Additionally, you may want to consider renaming lengthy file names that occupy the majority of the limit.

Related:

7022801: Wicked Ignores ETHTOOL_OPTIONS for bond configurations

A PTF to provde this functionality has now been created. It will be available via the normal maintenance channels at some point in the near future.
For now, the PRE_UP_SCRIPT functionality as described in ‘man 5 ifcfg’ may be used to effect desired settings.

Here is an example of using PRE_UP_SCRIPT:


In this example, a bond called ‘bond0’ has been created.


If it does not already exist, create a directory to house the scripts:

e.g /etc/wicked/scripts if it does not exists (directory name does not have to be ‘scripts’ and location can differ)


Create a script file in the directory you created:

e.g. /etc/wicked/scripts/script1


Add the desired command line/s to the script file:

e.g. ethtool -K bond0 tso off gso off


root needs the execute attribute on the script file:

e.g. chmod 744 /etc/wicked/scripts/script1


Edit file /etc/sysconfig/network/ifcfg-bond0 (substitute your bond name as required) and add:-

e.g. PRE_UP_SCRIPT=”wicked:/etc/wicked/scripts/script1″


Now, when ever the server is brought up or the network resources are restarted, the desired parameters will be applied.

Related:

App Layering error “A failure occurred while publishing the Layered Image: “Failed scanning a directory for files” because of Microsoft.MicrosoftOfficeHub

Recommended Solution: This issue has now been fixed in versions 4.6+ of App Layering. The simplest way to resolve this issue is to upgrade the latest version of the App Layering appliance.

* Update: This issue can also be caused by apps that use invalid windows file names. One example is CON.<anything>. CON is a reserved file name. In one case, CygWin was used to install a package which included /cygwin64/usr/share/avogadro/crystals/zeolites/CON.cif. The ELM will fail to copy this file because it is not a valid name. The only current solution is to delete the file.

For historical purposes, here is the original fix for those who are still using versions 4.5 or earlier of the App Layering product:

This error is most frequently caused by Microsoft OfficeHub. The “Program FilesWindowsAppsMicrosoft.MicrosoftOfficeHub” directory has a new type of reparse point that was recently invented by Microsoft, and ntfs-3g is currently unable to handle it. Thus, there is no way for our Linux virtual appliance (App Layering ELM) to correctly recognize these files. So we will need to remove them before working in App Layering. There is no negative effect to removing the OfficeHub files, as these files will be rebuilt automatically on end-user desktops.

The fix needs to be done in the VM or layer where the problem files are present. If the error occurs while publishing a VM (App Layering versions 4.x) or during desktop creation (versions 2/3.x), or while editing/creating layers, then you will need to execute the fix on the specific layer that is causing the issue. Usually, the problem is in the OS layer, so you would need to execute the solution on a new version of the OS layer. However, it is also possible that the offending files are on an application layer or the platform layer, so you may need to experiment to determine which layers the files are located on. If you cannot find them in file explorer for any of the layers, you should open a Technical Support case, and one of our engineers will be able to make that determination.

Solution 1: PowerShell

On the OS layer, running the following two PowerShell commands (from the command prompt as administrator) might be able to remove the folders without manually setting permissions and deleting them Sometimes, manually deleting the folders can be a long and painful process. Make sure to run the PowerShell commands as the admin that originally created the image. It is possible that OfficeHub may already be staged for the original user, and will deny removal from the following script if that is the case.

powershell -command "& {Get-AppxPackage -name Microsoft.MicrosoftOfficeHub -AllUsers | remove-appxpackage}"powershell -command "& {Get-AppxProvisionedPackage -online | Where-Object {$_.DisplayName -like "*Microsoft.MicrosoftOfficeHub*"} | remove-AppxProvisionedPackage -online}

Solution 2: Manually changing the file permissions, and then deleting them

Make sure that the files are located in the “Program FilesWindowsAppsMicrosoft.MicrosoftOfficeHub” directory. The files will need to be deleted out of this folder, and typically you’ll need to take ownership and change permissions in order to remove them.

Additionally, on Windows 10 Enterprise machines, you may also need to check and remove the OfficeHub directory from “usersAdministratorappdatalocalpackagesMicrosoft”

Lastly, make sure Program Files/WindowsApps/Deleted/Microsoft.MicrosoftOfficeHub_17.8010.5926.0_x64__8wekyb3d8bbweb6a07f30-3c9c-4a53-867e-42e7a1f58db8* is empty.

In extreme cases, the $recycle.bin may also need to be completed deleted.

The following command will delete the $RECYCLE.BIN – then the OS will refresh and recreate it automatically, without any artifacts from OfficeHub.

RD /S /QDrive-Letter:$Recycle.bin

Related:

Unable to deploy custom receiver from Store front. Getting ” An error occurred while saving changes on the “Deploy Citrix Receiver” property dialog. Please check the log in event viewer and try again.”

While trying to add customized “receiver.exe” to deploy receiver option in Storefront, you might get following error while saving it.

“An error occurred while saving changes on the “Deploy Citrix Receiver” property dialog. Please check the log in event viewer and try again”.

It works fine with default receiver.

This was the event:

Log Name: Citrix Delivery Services

Source: Citrix Delivery Services Admin

Event ID: 1

Description:

An error occurred running the command: ‘Update-DSWebReceiverHTML5Config’

Filepath ‘C:Program FilesCitrixReceiver StoreFrontReceiver ClientsWindowsFLExternalTest.EXE’ does not contains a filename.

At C:Program FilesCitrixReceiver StoreFrontManagementCmdletsWebReceiverModule.psm1:1658 char:41

+ $SourceTypeForInstallerForWindows = GetReceiverInstallerSourceType -Installe …

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

Filepath ‘C:Program FilesCitrixReceiver StoreFrontReceiver ClientsWindowsFLExternalTest.EXE’ does not contains a filename.

Citrix.DeliveryServices.PowerShell.Command.RunnerInterfaces.Exceptions.PowerShellExecutionException, Citrix.DeliveryServices.PowerShell.Command.RunnerInterfaces, Version=3.12.0.0, Culture=neutral, PublicKeyToken=e8b77d454fa2a856

An error occurred running the command: ‘Update-DSWebReceiverHTML5Config’

Filepath ‘C:Program FilesCitrixReceiver StoreFrontReceiver ClientsWindowsFLExternalTest.EXE’ does not contains a filename.

At C:Program FilesCitrixReceiver StoreFrontManagementCmdletsWebReceiverModule.psm1:1658 char:41

+ $SourceTypeForInstallerForWindows = GetReceiverInstallerSourceType -Installe …

+ ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

System.Management.Automation.ActionPreferenceStopException, System.Management.Automation, Version=3.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35

The running command stopped because the preference variable “ErrorActionPreference” or common parameter is set to Stop: Filepath ‘C:Program FilesCitrixReceiver StoreFrontReceiver ClientsWindowsFLExternalTest.EXE’ does not contains a filename.

System.Management.Automation.Interpreter.InterpretedFrameInfo: System.Management.Automation.Interpreter.InterpretedFrameInfo[]

at System.Management.Automation.Internal.PipelineProcessor.SynchronousExecuteEnumerate(Object input, Hashtable errorResults, Boolean enumerate)

at System.Management.Automation.PipelineOps.InvokePipeline(Object input, Boolean ignoreInput, CommandParameterInternal[][] pipeElements, CommandBaseAst[] pipeElementAsts, CommandRedirection[][] commandRedirections, FunctionContext funcContext)

at System.Management.Automation.Interpreter.ActionCallInstruction`6.Run(InterpretedFrame frame)

at System.Management.Automation.Interpreter.EnterTryCatchFinallyInstruction.Run(InterpretedFrame frame)

Related:

VNX: CAVA error VC: 3: 32: Server ‘x.x.x.x’ returned error ‘FAIL’ when checking file

Article Number: 480920 Article Version: 2 Article Type: Break Fix



VNX Event Enabler,VNX1 Series,VNX2 Series,Celerra

While virus checking is running, in the logs an error indicating that the VC service has failed to check it:

2016-03-29 11:38:44: VC: 3: 32: Server ‘x.x.x.x’ returned error ‘FAIL’ when checking file ‘root_vdm_idmount_pathfilename.ext’

The ‘FAIL’ message occurs when a scan request is opened (the VC service on the data mover sends a request to the CAVA servers) and when the CAVA server tries to open it the file is not found. This means that the file was deleted before it could be scanned. There are some scenarios where this could happen:

  • One way this occurs is if the file was a cookie, temporary file, or lock file. Microsoft office, for example, creates temporary files that follow the format ~$<original_filename.xxxx>. These files normally disappear when the file is saved or closed, and if this happens quickly the file can disappear before it has a chance to be scanned, leading to the FAIL message in the data mover log. The filenames that are failing scans usually identify this as the source of the issue.
  • Another way this can occur is if the file has a special ‘disposition’ on it. In SMB and SMB2 the user can set a disposition ‘delete on close’ when opening a file. If the file that is referred for scanning is opened by another user with this disposition set, the file is deleted before it can be scanned, leading to the FAIL message in the data mover logs. This option can be seen in packet traces by looking at SMB ‘Create’ or ‘SetInfo’ calls, but will be set by the user doing the deleting, and probably not the CAVA servers. This can make things difficult because normal traffic must be monitored (not just the AV server) to determine who is setting the flag.

The best resolution is to stop what is deleting the file (the external users deleting the file). This may mean disabling the use of temp files in office, or storing other temp files or cookies to a local directory instead of a shared one. If this cannot be done, then alter viruschecker.conf to exclude these types of files from being checked by altering the ‘excl’ line to exclude ~$*.* (for office files), *.tmp or any other extension that may be causing these errors.

viruschecker.conf:

CIFSserver=<CIFS server on data mover>

addr=<configured CAVA servers>

excl=~$*.*:*.accdb:*.laccdb:*.ldb:*.mdb:*.pst:*.tmp:????????

masks=*.*

shutdown=viruschecking

additional resources:

https://support.microsoft.com/en-us/kb/211632 (Description of how Word creates temporary files)

https://wiki.wireshark.org/SMB2/SMB2_FILE_DISPOSITION_INFO (SMB2_FILE_DISPOSITION_INFO addresses ‘delete on close’) feature

Related:

7022964: How to edit Custom Translation Tables for 3270 sessions in Reflection

The Reflection Desktop 16, Reflection 2014, and Reflection 2011 products allow the user to create custom Host Code Pages for 3270 Terminal Sessions, Printer Sessions, and File Transfers via the Edit3270.exe application. To start this utility make sure that no Reflection Host sessions are loaded or in memory. After the translation table is edited using this utility, it updates the file named R8NCS.DLL with the new translation information.

Here are basic instructions on how to use the utility:

1. Install Reflection Desktop 16.

2. Navigate to the Reflection Desktop directory (C:Program Files (x86)Micro FocusReflection)

3. Select and run Edit3270.exe as Administrator.

4. Accept the 3270 National Character set and Font.

5. Select the appropriate Ansi->Ebcdic or Ebcdic<-Ansi table to edit.

6. Make the appropriate edits to the table.

7. Notice that the time and date stamp on the file R8NCS.DLL (in the C:Program Files (x86)Micro FocusReflection) will be updated to the current time and date.

8. Load a Reflection Host session and test the translation table changes.

Note: When applying an Update, Service Pack, or Hotfix the R8NCS.DLL can get updated and overwritten, with the resulting loss of the customized file.

Related: