Mini Kabibi Habibi

Current Path : C:/Windows/System32/en-US/
Upload File :
Current File : C:/Windows/System32/en-US/WorkFoldersRes.dll.mui

MZ����@���	�!�L�!This program cannot be run in DOS mode.

$5�<�q�R�q�R�q�R�e���p�R�e�P�p�R�Richq�R�PEL�!�

��t@ <�8.rdata�@@.rsrc� �@@@��
T88@��$��8.rdata8x.rdata$zzzdbg @.rsrc$01@!�.rsrc$02 )��M(�l�w�'S
\�#��\&�ڰ��@��0�0�H�`�x���������	�			 8!���!�#܈�ܫ`�MUI����Eh�Ej��q׈�[��й^��Z쒕��������MUIen-USUWork Folders resources containing localizatble resources and error code descriptions.Work Folders ResourcesWork FoldersPA
2�2�|ȀMȀ�ȀȀ ;ȀȀG�Ȁ�Ȁ�GȀ1Ȁ0H3Ȁ>ȀLqȀȀ|y0Ȁ0Ȁ|0Ȁ0Ȁ�|8Syncing is in progress.

lThe data transferred isn't in the proper format.

�Your Work Folders location on the server has been deleted. Email your organization's tech support.

�There was a problem syncing because the server is currently busy. Sync will retry later.

�Data transfer for this sync batch is out of order. Sync will retry later.

�The administrator of the Work Folders server temporarily suspended your ability to sync. Try syncing again later.

�Your files are currently syncing on another PC or device. Sync will retry later.

|The user session cannot be found. Sync will retry later.

tThe sync request isn't valid. Sync will retry later.

xThe request exceeds the data size that can be handled.

dYour credentials don't match the account you used to set up Work Folders. To continue syncing, authenticate with the credentials you used when setting up Work Folders. If you recently changed domains or accounts, click Stop using Work Folders and then set up Work Folders again with your new account.

`The data transferred has an invalid length.

0The URI is invalid.

4The query is invalid.

XThe data transfer has an invalid index.

�The knowledge database size is zero or exceeded the max size. It is invalid.

\The data transfer has exceeded the limit.

hThe token used for the sync session is invalid.

�The requested session type is not valid. Supported types are upload or download.

PThe data content length is missing.

DThere's a problem with the permissions of your folder on the server. Email your organization's tech support and ask them to make you the owner of the folder.

�A sync share already exists in this path or in a subfolder or parent folder of this path.

One or more accounts aren't valid for configuring with a sync share. Accounts must be user accounts or security group accounts.

�A file was changed during sync, so it needs to be synced again.

�A file cannot be synced because it's in use. The file will be synced when it's no longer in use.

�The specified path isn't valid. The path must be on a local NTFS volume and can't be the root directory for the volume, a mount point for a root directory, a sync share, or a sync share staging folder.

�The Work Folders server received a request without a required HTTP header.

$The server has reached the maximum allowed concurrent sync sessions. Additional sync sessions will wait until some current sessions complete.

�Download batch cannot be found. The batch may not have been generated yet.

�Operation cannot be performed in the current sync session's state.

lThe length of a specified parameter isn't valid.

�The operation is being prevented since this sync object is being used by other objects. This could also happen if the sync object is trying to use other objects that are already being used by some other sync object.

PThe Cluster service is not running.

PThere was a problem with your user account or with your organization's Active Directory Federation Services configuration. Email your organization's tech support.

�The value specified for a parameter is outside its allowed range.

�The local folder that stores your Work Folders isn't accessible. This can occur if you renamed, moved, or deleted the folder, or if Work Folders was stored on a drive that was removed from your PC (such as a microSD card).

hThe UserFolderName parameter contains an incorrect value. The parameter specifies the folder-naming format for user folders and whether to sync a single subfolder. The parameter must contain [user] (case sensitive). The [user] parameter must be specified inside the first UserFolderName path component.

�The specified user couldn't be found. Confirm that the user account exists.

�The specified user couldn't be authorized on the server because the user account is currently blocked. This can occur if the user is a member of a blocked group, or if the user was explicitly blocked from syncing on this server.

�The sync share path should be on a shared volume when creating or modifying a sync share on a failover cluster.

�The specified sync object already exists. The name of the specified sync object is already in use.

�The settings aren't valid for the specified authentication type.

pThe computer is not a member of a failover cluster.

�The user can't be authenticated because the AD FS token signing certificate is missing or not supported.

�An error occurred while parsing the response from the AD FS server.

lThe specified sync share name couldn't be found.

lThe file is already present in the staging area.

pThis type of file isn't allowed on this sync share.

�The stream for this file has already been uploaded to the server.

�The staging quota for users (StagingQuotaPerUserGB) can't be set to a larger value than the staging quota (StagingQuotaGB) for the sync share. Reduce the StagingQuotaPerUserGB value or increase the StagingQuotaGB value for the sync share.

�There was a problem with the length of the version field for a file to be downloaded.

hThis sync session is already downloading files.

hThe download session is in an incorrect state.

lA request for a zero length stream was requested.

@ECS_E_AD_PROPERTY_NOT_FOUND

You're not set up on the server. Email your organization's tech support and ask them if they can give you access to Work Folders.

�The prepare request had multiple entries for a file with the same sync Id, which is not permitted.

8The file is larger than the maximum size allowed on the server. Remove the file from Work Folders or ask tech support to increase the file size limit.

$The name of the sync share is invalid. The name cannot contain the characters <>:"/\|?* or consist of a reserved file name like NUL or COM1.

�Your configuration is being updated by the server. Sync will continue in a little bit.

The Federation Service URL is incorrect, unreachable, or a relying party trust hasn't been set up for the sync server in AD FS.

�Unable to determine the type of authentication being used.

hThe server is too busy to handle sync requests.

�Work Folders needs to update its database on this PC. Sync will continue in a little bit.

�The Enterprise ID specified is invalid. Valid Enterprise IDs must be in second level domain format. The domain information for this machine too could not be determined to compute a default Enterprise ID. Please specify a valid Enterprise ID.

LClient connection has been lost.

XClient request not supported by server.

�Unknown tenant. The tenant may have been removed recently.

�The server encountered an error while invoking an Azure authentication api.

�The configuration required for Azure authentication is missing.

�The STS required for Azure authentication needs to be provided.

xA required configuration for encryption is not defined.

�The user file should not undergo any crypto transformation.

�The server cannot reach the ADFS server due to a timeout or a connection error. Sync will retry later.

tThe RMS encryption template has an expired validity.

`The sync service is currently unavailable.

�The user request was throttled by the service. Please retry again after some time.

XA configuration change has blocked the Work Folders service from running. This can occur if this Work Folders sync service has been superseded by a newer sync service.

�There were a large number of conflicts for a file. This can occur if many changes were made at roughly the same time on multiple PCs or devices. The file won't be synced until you remove or rename the conflicting files.

lA reparse point was detected and won't be synced.

dA hard link was detected and won't be synced.

�There was a problem transferring a file but Work Folders will try again later.

�Couldn't use the USN change journal to process changed files. Enumerating files instead.

�A file was skipped but will be synced during the next sync session.

�The processing of an item encountered a recoverable failure.

hA file or directory change can't be synced yet because a dependent folder is not yet synced. This item will sync after the dependent changes are synced. No action is required.

\A file or directory was skipped during this synchronization pass to rebuild the sync client's metadata. It will be synchronized in the next full synchronization attempt.

�The root directory of the sync share does not exist or could not be opened.

�Work Folders will rebuild its database during the next sync.

�Couldn't rename a file because the file was in use. Sync will try again later.

�The Azure sync database has requested an internal transaction status refresh.

�The Azure sync database write lease can not be obtained due to an already existing lease.

�The Azure sync database write lease has been lost due to another database writer.  The current operation will be aborted.

tA file was skipped due to conflict resolution policy.

�There was a problem transferring a file but Work Folders will try again later.

�The sync server needs the user's current user name and password.

`No sync server could be found for the user.

`An unknown server error has been received.

lThe server that stores your Work Folders is undergoing maintenance, but sync will continue when this is finished. Contact your organization's tech support for more information.

xSync settings couldn't be retrieved from the registry.

�The app that called the Work Folders API didn't set the impersonation level to allow impersonation.

PThe sync partnership is suspended.

�There was a problem saving sync settings. Work Folders is not set up.

There was a problem getting the sync server URL from Active Directory Domain Services. This can occur if the AD DS schema hasn't been extended or if the sync server URL attribute hasn't been set on the user account. Contact your organization's tech support.

hThere was a problem deleting the sync settings.

�The sync settings retrieved from the registry aren't valid. Sync needs more info from you.

XThis PC isn't connected to the network.

�This PC must have autolock set to 15 minutes or less. Once screen lock is configured, sync will resume.

LDownload request is out of order.

�The size or number of files in the sync batch are too big.

tThe download sync session has a sync ID in conflict.

`The download session response isn't valid.

�The download session hash has a conflict. Sync will retry.

�Couldn't finish downloading files. Sync will try again later.

dThis PC must have a password that is 6 or more characters to allow Work Folders to synchronize the data. Once a password that meets this guidelines is set, sync will resume.

8The Work Folders path has to be encrypted. You might have an application holding the Work Folders folder open or the folder might be compressed. Close File Explorer and any open files or apps, and check the folder Advanced properties to ensure that the folder is not compressed.

�The server staging folder is full. The server will free up some space and then try again.

You're out of space on the server. To fix this problem, remove some files from or ask your system administrator for more space.

dThere was a problem, but sync will try again.

`The email address you entered isn't valid.

�Sync has been cancelled. As a result, files won't be uploaded or downloaded from the server.

hThis PC doesn't have enough free space to sync.

�Sync can't be set up in the specified location because it's already set up for sync.

4Sync can't be set up in the specified location because the folder must be located on an NTFS-formatted volume and can't be inside the Windows folder.

�Sync couldn't complete because a file changed. Sync will try again later.

xThe session ID for the user's sync session isn't valid.

�The user couldn't be authenticated using Digest authentication.

�The user couldn't be authenticated using Kerberos authentication.

�The user couldn't be authenticated using AD FS authentication.

`There was a problem contacting the server.

|The server couldn't find the correct folder for the user.

�Sync completed, but some of the files didn't transfer properly.

dThe location that you chose for Work Folders overlaps with another sync technology on your PC, so you should pick a different location or disable the other sync technology.

�Choose a location that doesn't contain a drive mounted in a folder or another type of reparse point.

Choose a location that's on a fixed or removable drive, such as a hard drive or microSD card. You can't choose a network location.

�Choose a location that's on a drive formatted with the NTFS file system.

�Work Folders can't be located in the root folder of a volume.

�This folder can't be used because it was wiped by your organization. Delete the wiped folder or choose another location.

4This PC is incompatible with the Work Folders server and must be upgraded. Please contact your administrator for instructions for upgrading your PC.

�Choose a location that isn't reserved for use by Windows or apps.

�The proxy server used to access the Internet needs your current credentials.

DSearch indexing isn't enabled on your Work Folders location yet. This can occur if the Windows Search service takes more time to start up or isn't enabled at all after your PC is up and running for some time. Work Folders will keep checking periodically or upon "Sync now" if the issue is resolved. You can wait or try to start the service manually. Restarting your PC will also start the Windows Search service.

�Windows couldn't disable indexing on your Work Folders after turning off Work Folders. 

hCredential cannot be set when it is not needed.

�Access to Work Folders is blocked on this PC because the encryption key has been revoked. This can occur if your PC is no longer managed by your organization.

Don't delete the folder currently used by Work Folders if you want to recover files that haven't synced to other PCs and devices. To recover files, email your organization's tech support.

Click Stop using Work Folders to remove the sync partnership. To regain access, set up Work Folders again in a new folder.

�This PC doesn't meet the maximum failed password attempts policies set by your organization.

�This PC cannot meet the compliance policies set by your organization.

�The server's SSL certificate isn't valid. Email your organization's tech support.

�The server's SSL certificate was revoked. Email your organization's tech support.

The server's SSL certificate was issued by a certificate authority that isn't trusted by this PC. Email your organization's tech support.

LThe server's SSL certificate contains incorrect hostnames. The certificate can't be used to establish the SSL connection. Email your organization's tech support.

�The server's SSL certificate is expired. Email your organization's tech support.

�There was a problem validating the server's SSL certificate. Email your organization's tech support.

XThe specified path is not encryptable.

dAn uploaded file failed the signature check.

`Token Broker returned an unexpected error.

|The file being downloaded has been deleted on the server.

hData in the stream is not in the proper format.

�The Work Folders URL isn't in the correct format. Check the URL and try entering it again.

hThe Work Folders URL must start with https://.

DThe argument is out of range.

PRequest redirected too many times.

pRequest attempted service discovery too many times.

�ECS_E_OPERATION_ABORTED

The Kailani operation was aborted.

xThe replica's sync state cannot be loaded from the DAL.

`The ID used for a generic share is invalid.

LA sync session cannot be created.

TThe file name extension is too long.

pEncountered an error when handling a change batch.

�Caught a StorageException when interacting with Azure storage.

�Failed creating a staged file in Azure File when processing a prepare batch request.

xCannot get the tenant ID from the authentication token.

�Cannot get an authentication token from Azure Active Directory.

|Cannot get expected claims from the authentication token.

dThe active session is changed in the service.

hCannot create active session placeholder blob.

XCannot update watermark on the replica.

�The replica is not ready to perform the required operation.

dThe requested replica property was not found.

xBehavior version for current operation is not specified

`The queue task parameter passed is invalid 

`Bad argument error for management operation

`Bad request error for management operation

dAlready exists error for management operation

\Not found error for management operation

\Internal error for management operation 

TServer error for management operation

pResult set too large error for management operation

XThe exposure status cannot be set back

\The exposure percentage value is invalid

hThe requested operation was blocked by Kailani

xA file time in the request is outside the valid range.

tResult not ready yet; the client should keep polling

$Unknown error

`4VS_VERSION_INFO��@�#@�#?�StringFileInfo�040904B0LCompanyNameMicrosoft CorporationVFileDescriptionWork Folders Resources>FileVersion6.2.9200.16384FInternalNameWorkFoldersRes.dll�.LegalCopyright� Microsoft Corporation. All rights reserved.VOriginalFilenameWorkFoldersRes.dll.mui:
ProductNameWork FoldersBProductVersion6.2.9200.16384DVarFileInfo$Translation	�PADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADDINGXXPADDINGPADD