Export channel list (.scm) to a usb-stick; Open it with SamyCHAN, edit and save it; Import channel list (.scm) from usb-stick; Where do i find the export-option? Every SAMSUNG television (at least since the b-series) has the posibility to export the channels. The magic option is transfer channel list. This options is sometimes a bit hidden. Channellist UE32ES61001201.scm:invalid file format. Daca aveti idee la acest tip de smart TV, astept sugestii.
- Excel Cannot Open File Format Or File Extension Is Not Valid ..
- Channel List Scm Invalid File Format Download
- Download Samsung Channel Editor 0.12.0.0 Beta
SamsChannelEditor is a desktop application for editing a channel list from your Samsung TV. Now sorting channels should be much easier.
- We noticed that a file access issue occurs when the team name contains a single quote (' ). Renaming the group does not work. You must recreate. We have other file access issues but the proposed solution should work for you. I hope this will help. Update: We also notice that, in certain condition, files only avaible for Office 365 administrators.
- BitLocker-encrypted files can be copied to Azure Files. However, Azure Files does not support NTFS EFS. To copy a file over the network, you must first decrypt it. Use one of the following methods: Use the copy /d command. It allows the encrypted files to be saved as decrypted files at the destination. Set the following registry key.
|
Installation
There's no setup file, just download de binaries and execute the samschanneleditor.exe file. All files are avaiable here.
This application is written in C# so you need the .Net framework 2.0 (or newer) to be installed on your computer.
You can download here : http://msdn.microsoft.com/en-us/netframework
You can download here : http://msdn.microsoft.com/en-us/netframework
Source Code
Source code is aviable from Github and SourceForge
Bad file size error
Since version 0.9 you can define new sizes in SamsChannelEditor.exe.config. Just open with a text editor like notepad and add a new size for your file in section.
key: starts with 'fs_' and after comes the channel file name (without '-' after map) value: is a number list separated by commas. Each number specifies a possible record size.
To calculate your record size:
- change extension .scm to .zip
- Extract all files.
- Select file you are opening and look the size in file properties.
- record size is a 1000 multiple (divide your size by 1000 or 2000)
Example:
Libraries & Resources used
Developers and Collaborators
License
SamsChannelEditor is distributed under the GNU General Public License (GPL). For more information: GNU GPL.3.0
Changelog
Version 0.11
- Fixed channel names output. Names in Russian output correctly. Other languages must do so
- Channel data edit feature realized. You can edit channel name and favourites.
Version 0.10
- Applied a patch created by Andreas Winter to save sort order to file and restore after.
- Applied a patch created by Andreas Mayer to remove encrypted channels.
Version 0.9
- Moved record sizes to SamsChannelEditor.exe.config. Now are easy to add new record sizes for new models.
Version 0.8
- BUG [3468470] : Open map-SateD 144bytes length (LE37C670)
- MoveTo problems detected when out of range number is introduced.
Version 0.7
- Works on D Series
- Drag and Drop with auto scroll
- Added support for analog channels map-AirA and map-CableA
- Context menu: MoveTo
- Context menu: Renumber All
Version 0.6
- Added support for map-AstraHDPlusD (Astra Satellite Channels)
- Added support for configuration files as read-only
- Added support for SatDataBaseFile.dat (Satellite List)
- Added support for CloneInfo (TV info)
- Modified map-SateD
- Show more channel settings
Version 0.5
- Works on D Series
- Added support for map-SateD (Digital Satellite Channels)
- Added support for map-CableD (Satellite Channels?)
Version 0.4
- Added D Series Compatibility
- Code rewritted
- Only opens smc files
- Added support for editing various files inside scm
- Added support for map-CableD (Digital Cable TV Channels)
- Set channels number on fly
- Solved multiselect problem with checkboxes
Version 0.3
- User can delete channels.
Version 0.2
- Open and Save .scm files directly
- Uses #ziplib for read and update scm files
Version 0.1
- Tested in C650 series
- Open and Save map_AirD files
- Drag&Drop Channels
This article lists common problems that are related to Microsoft Azure Files when you connect from Windows clients. It also provides possible causes and resolutions for these problems. In addition to the troubleshooting steps in this article, you can also use AzFileDiagnostics to ensure that the Windows client environment has correct prerequisites. AzFileDiagnostics automates detection of most of the symptoms mentioned in this article and helps set up your environment to get optimal performance. You can also find this information in the Azure Files shares Troubleshooter that provides steps to assist you with problems connecting/mapping/mounting Azure Files shares.
Error 5 when you mount an Azure file share
When you try to mount a file share, you might receive the following error:
- System error 5 has occurred. Access is denied.
Cause 1: Unencrypted communication channel
For security reasons, connections to Azure file shares are blocked if the communication channel isn't encrypted and if the connection attempt isn't made from the same datacenter where the Azure file shares reside. Unencrypted connections within the same datacenter can also be blocked if the Secure transfer required setting is enabled on the storage account. An encrypted communication channel is provided only if the user's client OS supports SMB encryption.
Windows 8, Windows Server 2012, and later versions of each system negotiate requests that include SMB 3.0, which supports encryption.
Solution for cause 1
- Connect from a client that supports SMB encryption (Windows 8, Windows Server 2012 or later) or connect from a virtual machine in the same datacenter as the Azure storage account that is used for the Azure file share.
- Verify the Secure transfer required setting is disabled on the storage account if the client does not support SMB encryption.
Cause 2: Virtual network or firewall rules are enabled on the storage account
If virtual network (VNET) and firewall rules are configured on the storage account, network traffic will be denied access unless the client IP address or virtual network is allowed access.
Solution for cause 2
Verify virtual network and firewall rules are configured properly on the storage account. To test if virtual network or firewall rules is causing the issue, temporarily change the setting on the storage account to Allow access from all networks. To learn more, see Configure Azure Storage firewalls and virtual networks.
Cause 3: Share-level permissions are incorrect when using identity-based authentication
If users are accessing the Azure file share using Active Directory (AD) or Azure Active Directory Domain Services (Azure AD DS) authentication, access to the file share will fail with 'Access is denied' error if share-level permissions are incorrect.
Solution for cause 3
Validate that permissions are configured correctly:
- Active Directory (AD) see Assign share-level permissions to an identity.Share-level permission assignments are supported for groups and users that have been synced from the Active Directory (AD) to Azure Active Directory (AAD) using Azure AD Connect. Confirm that groups and users being assigned share-level permissions are not unsupported 'cloud-only' groups.
- Azure Active Directory Domain Services (Azure AD DS) see Assign access permissions to an identity.
Error 53, Error 67, or Error 87 when you mount or unmount an Azure file share
When you try to mount a file share from on-premises or from a different datacenter, you might receive the following errors:
- System error 53 has occurred. The network path was not found.
- System error 67 has occurred. The network name cannot be found.
- System error 87 has occurred. The parameter is incorrect.
Cause 1: Port 445 is blocked
System error 53 or system error 67 can occur if port 445 outbound communication to an Azure Files datacenter is blocked. To see the summary of ISPs that allow or disallow access from port 445, go to TechNet.
To check if your firewall or ISP is blocking port 445, use the AzFileDiagnostics tool or
Test-NetConnection
cmdlet.To use the
Test-NetConnection
cmdlet, the Azure PowerShell module must be installed, see Install Azure PowerShell module for more information. Remember to replace <your-storage-account-name>
and <your-resource-group-name>
with the relevant names for your storage account.If the connection was successful, you should see the following output:
Note
The above command returns the current IP address of the storage account. This IP address is not guaranteed to remain the same, and may change at any time. Do not hardcode this IP address into any scripts, or into a firewall configuration.
Solution for cause 1
Solution 1 - Use Azure File Sync
Azure File Sync can transform your on-premises Windows Server into a quick cache of your Azure file share. You can use any protocol that's available on Windows Server to access your data locally, including SMB, NFS, and FTPS. Azure File Sync works over port 443 and can thus be used as a workaround to access Azure Files from clients that have port 445 blocked. Learn how to setup Azure File Sync.
Solution 2 - Use VPN
By Setting up a VPN to your specific Storage Account, the traffic will go through a secure tunnel as opposed to over the internet. Follow the instructions to setup VPN to access Azure Files from Windows.
Solution 3 - Unblock port 445 with help of your ISP/IT Admin
Work with your IT department or ISP to open port 445 outbound to Azure IP ranges.
Solution 4 - Use REST API based tools like Storage Explorer/Powershell
Azure Files also supports REST in addition to SMB. REST access works over port 443 (standard tcp). There are various tools that are written using REST API which enable rich UI experience. See full list on icomjapan.com. Storage Explorer is one of them. Download and Install Storage Explorer and connect to your file share backed by Azure Files. You can also use PowerShell which also user REST API.
Cause 2: NTLMv1 is enabled
System error 53 or system error 87 can occur if NTLMv1 communication is enabled on the client. Azure Files supports only NTLMv2 authentication. Having NTLMv1 enabled creates a less-secure client. Therefore, communication is blocked for Azure Files.
To determine whether this is the cause of the error, verify that the following registry subkey is set to a value of 3:
HKLMSYSTEMCurrentControlSetControlLsa > LmCompatibilityLevel
For more information, see the LmCompatibilityLevel topic on TechNet.
Excel Cannot Open File Format Or File Extension Is Not Valid ..
Solution for cause 2
Revert the LmCompatibilityLevel value to the default value of 3 in the following registry subkey:
HKLMSYSTEMCurrentControlSetControlLsa
Error 1816 - Not enough quota is available to process this command
Cause
Error 1816 happens when you reach the upper limit of concurrent open handles that are allowed for a file or directory on the Azure file share. For more information, see Azure Files scale targets.
Solution
Reduce the number of concurrent open handles by closing some handles, and then retry. For more information, see Microsoft Azure Storage performance and scalability checklist.
To view open handles for a file share, directory or file, use the Get-AzStorageFileHandle PowerShell cmdlet.
To close open handles for a file share, directory or file, use the Close-AzStorageFileHandle PowerShell cmdlet.
Note
The Get-AzStorageFileHandle and Close-AzStorageFileHandle cmdlets are included in Az PowerShell module version 2.4 or later. To install the latest Az PowerShell module, see Install the Azure PowerShell module.
Error 'No access' when you try to access or delete an Azure File Share
When you try to access or delete an Azure file share in the portal, you may receive the following error:
No access
Error code: 403
Error code: 403
Cause 1: Virtual network or firewall rules are enabled on the storage account
Solution for cause 1
Verify virtual network and firewall rules are configured properly on the storage account. To test if virtual network or firewall rules is causing the issue, temporarily change the setting on the storage account to Allow access from all networks. To learn more, see Configure Azure Storage firewalls and virtual networks.
Cause 2: Your user account does not have access to the storage account
Solution for cause 2
Browse to the storage account where the Azure file share is located, click Access control (IAM) and verify your user account has access to the storage account. To learn more, see How to secure your storage account with Role-Based Access Control (RBAC).
Unable to delete a file or directory in an Azure file share
When you try to delete a file, you may receive the following error:
The specified resource is marked for deletion by an SMB client.
Cause
This issue typically occurs if the file or directory has an open handle.
Solution
If the SMB clients have closed all open handles and the issue continues to occur, perform the following:
- Use the Get-AzStorageFileHandle PowerShell cmdlet to view open handles.
- Use the Close-AzStorageFileHandle PowerShell cmdlet to close open handles.
Note
The Get-AzStorageFileHandle and Close-AzStorageFileHandle cmdlets are included in Az PowerShell module version 2.4 or later. To install the latest Az PowerShell module, see Install the Azure PowerShell module.
Slow file copying to and from Azure Files in Windows
You might see slow performance when you try to transfer files to the Azure File service.
- If you don't have a specific minimum I/O size requirement, we recommend that you use 1 MiB as the I/O size for optimal performance.
- If you know the final size of a file that you are extending with writes, and your software doesn't have compatibility problems when the unwritten tail on the file contains zeros, then set the file size in advance instead of making every write an extending write.
- Use the right copy method:
- Use AzCopy for any transfer between two file shares.
- Use Robocopy between file shares on an on-premises computer.
Considerations for Windows 8.1 or Windows Server 2012 R2
For clients that are running Windows 8.1 or Windows Server 2012 R2, make sure that the KB3114025 hotfix is installed. This hotfix improves the performance of create and close handles.
You can run the following script to check whether the hotfix has been installed:
reg query HKLMSYSTEMCurrentControlSetServicesLanmanWorkstationParametersPolicies
Channel List Scm Invalid File Format Download
If hotfix is installed, the following output is displayed:
HKEY_Local_MACHINESYSTEMCurrentControlSetServicesLanmanWorkstationParametersPolicies {96c345ef-3cac-477b-8fcd-bea1a564241c} REG_DWORD 0x1
Note
Windows Server 2012 R2 images in Azure Marketplace have hotfix KB3114025 installed by default, starting in December 2015.
No folder with a drive letter in 'My Computer' or 'This PC'
If you map an Azure file share as an administrator by using net use, the share appears to be missing.
Cause
By default, Windows File Explorer does not run as an administrator. If you run net use from an administrative command prompt, you map the network drive as an administrator. Because mapped drives are user-centric, the user account that is logged in does not display the drives if they are mounted under a different user account.
Solution
Mount the share from a non-administrator command line. Alternatively, you can follow this TechNet topic to configure the EnableLinkedConnections registry value.
Net use command fails if the storage account contains a forward slash
Cause
The net use command interprets a forward slash (/) as a command-line option. If your user account name starts with a forward slash, the drive mapping fails.
Solution
You can use either of the following steps to work around the problem:
- Run the following PowerShell command:
New-SmbMapping -LocalPath y: -RemotePath servershare -UserName accountName -Password 'password can contain / and etc'
From a batch file, you can run the command this way:Echo new-smbMapping .. | powershell -command –
- Put double quotation marks around the key to work around this problem--unless the forward slash is the first character. If it is, either use the interactive mode and enter your password separately or regenerate your keys to get a key that doesn't start with a forward slash.
Application or service cannot access a mounted Azure Files drive
Cause
Drives are mounted per user. If your application or service is running under a different user account than the one that mounted the drive, the application will not see the drive.
Solution
Use one of the following solutions:
- Mount the drive from the same user account that contains the application. You can use a tool such as PsExec.
- Pass the storage account name and key in the user name and password parameters of the net use command.
- Use the cmdkey command to add the credentials into Credential Manager. Perform this from a command line under the service account context, either through an interactive login or by using
runas
.cmdkey /add:<storage-account-name>.file.core.windows.net /user:AZURE<storage-account-name> /pass:<storage-account-key>
- Map the share directly without using a mapped drive letter. Some applications may not reconnect to the drive letter properly, so using the full UNC path may be more reliable.
net use * storage-account-name.file.core.windows.netshare
After you follow these instructions, you might receive the following error message when you run net use for the system/network service account: 'System error 1312 has occurred. A specified logon session does not exist. It may already have been terminated.' If this occurs, make sure that the username that is passed to net use includes domain information (for example: '[storage account name].file.core.windows.net').
Error 'You are copying a file to a destination that does not support encryption'
Download Samsung Channel Editor 0.12.0.0 Beta
When a file is copied over the network, the file is decrypted on the source computer, transmitted in plaintext, and re-encrypted at the destination. However, you might see the following error when you're trying to copy an encrypted file: 'You are copying the file to a destination that does not support encryption.'
Cause
This problem can occur if you are using Encrypting File System (EFS). BitLocker-encrypted files can be copied to Azure Files. However, Azure Files does not support NTFS EFS.
Workaround
To copy a file over the network, you must first decrypt it. Use one of the following methods:
- Use the copy /d command. It allows the encrypted files to be saved as decrypted files at the destination.
- Set the following registry key:
- Path = HKLMSoftwarePoliciesMicrosoftWindowsSystem
- Value type = DWORD
- Name = CopyFileAllowDecryptedRemoteDestination
- Value = 1
Be aware that setting the registry key affects all copy operations that are made to network shares.
Slow enumeration of files and folders
Cause
This problem can occur if there is no enough cache on client machine for large directories.
Solution
To resolve this problem, adjusting the DirectoryCacheEntrySizeMax registry value to allow caching of larger directory listings in the client machine:
- Location: HKLMSystemCCSServicesLanmanworkstationParameters
- Value mane: DirectoryCacheEntrySizeMax
- Value type:DWORD
For example, you can set it to 0x100000 and see if the performance become better.
Error AadDsTenantNotFound in enabling Azure Active Directory Domain Service (Azure AD DS) authentication for Azure Files 'Unable to locate active tenants with tenant ID aad-tenant-id'
Cause
Error AadDsTenantNotFound happens when you try to enable Azure Active Directory Domain Services (Azure AD DS) authentication on Azure Files on a storage account where Azure AD Domain Service(Azure AD DS) is not created on the Azure AD tenant of the associated subscription.
Solution
Enable Azure AD DS on the Azure AD tenant of the subscription that your storage account is deployed to. You need administrator privileges of the Azure AD tenant to create a managed domain. If you aren't the administrator of the Azure AD tenant, contact the administrator and follow the step-by-step guidance to Enable Azure Active Directory Domain Services using the Azure portal.
Error ConditionHeadersNotSupported from a Web Application using Azure Files from Browser
The ConditionHeadersNotSupported error occurs when accessing content hosted in Azure Files through an application that makes use of conditional headers, such as a web browser, access fails. The error states that condition headers are not supported.
Cause
Conditional headers are not yet supported. Applications implementing them will need to request the full file every time the file is accessed.
Workaround
When a new file is uploaded, the cache-control property by default is “no-cache”. To force the application to request the file every time, the file's cache-control property needs to be updated from “no-cache” to “no-cache, no-store, must-revalidate”. This can be achieved using Azure Storage Explorer.
Unable to mount Azure Files with AD credentials
Self diagnostics steps
First, make sure that you have followed through all four steps to enable Azure Files AD Authentication.
Second, try mounting Azure file share with storage account key. If you failed to mount, download AzFileDiagnostics.ps1 to help you validate the client running environment, detect the incompatible client configuration which would cause access failure for Azure Files, gives prescriptive guidance on self-fix and, collect the diagnostics traces.
Third, you can run the Debug-AzStorageAccountAuth cmdlet to conduct a set of basic checks on your AD configuration with the logged on AD user. This cmdlet is supported on AzFilesHybrid v0.1.2+ version. You need to run this cmdlet with an AD user that has owner permission on the target storage account.
The cmdlet performs these checks below in sequence and provides guidance for failures:
- CheckADObjectPasswordIsCorrect: Ensure that the password configured on the AD identity that represents the storage account is matching that of the storage account kerb1 or kerb2 key. If the password is incorrect, you can run Update-AzStorageAccountADObjectPassword to reset the password.
- CheckADObject: Confirm that there is an object in the Active Directory that represents the storage account and has the correct SPN (service principal name). If the SPN isn't correctly setup, please run the Set-AD cmdlet returned in the debug cmdlet to configure the SPN.
- CheckDomainJoined: Validate that the client machine is domain joined to AD. If your machine is not domain joined to AD, please refer to this article for domain join instruction.
- CheckPort445Connectivity: Check that Port 445 is opened for SMB connection. If the required Port is not open, please refer to the troubleshooting tool AzFileDiagnostics.ps1 for connectivity issues with Azure Files.
- CheckSidHasAadUser: Check that the logged on AD user is synced to Azure AD. If you want to look up whether a specific AD user is synchronized to Azure AD, you can specify the -UserName and -Domain in the input parameters.
- CheckGetKerberosTicket: Attempt to get a Kerberos ticket to connect to the storage account. If there isn't a valid Kerberos token, run the klist get cifs/storage-account-name.file.core.windows.net cmdlet and examine the error code to root-cause the ticket retrieval failure.
- CheckStorageAccountDomainJoined: Check if the AD authentication has been enabled and the account's AD properties are populated. If not, refer to the instruction here to enable AD DS authentication on Azure Files.
Unable to configure directory/file level permissions (Windows ACLs) with Windows File Explorer
Symptom
You may experience either symptoms described below when trying to configure Windows ACLs with File Explorer on a mounted file share:
- After you click on Edit permission under the Security tab, the Permission wizard does not load.
- When you try to select a new user or group, the domain location does not display the right AD DS domain.
Solution
We recommend you to use icacls tool to configure the directory/file level permissions as a workaround.
Errors when running Join-AzStorageAccountForAuth cmdlet
Error: 'The directory service was unable to allocate a relative identifier'
This error may occur if a domain controller that holds the RID Master FSMO role is unavailable or was removed from the domain and restored from backup. Confirm that all Domain Controllers are running and available.
Error: 'Cannot bind positional parameters because no names were given'
This error is most likely triggered by a syntax error in the Join-AzStorageAccountforAuth command. Check the command for misspellings or syntax errors and verify that the latest version of the AzFilesHybrid module (https://github.com/Azure-Samples/azure-files-samples/releases) is installed.
Need help? Contact support.
If you still need help, contact support to get your problem resolved quickly.