Problem registering DLL

Hi

I'm trying to migrate my website to a new Windows Server 2003 R2 Service Pack 2 server. I use an ActiveX component called Cast128 which allows me to do simple bits of encryption on the fly

On the old server I registered c:\windows\system32\cast.dll using REGSVR32 and all is well. On the new server I get the following error when I try to register the DLL:If I copy the DLL to, for example, c:\temp\ I can register it no trouble, although my ASP scripts can't use it. I'm guessing that this could be a permissions or dependency problem, but I'm a bit stumped. The odd thing is that if I try to open the DLL with, for example, Dependency Walker, I can't even see cast.dll in the open file dialog?

I'm absolutely baffled. So - two questions really:

1. Any ideas why REGSVR32 and other applications can't see cast.dll?

2. If I do register cast.dll in another folder, what steps do I need to carry out to enable Classic ASP to use the ActiveX component?

Thanks very much in advance

Haven't seen you here for a while!

For #2, it should not matter where the dll is physically located, since the component registration process abstracts the location of the file from the application, so the app only needs to know the progid to use the component. This holds for asp or any other COM compliant application. If you register ok on occasion but still can't use the component from asp I suspect you're right in guessing permissions.

As far as not being able to register the dll only in certain locations, assuming the acl's on the folder where the dll is located aren't blocking use of the dll, then my guess is the component relies on some other external component or file that isn't findable when the dll is in one of the failed-to-register locations. Just a guess.