Post a reply

Before posting, please read how to report bug or request support effectively.

Bug reports without an attached log file are usually useless.

Add an Attachment

If you do not want to add an Attachment to your Post, please leave the Fields blank.

(maximum 10 MB; please compress large files; only common media, archive, text and programming file formats are allowed)


Topic review


Re: WinSCP generate HTTP url error

I've never seen this problem before. From the little information on the error message I've found online, it seems that your system some restrictions on executing PowerShell scripts. It somehow connected to AppLocker and PowerShell Constrained Language Mode:

I'm afraid there's not much we can do about it on our side.

You might be able to get the WinSCP PowerShell scripts whitelisted.

Re: WinSCP generate HTTP url error

Yes, I do get the same error if I do it manually.

Re: WinSCP generate HTTP url error

I do not understand the error. There's no . operator.

Anyway, can you reproduce the error when executing the script manually?
To get the command to execute the script, you can press Shift+Ctrl while submitting the extension options dialog:

WinSCP generate HTTP URL error

Since SRP policy started on PC can't generate HTTP rural, getting an error:
C:\Program Files (x86)\WinSCP\Extensions\GenerateHttpUrl.WinSCPextension.ps1 : Cannot dot-source this command because it was defined in a different language mode. To invoke this command without importing its contents, omit the '.' operator.
+ CategoryInfo : InvalidOperation: (:) [GenerateHttpUrl.WinSCPextension.ps1], NotSupportedException
+ FullyQualifiedErrorId : DotSourceNotSupported,GenerateHttpUrl.WinSCPextension.ps1

On SRP logs don't see anything was restricted.
Can you maybe help how to figure how to fix it?
SRP not blocking .ps1, you can run regular .ps1 script manually.