How to troubleshoot installation issues¶

Introduction¶

This page provides some App Builder Windows installation troubleshooting tips.

Auto-starting¶

See Troubleshoot auto start behavior.

App Builder fails to start with a 500 error that indicates a configuration section is locked¶

Ensure that the ASP.NET 4.5 feature is installed. It is located under Web Server IIS → Web Server → Application Development.

App Builder starts up but doesn't create any databases on the SQL Server¶

Ensure that the connection file is named correctly. In particular, make sure the extension is .xml and not .txt.

Cannot upload license file¶

Get "An unknown error occurred." Detailed message includes "405 POST Method not allow". Or "Failed to deserialize license (d3fc6d4e835e)" error message.**

Uninstall or disable WebDAV on IIS, as it can interfere with App Builder. If WebDAV is required, contact Jitterbit support.

"Name not found" when granting application pool user permission to data directory¶

The Windows Server 2008 permissions editor is not able to find application pool identities. Administrators can use the command line instead. Start by launching the command prompt as an administrator. Switch to the installation root directory, e.g. C:\inetpub\wwwroot\AppBuilder, then run the following commands:

ICACLS data /grant "IIS AppPool\AppBuilder":F
ICACLS keys /grant "IIS AppPool\AppBuilder":F
ICACLS logs /grant "IIS AppPool\AppBuilder":F