• You are here:  
  • Home
  • Q&A
  • Q&A
  • PowerBuilder
  • Connect to Workspace fails with "The specified directory does not exist"

Subscribe via RSS
Toggle Submenu
  1. Categories
  2. Recent
  3. Tags
View Replies (3)

Resolved Connect to Workspace fails with "The specified directory does not exist"

  1. Issue
0
Votes
Undo
  1. Dick Alstein
    Dick Alstein
  2. PowerBuilder
  3. Wednesday, 10 October 2018 09:17 AM UTC

I am in the process of migrating our SVN repositories to the Native SVN format of PB2017.

As a test, I saved an existing application to the new repository. Then I used Connect to Workspace, to simulate what my co-workers would do in order to work on the application.

At first, this failed consistently with the error "The specified directory does not exist" right after clicking OK in the dialog. I assumed that the error refers to the Checkout Directory. However, I was sure that the checkout directory did exist.

I found that Connect to Workspace succeeded, as long as the checkout directory was located on the C: disk. Trying the same on the local D: disk always failed. Same for attempts on a network drive.

This is a problem, though, since the disks in our workstations have been configured for doing all development on the D: disk.

Has anyone else had the same experience? If so, have you found a workaround?

  1. SVN
Error While Exporting datawindow to Excel.
Appeon Mobile Doubts
Responses (3)
Erick Bergsma
Erick Bergsma Accepted Answer Pending Moderation
  1. Wednesday, 13 February 2019 13:41 PM UTC
  2. PowerBuilder
  3. # 1

Is there a resolution to this?  I am just now experiencing it.

Here is the scenario...

I am migrating from PB9 to 17.  I have successfully migrated the PBL previously, and the Connect To Workspace connected as expected.

We had a fairly significant PROD issue on the PB9 code, so we made the changes there, and now I am re-migrating the PB 9 PBLs.  I removed the Source Control from the PBW, copied over the PB9 PBLs, opened the PBW, and it determined that it needed to be migrated.

Migration was no issue...I did the "Add to Source Control" again, no issue.

Now, on other developers machines, I am trying to do the Connect to Workspace, but I get "the specified directory does not exist".  tried several different directories, all giving the same issue.

Thoughts anyone???

 

Comment
Dick Alstein
  1. Dick Alstein
  2. Thursday, 14 February 2019 06:55 AM UTC
This is caused by a bug in PB2017R3. The check for existence of the directory only succeeds if the directory has the "allow indexing" property set.



A workaround is to set the property on. (Open the Windows Explorer, right-click on the directory, select "Properties", go to "Advanced".)



Or you could install the recent maintenance release (build 1880), in which this bug should have been fixed.
  1. Helpful
Erick Bergsma
  1. Erick Bergsma
  2. Thursday, 14 February 2019 14:45 PM UTC
Thanks Dick!!

I updated to 1880 and it is all working as expected.
  1. Helpful 1
There are no comments made yet.
Dick Alstein
Dick Alstein Accepted Answer Pending Moderation
  1. Thursday, 11 October 2018 07:49 AM UTC
  2. PowerBuilder
  3. # 2

Thanks, I have opened a ticket. (Bug 1728)

Comment
There are no comments made yet.
Chris Pollach @Appeon
Chris Pollach @Appeon Accepted Answer Pending Moderation
  1. Wednesday, 10 October 2018 13:52 PM UTC
  2. PowerBuilder
  3. # 3

Hi Dick;

  This sounds like it might be a GIT interface issue. Please open a Support Ticket in order for our Support Team to analyze this further. AFAIK it should be able to map to you local repository no matter where the repository is located drive wise (IMHO).

Regards ... Chris

Comment
There are no comments made yet.
  • Page :
  • 1


There are no replies made for this question yet.
However, you are not allowed to reply to this question.