Skip to content

400130: Bad Request There was a problem querying the crosstab for view #1126

Open

Description

@jtsai01-bsc

Describe the bug
When a workbook's view contains no data, the export to excel would throw the following error.
400130: Bad Request
There was a problem querying the crosstab for view

Versions
Details of your environment, including:

  • Tableau Server version (or note if using Tableau Online) v.2022.1.6
  • Python version Python 3.7.4
  • TSC library version 0.23

To Reproduce
python D:\Tableau\server-client-python\samples\export.py -s http://txxxxx.mybsc.com --site "" -u svcUser --xlsx -f "\bsc\cq\Care1st\FISERV\AUTOPAY ENROLLMENT OOS\Refund.xlsx" exxxxxxx-1xxx-xxxx-xxxx-xxxxxxxxxxx

Signing in...
Server: http://txxxxxx.mybsc.com
Site:
Username: svcUser

Connected
Item found: MAPD Autopay Refund Report
Traceback (most recent call last):
File "D:\Tableau\server-client-python\samples\export.py", line 127, in
main()
File "D:\Tableau\server-client-python\samples\export.py", line 120, in main
f.writelines(getattr(item, member_name))
File "D:\Program Files\Python37\lib\site-packages\tableauserverclient\server\endpoint\views_endpoint.py", line 149, in _get_view_excel
with closing(self.get_request(url, request_object=req_options, parameters={"stream": True})) as server_response:
File "D:\Program Files\Python37\lib\site-packages\tableauserverclient\server\endpoint\endpoint.py", line 129, in get_request
parameters=parameters,
File "D:\Program Files\Python37\lib\site-packages\tableauserverclient\server\endpoint\endpoint.py", line 72, in _make_request
self._check_status(server_response, url)
File "D:\Program Files\Python37\lib\site-packages\tableauserverclient\server\endpoint\endpoint.py", line 87, in _check_status
raise ServerResponseError.from_response(server_response.content, self.parent_srv.namespace, url)
tableauserverclient.server.endpoint.exceptions.ServerResponseError:

    400130: Bad Request
            There was a problem querying the crosstab for view 'exxxxxxx-1xxx-xxxx-xxxx-xxxxxxxxxxx'.

Results
400130: Bad Request
There was a problem querying the crosstab for view 'exxxxxxx-1xxx-xxxx-xxxx-xxxxxxxxxxx'.

NOTE: Be careful not to post user names, passwords, auth tokens or any other private or sensitive information.

Activity

  1. jorwoods commented on Oct 5, 2022

    @jorwoods
    Contributor

    According to the REST API Reference, the error of 400130 is "The view ID in the URI doesn't correspond to a view available on the specified site."

    Are you sure you passed in the correct ID or that ID exists on that site?

  2. jtsai01-bsc commented on Oct 5, 2022

    @jtsai01-bsc
    Author
  3. added
    help wantedA user needs help, may be a mistake, a bug or a feature request
    on Oct 7, 2022
  4. jtsai01-bsc commented on Oct 11, 2022

    @jtsai01-bsc
    Author

    When the export view has no data,

    • the CSV output file is generated and it has size zero.
    • the Excel (xlsx) output file is not generated due to this There was a problem querying the crosstab for view 'e4b22ed2-1ddd-43ad-b836-423f843ff4dd' error.

    It'd be a crosstab query fix to avoid checking if there is no data and simply output to an Excel file with size zero.

  5. jacalata commented on Oct 15, 2022

    @jacalata
    Contributor

    Thanks for reporting this - it looks like it will need to be a server-side fix to avoid sending back the Bad Request error, so it won't be immediate but we'll get it fixed.

  6. added and removed
    help wantedA user needs help, may be a mistake, a bug or a feature request
    on Oct 15, 2022
  7. wlodi83 commented on Feb 1, 2023

    @wlodi83
    Contributor

    This is not always the case unfortunately. I have found out, that this error occurs also if CSV export returns data, but crosstab does not work at all.

    When the export view has no data,

    • the CSV output file is generated and it has size zero.
    • the Excel (xlsx) output file is not generated due to this There was a problem querying the crosstab for view 'e4b22ed2-1ddd-43ad-b836-423f843ff4dd' error.

    It'd be a crosstab query fix to avoid checking if there is no data and simply output to an Excel file with size zero.

  8. sarikatla-rga commented on Jul 11, 2024

    @sarikatla-rga

    This is not always the case unfortunately. I have found out, that this error occurs also if CSV export returns data, but crosstab does not work at all.

    When the export view has no data,

    • the CSV output file is generated and it has size zero.
    • the Excel (xlsx) output file is not generated due to this There was a problem querying the crosstab for view 'e4b22ed2-1ddd-43ad-b836-423f843ff4dd' error.

    It'd be a crosstab query fix to avoid checking if there is no data and simply output to an Excel file with size zero.

    What is the solution for this issue? We now have the same error.

  9. github-actions commented on Aug 18, 2026

    @github-actions

    This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 14 days if no further activity occurs. If this is still relevant, please comment to keep it open.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions