SAPIEN Technologies

The cause is a broken Windows API. We will have to replace that portion. Expect a fix in the next service build.

Thanks, I will check on that.

That stems from the necessary code modification to support debugging for PowerShell 1.0.
The next version of PrimalScript will only support PowerShell 2.0 and this issue is addressed.
For now we recommend to write parameters in one line or one parameter per line.

Have you added Import-Module Pscxto the PrimalScript profile? Users<UserName>DocumentsWindowsPowerShellprimalscript.profile.ps1 Depending on your OS the location of this profile may vary. Please remember that different hosts MUST use different profiles as documented by Microsoft. Alexander Riedel201...

I have been trying to replicate this for a while now, with no such luck. All queries run fine, hundreds of times in a row.
I will put some additional diagnostics in and release it with the next service build.

I will post here when it is available.

The execution policy is set in the registry, I am assuming you are running Windows 7. Most likely your user account cannot change the registry entry sucessfully. Windows 7 often returns no error in such a case but ignores the change. Run the elevated version of PrimalScript (see start menu) and chan...

Nothing has changed in regards to FTP transfers. That screenshot really doesn't provide any information. Direct FTP editing really relies on constant and uninterupted connectivity. If that is not the case symptoms like this can occur. Which is exactly why best practices recommend local editing and f...

Ok, thanks, we will look into it at once.

ok. Approximately how many records does a query produce? Just to have some information when setting up a test.
Also, did you use this with previous builds and it worked or is it the first time you are using SQL in PrimalScript?

So when exactly is that crash happening? When you are trying to run it?