Shadow copies revert button quickbooks

shadow copies revert button quickbooks

Rogue. 3. When the full scan is completed, press the "Delete" button to remove all malicious items found. You can restore lost or damaged files from Shadow Copies. 1. (Change the Startup type to Automatic & restart the computer). Reply Is there a way to get quickbooks through shadow explorer? To reset a configuration key back to its default value, use the -d option: Note: Tableau Server always attempts to create a shadow copy of a.xls file. This option​. I see some files/folders marked in red color, when I click the Change button. Why​? Can I use IDrive's sync feature to synchronize my Outlook data files or QuickBooks files? In order to avoid data loss, a copy of the file / folder is created.

Shadow copies revert button quickbooks - think, that

tsm configuration set Options

Below is a list of configuration options or keys that you can set with the command. In many cases you can find out the current value of a configuration key with the command.

This list is not intended to be an exhaustive list of Tableau Server configuration settings. It represents a subset of configuration keys that can be set by server administrators.  Finally, some keys used internally by Tableau Server do not appear in this list.

Note: Configuration keys are case-sensitive.

Basic Use of tsm configuration keys

Setting a configuration key

In some cases, you must include the option to set a configuration value for a key that has not been set before. For more information, see "Unknown key" responses.

After setting a configuration key value you must apply the pending configuration changes using . Until you do, the new value will not be used by Tableau or show up in the results of a command. You can view pending changes using . For more information, see tsm pending-changes.

Resetting a configuration key to default

To reset a configuration key back to its default value, use the option:

Viewing the current value of a configuration key

To see what a configuration key is currently set to, use the command:

In certain cases you cannot get a configuration value for a key that has not been set before. Instead the command will return an "Unknown key" response. For more information, see "Unknown key" responses.

Configuration Keys

adminviews.disabled

Default value: 

Disables access to the Tableau Administrative views. By default, access to views is enabled (this option is set to "false").

api.server.enabled

Default value: 

Allows access to the Tableau Server REST API(Link opens in a new window). By default, this functionality is enabled.

auditing.enabled

Default value: 

Allows access to the PostgreSQL (Tableau Server's own database) historical auditing tables.

backgrounder.enable_parallel_adsync

Note: Added in version 2018.3.6

Default value: 

Controls whether parallel processing of external directory group synchronization jobs is allowed when there are multiple backgrounders. By default a scheduled synchronization of external directory groups is handled serially, by a single backgrounder. Set this to to enable parallel processing on multiple backgrounder instances.

backgrounder.externalquerycachewarmup.enabled

Default value: 

Controls the caching of workbook query results after scheduled extract refresh tasks.

backgrounder.externalquerycachewarmup.view_threshold

Default vaule: 

The threshold for caching workbook query results after scheduled extract refresh tasks. The threshold is equal to the number of views that a workbook has received in the past seven days divided by the number of refreshes scheduled in the next seven days.

The following two backgrounder command options determine how long a flow task can run before the flow background task is canceled. These two commands together determine the total timeout value for flow tasks.

backgrounder.extra_timeout_in_seconds

Default value: 

The number of seconds beyond the setting in before a background task is canceled. This setting makes sure that tasks do not hold up subsequent jobs if they are stalled. The setting applies to processes listed in . 1800 seconds is 30 minutes.

backgrounder.default_timeout.run_flow

Default value:

The number of seconds for a flow run task is canceled. 14,400 seconds is 4 hours.

backgrounder.failure_threshold_for_run_prevention

Default value: 

The number of consecutive failures of a subscription, extract, or flow run job before that job is suspended. Suspending continuously failing jobs helps preserver backgrounder resources for other jobs. To disable suspension of failing background tasks, set this to .

backgrounder.log.level

Note: Added in version 2020.3.0

Default value: 

The logging level for the backgrounder process. This is dynamically configurable, so if you are only changing this you do not have to restart Tableau Server. For more information, see Change Logging Levels.

backgrounder.querylimit

Default value: 

Longest allowable time, in seconds, for completing a single extract refresh task or subscription task. 7200 seconds = 2 hours.

Note: If a background task reaches this time limit, it may continue to run for an additional several minutes while being canceled.

backgrounder.notifications_enabled

Default value: 

Controls whether extract refresh and flow run alerts are enabled for all sites on the server. By default alerts are enabled. To disable the alerts for all sites on a server, set this to .

Extract alerts can be enabled or disabled on a site basis by site administrators in site settings, or at the user level in user settings.

backgrounder.sort_jobs_by_type_schedule_boundary_heuristics_milliSeconds

Default value: 

Controls the time window that identifies backgrounder jobs which are determined to have the same scheduled start time.

The backgrounder process orders work that is scheduled at the same time to be executed by job type, running the fastest category of jobs first: Subscriptions, then Incremental Extracts, then Full Extracts.

Jobs are batched to determine which jobs are scheduled at the “same time”. A value 60,000 milliseconds (the default) indicates jobs for schedules starting within a 1 minute window should be classified in the same batch and so are ordered by type within that batch.

backgrounder.subscription_failure_threshold_for_run_prevention

Default value:

Determines the number of consecutive subscription failures that must occur before alerting for a condition is suspended. When set to the default of , alerting is suspended after 5 consecutive subscription failures. A value of will allow notification email to continue indefinitely. This threshold is server-wide, so applies to all subscriptions defined on the server.

backgrounder.subscription_image_caching

Default value: 

Controls whether backgrounder will cache images that are generated for subscriptions. Cached images do not have to be regenerated each time so caching improves subscription performance. By default image caching is enabled. To disable image caching for all sites on a server, set this to .

backgrounder.timeout_tasks

Default value: 

The list of tasks that can be canceled if they run longer than the combined values in and . The list of tasks is delimited with commas. The default list represents all the possible values for this setting.

basefilepath.backuprestore

Default value: 

The location in which the command creates the backup. This is also the location where the backup file must be when restored using the command or the command. For more information, see tsm File Paths.

basefilepath.log_archive

Default value: 

The location in which the command creates the zipped archive. For more information, see tsm File Paths.

basefilepath.site_export.exports

Default value: 

The location in which the command creates the export file. For more information, see tsm File Paths.

basefilepath.site_import.exports

Default value: 

The location in which the command expects the import file to be located. For more information, see tsm File Paths.

clustercontroller.log.level

Note: Added in version 2020.3.0

Default value: 

The logging level for Cluster Controller. This is dynamically configurable, so if you are only changing this you do not have to restart Tableau Server. For more information, see Change Logging Levels.

clustercontroller.zk_session_timeout_ms

Default value: 

The length of time, in milliseconds, that Cluster Controller will wait for the Coordination Service (ZooKeeper), before determining that failover is required.

dataAlerts.checkIntervalInMinutes

Default value: 

The frequency, in minutes, at which Tableau Server checks to determine if data-alert conditions are true.

(The server also checks whenever extracts related to data alerts are refreshed.)

dataAlerts.retryFailedAlertsAfterCheckInterval

Default value: 

Determines how often Tableau Server rechecks failing data alerts. When set to , the server rechecks failing alerts at the frequency defined by . When set to , the server rechecks failing alerts every five minutes, more quickly notifying alert recipients if data conditions have changed, but reducing server performance.

(The server also checks whenever extracts related to data alerts are refreshed.)

dataAlerts.SuspendFailureThreshold

Default value: 

Determines the number of consecutive data alert failures that must occur before alerting for a condition is suspended. When set to the default of 350, alerting is suspended after roughly two weeks of alerts. This threshold is server-wide, so applies to any data alert defined on the server.

dataserver.log.level

Note: Added in version 2020.3.0

Default value: 

The logging level for Data Server. This is dynamically configurable, so if you are only changing this you do not have to restart Tableau Server. For more information, see Change Logging Levels.

dataengine.port

Default value: 

Port that the data engine runs on.

dataserver.port

Default value: 

Port that the data server runs on.

DataServerRefreshMetadataPerSession

Default value: 

Determines whether Tableau Server will make additional queries to get updated schema data for a published data source when there have been changes in the underlying schema structure. This is disabled by default for performance reasons, and there is a delay in the display of schema changes. If you want changes in the schema of a live published data source to be reflected quickly, or if you see errors (for example, "An error occurred while communicating with the data source: Invalid column name. Statement could not be prepared.") set this to . When set to , Tableau Server makes additional queries to update the schema.

elasticserver.vmopts

The default value varies based on the amount of system memory. Use the table below to determine your default value:

System MemoryDefault Value
29 GB or less (256 MB)
30 GB to 45 GB (1 GB)
46 GB to 58 GB (2 GB)
59 GB to 100 GB (4 GB)
Greater than 100 GB (8 GB)

Controls the Elastic Server heap size. Increasing the heap size beyond the default value may improve Ask Data performance. The heap size should usually be less than half of the full machine memory. Append the letter 'k' to the value to indicate kilobytes, 'm' for megabytes, or 'g' to indicate gigabytes. As a general rule, set initial heap size () equal to the maximum heap size () to minimize garbage collections.

Here is a suggestion of how much memory to allocate, based on the number of data sources and available memory. Actual performance will vary depending on the server, the number of fields in your data sources, and other factors.

  • 1 to 100 data sources: 256 MB (minimum)
  • 100 to 500 data sources: 1 GB (recommended)
  • 500 to 1,000 data sources: 2 GB
  • 1,000 to 2,000 data sources: 4 GB
  • 2,000 to 4,000 data sources: 8 GB
  • 4,000 to 8,000 data sources: 16 GB
  • 8,000 or more data sources: 32 GB

This option was added beginning with Tableau Server version: 2019.1.

excel.shadow_copy_all_remote.enabled

Default value:

Controls whether Tableau Server creates a "shadow copy" of a shared Excel spreadsheet ( or ) that is being used as a live data source. When enabled, this option prevents Excel users from seeing a "Sharing Violation Error" and a message that the file is "currently in use." This option can have a performance impact with large Excel files. If Excel users do not need to edit the shared file, you do not need to enable this option.

Note: Tableau Server always attempts to create a shadow copy of a file. This option does not change that behavior.

This option was added beginning with Tableau Server versions: 2019.1.5, 2019.2.1.

features.ActiveMQ

Default value: 

Controls whether Tableau Server uses the Apache ActiveMQ service (Tableau Server Messaging Service) for the internal messaging mechanism.

This option was added beginning with Tableau Server version: 2019.4.

features.DesktopReporting

Default value:

Controls whether Desktop License Reporting is enabled on the server. When set to (the default), no Administrative Views related to desktop licenses are available. Set this to to enable license reporting and make license usage and expiration Administrative Views visible on the Server Status page. Note: Desktop License Reporting must be enabled on the client (Tableau Desktop) in order for information to be reported to Tableau Server.

features.MessageBusEnabled

Default value: 

Controls whether Tableau Server uses the new internal messaging mechanism.

This option was added beginning with Tableau Server version: 2019.4.

features.PasswordlessBootstrapInit

Default value: 

Controls whether Tableau Server allows embedded credentials in bootstrap files. When enabled (the default), embedded credentials are included in the bootstrap file unless you specify that they should not be included. Set this to if credentials should never be included in any bootstrap file you generate. For more information on generating bootstrap files, see tsm topology nodes get-bootstrap-file.

This option was added beginning with Tableau Server version 2019.3.

features.PasswordReset

Default value: 

Applies only to servers that use local authentication. Set to to let users reset their passwords with a "Forgot password" option on the sign-in page.

filestore.log.level

Note: Added in version 2020.3.0

Default value: 

The logging level for File Store. This is dynamically configurable, so if you are only changing this you do not have to restart Tableau Server. For more information, see Change Logging Levels.

gateway.http.cachecontrol.updated

Default value:

The Cache-Control HTTP header specifies whether the client browser should cache content sent from Tableau Server. To disable caching of Tableau Server data on the client, set this option to .

gateway.http.hsts

Default value:

The HTTP Strict Transport Security (HSTS) header forces browsers to use HTTPS on the domain where it is enabled.

gateway.http.hsts_options

Default value: 

By default, HSTS policy is set for one year (31536000 seconds). This time period specifies the amount of time in which the browser will access the server over HTTPS.

gateway.http.request_size_limit

Default value:

The maximum size (bytes) of header content that is allowed to pass through the Apache gateway on HTTP requests. Headers that exceed the value set on this option will result in browser errors, such as HTTP Error 413 (Request Entity Too Large) or authentication failures.

A low value for can result in authentication errors. Single sign-on solutions that integrate with Active Directory (SAML and Kerberos) often require large authentication tokens in HTTP headers. Be sure to test HTTP authentication scenarios before deploying into production.

We recommend setting option to the same value that you set for this option.

gateway.http.x_content_type_nosniff

Default value:

The X-Content-Type-Options response HTTP header specifies that the MIME type in the Content-Type header should not be changed by the browser. In some cases, where MIME type is not specified, a browser may attempt to determine the MIME type by evaluating the characteristics of the payload. The browser will then display the content accordingly. This process is referred to as "sniffing." Misinterpreting the MIME type can lead to security vulnerabilities. The X-Content-Type-Options HTTP header is set to 'nosniff' by default with this option.

gateway.http.x_xss_protection

Default value: 

The HTTP X-XSS-Protection response header is sent to the browser to enable cross-site scripting (XSS) protection. The X-XSS-Protection response header overrides configurations in cases where users have disabled XXS protection in the browser. The X-XSS-Protection response header is enabled by default with this option.

gateway.log.level

Note: Added in version 2020.3.0

Default value: 

The logging level for Gateway. This is dynamically configurable, so if you are only changing this you do not have to restart Tableau Server. For more information, see Change Logging Levels.

gateway.public.host

Default value: <hostname>

The name (URL) of the server, used for external access to Tableau Server. If Tableau Server is configured to work with a proxy server or external load balancer, it is the name entered in a browser address bar to reach Tableau Server. For example, if Tableau Server is reached by entering , the name for gateway.public.host is .

gateway.public.port

Default value: (if SSL)

Applies to proxy server environments only. The external port the proxy server listens on.

gateway.slow_post_protection.enabled

Default value: 

Enabling this can provide some help in protecting against slow POST (Denial-of-Service) attacks by timing out POST requests that transfer data at extremely slow rates.

Note: This will not eliminate the threat of such attacks, and could have the unintended impact of terminating slow connections.

gateway.slow_post_protection.request_read_timeout

Default value: 

When enabled by the preceding option, , this option sets the Apache httpd ReadRequestTimeout. The httpd directive is documented at Apache Module mod_reqtimeout(Link opens in a new window). The primary use of this option is as a defense the Slowloris attack. See the Wikipedia entry, Slowloris (computer security)(Link opens in a new window).

gateway.timeout

Default value: 

Longest amount of time, in seconds, that the gateway will wait for certain events before failing a request (7200 seconds = 2 hours).

gateway.trusted

Default value: IP address of proxy server machine

Applies to proxy server environments only. The IP address(es) or host name(s) of the proxy server.

gateway.trusted_hosts

Default value: Alternate names of proxy server

Applies to proxy server environments only. Any alternate host name(s) for the proxy server.

hyper.file_partition_size_limit

Default value:

When set to 0, the size is set to unlimited and will use all the disk space that is available.

This option is used to set the disk space limit for a query that spools to disk. If your disk space usage by the spool.<id>.tmp file is higher than where you need it to be for your environment, it means that queries are spooling and taking up disk space. Use this option to limit the amount of disk space that any one query can use. The spool.<id>.tmp file can be found in the temp folder of the user account running Tableau Server. You can specify this value in K(KB), M(MB), G(GB), or T(TB) units. For example, you can specify the size limit as 100G when you want to limit the disk space usage to 100 GB.

For more information about spooling see the Memory and CPU Usage section in Tableau Server Data Engine.

hyper.global_file_partition_size_limit

Default value:

When set to 0, the size is set to unlimited and will use all the disk space that is available.

This option is used to set the disk space limit for all queries that spool to disk. If your disk space usage by the spool.<id>.tmp file is higher than where you need it to be for your environment, it means that queries are spooling and taking up disk space. The spool.<id>.tmp file can be found in the temp folder of the user account running Tableau Server. Use this option to limit the amount of disk space in sum total that all queries use when spooling to disk . You can specify this value in K(KB), M(MB), G(GB), or T(TB) units. For example, you can specify the size limit as 100G when you want to limit the disk space usage to 100 GB. Tableau recommends that you start with this configuration when fine tuning your spooling limits.

For more information about spooling see the Memory and CPU Usage section in Tableau Server Data Engine.

hyper.log_queries

Default value:

When set to true, query information is logged.

By default query information is logged. If however you find that the log files are too large for the amount of disk space available, you can set it to to disable logging query information. Tableau recommends leaving this configuration set to .

hyper.log_query_cpu

Default value:

Use this setting to log how much time each query takes and the CPU usage.

hyper.log_timing

Default value: 

This setting is useful to find out more information about the queries, like compilation and parsing times. By default this setting is disabled. You can turn this by setting the value to  to collect more details about your queries. Note, however that this will increase the size of your data engine log files (\logs\hyper).

hyper.log_troublesome_query_plans

Default value: 

When set to , logs query plans of query that are identified as problematic. Queries that are either canceled, running slower than 10 seconds, or if the queries are spooling to disk fall into this category. The information in the logs can be useful to troubleshoot problematic queries. You can change the setting to if you are concerned about the size of the logs.

hyper.memory_limit

Default value: 

Controls the maximum amount of memory used by Hyper. Specify the number of bytes. Append the letter 'k' to the value to indicate kilobytes, 'm' to indicate megabytes, 'g' to indicate gigabytes, or 't' to indicate terabytes. For example, . Alternatively, specify the memory limit as a percentage of the overall available system memory. For example, .

hyper.memtracker_hard_reclaim_threshold

Default value: 

This setting only applies to Windows. Hyper keeps decompressed and decrypted parts of the extract in memory to make subsequent accesses faster. This setting controls when worker threads will start writing this data out to a disk cache to reduce memory pressure. If given as a percentage, the value is interpreted as a percentage of the overall setting. For example, . Absolute values can be specified as 'k' (kilobytes), 'm' (megabytes), 'g' (gigabytes), or ‘t’ (terabytes). For example, . The value should be larger than the threshold.

hyper.memtracker_soft_reclaim_threshold

Default value: 

This setting only applies to Windows. When interacting with a Hyper file, Hyper will write out some data for caching or persisting the data. Windows has the special behavior that it locks freshly written data into memory. To avoid swapping, we force out the data when Hyper reaches the configured limit for the reclaim threshold. When the soft reclaim threshold is reached, Hyper will try to reclaim cached data in the background to attempt to stay below the reclaim threshold. In situations where swapping would happen otherwise, triggering reclamation in Hyper can lead to a better outcome. Therefore, if your Tableau Server installation experiences a lot of swapping, this setting can be used to attempt to reduce the memory pressure.

Specify the number of bytes. Append the letter 'k' to the value to indicate kilobytes, 'm' to indicate megabytes, 'g' to indicate gigabytes, or 't' to indicate terabytes. Alternatively, specify the value as a percentage of the overall configured memory for Hyper. For example, .

hyper.network_threads

Default value: 

Controls the number of network threads used by Hyper. Specify either the number of network threads (for example, ) or specify the percentage of threads in relation to the logical core count (for example, ).

Network threads are used for accepting new connections and sending or receiving data and queries. Hyper uses asynchronous networking, so many connections can be served by a single thread. Normally, the amount of work that is done on network threads is very low. The one exception is opening databases on slow file systems, which can take a long time and block the network thread. If connection times are slow when you try to view or edit dashboards that use extracts and have not been used in a while and you frequently see “asio-continuation-slow” messages in the Hyper log and long “construct-protocol” times to Hyper in the Tableau log, try to increase this value.

hyper.objectstore_validate_checksums

Default value: 

A boolean setting that controls file integrity checks in Hyper. When set to , Hyper will check the data in an extract file when it is first accessed. This allows silent corruption and corruption that would crash Hyper to be detected. In general, it is advisable to turn this setting on except for installations with very slow disks where it could cause performance regressions.

hyper.query_total_time_limit

Default value:  (which means unlimited)

Sets an upper bound on the total thread time that can be used by individual queries in Hyper. Append 's' to the value to indicate seconds, 'min' to indicate minutes, or 'h' to indicate hours. For example, to restrict all queries to a total time usage of 1500 seconds of total thread time: .

This setting allows you to automatically control runaway queries that would otherwise use too many resources. Hyper executes queries in parallel. For example, if a query executes for 100 seconds and during this time is running on 30 threads, the total thread time would be 3000 seconds. The thread time of each query is reported in the Hyper log in the “query-end” log entries in the “total-time” field.

hyper.session_memory_limit

Default value:  (which means unlimited)

Controls the maximum memory consumption that an individual query can have. Specify the number of bytes. Append the letter 'k' to the value to indicate kilobytes, 'm' to indicate megabytes, 'g' to indicate gigabytes, or 't' to indicate terabytes. For example, . Alternatively, specify the session memory limit as a percentage of the overall available system memory. For example, .

Lowering this value can help when a query is using excessive amounts of memory and making other queries fail over a long period of time. By lowering the limit, the single big query would fail (or resort to spooling if spooling isn’t turned off) and not have a negative impact on other queries.

hyper_standalone.consistent_hashing.enabled

Default value: 

Improves the chance that the extract for a query is already cached. If the node with the extract cached cannot support additional load, you will be routed to a new node and the extract will be loaded into cache on the new node. This results in better system utilization because extracts are only loaded into memory if there is load that justifies the need.

hyper_standalone.health.enabled

Default value: 

Switches the load balancing metric from random selection to picking the Data Engine (Hyper) node based on a health score that is made of up of a combination of current Hyper activity and system resource usage. Based on these values, the load balancer will pick the node that is most capable of handling an extract query.

hyper.temp_disk_space_limit

Default value: 

Sets the upper limit of disk space at which Hyper will stop allocating space for temporary files. This setting can help to stop the hard disk from filling up with temporary files from Hyper and running out of disk space. If disk space reaches this threshold, Hyper will attempt to recover automatically without administrator intervention.

Specify it as percentage of the overall available disk space to be used. For example, . When set to 100%, all of the disk space that is available can be used.

For Data Engine to start, the configured amount of disk space must be available. If not enough disk space is available, you will see a Data Engine log entry that says, “Disk limit for temporary files has been reached. Please free up disk space on the device. See the Hyper log for more information: No space left on device”.

hyper.hard_concurrent_query_thread_limit

Default value: 150%

Use this option to set the maximum number of threads Hyper should use for running queries. Use this when you want to set a hard limit on the CPU usage. Specify either the number of threads or specify the percentage of threads in relation to the logical core count. Hyper will most likely not use more resources than are configured by this setting but Hyper background and network threads are not affected by this setting (though they tend to not be CPU intensive).

It is important to consider that this setting controls the number of concurrent queries that can be executed. So, if you decrease this setting, the chance of queries needing to wait for currently running queries to complete increases, which may affect workbook load times.

hyper.soft_concurrent_query_thread_limit

Default value: 100%

Use this option to specify the number of threads that a single query can be parallelized across if sufficiently many threads are available given the setting. Specify either the number of threads or specify the percentage of threads in relation to the logical core count.

To illustrate this, here is a simplified example:

Let's say you set this value to 10 threads, this means queries can be parallelized up to 10 threads. If only 2 queries are running, the remaining 8 threads are used to parallelize the 2 queries.

The hyper. hard_concurrent_query_thread_limit, and hyper.soft_concurrent_query_thread_limit options work together to give you some options to manage your CPU usage while maximizing available CPU resources to complete queries faster. If you don't want the Data Engine to use all the available CPU on the machine, change it to less than 100% to a percentage that is optimal for your environment. The soft limit is a way for you to limit CPU usage but allow it to go beyond the soft limit up to the hard limit if necessary.

Note: The hyper.hard_concurrent_query_thread_limit and hyper.soft_concurrent_query_thread_limit options replace hyper.num_job_worker_threads and hyper.num_task_worker_threads options available in Tableau Server versions 2018.3 and earlier, and are deprecated in the current version.

hyper.use_spooling_fallback

Default value: 

When set to , it allows spooling to disk when querying extracts exceeds set RAM usage (80% of installed RAM). In other words, it allows Hyper to execute a query using the disk if it exceeds RAM usage.

Tableau recommends that you use the default setting. You can turn this off by setting the value to  if you are concerned about disk usage. If you turn this setting off, queries that use more than 80% of installed RAM will be canceled. Spooling queries usually take substantially longer to finish.

For more information about spooling see the Memory and CPU Usage section in Tableau Server Data Engine.

install.firewall.allowedprograms.manage

Default value: 

Controls whether Tableau Server can add firewall rules. When set to (the default), Tableau Server will add new firewall rules to allow its processes to make connections through Windows Firewall. Change this to if you want to manage all firewall rules yourself and do not want Tableau Server to add new rules.

java.heap.size

Default value: 128m

Size of heap for Tomcat (repository and solr). This generally does not need to change except on advice from Tableau.

licensing.login_based_license_management.default_requested_duration_seconds

Default value:

Set to the duration (in seconds) that a user’s login-based license should last before they are prompted to activate Tableau again.

licensing.login_based_license_management.enabled

Default value:

Set to true to enable login-based license management. Set to false to disable login-based license management.

Note: In order to use login-based license management, you must activate a product key that is enabled for login-based license management. You can use the to see which product keys have login-based license management enabled.

licensing.login_based_license_management.max_requested_duration_seconds

Default value:

Set to the maximum duration (in seconds) that a user’s login-based license should last before they are prompted to activate Tableau again. The maximum value is 15552000 seconds (180 days).

maestro.app_settings.sampling_max_row_limit

Default value:

Sets the maximum number of rows for sampling data from large data sets with Tableau Prep on the web.

maestro.input.allowed_paths

Default value: ""

By default, access to any directory will be denied, and only publishing to Tableau Server with content that is included in the tflx file is allowed.

A list of allowed network directories for flow input connections. You must enable Tableau Prep Conductor to schedule flows on your Tableau Server. For more information, see Tableau Prep Conductor.

The following rules apply and must be considered when configuring this setting:

  • Paths should be accessible by Tableau Server. These paths are verified during server startup and at flow run time.

  • Network directory paths have to be absolute and cannot contain wildcards or other path traversing symbols. For example or are invalid paths and would result in all the paths as disallowed. The correct way to safelist any folder under myShare would be .

    Note: The configuration will not allow . In order to safe list both of these folders one would have safe list them as \\myhost\myShare; \\myhost\myShare1.

  • The value can be either , to allow any network directory, or a list of network directory paths, delimited by “;”.

  • No local directory paths are allowed even when the value is set to .

Important:
This command overwrites existing information and replaces it with the new information you provided. If you want to add a new location to an existing list, you must provide a list of all the locations, existing and the new one you want to add. Use the following commands to see the current list of input and output locations:


For more information and details about configuring allowed directories for flow input and output connections, see Safe list Input and Output Locations(Link opens in a new window).

maestro.output.allowed_paths

Default value: ""

By default, access to any directories will be denied.

A list of allowed network directories for flow output connections. You must enable Tableau Prep Conductor to schedule flows on your Tableau Server. For more information, see Tableau Prep Conductor.

The following rules apply and must be considered when configuring this setting:

  • Paths should be accessible by Tableau Server. These paths are verified during server startup and at flow run time.

  • Network directory paths have to be absolute and cannot contain wildcards or other path traversing symbols. For example or are invalid paths and would result in all the paths as disallowed. The correct way to safelist any folder under myShare would be .

    Note: The configuration will not allow . In order to safe list both of these folders one would have safe list them as \\myhost\myShare; \\myhost\myShare1.

  • The value can be either , to allow any network directory, or a list of network directory paths, delimited by “;”.

  • No local directory paths are allowed even when the value is set to .

  • Note: If a path is both on the flows allowed list and internal_disasslowed list, internal_disallowed takes precedence.

For more information and details about configuring allowed directories for flow input and output connections, see Safe list Input and Output Locations(Link opens in a new window).

maestro.sessionmanagement.maxConcurrentSessionPerUser

Default value:

Sets the maximum number of flow web editing sessions that a user can have open at one time.

metadata.ingestor.pipeline.throttleEventsEnable

Default value:

Controls whether indexing of new and updated content, also called eventing, is regulated across all sites on the server. By default, event throttling is turned off. To turn on event throttling, change this setting to using the following command: 

For more information about event throttling, see Enable Tableau Catalog.

metadata.ingestor.pipeline.throttleLimit

Default value:

When event throttling is enabled, this is the maximum number of new and updated content items that can be indexed during a specified period of time. Once the specified limit is reached for a specific item, indexing is deferred.

By default, the limit is set to and can't be set to lower than . You can use the following command to change the limit: 

Throttled events can be identified in the server "noninteractive" log files as .

metadata.ingestor.pipeline.throttlePeriodLength

Default value:

When event throttling is enabled, this is the period of time, in minutes, a specified maximum number of new and updated content items can be indexed. Once the specified time is reached, indexing of any additional new and updated content is deferred.

By default, the time is set to 30 minutes. You can use the following command to change the time:

metadata.query.limits.time

Default value:

This is the longest allowable time, in seconds, for a Catalog or Metadata API query to run before a timeout occurs and the query is canceled. Tableau recommends incrementally increasing the timeout limit to no more than 60 seconds using the following command:

Important: This option should be changed only if you see the error described here, Timeout limit and node limit exceeded messages. Increasing the timeout limit can utilize more CPU for longer, which can impact the performance of tasks across Tableau Server. Increasing the timeout limit can also cause higher memory usage, which can cause issues with the interactive microservices container when queries run in parallel.

metadata.query.limits.count

Default value:

This is the number of objects (which can loosely map to the number of query results) that Catalog can return before the node limit is exceeded and the query is canceled. Tableau recommends incrementally increasing the timeout limit, to no more than 100,000 using the following command:

Important: This option should be changed only if you see the error described here, Timeout limit and node limit exceeded messages. Increasing the node limit can cause higher memory usage, which can cause issues with the interactive microservices container when queries run in parallel.

metricsservices.checkIntervalInMinutes

Default value:

Controls the interval, in minutes, between refreshes for metrics that rely on live data sources. A metric refreshes when the server checks for new data via the metric’s connected view.

metricsservices.failureCountToWarnUser

Default value:

Controls the number of consecutive refresh failures that must occur before the metric owner is warned. When set to the default of 10, a metric refresh must fail 10 times in a row before the owner is sent a notification about the failure.

metricsservices.maxFailedRefreshAttempts

Default value:

Controls the number of consecutive refresh failures that must occur before a metric refresh is suspended.

mobile.deep_linking.on_prem.enabled

Default value:

Controls whether links to Tableau Server are treated as deep links by the Tableau Mobile app. When set to , links to supported content types open in the app. When set to , links open in the mobile browser. For more information see, Control deep linking for Tableau Mobile.

monitoring.dataengine.connection_timeout

Default value: 

The length of time, in milliseconds, that Cluster Controller will wait for the data engine, before determining that a connection timeout occurred. The default is 30,000 milliseconds (30 seconds).

native_api.connection.limit.<connection class>

Set parallel query limit for the specified data source (connection class). This overrides the global limit for the data source.

native_api.connection.globallimit

Default value: 

Global limit for parallel queries. Default is 16 except for Amazon Redshift which has a default of 8.

native_api.force_alternative_federation_engine

Default value: 

Override the operation restrictions when joining data from a single file connection and a single SQL database connection. Set this option to to force Tableau to process the join using the live database connection.

native_api.ProtocolTransitionLegacyFormat

Default value: 

Use the legacy name format for constrained delegation.

The name format was changed in version 10.1 to allow cross-domain protocol transition (S4U). If this causes problems with existing configurations and you don't need cross-domain protocol transition, configure Tableau Server to use the old behavior by setting this to .

native_api.InitializeQueryCacheSizeBasedOnWeights

Default value: 

Controls whether the query cache size is initialized automatically based on the amount of available system memory. The query cache consists of the logical query cache, metadata cache, and native query cache. By default, this functionality is enabled.

native_api.QueryCacheMaxAllowedMB

The maximum size of the query cache in megabytes. This value varies based on the amount of system memory. The query cache consists of the logical query cache, metadata cache, and native query cache. Use the table below to determine your default value:

System MemoryDefault Value for Tableau ServerDefault Value for Tableau Desktop
64 GB and more
From 32 GB to 64 GB
From 16 GB to 32 GB
16 GB and less

native_api.LogicalQueryCacheMaxAllowedWeight

Default value: 

The weight of logical query cache size limit in the total query cache size.

native_api.MetadataQueryCachMaxAllowedWeight

Default value: 

The weight of metadata query cache size limit in the total query cache size.

native_api.NativeQueryCacheMaxAllowedWeight

Default value: 

The weight of native query cache size limit in the total query cache size.

native_api.QueryCacheEntryMaxAllowedInPercent

Default value: 

Specifies the maximum size of query results that can be put into the query cache. It is set as the percentage of the total query cache size. For example, if the logical query cache size is 100 MB and is set to 60 percent, then only query results that are smaller than 60 MB can be put into the logical query cache.

nlp.concepts_shards_count

Default value: 1

Note: The default shard count value is sufficient for most Tableau Server installations.

Controls the number of data shards for the Elastic Search Concepts index that stores field names, field synonyms, and analytical terms. The shard count partitions the search index to reduce total index size, which may improve the performance of Ask Data's semantic parser. Adjusting the shard count is another performance enhancement measure that you can take along with increasing the heap size through .

Tableau recommends increasing the shard count by 1 for every 50 GB. To reduce the number of times you need to adjust the shard count, calculate the total index size by adding 50% to the current index. For example, if the total index size is less than 50 GB, then 1 shard is sufficient. Actual performance will vary depending on the server, the rate at which the index size grows, and other factors.

  • 0 to 50 GB: 1
  • 50 GB to 100 GB: 2
  • 100 GB to 150 GB: 3

You can use the following command to increase the Concepts index shard count from default to 2:

nlp.values_shards_count

Default value: 1

Controls the number of data shards for the Elastic Search Values index that stores values, value synonyms, and aliases. The shard count partitions the search index to reduce total index size, which may improve the performance of Ask Data's semantic parser. Adjusting the shard count is another performance enhancement measure that you can take along with increasing the heap size through .

Tableau recommends increasing the shard count by 1 for every 50 GB. To reduce the number of times you need to adjust the shard count, calculate the total index size by adding 50% to the current index. For example, if the total index size is less than 50 GB, then 1 shard is sufficient. Actual performance will vary depending on the server, the rate at which the index size grows, and other factors.

  • 0 to 50 GB: 1
  • 50 GB to 100 GB: 2
  • 100 GB to 150 GB: 3

You can use the following command to increase the Values index shard count from default to 2:

nlp.defaultNewSiteAskDataMode

Default value:

Use this option to set the initial value of the Ask Data Mode when a site is created. For more information see Enable or disable Ask Data for a site.

Valid options are (the default), , and .

This option was added beginning with Tableau Server versions: 2019.4.5, 2020.1.3.

noninteractivecontainer.vmopts

Default value:

The default value varies based on the amount of system memory. You can use the table below to determine the default value for your system.

System MemoryDefault Value
16 GB (1 GB)
32 GB (2 GB)
64 GB (4 GB)

This option controls the JVM heap size for Tableau Catalog ingestion. Because the default value scales automatically, use this option to override the default value only when absolutely necessary by modifying the  argument. For example, you can use the following command to increase the max heap size to 2 GB:

For more information, see Memory for non-interactive microservices containers.

pgsql.port

Default value: 

Port that PostgreSQL listens on.

pgsql.preferred_host

Specifies the computer name of the node with the preferred repository installed. This value is used if the or option is specified with the tsm topology failover-repository command.

Example:

Note: The is case-sensitive and must match the node name shown in the output of .

pgsql.verify_restore.port

Default value: 

Port used to verify the integrity of the PostgreSQL database. See tsm maintenance backup for more information.

recommendations.enabled

Default value: 

Controls the recommendations feature, which powers recommendations for data sources and tables (for Tableau Desktop) and recommendations for views (for Tableau Server). Recommendations are based on the popularity of content and on content used by other users determined to be similar to the current user.

recommendations.vizrecs.enabled

Default value: 

Controls recommendations for views for Tableau Server users. This option is a child of and will have no effect if the parent option is set to false. When the parent option is set to true, and this option is set to false, data sources and tables will still be recommended to Tableau Desktop users, but recommendations for views on Tableau Server will be disabled.

redis.max_memory_in_mb

Default value: 

Specifies the size in megabytes of the cache server external query cache.

refresh_token.absolute_expiry_in_seconds

Default value: 

Specifies the number of seconds for absolute expiry of refresh and access tokens. The tokens are used by clients (Tableau Mobile, Tableau Desktop, Tableau Prep, etc) for authentication to Tableau Server after initial sign-in. This configuration key also governs personal access token expiry. All refresh and access tokens are a type of OAuth token. To remove limits set to . To disable OAuth tokens, see Disable Automatic Client Authentication.

refresh_token.idle_expiry_in_seconds

Default value: 

Specifies the number of seconds when idle OAuth tokens will expire. The OAuth tokens are used by clients for authentication to Tableau Server after initial sign-in. To remove limits set to .

refresh_token.max_count_per_user

Default value: 

Specifies the maximum number of refresh tokens that can be issued for each user. If user sessions are expiring more quickly than you expect, either increase this value or set it to to entirely remove token limits.

rsync.timeout

Default value: 

Longest allowable time, in seconds, for completing file synchronization (600 seconds = 10 minutes). File synchronization occurs as part of configuring high availability, or moving the data engine and repository processes.

schedules.display_schedule_description_as_name

Default value: 

Controls whether a schedule name displays when creating a subscription or extract refresh (the default), or the "schedule frequency description" name describing the time and frequency of the schedule displays. To configure Tableau Server to display timezone-sensitive names for schedules, set this value to .

When true, the "schedule frequency description" is also displayed after the schedule name on the schedule list page.

schedules.display_schedules_in_client_timezone

Default value: 

Shows the "schedule frequency description" in the timezone of the user when true (uses the client browser timezone to calculate the "schedule frequency description").

searchserver.connection_timeout_milliseconds

Added in version 2019.1.

Default value, in milliseconds: 

Specifies, in milliseconds, the amount of time Search & Browse clients will wait to establish a connection to the Search & Browse server.

On especially busy Tableau Server computers, or if you see log errors "Failed zookeeper health check. Refusing to start SOLR." increase this value.

For more information, see Client session timeouts.

searchserver.javamemopts

Added in version 2019.1.

Default value: 

Determines JVM options for SOLR.

Of all configurable options, the maximum heap memory, configured by the parameter, is the most important when tuning the searchserver. In most cases this should be set as high as is possible, up to 24 GB, based on available physical memory on the Tableau Server computer. To change only the max heap memory, specify the entire default string but only change the value for .

Valid values for depend on available memory on the Tableau Server computer, but cannot be greater than 24 GB. For more information, see Search & Browse Max Heap Memory.

searchserver.startup.zookeeper_healthcheck_timeout_ms

Added in version 2020.1.

Default value, in milliseconds: 

Specifies, in milliseconds, the amount of time Tableau Server should wait for a successful Zookeeper health check on startup.

On especially busy Tableau Server computers, or if you see log errors "Failed zookeeper health check. Refusing to start SOLR." increase this value.

For more information, see Zookeeper connection health check timeout at startup.

searchserver.zookeeper_session_timeout_milliseconds

Default value, in milliseconds: 

Specifies, in milliseconds, the amount of time Search & Browse clients will wait to establish a connection to the Coordination Service (Zookeeper).

For more information, see Client session timeouts.

ServerExportCSVMaxRowsByCols

Added in version 2020.3.

Default value:  (no limit)

Specifies the maximum number of cells of data that can be downloaded from View Data into a CSV file. By default, there is no limit. Specify the number of cells. For example to set a limit of 3 million: 

tsm configuration set -k ServerExportCSVMaxRowsByCols -v 3000000 tsm pending-changes apply

service.jmx_enabled

Default value: 

Setting to enables JMX ports for optional monitoring and troubleshooting.

service.max_procs

Default value: <number>

Maximum number of server processes.

service.port_remapping.enabled

Default value: 

Determines whether or not Tableau Server will attempt to dynamically remap ports when the default or configured ports are unavailable. Setting to disables dynamic port remapping.

session.ipsticky

Default value: 

Makes client sessions valid only for the IP address that was used to sign in. If a request is made from an IP address different from that associated with the session token, the session token is considered invalid.

In certain circumstances—for example, when Tableau Server is being accessed by computers with known and static IP addresses—this setting can yield improved security.

Note: Consider carefully whether this setting will help your server security. This setting requires that the client have a unique IP address and an IP address that stays the same for the duration of the session. For example, different users who are behind a proxy might look like they have the same IP address (namely, the IP address of the proxy); in that case, one user might have access to another user's session. In other circumstances, users might have a dynamic IP address, and their address might change during the course of the session. If so, the user has to sign in again.

sheet_image.enabled

Default value: 

Controls whether you can get images for views with the REST API. For more information, see REST API Reference.

solr.rebuild_index_timeout

Default value: 

When Tableau Server is upgraded or when a .tsbak file is restored, the background task rebuilds the search index. This setting, in seconds, controls the timeout setting for that task (7200 seconds = 120 minutes).

ssl.ciphersuite

Default value: 

Specifies the cipher algorithms that are allowed for SSL.

For acceptable values and formatting requirements, see SSLCipherSuite(Link opens in a new window) on the Apache website.

ssl.client_certificate_login.blocklisted_signature_algorithms

Default value: 

The default value blocks certificates with the SHA-1 signing algorithm. Specifies the client signing algorithms that are blocked for SSL. To disable blocking of all signature algorithms, run this key with an empty set of quotes.

For more information about this key, see the Knowledge Base article, Mutual SSL Fails After Upgrading if Certificates Signed with SHA-1(Link opens in a new window).

storage.monitoring.email_enabled

Default value: 

Controls whether email notifications are enabled for server disk space monitoring. By default, email notifications are enabled. To enable notifications for disk space monitoring, set this to .

SMTP must be configured for notifications to be sent. For details, see Configure SMTP Setup.

storage.monitoring.warning_percent

Default value: 

Warning threshold of remaining disk space, in percentage of total disk space. If disk space falls below this threshold, a warning notification is sent.

storage.monitoring.critical_percent

Default value: 

Critical threshold of remaining disk space, in percentage of total disk space. If disk space falls below this threshold, a critical notification is sent.

storage.monitoring.email_interval_min

Default value: 

How often, in minutes, that email notifications should be sent when disk space monitoring is enabled and a threshold is crossed.

Источник: https://help.tableau.com/current/server/en-us/cli_configuration-set_tsm.htm
shadow copies revert button quickbooks

3 thoughts to “Shadow copies revert button quickbooks”

Leave a Reply

Your email address will not be published. Required fields are marked *