KB-1406 Tempo tabs do not populate after upgrade

Jordan Horwat — Mon, 23 Jul 2018 13:14:32 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 7/23/2018 1:14:32 PM

Symptoms

After upgrading Appian, some users have experienced the following issue after starting up their Appian instance and accessing Tempo:

Essentially, Tempo tabs do not load correctly.

Cause

The issue is with the Appian data source, where the usernames in the "usr" table did not match the usernames in the Admin Console.

Note: Usernames in Appian are case sensitive.

Action

Ensure that the username in the “usr” table name matches the username in the Admin Console. If it doesn’t, edit the table to match the Admin Console.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2017

Tags: database, admin console, users, infrastructure

KB-1406 Tempo tabs do not populate after upgrade

Parmida Borhani — Wed, 24 Jan 2018 00:54:05 GMT

Revision 8 posted to Appian Knowledge Base by Parmida Borhani on 1/24/2018 12:54:05 AM

Symptoms

After upgrading Appian, some users have experienced the following issue after starting up their Appian instance and accessing Tempo:

Essentially, Tempo tabs do not load correctly.

Cause

The issue is with the Appian data source, where the usernames in the "usr" table did not match the usernames in the Admin Console.

Note: Usernames in Appian are case sensitive.

Action

Ensure that the username in the “usr” table name matches the username in the Admin Console. If it doesn’t, edit the table to match the Admin Console.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2017

Tags: database, admin console, users

KB-1406 Tempo tabs do not populate after upgrade

Nick Vigilante — Wed, 18 Oct 2017 19:51:12 GMT

Revision 7 posted to Appian Knowledge Base by Nick Vigilante on 10/18/2017 7:51:12 PM

Symptoms

After upgrading Appian, some users have experienced the following issue after starting up their Appian instance and accessing Tempo:

Essentially, Tempo tabs do not load correctly.

Cause

The issue is with the Appian data source, where the usernames in the "usr" table did not match the usernames in the Admin Console.

Note: Usernames in Appian are case sensitive.

Action

Ensure that the username in the “usr” table name matches the username in the Admin Console.

Note: If it doesn’t edit the table to match the Admin Console.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2017

Tags: database, admin console, users

KB-1406 Tempo tabs do not populate after upgrade

Nick Vigilante — Wed, 18 Oct 2017 15:51:12 GMT

Revision 6 posted to Appian Knowledge Base by Nick Vigilante on 10/18/2017 3:51:12 PM

Symptoms

After upgrading Appian, some users have experienced the following issue after starting up their Appian instance and accessing Tempo:

Essentially, Tempo tabs do not load correctly.

Cause

The issue is with the Appian data source, where the usernames in the "usr" table did not match the usernames in the Admin Console.

Note: Usernames in Appian are case sensitive.

Action

Ensure that the username in the “usr” table name matches the username in the Admin Console.

Note: If it doesn’t edit the table to match the Admin Console.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2017

Tags: database, admin console, users

KB-XXXX Tempo tabs do not populate after upgrade

Nick Vigilante — Wed, 18 Oct 2017 15:50:43 GMT

Revision 5 posted to Appian Knowledge Base by Nick Vigilante on 10/18/2017 3:50:43 PM

Symptoms

After upgrading Appian, some users have experienced the following issue after starting up their Appian instance and accessing Tempo:

Essentially, Tempo tabs do not load correctly.

Cause

The issue is with the Appian data source, where the usernames in the "usr" table did not match the usernames in the Admin Console.

Note: Usernames in Appian are case sensitive.

Action

Ensure that the username in the “usr” table name matches the username in the Admin Console.

Note: If it doesn’t edit the table to match the Admin Console.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2017

Tags: database, admin console, users

KB-XXXX Tempo tabs do not populate after upgrade

Stephen Okala — Wed, 18 Oct 2017 14:27:11 GMT

Revision 4 posted to Appian Knowledge Base by Stephen Okala on 10/18/2017 2:27:11 PM

Symptoms

After upgrading Appian, some users have experienced the following issue after starting up their Appian instance and accessing Tempo:

Cause

The issue is with the Appian data source, where the usernames in the "usr" table did not match the usernames in the admin console.

Note: Usernames in Appian are case sensitive.

Action

Ensure that the username in the “usr” table name matches the username in the Admin Console.

Note: If it doesn’t edit the table to match the Admin Console.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2017

Tags: database, admin console, users

KB-XXXX Tempo tabs do not populate after upgrade

Stephen Okala — Wed, 18 Oct 2017 14:26:33 GMT

Revision 3 posted to Appian Knowledge Base by Stephen Okala on 10/18/2017 2:26:33 PM

Symptoms

After upgrading Appian, some users have experienced the following issue after starting up their Appian instance and accessing Tempo:

Cause

The issue is with the Appian data source, where the usernames in the "usr" table did not match the usernames in the admin console.

Note: Usernames in Appian are case sensitive.

Action

Ensure that the username in the “usr” table name matches the username in the Admin Console.

Note: If it doesn’t edit the table to match the admin console.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2017

Tags: database, admin console, users

KB-XXXX Tempo tabs do not populate after upgrade

Nick Vigilante — Tue, 17 Oct 2017 17:06:21 GMT

Revision 1 posted to Appian Knowledge Base by Nick Vigilante on 10/17/2017 5:06:21 PM

Symptoms

After upgrading Appian, some suers have experienced the following issue after starting up their Appian instance and accessing Tempo:

Cause

This article explains the cause of the issue.

If this is a product defect, use the following language:

This issue has been reported to the Appian product team. The reference number for this issue is AN-XXXXX.

Ensure the JIRA ticket number is bold.

If the ticket has been fixed, use the following language:

This issue has been addressed via AN-XXXXX in the following hotfixes/versions:

Appian X.X Hotfix Package X
Appian X.X

When logging a product defect, ensure you use the known issues tag as well as the open issues or fixed issues tag, depending if the issue is fixed or not.

Action

This section contains the steps to resolve the issue. If no action is required for this, indicate so in this section. If there is a bug with no workaround, say "No action is available at this time while the Appian product team investigates this issue."

If there is a bug with a workaround, the action should include that workaround.

Workaround

This section is optional. Workarounds typically are ways for a customer to correct their issue at some technical debt (not a complete solution or requires extra work at the cost of not upgrading).

Affected Versions

This section will list any specific configurations that this article applies to. Some examples are as follows:

This article applies to all versions of Appian.

This article applies to Appian 16.2 and later.

This article applies to Appian 17.1 and earlier.

This article applies to Appian 17.1 and 17.2.

This article applies to Appian 16.1, 16.2, and 16.3.

You can also include additional configurations, such as "using JBoss EAP as an application server", "using Internet Explorer 11 as a web browser", or "using SQL Server as a data source".

Last Reviewed: Month YYYY

KB-XXXX Tempo tabs do not populate after upgrade

Stephen Okala — Tue, 17 Oct 2017 14:55:09 GMT

Revision 2 posted to Appian Knowledge Base by Stephen Okala on 10/17/2017 2:55:09 PM

Symptoms

After upgrading Appian, some suers have experienced the following issue after starting up their Appian instance and accessing Tempo:

Cause

The following are possible cause for this issue:

The issue is with the primary ds, where the usernames in the "usr" table did not match the usernames in the admin console.
- Note: Usernames in Appian are case sensitive Action

Action

Ensure that the username in your “usr” name matches the username in the admin console.
- Note: If it doesn’t edit the table to match the admin console

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: October 2017

Tags: database, admin console, users