error : Illegal characters in path.

The Welkin Suite Forum

error : Illegal characters in path.



error : Illegal characters in path.

  • Please log in to reply

#1

krp.sindhu

    Posted 13 Oct 2015

    Hi Team,



    While re-opening of my project from project solution or opening my existing project from "open project". I always face this issue of illegal character in the path.


    What possibly would be the issue? please suggest. It really frustrating to download project every time before starting my development.



    7 replies to this topic

    #2

    krp.sindhu

      Posted 16 Oct 2015

      Hi team,


      Is there any specific fix to solve this issue.



      #3

      irina.tykhonova

        Posted 16 Oct 2015

        Hi Krp.sindhu


        Please excuse the delay in our reply because it took us some time to reproduce your issue. Unfortunately, it didn’t work out to reproduce your issue.


        Currently, we want to understand the peculiarities of your project.


        We would highly appreciate if you provide us with the following additional information:


        1) Do you have any specific or non-Latin symbols in the names of the files/folders in your project?


        2) Do you have any specific or non-Latin symbols in the names of the metadata that you downloaded to the Welkin Suite?


        3) Please, could you provide us with the path to your solution? Or you can try to create a project in a folder that definitely doesn't have non-Latin symbols - for example somewhere in the root of the C drive just.


        All these details would  be helpful for us.


        Thank you,

        Irina



        #4

        paynecrl97

          Posted 14 Jun 2016

          I too get this issue.


          I can confirm that I checked and could not see any non-latin characters in any file paths or file/ object names.


          Is there a way to enable debug logging, so that I can check to see if there are any clues in that?



          #5

          kate.dulko

            Posted 15 Jun 2016

            Hi,


            Thank you for your investigation and answer.


            Currently, there is no way to enable debug logging. 

            We have some ideas what can be the reason for this issue. 

            Our developers will work on them.


            I'll keep you updated when the issue will be resolved.


            Regards,

            Kate


            Kate Dulko
            Customer Relations

            The Welkin Suite

            twitter: @KateDulko
            skype id: d_katerina
            e-mail: kate.dulko@welkinsuite.com

             

              


            #6

            bbowers

              Posted 14 Jun 2017

              I'm having the same issue.  I am using periods in the file path, but no non-Latin characters.  I can open and edit most project files, but I can't create a new Anonymous Apex file.



              #7

              bbowers

                Posted 14 Jun 2017

                UPDATE: I can build/push code changes from my local workspace to my SF instance, but cannot pull files down from my SF org--which is strange, since I pulled the entire project from SF without any changes to the directory names in the file path.



                #8

                kate.dulko

                  Posted 15 Jun 2017

                  Hi Brent,


                  Thank you for sharing the issue you are faced with us.


                  I kindly ask you to send us a bug report with attached log files directly from the IDE right after the issue would be reproduced. This option is present in the menu Help -> Report a Bug. Also, may I please ask you to write the full path of your project in the bug report? You can easily get it using the option 'Copy full Path' by right click on the name of any opened file in the code editor.

                  Also, can you please tell me what name do you use for your new Anonymous Apex file? Is it possible to create the file using the default name which is provided by the IDE?

                  In addition, we will appreciate if you can provide us with a screenshot of the error.


                  Can you also tell me, if pulling of files from your Salesforce Org fails with the same error?


                  All this information will help us to find the reason for the issue, and will have an ability to solve it.


                  Thank you greatly,

                  Kate



                  Kate Dulko
                  Customer Relations

                  The Welkin Suite

                  twitter: @KateDulko
                  skype id: d_katerina
                  e-mail: kate.dulko@welkinsuite.com

                   

                    





                  Boost Your Productivity. Get Started Today

                  Try Free Trial