For Windows 2003 it appears that .NET 3.5 works while .NET 4 doesn't. Not sure of all the details, but I will try some other combinations to see if I can pinpoint the issue a litter more.

BTW, I was not able to get Fuslogvw to show me anything on Windows 7 or Windows 2003. Thanks for the suggestion though.

Tom

Try debugging this using Fuslogvw
https://learn.microsoft.com/en-us/dotnet/framework/tools/fuslogvw-exe-assembly-binding-log-viewer
Or attach its log here.

I installed this version using Windows Update.

What version of .NET framework do you have on the server?

I am able to register and use the COM interface to WinSCPnet from my Windows 7 desktop, but when I attempt to deploy on Windows 2003 I get an error that the COM object could not be created. Registration went fine in both cases.

I used the Windows OLE/COM viewer tool (OLEview.exe) on both machines and on Windows 7 I am able to browse the various exposed interfaces. But when I attempt the same operation on Windows 2003 I get a file cannot be found error. The exact wording in the error dialog is:

CoGetClassObject failed.
The system cannot find the file specified.
severity: SEVERITY_ERROR, facility: FACILITY_WIN32 ($80070002)

I tried placing the winscp directory on the PATH, but it didn't help.

Has anyone seen this before? If so, is there a work around? I can provide screen shots from the COM Browser application if this would help.