Server 2003 ActiveX control registration

[SnyAc]

I am maintaining a legacy app that is running under VFP7 and uses a particular ActiveX control for image editing that has been in use for the last 8-10 years. On this particular installation the ActiveX control that registers successfully using REGSVR32 throws and OLE error 'class not registered' in the application's creation of the object.

VFP 7
Windows Server 2003
Domain controlled
Application Network based (executed from the mapped network path.... not the way I would have designed it)

Are there any permissions issues that could affect the ActiveX registration / instantiation ?

Andy Snyder
SnyAc Software Services

http://www.snysoft.com

Hyperware Inc. a division of AmTech Software

http://www.hyperwareinc.com

 

[Dan Freeman]

Just out of curiosity, why do you have an end-user running Windows Server?

 

[SnyAc]

The workstations are running OS's earlier than Vista... (primarily XP) The server is not used as a workstation.... Corporate domain controlled network as opposed to home/workgroup peer to peer. I have to consult with the customer's IT services people to find out what might have changed on their system in the last couple of months. This application has been installed and running on their site for 5+ years.

I listed the server's OS version in my original post because the activex control behaves the same way on it as it does on the workstations.

Andy Snyder
SnyAc Software Services

http://www.snysoft.com

Hyperware Inc. a division of AmTech Software

http://www.hyperwareinc.com

 

[Dan Freeman]

You need to nail down the environment in your own head.

If the workstations are not running Server 2003, then there is no reason to troubleshoot Server 2003. It's just a file repository. You should troubleshoot the workstations.

Where is this ActiveX control running? Is it running on the workstations?

 

[SnyAc]

I did tell you about the environment and I'm very clear about what I'm trying to troubleshoot... Unfortunately what I'm trying to troubleshoot isn't actually a VFP problem but a Windows OCX registration problem. I asked the question on this forum in case any of our peers had run into an ActiveX registration issue like this before. The activex control has to be registered on any workstation that is going to run the application. I'm going to have to wait till I can consult with the customer's IT network administration people to find out what has changed in their environment.

Andy Snyder
SnyAc Software Services

http://www.snysoft.com

Hyperware Inc. a division of AmTech Software

http://www.hyperwareinc.com

 

[Olaf Doschke]

Andy,

Before Vista and it's UAC, registration of an ocx is a straight forward process when manually registering. Anyway, an activex should rather come with a setup.

I can only assume there are dependant files missing eg support dlls or a license file.

I can speak for exontrol exgrid installation, which works fine via the setup. I would never try this manually, though. IT's only one control out of a whole suite and there is a license installed with it, I (and our customer) simply relies on that setup.

The error may simply be, because you successfully registered a newer version than used in the vfp application, eg CLSID isn't matching. Different version, different component GUID/CLSID.

Bye, Olaf.