Hi Praveen! Can you give us the steps you went through to reach that error? Have you ever imported a site successfully before?
Also, What versions of Server? If you are running version 9.0.10 or earlier, there looks to be a similar defect that caused that error that was fixed in Tableau Server 9.0.11 - 9.0.11 | Tableau Software
Exporting a Tableau Server site using the "tabadmin exportsite" command sometimes resulted in a "commit failed" error.
I encountered the same error. Source server is ver9.3 and the target server is ver10.0. Would that be the cause of the error? Please help.
I am getting the exact error when attempt to export site. I am running 9.2. I am using the steps as per
Script and Error
D:\Tableau Server\9.2\bin>tabadmin exportsite Foundry_Operations --file N:\Temp\
-- Locked site Foundry_Operations
===== Exporting site Foundry_Operations
-- Unlocked site Foundry_Operations
*** org.springframework.orm.jpa.JpaSystemException: org.hibernate.TransactionE
xception: commit failed; nested exception is javax.persistence.PersistenceExcept
ion: org.hibernate.TransactionException: commit failed
I am getting exactly the same error. I'm using Tableau 10. Any thoughts at all?
Many thanks, Edyta
I don't know if it is possible to importsite from an older version of Tableau Server - I'm not saying it won't work, I just don't know if it will. I was unable to find any documentation stating weather it was possible or not. You may want to test it out with a fresh server install using dummy data to verify it will work. This defect was specific to an older version of Tableau Server so it is likely not the thing impacting you at the moment. You may want to contact Tableau Technical Support for further investigation.
Hope this helps!
The defect I referenced was specific to version 9.0.10 and earlier. If you are running a later version of Tableau Server, it will likely need investigation by Tableau Technical Support to determine why the import or export failed.
I think I have seen this error come up recently a few times. I think it might be a good idea to open up a support ticket to track it,
What resolved it on a similar case that i saw was changing the schema in the import. Not exactly sure how support did it, but it was done!
I was able to resolve it
In my case, when I verify the site mapping files, the file mappingsScheduleMapper have question marks (???) in target_name and target_scheduled_action_type fields on one of the line. That line corresponds to a custom schedule.
- I created a custom schedule on the target site with the same name/value of the source_name and source_scheduled_action_type fields.
- Run again the tabadmin importsite tool. There should be no question marks (???) anymore on the said file (mappingsScheduleMapper ).
That's great news! Thanks for coming back and letting us know how you fixed it!