Ok. I finally figure out how to create the views data export. I see that the views all work in the views ui preview. I then try to run the views directly, www.sitename/report1. This is what happens.
First. It shows the progress bar with Export is starting. Then I get
' Building export Export has encountered an error. Please continue to the error page An HTTP error 500 occurred. /batch?id=15&op=do'
I click the link to error page. I get a blank page. So I hit the back button.
Then I get 'Export has encountered an error. Please continue to the error page An HTTP error 403 occurred. /batch?id=18&op=do'.
I can not figure out what is going on. There currently is not much data, yet. So, size should be an issue. I have it on a local development sandbox. I runs fine. Any suggestions.
Thank you,
Pam

Comments

JefferyMac-dupe’s picture

JefferyMac-dupe CreditAttribution: JefferyMac-dupe commented

I'm seeing the same issue on D7 with Views Data Export 7.x-3.0-beta2 + Views 7.x-3.0-alpha1. The error message is as follows:

An AJAX HTTP error occurred. HTTP Result Code: 500 Debugging information follows. Path: /batch?id=5&op=do StatusText: Service unavailable (with message) ResponseText: PDOException: SQLSTATE[22001]: String data, right truncated: 1406 Data too long for column 'data' at row 1: [full sql query].

I'm returning about 40 rows, and it works fine in Views preview.

needle’s picture

needle CreditAttribution: needle commented

Views Data Export stores a clone of the view for each export request. I found that for any reasonably complex views, this can be very large - or at least larger than the 64k that BLOB generally accepts. I changed the type of the data column in the views_data_export_object_cache table to MEDIUMBLOB, and everything works fine. (Update: I should add that this was for the 7.x-3.0-beta2 version)

johnv’s picture

johnv
Primary language Dutch
CreditAttribution: johnv commented

@needle, what was the original field type of field 'data'?
I already have applied #1008240: Change 'data' column to a 'big' 'text' column in my D7-system, and there the type is LONGTEXT.
[Edit: Now i read your post better, you alredy state that you change from BLOB to Medium BLOB]

Vali Hutchison’s picture

Vali Hutchison CreditAttribution: Vali Hutchison commented

@needle Thanks! I was getting the same error and this worked for me too. Changed the datatype for the data field to mediumblob and now working - at least on my initial tests. Haven't tried a big export yet.

Steven Jones’s picture

Steven Jones CreditAttribution: Steven Jones commented
Status: Active » Closed (duplicate)

Duplicate of #1008240: Change 'data' column to a 'big' 'text' column. Guess we should probably do a release...

Reno Greenleaf’s picture

Reno Greenleaf CreditAttribution: Reno Greenleaf commented
Version: 6.x-2.0-beta3 » 7.x-3.0-beta5

Turning off "Batched export" setting can help. Of course you should take care about time limits after that.

jlyon’s picture

jlyon CreditAttribution: jlyon commented

I can confirm that running
ALTER TABLE views_data_export_object_cache MODIFY COLUMN data MEDIUMBLOB; fixed this for me as well.

travismark’s picture

travismark CreditAttribution: travismark commented
Issue summary: View changes

The original property of column "data" was longtext unfortunately for me changing it to mediomblob did not solve my case...any other solution for this?

Evgeny_Yudkin’s picture

Evgeny_Yudkin CreditAttribution: Evgeny_Yudkin commented

Just now faced with this problem.
In my situation reason was in a theming download-csv link: GET-parameter "attached" is necessary, but it was accidentally removed.
It works so: Drupal renders view, then view trying to render exposed form, this form is processing and without this parameter calls reset_form() and cleans $form_state["no_redirect"] property - so after that we have drupal_redirect form() and drupal_goto() in batch - and batch error.