1 2 Previous Next 24 Replies Latest reply on May 11, 2018 6:15 AM by Jeff Strauss

    TABCMD error 411 Length Required

    John Hobby

      Howdy,

       

      I have the TS 10.4 running and TabCMD 10.4.  I have a data source that i'm trying to publish using tabcmd but keep getting a 411 Length Required error.  The tabcmd can log in / out of the server just fine, it can also run the tabcmd to create a new project, give it a description.  I can publish this same datasource using desktop 10.3 / 10.4 to our production server.  But I cannot get past this stupid error.  I have rebooted the machine this is on.  Has anyone else seen this error and how do you get past it?

       

      This same script works to publish the same data source to our qa environment.

       

      here's the batch file that I have setup to try and publish this datasource:

       

      rem connect to the site

      tabcmd login -s https:/my.server.com -t "MySiteName" -u %TABUserNM% -p %TABUserPW%

       

      rem publish

      tabcmd publish "\\c:\BigLongPath\Pro\Pt_v4_PC.tds" -n "Patients" -r "Default" --db-password "xxxxxxxxx" --save-db-password

       

      rem disconnect from the site

      tabcmd logout

       

      Currently baffled (I'm sure it'll be something simple)

       

      John

        • 1. Re: TABCMD error 411 Length Required
          Jeff Strauss

          hi there.  It looks like your path for the publish is using a UNC syntax.  Generally from what I've encountered, there should not be a colon in the path.  So it should look something like this instead:  \\c\BigLongPath\Pro\Pt_v4_PC.tds

          • 2. Re: TABCMD error 411 Length Required
            John Hobby

            Thanks Jeff - but that didn't work 

             

            rem publish

            tabcmd publish "\\c\BigLongPath\Pro\Pt_v4_PC.tds" -n "Allied Rehab Care Specialists Patients" -r "Default" --db-password "xxxxxxxxxxx" --save-db-password

             

            this still give the *** 411 Length Required    error when running this line.

            • 3. Re: TABCMD error 411 Length Required
              Jeff Strauss

              Are you running tabcmd on the server itself, or remote?  If it's on the server, can you try and change it to the absolute path and see if this helps?  c:\BigLongPath\Pro\Pt_v4_PC.tds

               

              If tabcmd is remote, then you need to setup a share to get the UNC to work.

              • 4. Re: TABCMD error 411 Length Required
                John Hobby

                It's from one of our remote machines that I do all the builds on, so, it's not running on the production server.  Do you have any helpful links for setting up the share to unc for tabcmd or is that just normal networking setup?

                • 6. Re: TABCMD error 411 Length Required
                  John Hobby

                  Thanks Jeff - I'll work with my networking team to see if there are some ports that need to be open to allow for tabcmd to cross.  I'll flag your answer above as correct in hopes that the UNC will resolve the issue    if not, i'll be back and flag this message again.

                  • 7. Re: TABCMD error 411 Length Required
                    John Hobby

                    So, I don't think it's the UNC path or even a port issue.  the tabcmd works fine from the remote server to the prod server to allow the 'login' / 'create' functions.  but the 'publish' for a data source still fails with a 411 length required error.

                     

                    Other thoughts / suggestions?

                    • 8. Re: TABCMD error 411 Length Required
                      John Hobby

                      Anyone ever run into this before?

                      • 9. Re: TABCMD error 411 Length Required
                        Jeff Strauss

                        Here's a local example that I ran yesterday, and it works fine.  I was on 10.3.3 and am now on 10.5.3

                         

                        tabcmd login -s http://servername -u username -p xxxxxxxxxxxxxxxx --site sitename

                        tabcmd publish G:/Scripts/ServerAdmin/TableauAdminData/ServerReplicatedData/pds.tdsx --name "pds"

                        • 10. Re: TABCMD error 411 Length Required
                          John Hobby

                          Hey Jeff,

                           

                          Thought that was good and it would work but still getting the **411 length required error using the following:

                           

                          tabcmd publish "c:\foobar.tds" --name "jehfoo" --project "Default"

                           

                          i've tried multiple versions of c:\foobar.tds and \\c:\foobar.tds and c:/foobar.tds and all result in the same error.  I even edited the xml and checked that the extract path was the same location

                           

                          <connection class='dataengine' dbname='C:/foobar.tde' schema='Extract' tablename='Extract' update-time='05/03/2018 03:39:23 PM'>

                          • 11. Re: TABCMD error 411 Length Required
                            Jeff Strauss

                            I don't think you have to specify --project if it's going to default.

                             

                            Have you tried packaging up the tds / tde into a tdsx?  This is what my example has.  You can just go into desktop, open your tds, and then save it locally as tdsx I think under the data window.

                             

                            Is your version of tabcmd the same as the version of Tableau Server and both either 32-bit or 64-bit?

                             

                            I'm not sure what else it could possibly be, unless there was some bug that I didn't encounter with 10.4 because I jumped from 10.3 to 10.5

                            • 12. Re: TABCMD error 411 Length Required
                              John Hobby

                              I checked the version just to make sure and both are 10.4  64-bit.  I've tried publishing most everything (tds / tde / twbx / twb) - all gives the same error.  I am publishing from my qa server running tabcmd 10.4 to my prod server running 10.4.  I'm even trying to run all the same scripts on the actual box the server is installed on- - still no go.

                               

                              weird thing is the exact same script will publish to my QA server just fine and will even fire off the refresh after the extract has been published.

                               

                              I've got a case opened with support but haven't heard back from anyone yet   

                               

                              This is getting frustrating because I have over 1500 data source extracts on my prod server that all need to upgraded to a new version - I'm tired of publishing them via the desktop and need a much better way.

                              • 13. Re: TABCMD error 411 Length Required
                                Jeff Strauss

                                Sorry for your frustration.  I will continue to try and help if that's ok.  I am just a volunteer, but am interested in providing help where I can and learning root cause for such problems.

                                 

                                The one file format you didn't mention was tdsx, but that's ok, because most likely, this isn't the problem.

                                 

                                being that qa works and prod does not, you should dig into what is different.  And hopefully this will lead to root cause and resolution.   Some ideas are below, the leading ones in my mind are some kind of disk encryption / encoding or anti-virus or nexpose or traps interfering.

                                 

                                ideas:

                                disk encryption / encoding

                                anti-virus

                                different OS version

                                firewall

                                traps

                                nexpose

                                firewall

                                ssl

                                proxy

                                disk architecture

                                 

                                 

                                Or respond to this stackoverflow and see if this guy ever figured it out.  tableau - Tabcmd worksheet publish error - Stack Overflow

                                • 14. Re: TABCMD error 411 Length Required
                                  John Hobby

                                  No worries Jeff - I enjoy actually being able to get different feedback to help resolve the problem.

                                   

                                  Let me give you an update of what we found so far....

                                   

                                  We were finally successful in getting a data source to publish - however, we had to pretty much strip out a ton of the xml data from the TDS.  After removing stuff, trying, removing, trying - it finally succeeded when we removed the extract.  It looked like:

                                   

                                  <extract count='-1' enabled='true' units='records'>

                                      <connection class='dataengine' dbname='C:/foobar.tde' schema='Extract' tablename='Extract' update-time='05/03/2018 03:39:23 PM'>

                                        <relation name='Extract' table='[Extract].[Extract]' type='table' />

                                   

                                  This, however, created a LIVE connection with the TDS ... not the desired result, but hey, it published.

                                   

                                  I finally got a response to my case #03835093 411 length required error ... I just responded, so will maybe get some more info tomorrow that I can post out here if we get a resolution.

                                   

                                  We'll keep hacking away !

                                  1 2 Previous Next