The winscp.exe executable was not found at location of the a

Advertisement

sonitapradhan86@gmail.com
Joined:
Posts:
2

The winscp.exe executable was not found at location of the a

Hi,
I am developing application in ASP.Net. My development server is Win7, production server is Windows server 2008. I am using WinSCP in ASP.Net to transfer files from Linux to Window server. In Win7, it is working fine even if I deploy it in IIS. However, when I deploy the application in Windows Server 2008, it is giving me the error message "The winscp.exe executable was not found at location of the assembly (C:\inetpub\wwwroot\Project_name\bin), nor in an installation path. You may use Session.ExecutablePath property to explicitly set path to winscp.exe.".

WinSCP.dll exists in the bin folder. But still I am getting the above message. Please help.

Thanks and Regards,
Sonita

Reply with quote

Advertisement

martin
Site Admin
martin avatar
Joined:
Posts:
28,671
Location:
Prague, Czechia

Re: The winscp.exe executable was not found at location of the a

sonitapradhan86@gmail.com wrote:

WinSCP.dll exists in the bin folder. But still I am getting the above message. Please help.
The error is about winscp.exe, not winscp.dll.
_________________
Martin Prikryl

Reply with quote

sonitapradhan86@gmail.com
Joined:
Posts:
2

Re: The winscp.exe executable was not found at location of the a

But prikryl I cannot find winscp.exe anywhere neither in Win7 machine nor in Windows server 2008. All I can find is winscp.dll. But still it runs without any error in Win7 and not running in Windows Server 2008 (showing the mentioned error). Please let me know what could be the problem and how to rectify it.

Thanks,
Sonita

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
28,671
Location:
Prague, Czechia

Re: The winscp.exe executable was not found at location of the a

WinSCP .NET assembly cannot run without winscp.exe. So you definitely have a copy somewhere on Windows 7 machine. You can set Session.SessionLogPath to enable logging and find a location of winscp.exe the assembly is using in the log.

Make sure you follow installation instructions at:
https://winscp.net/eng/docs/library_install

Reply with quote

Hellduck
Guest

I have the same problem during à migration from windows 2003 server to windows 2008 server

I solve it by copying the WinSCP directory from c:\program files (x86)\ to c:\program files\
You can also reinstall WinSCP directly into c:\program files\

Reply with quote

Advertisement

acrawford
Joined:
Posts:
1

Me too

I too had the same problem. Seems to be a common thread. I had winscp synchronization working great in powershell on the server, however due to powershell's lame quirks in other areas(like running with proper exit codes in sql server agent) I decided to migrate it to SSIS script task. Did so and had to go through the GAC set up. Now powershell(which worked fine previously) gives me the error that's described here. So something about the GAC install screwed it up.

Hellduck wrote:

I have the same problem during à migration from windows 2003 server to windows 2008 server

I solve it by copying the WinSCP directory from c:\program files (x86)\ to c:\program files\
You can also reinstall WinSCP directly into c:\program files\

Reply with quote

martin
Site Admin
martin avatar
Joined:
Posts:
28,671
Location:
Prague, Czechia

Re: Me too

acrawford wrote:

I too had the same problem. Seems to be a common thread. I had winscp synchronization working great in powershell on the server, however due to powershell's lame quirks in other areas(like running with proper exit codes in sql server agent) I decided to migrate it to SSIS script task. Did so and had to go through the GAC set up. Now powershell(which worked fine previously) gives me the error that's described here. So something about the GAC install screwed it up.
The the winscp.dll is in the GAC, you have to set Session.ExecutablePath.
See https://winscp.net/eng/docs/library_install#gac
_________________
Martin Prikryl

Reply with quote

Advertisement

You can post new topics in this forum