Powershell Studio hanging/freezing with unreachable network locations

Support for all customers who have purchased a SAPIEN PowerShell Studio product license. This forum does not offer a response time guarantee.
Forum rules
DO NOT POST SUBSCRIPTION NUMBERS, LICENSE KEYS OR ANY OTHER LICENSING INFORMATION IN THIS FORUM.
Only the original author and our tech personnel can reply to a topic that is created in this forum. If you find a topic that relates to an issue you are having, please create a new topic and reference the other in your post.
User avatar
FlightUK
Posts: 4
Joined: Mon Oct 10, 2016 7:41 am

Powershell Studio hanging/freezing with unreachable network locations

Post by FlightUK » Fri Jul 14, 2017 4:31 am

Product, version and build: Powershell Studio - 1.0.21
32 or 64 bit version of product: 64 bit
Operating system: Win10 Pro
32 or 64 bit OS: 64 bit

Hi all,

Recently some network changes where I work have made it so that a server I reference "\\ServerName\c$\Whatever.txt" is no longer accessible from the machine I script with, this isn't a problem as I just compile to an executable and run it on the target machine, however when working on the script I get hangs/freezes for 5-10 seconds at a time every minute or so at random. I figured this was referencing the network locations in the script, timing out and then letting me resume writing, I confirmed this by commenting out of all of the network locations, and now I have no issues, but I can't comment and un-comment 50-100 lines of script every time I need to run/test/modify the form/script.

My questions are:
Why does the script writing component of the application attempt to connect with these locations/read them without me running or saving the script?
How can I work around this? I can't be the first person that's writing scripts designed not to be run on the machine you're writing on.

Many thanks,
Miles

User avatar
davidc
Posts: 4745
Joined: Thu Aug 18, 2011 4:56 am

Re: Powershell Studio hanging/freezing with unreachable network locations

Post by davidc » Fri Jul 14, 2017 8:30 am

Can you verify PowerShell Studio's build again? The current build is 5.4.141 and you reported 1.0.21.

If you dot source any file, PowerShell Studio will attempt to read it for PrimalSense purposes. I recommend disabling Options->General->Enable remote file status check option.
Enable Remote File Status Check.png
Enable Remote File Status Check.png (36.02 KiB) Viewed 77 times
You can also disable Options->PrimalSense->Enable dot sourcing PrimalSense:
Enable dot sourcing PrimalSense.png
Enable dot sourcing PrimalSense.png (25.75 KiB) Viewed 77 times
Please let us know if this helps. We will also check if we can improve the process so it doesn’t trigger a delay every time.
David
SAPIEN Technologies, Inc.

User avatar
FlightUK
Posts: 4
Joined: Mon Oct 10, 2016 7:41 am

Re: Powershell Studio hanging/freezing with unreachable network locations

Post by FlightUK » Mon Jul 17, 2017 7:54 am

Hi David,

Apologies, you're quite right, that was not my build number. I think that's the build number of the the updater tool itself which fooled me. I've checked in Add/Remove programs and it states 5.4.141 which is evidently the one :)

I've just tried the two options you mentioned, the PrimalSense "dot sourcing" had no impact but the minute I disabled "remote file status check" the problem appears to have stopped, so I think you're on the money there.

I really appreciate your help on this one, I'll see how I get on from here.

Many thanks,
Miles

User avatar
davidc
Posts: 4745
Joined: Thu Aug 18, 2011 4:56 am

Re: Powershell Studio hanging/freezing with unreachable network locations

Post by davidc » Mon Jul 17, 2017 8:41 am

We made some changes in the upcoming service release to hopefully will help mitigate this issue when the remote file check is enabled.
David
SAPIEN Technologies, Inc.

User avatar
davidc
Posts: 4745
Joined: Thu Aug 18, 2011 4:56 am

Re: Powershell Studio hanging/freezing with unreachable network locations

Post by davidc » Thu Jul 20, 2017 9:37 am

Please try the latest service release (v5.4.142) and let us know if it improves your situation when you have the remote file status check enabled.
David
SAPIEN Technologies, Inc.

Who is online

Users browsing this forum: No registered users and 2 guests