Error: “Cannot Complete Your Request” due to “Default.htm” file being corrupted on Storefront

If you get this error after upgrading the Storefront server, then navigate to C:inetpubwwwrootCitrix<StoreName>Web and delete Default.htm file.

Create a new test store and copy Default.htm to C:inetpubwwwrootCitrix<StoreName>Web. Delete the test store.

The upgrade process occasionally corrupts the IIS default.html file.

Related:

Mirror AppdataLocalPackages cannot work in UPM 1912 and later version.

We introduce a new fix in UPM1912.

​https://docs.citrix.com/en-us/profile-management/1912-ltsr/whats-new/1912-ltsr-initial-release/fixed-issues.html

The Folders to mirror policy and the Exclusion list policies do not work together. The issue occurs because Profile Management does not support using the Folders to mirror policy along with either the Exclusion list – files nor the Exclusion list – directories policy. [UPM-1708]

​Under this background, it means if AppdataLocalPackages is configured as exclusion directory, the folder will not be synchronized even it is a mirror folder.

And we find that the path is in the default exclusion list of UPMPolicyDefaults_all.ini, so mirror cannot work.

Related:

  • No Related Posts

How to Remove Files Remaining on System after Uninstalling Receiver for Mac

After uninstalling the Receiver and rebooting the system, ensure that the files or folders listed in this section have been removed from your system. If they still exist, remove them manually.

  1. /Applications-

    Citrix Receiver.app

  2. /Library

    – /Internet plug-ins/CitrixICAClientPlugIn.plugin

    – /LaunchAgents/com.citrix.AuthManager_Mac.plist

    – /LaunchAgents/com.citrix.ServiceRecords.plist

  3. /Users/Shared

    – /Citrix/Receiver Integration (entire folder)

  4. ~/Library

    – /Internet plug-ins/CitrixICAClientPlugIn.plugin

    – /Application Support/Citrix Receiver

    – CitrixID

    – Config

    – Module

    – /Preferences/com.citrix.receiver.nomas.plist

    – /Preferences/com.citrix.receiver.nomas.plist.lockfile

    – /Preferences/com.citrix.ReceiverFTU.AccountRecords.plist (added in 11.6)

    – /Preferences/com.citrix.ReceiverFTU.AccountRecords.plist.lockfile (added in 11.6)

  5. ~/Applications

    – Under this folder, you can delete any applications you previously added via the Receiver UI.

  6. /private/var/db/receipts

    – com.citrix.ICAClient.bom

    – com.citrix.ICAClient.plist

Important Notes

  • A tilde (~) placed at the beginning of a folder path refers to that folder’s location within the user profile. For example, ~/Library/Preferences/ refers to the Preferences folder within the user’s Library folder (e.g. /Users/<username>/Library/Preferences/). A path without a tilde refers to the system-wide version of that folder at the root of the system (e.g. /Library/Preferences/).

  • Note that certain folder mentioned in the list can be hidden directories on the system.

  • It is important to remember that certain items mentioned in this article might not exist on your system depending on the Receiver version(s) you previously installed.

Follow Me Data Notes

In version 11.6, the Follow Me Data feature is integrated into the Citrix Receiver for Mac. The files and folders that are compatible with this feature are listed.

You can remove the files that were not properly cleaned up by the uninstaller. You can also keep the user data that was previously synchronized on your system by Follow Me Data.

  1. The following locations should be cleaned up after running the uninstaller utility:

    – ~/Applications/Citrix/FollowMeData (this is a hidden folder that contains the application binary)

    – ~/Library/Application Support/ShareFile (contains user specific configurations)

    – /Library/PreferencePanes/FMDSysPrefPane.prefPane

  2. Installation information files that are okay to remove after uninstall:

    – /private/var/db/receipts/com.citrix.ShareFile.installer.plist

    – /private/var/db/receipts/com.citrix.ShareFile.installer.bom

File not cleaned up during uninstall that you may or may not want to delete depending on your needs:

– ~/ShareFile (contains the user data synchronized by Follow Me Data)

– /private/var/db/receipts

– com.citrix.ShareFile.installer.plist

– com.citrix.ShareFile.installer.bom


If you are Unable to find the Citrix WorkSpace App running on your MAC and if you want to forcefully quit

Press Cmd + Alt + Escape to see the Force Quit Applications menu.

This will show running apps, and lets you force-quit them if necessary – just highlight the Citrix WorkSpace App and click Force Quit.

Related:

How to fix Event ID 455 ESENT error on Windows 10

ESENT is a built-in database search engine on your PC which helps File Explorer, Windows Search to search for parameters throughout your Windows 10 computer. If you’re encountering the Event ID 455 ESENT error on your Windows 10 device, then this post is intended to help you. In this post, we will provide the potential solutions you can try to mitigate this issue.

When this error occurs, you’ll see in the event log the following error description;

svchost (15692,R,98) TILEREPOSITORYS-1-5-18: Error -1023 (0xfffffc01) occurred while opening logfile

C:WINDOWSsystem32configsystemprofileAppDataLocalTileDataLayerDatabaseEDB.log.

Fix Event ID 455 ESENT error

If you’re faced with this Event ID 455 ESENT error on your Windows 10 PC, you can try either of our two recommended solutions presented below to resolve the issue.

  1. Create Database folder in TileDataLayer folder via File Explorer
  2. Create Database folder in TileDataLayer folder via Command Prompt

Let’s take a look at the description of the process involved concerning either of the listed solutions.

1] Create a Database folder in TileDataLayer folder via File Explorer

To create a Database folder in TileDataLayer folder via File Explorer, do the following:

  • Press Windows key + R to invoke the Run dialog.
  • In the Run dialog, copy and paste the directory path (assuming the C drive is housing your Windows 10 installation) below and hit Enter.
C:Windowssystem32configsystemprofileAppDataLocal
  • Now, right-click on the open space and then click New >Folder to create a folder in that location.
  • Next, rename the new folder as TileDataLayer.
  • Now, double-click the newly created TileDataLayer folder on it to explore it.
  • Again right-click on the space within the open folder and then click New >Folder to create a new folder.
  • Rename the new folder as Database.
  • Exit File Explorer
  • Reboot your computer.

After rebooting the Event ID 455 ESENT error should be fixed.

Alternatively, to achieve the same result using File Explorer, you can use the CMD Prompt. Continue below to see how.

2] Create a Database folder in TileDataLayer folder via Command Prompt

To create a Database folder in TileDataLayer folder via Command Prompt, do the following:

  • Press Windows key + R to invoke the Run dialog.
  • In the Run dialog box, type cmd and then press CTRL + SHIFT + ENTER to open Command Prompt in admin/elevated mode.
  • In the command prompt window, copy and paste the syntax below one by one and hit Enter after each line to execute them sequentially on your computer.
cd configsystemprofileAppDataLocalmkdir TileDataLayercd TileDataLayermkdir Database
  • Once the task completes, exit the CMD prompt.
  • Reboot your computer.

After rebooting the Event ID 455 ESENT error should be fixed.

ESENT

ESENT is an embeddable, transactional database engine. It first shipped with Microsoft Windows 2000 and has been available for developers to use since then. You can use ESENT for applications that need reliable, high-performance, low-overhead storage of structured or semi-structured data. The ESENT engine can help with data needs ranging from something as simple as a hash table that is too large to store in memory to something more complex such as an application with tables, columns, and indexes.

Active Directory, Windows Desktop Search, Windows Mail, Live Mesh, and Windows Update, currently rely on ESENT for data storage. And Microsoft Exchange stores all of its mailbox data (a large server typically has dozens of terabytes of data) using a slightly modified version of the ESENT code.

Features

Significant technical features of ESENT include:

  • ACID transactions with savepoints, lazy commits, and robust crash recovery.
  • Snapshot isolation.
  • Record-level locking (multi-versioning provides non-blocking reads).
  • Highly concurrent database access.
  • Flexible meta-data (tens of thousands of columns, tables, and indexes are possible).
  • Indexing support for integer, floating-point, ASCII, Unicode, and binary columns.
  • Sophisticated index types, including conditional, tuple, and multi-valued.
  • Columns that can be up to 2GB with a maximum database size of 16TB.

Benefits

  • No additional download needed. ManagedEsent uses the native esent.dll that already comes as part of every version of Microsoft Windows.
  • No administration required. ESENT automatically manages log files, database recovery, and even the database cache size.

Note: The ESENT database file cannot be shared between multiple processes simultaneously. ESENT works best for applications with simple, predefined queries; if you have an application with complex, ad-hoc queries, a storage solution that provides a query layer will work better for you.

Related:

Citrix Files WebApp: How to Upload a File

When viewing a folder, there are multiple ways to upload a file. You can:

  • Drag your files right into the web browser
  • Access the blue circular Action Button and choose Upload.

User-added image

NOTE: Citrix recommends waiting for uploads to finish before navigating away from the folder menu.

No Upload Button?

You can only upload files to folders to which you have Upload Permissions. If you do not see the Create Folder or Create Shared Folder options, or do not have the blue action button at all, contact your Workspace administrator to obtain Upload permissions.

Limitations

  • You cannot upload more than 10,000 items into an individual folder.
  • While you can upload files up to 10GB or 100GB, depending on plan level, any upload that takes longer than 18 hours to complete will fail.

FAQ

What file formats can I upload?

Any file type may be uploaded to Citrix Files WebApp.

NOTE: Not all file types may be previewed.

What is the maximum file size I can upload?

Workspace supports the upload and download of files up to 10GB or 100GB in size, depending on plan level. If your upload process cannot be completed within 18 hours, Workspace recommends breaking your upload into smaller segments.

Related:

Steps to uninstall MAC receiver properly

1.Launch the Terminal app on your Mac by either searching for it in Spotlight or locating it in the Utilities folder under Applications.

2.Type in the following command: “sudo rm -r” (without quotes) and then drag and drop the receiver on the terminal window.

Note : “sudo rm -r” is most powerful command which will delete all the files and directories under the present working directory, please make sure you are executing this command under correct required directory

3.Hit Enter on your keyboard.

4.You may be prompted to enter your OS X user password. Type it in and then hit Enter on your keyboard.

5.All the directories & files would be successfully removed.

6.Install the latest receiver and test.

Related:

UPM included file with wildcard in name, getting deleted by Cleanup Profile Policy (Parent folder is in exclusion List)

UPM included file with wildcard in name is getting deleted by Cleanup Profile Policy (Parent folder is in exclusion List

Scenario

Customer configure exclude folder Policy for the folder “Test ”

They have an include File to Synchronize policy for the file “Test *.849C9593-D756-4E56-8D6E-42412F2A707B” . and have enabled Logon Exclusion Check and set to delete Excluded Files and Folders.

When a users logon and configure the profile and logoff the file “Test Apps.849C9593-D756-4E56-8D6E-42412F2A707B” is written to the store for the first time. Next Time when the users tries to logon, we see that the file is disappearing from the profile store. When we don’t use the wildcard in the include file policy, the file is remaining there. When we disable Logon Exclusion Check, the file is remaining, too.

Related: