Register .dll on web server

[dsmith1000]

I am having a problem registering a custom .dll I created for a threaded message board. I did what the tutorials on the subject have suggested - use regsvr32.exe - but I am getting an error that seems to say that the component is not registered. This is the error -

databaseAccess error '800a01ae'

Class does not support Automation or does not support expected interface

Any ideas or suggestions? Thought about installing VB on the server and compiling the .dll on that machine. I am running win2k pro at my desk and it works fine with IIS there. Web server is nt 4.0, IIS 4.

dave

 

[shaddow]

U used regsvr32.exe mycomponent.dll or ocx?
If this did'nt work this means that your componnet is not an component (activex) ________

George

 

[dsmith1000]

I did. And it gave confirmation that it worked. And my component is Project Type: ActiveX DLL.

Any Ideas? Should I try it again? Do I need to make a cab file and install it on the server that way?

Thanks,
dave

 

[dsmith1000]

Is there any restrictions on where the .dll has to be located on the drive (which folder, directory...etc)? I created a new folder on the E: drive and stuck it in there. When I registered the component I spelled out the entire path to the .dll (regsvr32.exe E:/inetpub/...).

dave

 

[Extentec]

Are you installing to a remote server over a connection or are you at the server?

If at the server:
I would try setting the .dll as an MTS no transactions component (class properties window, MTSTransactionMode = 1-NoTransactions). Recompiling and registering it as an MTS package on the server.

If over connection:
Check to be sure you are actually on the server via remote control (ControlIT, VNC, PCAnywhere, ect) and have the correct permissions on the .dll