Post a reply

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


Installed .NET 3.5 and it's working now

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.



I installed this version using Windows Update.

Re: Problem using COM interface with Windows 2003

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

Problem using COM interface with Windows 2003

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.