EducationSoftwareStrategy.com
StrategyCommunity

Knowledge Base

Product

Community

Knowledge Base

TopicsBrowse ArticlesDeveloper Zone

Product

Download SoftwareProduct DocumentationSecurity Hub

Education

Tutorial VideosSolution GalleryEducation courses

Community

GuidelinesGrandmastersEvents
x_social-icon_white.svglinkedin_social-icon_white.svg
Strategy logoCommunity

© Strategy Inc. All Rights Reserved.

LegalTerms of UsePrivacy Policy
  1. Home
  2. Topics

KB424198: The following error message appears "Encounter error when wrangling your data" when clicking on the Wrangle functionality in MicroStrategy Web 10.4


Franklin Silva

Senior Cloud Support Engineer II • MicroStrategy


This Knowledge Base article describes a non-issue in MicroStrategy Web 10.4 that occurs when clicking on the Wrangle option due to a network limitation. Additionally, it's included the resolution steps

SYMPTOM
When importing external data and clicking on the Wrangle option in Strategy Web 10.4, the following error message shows up:

ka02R000000kas6QAA_0EM440000002MwC.jpeg

 


Data Import
Encounter error when wrangling your data. Details
Http Status 500 - 
Type Exception report
​message

Information collected in Fiddler 

<!DOCTYPE html><html><head><title>Apache Tomcat/8.0.33 - Error report</title><style type="text/css">H1 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:22px;} H2 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:16px;} H3 {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;font-size:14px;} BODY {font-family:Tahoma,Arial,sans-serif;color:black;background-color:white;} B {font-family:Tahoma,Arial,sans-serif;color:white;background-color:#525D76;} P {font-family:Tahoma,Arial,sans-serif;background:white;color:black;font-size:12px;}A {color : black;}A.name {color : black;}.line {height: 1px; background-color: #525D76; border: none;}</style> </head><body><h1>HTTP Status 500 - </h1><div class="line"></div><p><b>type</b> Exception report</p><p><b>message</b> <u></u></p><p><b>description</b> <u>The server encountered an internal error that prevented it from fulfilling this request.</u></p><p><b>exception</b></p><pre>java.lang.NullPointerException 
com.Strategy.web.controller.TaskProcessor.processRequest(Unknown Source) 
com.Strategy.web.controller.TaskProcessorController.processRequest(Unknown Source) 
com.Strategy.web.servlets.TaskProcessorServlet.doGet(Unknown Source) 
com.Strategy.web.servlets.TaskProcessorServlet.doPost(Unknown Source) 
javax.servlet.http.HttpServlet.service(HttpServlet.java:648) 
javax.servlet.http.HttpServlet.service(HttpServlet.java:729) 
org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) 
</pre><p><b>note</b> <u>The full stack trace of the root cause is available in the Apache Tomcat/8.0.33 logs.</u></p><hr class="line"><h3>Apache Tomcat/8.0.33</h3></body></html>

Tomcat - localhost.date.log

Date Time SEVERE [http-nio-8080-exec-1] org.apache.catalina.core.StandardWrapperValve.invoke Servlet.service() for servlet [TaskProcessorServlet] in context with path [/w104hf3] threw exception 
java.lang.NullPointerException 
at com.Strategy.web.controller.TaskProcessor.processRequest(Unknown Source) 
at com.Strategy.web.controller.TaskProcessorController.processRequest(Unknown Source) 
at com.Strategy.web.servlets.TaskProcessorServlet.doGet(Unknown Source) 
at com.Strategy.web.servlets.TaskProcessorServlet.doPost(Unknown Source) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:648) 
at javax.servlet.http.HttpServlet.service(HttpServlet.java:729) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:292) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) 
at org.apache.tomcat.websocket.server.WsFilter.doFilter(WsFilter.java:52) 
at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:240) 
at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:207) 
at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:212) 
at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:106) 
at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:502) 
at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:141) 
at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:79) 
at org.apache.catalina.valves.AbstractAccessLogValve.invoke(AbstractAccessLogValve.java:616) 
at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:88) 
at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:522) 
at org.apache.coyote.http11.AbstractHttp11Processor.process(AbstractHttp11Processor.java:1095) 
at org.apache.coyote.AbstractProtocol$AbstractConnectionHandler.process(AbstractProtocol.java:672) 
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.doRun(NioEndpoint.java:1502) 
at org.apache.tomcat.util.net.NioEndpoint$SocketProcessor.run(NioEndpoint.java:1458) 
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 
at org.apache.tomcat.util.threads.TaskThread$WrappingRunnable.run(TaskThread.java:61) 
at java.lang.Thread.run(Thread.java:745)

CAUSE
The 3333 Refine Server port was not accessible for external incoming requests.
ACTION
Make sure the 3333 Refine Server port is accessible. It's possible to check the refine server port access by running the "nmap -A xxx.xxx.xxx.xxx/32 -p 3333" command, as shown:
Filtered 

nmap -A xxx.xxx.xxx.xxx/32 -p 3333
Starting Nmap 5.51 ( http://nmap.org ) at 2017-05-29 16:55 EDT
Nmap scan report for host.domain.com (xxx.xxx.xxx.xxx.xxx)  'ip'
Host is up (0.00010s latency).
PORT     STATE    SERVICE   VERSION
3333/tcp filtered dec-notes

Open

nmap -A xxx.xxx.xxx.xxx/32 -p 3333
Starting Nmap 5.51 ( http://nmap.org ) at 2017-xx-xx hh:mm EDT
Nmap scan report for host.domain.com (xxx.xxx.xxx.xxx.xxx)  'ip'
Host is up (0.00011s latency).
PORT     STATE SERVICE VERSION
3333/tcp open  http    Jetty httpd 9.2.9.v20150224

Further information for windows installation, refer to the Strategy Knowledge Base article KB244901: MicroStrategy 10.x Data Wrangler fails to start with the error "Encounter error when wrangling your data"
  KB424198


Comment

0 comments

Details

Knowledge Article

Published:

May 30, 2017

Last Updated:

January 4, 2019