Thank you. :mrgreen:
- Guest
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.
Topic review
- martin
Re: KeepLocalUpToDate / Using Extensions
I assume you do not have WinSCP .NET assembly package extracted along with your script.
That, combined with PowerShell 2.0 or older, gives you this cryptic error message.
That, combined with PowerShell 2.0 or older, gives you this cryptic error message.
- halycon
KeepLocalUpToDate / Using Extensions
Hey,
i need to keep a locale dir syncronized with a remote dir, but i don't get the Extension "KeepocalUpToDate" running.
WinSCP is version 5.9.6, my OS is Windows Server 2008 R2.
When i try to execute the powershell script i only get the following error:
The error says "the argument can not be bind to the parameter "path" because it's NULL:"
When i do the same thing on a windows 10 x64 machine, the script is running.
Is there some conditions regarding powershell versions or something?
Cheers,
halycon
i need to keep a locale dir syncronized with a remote dir, but i don't get the Extension "KeepocalUpToDate" running.
WinSCP is version 5.9.6, my OS is Windows Server 2008 R2.
When i try to execute the powershell script i only get the following error:
C:\Program Files (x86)\WinSCP>powershell.exe -ExecutionPolicy Bypass -File "c:\P
rogram Files (x86)\winscp\Extensions\KeepLocalUpToDate.WinSCPextension.ps1"
Cmdlet KeepLocalUpToDate.WinSCPextension.ps1 an der Befehlspipelineposition 1
Geben Sie Werte für die folgenden Parameter an:
localPath: "c:\"
remotePath: "/"
Error: Das Argument kann nicht an den Parameter "Path" gebunden werden, da es NU
LL ist.
The error says "the argument can not be bind to the parameter "path" because it's NULL:"
When i do the same thing on a windows 10 x64 machine, the script is running.
Is there some conditions regarding powershell versions or something?
Cheers,
halycon