Forum » .NET assembly / COM library »

Post a reply

Options
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)

Options

Topic review

martin

Re: automation error on Win10 64 bit

gwsftp wrote:

I have the same issue (automation error) on some PC with Win10 64 bit... I've downloaded 5.14 beta and still issues.
How can I do?

We need to know more. There are several separate problems described in this thread. Was it ever working on those PCs? What did you do to register the assembly? How are you using the assembly? Please start a new thread for your problem.
gwsftp

automation error on Win10 64 bit

reyemenork wrote:

5.14 Beta works.


I have the same issue (automation error) on some PC with Win10 64 bit... I've downloaded 5.14 beta and still issues.
How can I do?
martin

Re: Automation error in v5.13.14

hans.wirz@xmv.ch wrote:

What if "all versions" .dll not available anymore or not kwowing what versions have been registered at all? Is there a way to "clean up everything"?
I had the same problem with older version, didn't get it running.
Please help

This issue has been added to the tracker:
https://winscp.net/tracker/1706

I'm sending you an email with a development version of WinSCP to the address you have used to register on this forum.
hans.wirz@xmv.ch

Re: Automation error in v5.13.14

martin wrote:

Try unregistering all versions (including the old one) and re-register the new one again.

What if "all versions" .dll not available anymore or not kwowing what versions have been registered at all? Is there a way to "clean up everything"?
I had the same problem with older version, didn't get it running.
Please help
reyemenork

5.14 Beta works.
reyemenork

It's 32 bit.
martin

Do you have 32-bit or 64-bit installation of Access?
reyemenork

Still haven't got it working. This is the code I used to register: 
%WINDIR%\Microsoft.NET\Framework\v4.0.30319\RegAsm.exe %LDIR_WinSCP%\WinSCPnet.dll /codebase /tlb:WinSCPnet32.tlb

This registers successfully, and I can add the tlb file in references in VBA. I'm using this in Access VBA. like this: 
'Set pSession = New WinSCPnet.Session

'Set pSessionOptions = New WinSCPnet.SessionOptions

Set pSession = CreateObject("WinSCP.Session")

Set pSessionOptions = CreateObject("WinSCP.SessionOptions")

Early binding gives the automation error, late binding the active-x error.
martin

reyemenork wrote:

I'm also having the same issue, curious if you came up with anything? I've tried un-registering and re-registering, and registering on a fresh install of windows 10. Get the same error.

So did you ever made it working?
What exactly did you do on the fresh install of Windows 10?
How exactly are you loading and using the assembly?
reyemenork

I'm also having the same issue, curious if you came up with anything? I've tried un-registering and re-registering, and registering on a fresh install of windows 10. Get the same error.
martin

Re: Automation error in v5.13.14

Try unregistering all versions (including the old one) and re-register the new one again.
PaulTakla

Automation error in v5.13.14

I have been using the .NET assembly registered for COM for several years. After updating the version to v5.13.4, I get an "Automation Error" in VBA if using early binding, or an "ActiveX control can't create object" error when using late binding. I am using 32-bit office and have registered the component in both 32 and 64 bit forms, and both give the same result. I have used the version 4.0.30319 RegAsm.exe. Does anyone have any ideas what the issue might be and how to resolve it?

Documentation

Support

Associations

Follow Us