Important: You must run the tableau-server-obliterate script from a bit command prompt. For example, run cmd. If you run the script from a bit command prompt, the script will not completely remove Tableau, and subsequent installations may fail. If the result includes "64" AMD64 for example , the command prompt is a bit prompt.
If the result includes "x86" you are running a bit prompt. For more information, see the appropriate Microsoft documentation for your versions of Windows.
A failed install attempt can leave the computer in a state that causes subsequent attempts to also fail with errors that don't seem directly related to a previous install attempt. To fix this problem, run the tableau-server-obliterate script to clean up any left over remnants of the previous install attempt and then restart the computer. For more information, see Running the tableau-server-obliterate script. If you use Control Panel to uninstall Tableau Server and then run the tableau-server-obliterate script to completely remove Tableau from your computer, the script may generate an error about the refresh-environment-variables.
This occurs because a second script called by the obliterate script was not moved to the temp directory. You can ignore this error. Tableau Server cannot install if the computer you are installing on does not meet the minimum hardware requirements. The requirements apply to all computers on which you are installing Tableau Server. For details on minimum hardware requirements, see Minimum Hardware Requirements and Recommendations for Tableau Server.
Beginning in version You cannot install or upgrade Tableau Server You may see this error message when installing a new installation, or in preparation for upgrading an existing installation:. The SSE4. To successfully install or upgrade Tableau on a VM, make sure the Processor compatibility mode is turned off. Beginning with Tableau version If your current instance of Tableau Server is communicating with Active Directory over a non-encrypted channel, upgrade will fail.
Run the following commands to allow an insecure connection on your current version of Tableau Server before you upgrade:. After upgrade completes, we recommend securing the channel and then setting this option to false. Note : By default when wgserver. If you are upgrading from version For more details on internet access requirements, see Communicating with the Internet.
When upgrading, if you run the upgrade-tsm script from the scripts. If you get this error, change to the scripts. By default the upgrade log, app-upgrade. If you attempt to initialize an additional node when upgrading Tableau Server and see this error:. This can happen for multiple reasons:. The credentials you entered are not valid or you mistyped them. The credentials must be for a user who has administrative permissions on the computer where Tableau Server was first installed.
You do not need to use the credentials of the user who created the bootstrap file but doing so will ensure you are using valid credentials. The local firewall of the computer you are trying to add is not allowing communication to the initial node. For more information, see Local firewall configuration.
In certain instances, the upgrade-tsm. The cause of this depends on what point the script stops. You can restart Tableau Server Service Manager manually to work around this issue.
For details, see the Tableau Community Link opens in a new window. If there is not enough disk space for the Tableau Server Setup program to run and do the upgrade, the installation will fail. The amount of disk space required will depend on the size of your repository database and the number and size of your extracts.
This backup file has a. After you upgrade successfully, you can safely delete this file to free up space make a copy on a computer that is not part of your Tableau Server installation in case you need the file for any reason. Do not delete this file until you have completed the upgrade and know it is working.
Create a log archive snapshot using the tsm maintenance ziplogs command. After you create the ziplogs file, save it to a safe location that is not part of your Tableau Server installation.
Clean up unnecessary files using the tsm maintenance cleanup command. For more information, see Remove Unneeded Files. Beginning with version At this point all services have been upgraded, so if this job fails, you can manually reset the search server by running the tsm maintenance reset-searchserver command. You do not need to obliterate and start over. On the initial node, open a command prompt as administrator. This must be a new command prompt because the upgrade script updates system environment for the new version.
Rebuild the search index using the tsm maintenance reset-searchserver command. In general, this is most useful for experienced server administrators and IT professionals who are comfortable with Tableau Server log files and are willing to search through them. But the feature can help in all failed upgrades because it allows you to rerun the upgrade-tsm script, and the script is run from the last successful step, saving time.
For those with experience, it may be possible to identify problems like disk space problems, or permissions issues, correct them, and rerun the upgrade. If you are upgrading to version Rerun the upgrade-tsm script. Upgrade failures are sometimes a result of timeouts during the upgrade process, and rerunning the script can allow the upgrade to get beyond intermittent or occasional timing issues.
This is also a step that is safe to do, and easy. Rerunning the script will do no harm, and at worst, the upgrade will fail again at the same point, but without needing to go through any previous steps. If your Tableau Server upgrade isn't successful when you rerun the upgrade-tsm script, and you are comfortable with Tableau Server logs, you can take these additional troubleshooting steps:. Look at the output of the script in the command window rerun the script if you no longer have the command window open.
You need to run the script in a command windows with administrator access. Useful error messages may help you identify the cause of the upgrade failure and give you some ideas for how to correct the issue. Look in the app-upgrade. Any errors that are displayed at the command line will also appear in the app-upgrade. Mac OS X already has Perl installed. Open a Terminal application in the Utilities folder of your Applications folder and run perl -v to find out which version.
This is the simplest way to install the latest version of Perl. ActiveState Perl ActiveState offers both a free community version and a commercially supported binary distribution of Perl for Win32 and Perl for Win Help is available from other Windows Perl developers on the win32 irc channel on irc. Download Strawberry Perl. Source Consider looking at App::perlbrew to help compile and manage Perl from source. Toggle navigation. However, Microsoft. NET Framework 4 changed the runtime activation policy.
The Windows PowerShell 2. Such cases are expected to be rare. Many programs that require the Windows PowerShell 2. These instructions are included for the rare situations in which you need to start the engine manually. Windows PowerShell 2. For more information, see the announcement on the PowerShell blog.
We highly, highly recommend that users not use it if they can help it. Before starting the Windows PowerShell 2. NET Framework 3. For instructions, see Installing Windows PowerShell. Systems on which Windows Management Framework 3.
0コメント