Announcement

Collapse
No announcement yet.

10374 Blank FTP errors

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • 10374 Blank FTP errors

    Here, and FTP copy reports "11 errors", but the File Operation Errors window shows only 11 blank lines:


    Known issue? Any workaround? Fix planned?
    Last edited by chrisjj; 29-Jun-2009, 04:24 AM.

  • #2
    This is not a known issue.

    Did you save a copy of the FTP log? Would you be able to send it and a link to this forum post to support@scootersoftware.com ? With the log we may be able to see what errors happened or should have been present.
    Aaron P Scooter Software

    Comment


    • #3
      > This is not a known issue.

      Thanks.

      > Did you save a copy of the FTP log?

      None except the extract in the OP.

      > With the log we may be able to see what errors happened or should have been present.

      My OP log shows apparently four of the errors misreported. Is that not sufficient?

      Comment


      • #4
        Hello Chrisjj,

        Which FTP server software are you running and which version is it?
        Aaron P Scooter Software

        Comment


        • #5
          > Which FTP server software are you running and which version is it?

          I am not the one running it. It is "Mac OS X Server 10.3.9 003 - +GSSAPI".

          Comment


          • #6
            > Did you save a copy of the FTP log?

            This time

            http://img526.imageshack.us/content....7/23519131.gif

            I did.

            > Would you be able to send it and a link to this forum post to
            > support@scootersoftware.com ?

            Done.

            Comment


            • #7
              Have you changed the character encoding that's used for the FTP connection? If I had to guess, I'd say the server is using UTF-8, but BC thinks it's using one of the ANSI code pages. You can change that using the "Encoding" dropdown on the "General" tab of the FTP profile. UTF-8 is the 6th item on the list. If you've been using the wrong encoding and uploading files whose filenames contain extended characters you'll see some strange behavior, and it might not clear up unless you rename the files. Do you have local access to the Mac?
              ZoŽ P Scooter Software

              Comment


              • #8
                > If you've been using the wrong encoding and uploading files
                > whose filenames contain extended characters you'll see some strange behavior

                I expect to possibly see errors... correctly reported by BC.

                Is there any further information I can give you to help you address the BC error reporting failure?

                Comment


                • #9
                  Does changing the dropdown correct the problem? That would indicate Craig's diagnosis was correct, and would help us know what was going wrong.

                  We can't add in any additional feedback until we know what was happening.

                  Also, do you have local access to the Mac?
                  Aaron P Scooter Software

                  Comment


                  • #10
                    > Does changing the dropdown correct the problem?

                    Are you suggesting that will fix BCs faulty error reporting? I thought Craig was suggesting only that is might avod the error.

                    > Also, do you have local access to the Mac?

                    I really fail to see what the Mac server has got to do with faulty BC error reporting!

                    Comment


                    • #11
                      Please answer our questions to help track the underlying problem.

                      The empty messages are from the OS X Server returning an empty string as the error message; we will improve BC's handling of this case and report our own error when that occurs.
                      Aaron P Scooter Software

                      Comment


                      • #12
                        > Please answer our questions to help track the underlying problem.

                        Would you please first address the BC failure I am reporting?

                        > The empty messages are from the OS X Server returning an empty
                        > string as the error message

                        Uh?? Where does that log show OS X Server returning an empty string as the error message? On the only errors I see, it returns an "Invalid argument" string.

                        Comment


                        • #13
                          Chris,

                          I made the comments I did and asked the questions I did to try to solve this issue. If you want me to be more explicit: "Does changing the character encoding solve the issue?" Knowing the answer to that will help us repeat and fix the error. If you want be difficult be my guest, but I'm not going to waste my time making random changes hoping that they fix the issue if you're not willing to confirm the suspected cause in the first place.
                          ZoŽ P Scooter Software

                          Comment


                          • #14
                            > I'm not going to waste my time making random changes hoping
                            > that they fix the issue

                            That good to hear - nor am I.

                            Now, could you please tell me where in the log are these empty error messages on which the failure is being blamed?

                            Comment


                            • #15
                              Please let us know if changing the "Encoding" dropdown to UTF-8 eliminates the empty error messages.
                              Tim T Scooter Software

                              Comment

                              Working...
                              X