1. Pierre DETE
  2. PowerBuilder
  3. Monday, 24 June 2019 13:33 PM UTC

Hello PB users,

 

It takes a very very long time to open (+read/save) a workspace on a mapped network drive. I think it's a network issue but as Powerbuilder environment is the only one to have this problem for now on my laptop, I don't know what to ask and say to our network admin.

The only strange thing I can see is that with procmon, I can see PB170.exe process trying to cache network drive into c:\windows\CSC\v2.0.6 even the "file offline" option is off. I have read many web page about people with difficulties to disable "file offline". Maybe it's not the cache process the issue, but there is so many lines like this :

15:31:50.5849923 PB170.EXE 12280 CreateFile C:\Windows\CSC\v2.0.6\namespace\naspar NAME NOT FOUND Desired Access: Read EA, Write EA, Read Attributes, Write Attributes, Delete, Read Control, Synchronize, Disposition: Open, Options: Synchronous IO Non-Alert, Attributes: n/a, ShareMode: Read, Write, Delete, AllocationSize: n/a

....

Is it a Windows10, a network configuration or Powerbuilder issue?

Any idea?

 

Pierre DETE Accepted Answer Pending Moderation
  1. Monday, 15 July 2019 13:39 PM UTC
  2. PowerBuilder
  3. # 1

It was a network issue but I have not the solution.

Now we are able to work directly on the network as before.

 

Thank you for your replies.

Comment
There are no comments made yet.
Pierre DETE Accepted Answer Pending Moderation
  1. Tuesday, 25 June 2019 08:40 AM UTC
  2. PowerBuilder
  3. # 2

Thank you for your reply.

We are a small team of 5 developers we are developing and correcting our application locally but the master copy is on a common network drive, and we have to report the modification. We are working like this since many years, about 20 years :). And it was acceptable. But since 2 months it becomes very long to modify common network sources. During this period there was Powerbuilder 2017, Windows 10 evolution of our laptops, and network domain modification by the IT. So we don't know where is the problem.

Comment
  1. Roland Smith
  2. Tuesday, 25 June 2019 10:12 AM UTC
You need to start using a source control system.That would allow you to work locally and the source control system repository would be on the network.
  1. Helpful
  1. David Peace (Powersoft "The PowerBuilder & C# People")
  2. Thursday, 27 June 2019 15:40 PM UTC
I agree with Roland, you should not have PBLs on a network but should hold your source in source control on the network.
  1. Helpful
There are no comments made yet.
Roland Smith Accepted Answer Pending Moderation
  1. Monday, 24 June 2019 22:36 PM UTC
  2. PowerBuilder
  3. # 3

Never run PowerBuilder with libraries on the network.

If you are concerned with backups, place the workspace under your documents folder and make sure that your profile is being saved to the network when you log out, or just run an automatic backup tool.

 

Comment
There are no comments made yet.
Olan Knight Accepted Answer Pending Moderation
  1. Monday, 24 June 2019 19:57 PM UTC
  2. PowerBuilder
  3. # 4

This is both a network issue and a PB issue.

Normally, it's a TERRIBLE idea to have your PBLs on a network, and try to edit them on a laptopm - especially if you are not hard-wired into the LAN.

Having said that, this CAN be done, but the price for this configuration is performance.

If there is ANY way you can have a local copy of the PBL on which to do your work, and then upload your changed PBL when you are finished with the task, then I'd strongly recommend that you use that option.


Olan

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.