KB-1829 Export SQL to Excel Smart Service fails with "The following error was raised by the Export to Excel function: null" message

Jordan Horwat — Thu, 03 Jan 2019 16:18:55 GMT

Current Revision posted to Appian Knowledge Base by Jordan Horwat on 1/3/2019 4:18:55 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading to 18.3, the Export SQL to Excel Smart Service which is a part of the Excel Tools Shared Component throws the error below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

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

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: January 2019

Tags: administration, smart-service, plug-ins, integration, Export, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Jordan Horwat — Thu, 03 Jan 2019 11:13:34 GMT

Revision 19 posted to Appian Knowledge Base by Jordan Horwat on 1/3/2019 11:13:34 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading to 18.3, the Export SQL to Excel Smart Service which is a part of the Excel Tools Shared Component throws the error below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

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

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to Appian 18.3 and later.

Last Reviewed: January 2019

Tags: administration, smart-service, integration, shared components, Export, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Jordan Horwat — Thu, 03 Jan 2019 11:13:16 GMT

Revision 18 posted to Appian Knowledge Base by Jordan Horwat on 1/3/2019 11:13:16 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading to 18.3, the Export SQL to Excel Smart Service which is a part of the Excel Tools Shared Component throws the error below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

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

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: January 2019

Tags: administration, smart-service, integration, shared components, Export, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Thu, 03 Jan 2019 09:45:47 GMT

Revision 17 posted to Appian Knowledge Base by Iram Khan on 1/3/2019 9:45:47 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading to 18.3, the Export SQL to Excel Smart Service which is a part of the Excel Tools Shared Component throws the error below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

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

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: December 2018

Tags: administration, smart-service, shared components, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Tue, 18 Dec 2018 13:23:34 GMT

Revision 16 posted to Appian Knowledge Base by Iram Khan on 12/18/2018 1:23:34 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading to 18.3, the Export SQL to Excel Smart Service which is a part of the Excel Tools Shared Component throws the error below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

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

Appian 18.3 Hotfix Package E
Appian 18.4 Hotfix Package B
Appian 19.1

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: December 2018

Tags: administration, smart-service, shared components, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Tue, 18 Dec 2018 13:19:28 GMT

Revision 15 posted to Appian Knowledge Base by Iram Khan on 12/18/2018 1:19:28 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading to 18.3, the Export SQL to Excel Smart Service which is a part of the Excel Tools Shared Component throws the error below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: December 2018

Tags: administration, smart-service, shared components, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Parmida Borhani — Mon, 17 Dec 2018 23:07:33 GMT

Revision 14 posted to Appian Knowledge Base by Parmida Borhani on 12/17/2018 11:07:33 PM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading to 18.3, the Export SQL to Excel Smart Service which is a part of the Excel Tools Shared Component throws the error below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: December 2018

Tags: administration, smart-service, shared components, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Mon, 17 Dec 2018 11:00:55 GMT

Revision 13 posted to Appian Knowledge Base by Iram Khan on 12/17/2018 11:00:55 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service which is a part of the Excel Tools throws the error given below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: December 2018

Tags: administration, smart-service, shared components, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Mon, 17 Dec 2018 11:00:21 GMT

Revision 12 posted to Appian Knowledge Base by Iram Khan on 12/17/2018 11:00:21 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service which is a part of the Excel Tools throws the error given below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Check the JNDI name on the "Value" parameter in the configuration and make sure that there are no quotes(") around the JNDI name. This also applies if a constant is used for the JNDI name.

Apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: November 2018

Tags: administration, smart-service, shared components, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Mon, 17 Dec 2018 10:58:32 GMT

Revision 11 posted to Appian Knowledge Base by Iram Khan on 12/17/2018 10:58:32 AM

This issue has been resolved in an Appian hotfix/new Appian version. Please apply the latest hotfix to your Appian installation or upgrade to the latest version of Appian.

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service which is a part of the Excel Tools throws the error given below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Check the JNDI name on the "Value" parameter in the configuration and make sure that there are no quotes(") around the JNDI name. This also applies if a constant is used for the JNDI name.

Upgrade to the latest version of the Hotfix to resolve this issue.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: November 2018

Tags: administration, smart-service, shared components, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Mon, 17 Dec 2018 10:55:18 GMT

Revision 10 posted to Appian Knowledge Base by Iram Khan on 12/17/2018 10:55:18 AM

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service which is a part of the Excel Tools throws the error given below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Check the JNDI name on the "Value" parameter in the configuration and make sure that there are no quotes(") around the JNDI name. This also applies if a constant is used for the JNDI name.

Upgrade to the latest version of the Hotfix to resolve this issue.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: November 2018

Tags: administration, smart-service, shared components, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Fri, 23 Nov 2018 12:53:18 GMT

Revision 9 posted to Appian Knowledge Base by Iram Khan on 11/23/2018 12:53:18 PM

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service which is a part of the Excel Tools throws the error given below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Check the JNDI name on the "Value" parameter in the configuration and make sure that there are no quotes(") around the JNDI name. This also applies if a constant is used for the JNDI name.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: November 2018

Tags: administration, smart-service, shared components, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Fri, 23 Nov 2018 12:46:40 GMT

Revision 8 posted to Appian Knowledge Base by Iram Khan on 11/23/2018 12:46:40 PM

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service which is a part of the Excel Tools throws the error given below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Check the JNDI name on the "Value" parameter in the configuration and make sure that there are no quotes(") around the JNDI name. This also applies if a constant is used for the JNDI name.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: November 2018

Tags: administration, smart-service, shared components, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Wed, 14 Nov 2018 11:42:35 GMT

Revision 7 posted to Appian Knowledge Base by Iram Khan on 11/14/2018 11:42:35 AM

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service throws the error given below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Check the JNDI name on the "Value" parameter in the configuration and make sure that there are no quotes(") around the JNDI name. This also applies if a constant is used for the JNDI name.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: November 2018

Tags: administration, smart-service, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Wed, 14 Nov 2018 11:41:52 GMT

Revision 6 posted to Appian Knowledge Base by Iram Khan on 11/14/2018 11:41:52 AM

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service throws the error given below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Check the JNDI name on the "Value" parameter in the configuration and make sure that there are no quotes(") around the JNDI name. This also applies if a constant is used for the JNDI name.

Affected Versions

This article applies to all versions of Appian running 18.3 and later.

Last Reviewed: November 2018

Tags: smart-service, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Wed, 14 Nov 2018 11:41:11 GMT

Revision 5 posted to Appian Knowledge Base by Iram Khan on 11/14/2018 11:41:11 AM

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service throws the error given below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Check the JNDI name on the "Value" parameter in the configuration and make sure that there are no quotes(") around the JNDI name. This also applies if a constant is used for the JNDI name.

Affected Versions

This article applies to all versions of Appian running 18.3 and above.

Last Reviewed: November 2018

Tags: smart-service, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Fri, 09 Nov 2018 17:24:24 GMT

Revision 1 posted to Appian Knowledge Base by Iram Khan on 11/9/2018 5:24:24 PM

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service throws the error given below:

The following error was raised by the Export to Excel function: null

Cause

Action

Affected Versions

This article applies to all versions of Appian running 18.3 and above.

Last Reviewed: November 2018

Tags: smart-service, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Fri, 09 Nov 2018 12:32:31 GMT

Revision 4 posted to Appian Knowledge Base by Iram Khan on 11/9/2018 12:32:31 PM

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service throws the error given below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Check the JNDI name on the "Value" parameter in the configuration and make sure that there are no quotes(") around the JNDI name. This also applies if a constant is used for the JNDI name.

Affected Versions

This article applies to all versions of Appian running 18.3 and above.

Last Reviewed: November 2018

Tags: smart-service, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Fri, 09 Nov 2018 12:31:44 GMT

Revision 3 posted to Appian Knowledge Base by Iram Khan on 11/9/2018 12:31:44 PM

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service throws the error given below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Check the JNDI name on the "Value" parameter in the configuration and make sure that there are no quotes(") around the JNDI name. This also applies if a constant is used for the JNDI name.

Affected Versions

This article applies to all versions of Appian running 18.3 and above.

Last Reviewed: November 2018

Tags: smart-service, Export, 18.3, excel

DRAFT KB-XXXX Smart Service Export SQL to excel fails

Iram Khan — Fri, 09 Nov 2018 12:31:03 GMT

Revision 2 posted to Appian Knowledge Base by Iram Khan on 11/9/2018 12:31:03 PM

Symptoms

After upgrading to 18.3, the Export SQL to excel smart service throws the error given below:

The following error was raised by the Export to Excel function: null

In the tomcat-Stdout.log, the following log entry is printed:

Caused by: javax.naming.NameNotFoundException: Name ["java:/jdbc/Appian"] is not bound in this Context. Unable to find [java:/jdbc/Appian]. at org.apache.naming.NamingContext.lookup(NamingContext.java:816) ...

Cause

There is an issue with the JNDI name used in the configuration.

Action

Please follow the following steps to remediate the issue:

Check the JNDI name on the "Value" parameter in the configuration and make sure that there are no quotes(") around the JNDI name. This also applies if a constant is used for the JNDI name.

Affected Versions

This article applies to all versions of Appian running 18.3 and above.

Last Reviewed: November 2018

Tags: smart-service, Export, 18.3, excel