Citrix

Produktdokumentation



Ganzes Dokument herunterladen

System Check issues

Jun. 15, 2016

The System Check step in the Configure AppDNA Environment wizard performs a number of checks on your system. The checks that are performed depend on what you are doing and how your environment is configured.

Some of the checks test for critical issues that must be fixed before you can proceed and some are warnings that it may be safe to ignore. When some checks fail, the wizard provides an option to fix them. This section explains what the wizard attempts to do if you use this option and what you can do to fix the problem yourself if there is no automatic fix or the automatic fix fails.

Current machine checks

Free disk space – Checks that the drive on which the operating system is installed has the minimum required space for a new installation. The wizard does not provide an automatic fix for this issue. If necessary, clean up the disk to free up disk space.

You can ignore this if you know that sufficient disk space is available, perhaps because you are doing an upgrade, which requires less free disk space.

AppDNA license server is running – Checks that the AppDNA license server is running. This is a critical issue. The automatic fix option attempts to start the AppDNA license server.

  • If the automatic fix fails, start the AppDNA license server manually.
  • By default, the AppDNA license server uses port 8079. If this port is already in use, you may need to configure it to use a different port. Alternatively, if the AppDNA license server has been configured to use a different port, you may need to return to the License Database step to enter the correct port number.
  • If the AppDNA license server is located on a different machine, check that you entered its machine name and port correctly in the License Database step. Check that the machine is running and the network cable is plugged in. Check whether the firewall is blocking access.
  • Check the Windows event log in the Windows Event Viewer.
  • For more information, see Licensing issues.

SQL Server checks

Roles – If you are creating a new database, the wizard checks that the user account has the sysadmin server role. For other database operations, the wizard checks that the user has the bulkadmin server role and db_owner database role.

This is a critical issue. The wizard does not provide an automatic fix for this issue. The database operation is likely to fail without the correct roles. If necessary, you can assign the roles or return to the step where you entered the database credentials and enter a different user account. If you are using Windows authentication, click Cancel to exit the wizard and then start again under a different user account.

Database collation – Checks that the collation defined for the database is Latin1_General_CI_AS. This is a critical issue. The wizard does not provide an automatic fix for this issue.

SQL Server collation – Checks that the collation defined for the SQL Server instance is Latin1_General_CI_AS. This is a critical issue. The wizard does not provide an automatic fix for this issue. If necessary, click Cancel to exit the wizard, configure the SQL Server instance to use the required collation, and then run the wizard again.

Version – This checks that the SQL Server version is one of the supported versions. This is a critical issue. The wizard does not provide an automatic fix for this issue. If necessary, click Cancel to exit the wizard, install one of the supported versions of SQL Server, and then run the wizard again.

Internet Explorer (IE) checks

JavaScript – Checks that JavaScript is enabled in Internet Explorer. This is a critical issue because JavaScript is required to view AppDNA reports.

Unencrypted forms – Checks that unencrypted forms are enabled in Internet Explorer. This is a critical issue because unencrypted forms must be enabled to view AppDNA reports.

IIS checks

These checks are performed only if you are configuring a complete installation and are using an IIS web server.

Common HTTP features – Checks that common HTTP features are enabled in IIS. This is a critical issue. The automatic fix option attempts to enable the common HTTP features. If this is successful, you need to restart your computer before continuing.

ASP .NET – Checks that ASP .NET is enabled. This is a critical issue.

IIS pipeline mode – Checks that IIS pipeline mode is set to Classic. This is a not a critical issue – you can run AppDNA without the pipeline mode set to Classic. However, it is recommended and improves performance. The automatic fix option attempts to set the IIS pipeline mode to Classic.

Idle time out – Checks that the application pool idle time-out is zero. This is a not a critical issue – you can run AppDNA without this IIS setting. However, it is recommended and improves performance. The automatic fix option attempts to set the application pool idle time-out to zero.

Ping – Checks that ping is disabled for the application pool. This is a not a critical issue – you can run AppDNA with ping enabled for the application pool. However, disabling ping is recommended and improves performance. The automatic fix option attempts to disable ping for the application pool.

AppPool recycling – Checks that recycling of the application pool is set to zero. This a not a critical issue – you can run AppDNA without this setting. However, it is recommended and improves performance. The automatic fix option attempts to set the application pool recycling to zero.

Machine name – Checks that your machine name meets the IIS requirements for a domain name.

Web site connect user is local administrator – Checks that the web site user account is a member of the local Administrators group. If necessary, return to the Web site credentials step and enter a user account that is a member of the local Administrators group.

Back to Top