11 Replies Latest reply on Apr 22, 2015 2:43 AM by Willem Botha

How to isolate an error in creating an extract?

Jeremy Becker Jun 4, 2014 9:35 AM

Are you able to take the details logged in the backgrounder log files to work backwards and discover exactly what's causing an extract to fail?

I tried to convert a live data connection to an extract last evening. During the run to create the extract an error is being logged that fails the process. The error, while descriptive, falls short of telling me exactly where the problem lies. I'm posting it below (I think. These things are fun to read).

C:\ProgramData\Tableau\Tableau Server\data\tabsvc\vizqlserver\Logs\backgrounder_8250_2014_06_04_04_31_29.txt

What I'm trying to determine is, where is this going wrong and how can I troubleshoot?

2014-06-04 07:05:02.463 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 2b5c: Starting AsyncTask for SessionID: F28271A825B04237A584FDD8582BA629-0:0.

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 2b5c: HTTPRequestor::DoWork::HTTPException 500 http://localhost:80/dataserver/d/Fact_Quote/82B4539823084CEB97E5FD3BCEC1C4A8-0:0/prepare.xml <?xml version='1.0' encoding='utf-8' ?>

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 2b5c:

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 2b5c: <exception name='class DataSourceException' type='Unknown'>

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 2b5c: <error>DataServer::Dispatch</error>

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 2b5c: <details>

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 2b5c: <detail>[Microsoft][SQL Server Native Client 10.0][SQL Server]Arithmetic overflow error converting expression to data type int.
</detail>

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 2b5c: <detail>prepare.xml</detail>

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 2b5c: </details>

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 2b5c: </exception>

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 2b5c:

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 2b5c: WorkItemSetComplete: 0x000000001115df10

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500: An unknown error related to remote content was detected (500)

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500:

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500: HTTPRequestor: rethrow exception

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500: DataSourceException: type=Unknown

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500: DataSourceException: type=Disconnect

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500: throw DataSourceException (type=Disconnect): [Microsoft][SQL Server Native Client 10.0][SQL Server]Arithmetic overflow error converting expression to data type int.

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500: prepare.xml

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500: class DataSourceException

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500:

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500: Removing path: C:\ProgramData\Tableau\Tableau Server\data\tabsvc\temp\TableauTemp\0xht3j20ajfdrb12a2gg40wg2zh9.tmp

2014-06-04 07:05:17.954 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500: Removing path: C:\ProgramData\Tableau\Tableau Server\data\tabsvc\temp\TableauTemp\1ihyink1du49ku1dvyqzs11drz0x.tmp

2014-06-04 07:05:17.970 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500: [Count] Query returned 0 records from the cache (Q128).

2014-06-04 07:05:17.970 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500: WorkItemCreate: 0x000000000cb428e0, 0x000000001115d890

2014-06-04 07:05:17.970 (,,F28271A825B04237A584FDD8582BA629-0:0,-) 1500: AsyncTaskSvcExecute: 0x000000001115d890

1. Re: How to isolate an error in creating an extract?

Tom W Jun 4, 2014 9:40 AM (in response to Jeremy Becker)

I find it easiest to read from the bottom up (given that the error is likely to have occurred towards the end of the log).

This one was pretty easy to find;
throw DataSourceException (type=Disconnect): [Microsoft][SQL Server Native Client 10.0][SQL Server]Arithmetic overflow error converting expression to data type int.

Tableau can only provide details the database provides it back. That error there is the extent of what MS SQL has provided.

Is your connecting within Tableau custom SQL, views/tables or a stored procedure?
Like Show 0 Likes(0)

Actions
2. Re: How to isolate an error in creating an extract?

Jeremy Becker Jun 4, 2014 9:44 AM (in response to Tom W)

I'm using a custom SQL connection there, for sure. This must be a
discrepancy in converting to a Tableau Extract, right? I'm not seeing this
error when I use a live connection.

Ideas?

--
Jeremy Becker
Data Warehouse and BI Tech Lead

Clean Power Finance

(t) 866.525.2123 x4938, (m) 415.726.2556
www.cleanpowerfinance.com

This email and its attachments may contain private and confidential
material, and therefore should not be reviewed, copied or distributed by
others without permission. If you are not the intended recipient, please
alert the sender immediately and delete the original.

On Wed, Jun 4, 2014 at 9:40 AM, Tom W <tableaucommunity@tableausoftware.com>
Like Show 0 Likes(0)

Actions
3. Re: How to isolate an error in creating an extract?

Tom W Jun 4, 2014 9:52 AM (in response to Jeremy Becker)

The same SQL when executed through Management Studio runs OK?

If that's the case, have you converted any dimensions within tableau to measures? Or created a calculated field which converts a string to an INT?
Like Show 0 Likes(0)

Actions
4. Re: How to isolate an error in creating an extract?

Jeremy Becker Jun 5, 2014 10:06 AM (in response to Tom W)

Thanks Tom, that's a great idea and yes I've several such fields. I guess
I'm just curious why it doesn't fail in the live connection but when I try
to create the extract it gives me a headache. I'll investigate the
calculated fields in question and see what I can do with them.

--
Jeremy Becker
Data Warehouse and BI Tech Lead

Clean Power Finance

(t) 866.525.2123 x4938, (m) 415.726.2556
www.cleanpowerfinance.com

This email and its attachments may contain private and confidential
material, and therefore should not be reviewed, copied or distributed by
others without permission. If you are not the intended recipient, please
alert the sender immediately and delete the original.

On Wed, Jun 4, 2014 at 9:53 AM, Tom W <tableaucommunity@tableausoftware.com>
Like Show 0 Likes(0)

Actions
5. Re: How to isolate an error in creating an extract?

Tom W Jun 5, 2014 10:36 AM (in response to Jeremy Becker)

I ran into a similar problem earlier in the year when I was starting out here - Calculated field behaviour - sent to the DB?

If you're doing a conversion in a calculated field which is forcing the row level calculation back into the database, this is where your problem lies and this is why you can't reconcile the behavior between Tableau and SQL Server.
If you really want to prove this is the case, you could run a trace while you're performing the extract or use Tableau Performance Manager to see the generated SQL.
Like Show 0 Likes(0)

Actions
6. Re: How to isolate an error in creating an extract?

Robert Sinclair Dec 16, 2014 11:02 AM (in response to Tom W)

What if I am able to generate the extracts with no problems, but only receive the error ( An unknown error related to the remote content was detected (500)) when attempting to publish the workbook to Tableau Server>
Like Show 0 Likes(0)

Actions
7. Re: How to isolate an error in creating an extract?

Tom W Dec 16, 2014 11:47 AM (in response to Robert Sinclair)

I'm not really sure it's related to the solve above Robert.
I think your best bet would be to create a separate thread but I would highly suggest contacting Tableau support in the first instance.
Like Show 0 Likes(0)

Actions
8. Re: How to isolate an error in creating an extract?

Robert Sinclair Dec 16, 2014 11:52 AM (in response to Tom W)

Thanks, that's what I'll do.

On Tue, Dec 16, 2014 at 1:48 PM, Tom W <tableaucommunity@tableausoftware.com
Like Show 0 Likes(0)

Actions
9. Re: How to isolate an error in creating an extract?

Willem Botha Apr 10, 2015 6:49 AM (in response to Robert Sinclair)

Hi Robert,

Having a similar problem to yours, did you get it solved?

Thanks,
Willem
Like Show 0 Likes(0)

Actions
10. Re: How to isolate an error in creating an extract?

Robert Sinclair Apr 10, 2015 7:48 AM (in response to Willem Botha)

Hi Willem -

I never did run down the source of the problem, although it only seemed to effect workbooks with numerous linked tables. That said, we have found that rebooting the "Server" and the local box using desktop to publish from corrects the problem - at least in my instance. (it has worked in correcting the same issue in two separate workbooks)

On a side note. I was experiencing another query-related error that was fixed in version 9.0 (just released). Furthermore, I have yet to experience the 500 error since upgrading. I don't know if it's possible to upgrade in your environment, but is so you may wish to try that first. Rebooting the server is a pain.

All the best,
Robert
Like Show 0 Likes(0)

Actions
11. Re: How to isolate an error in creating an extract?

Willem Botha Apr 22, 2015 2:43 AM (in response to Willem Botha)

Turns out we were just running out of space. I'd have thought that would be a *known* error.

Thanks for the recommendations though, we'll hopefully be running v9 soon!
Like Show 0 Likes(0)

Actions