One or our clients is getting an OIPI Runtime Error 367 when running OIPI on a new W2K workstation. The error message says Can't register or load custom control SSUTIL.OCX. I've got them to perform the client install and restart, but this doesn't make any difference. This file does exist in the WINNT\SYSTEM directory and the application works fine on other W2K workstations.

Can anyone shed any light on this?

Thanks, M@

Matt-

Try running the following command form the workstation directory where the ssutil.ocx file resides:

REGSVR32 SSUTIL.OCX

Hope it helps-

Mike Ruane

Thanks Mike,

I passed that on but "I got an error message: 'ssutil.ocx' is not an executable file and no registration helper is registered for this file type. I was logged in as administrator as well."

BTW they are still using OIPI 3.81, if that makes any difference.

Cheers, M@

M@,

One or our clients is getting an OIPI Runtime Error 367 when running OIPI on a new W2K workstation. The error message says Can't register or load custom control SSUTIL.OCX.

I and my many clients have used OIPI for a long time, both 3.81 and other versions, but I can't remember having seen the particular error message you mention.

(Not with SSUTIL.OCX, that is. I might have seen it with a different file, but then the file was really missing.)

'ssutil.ocx' is not an executable file and no registration helper is registered for this file type.

According to this error message means:

SSUTIL.OCX is not an executable file (.exe, .dll, or .ocx). For example, typing regsvr32 autoexec.bat generates this error message.

Meaning what in your client's case? That the SSUTIL.OCX file in his WinNT/System folder is damaged? In that case - could you try and install it by hand, e.g first copy it in from a different PC where OIPI runs OK, and then REGSVR32 it?

Or is something wrong with Win2000 itself on your client's PC?

- Oystein -

Hi Matt,

Mike's suggestion is the best place to start, but the SSUTIL.OCX is a 16-bit ActiveX control – so try this command:

regsvr drive:\path\ssutil.ocx

I have tested the OIPI 3.81 installation on a relatively new Win2000 box – with no problems. This OCX does not have any external dependencies (MFC is statically linked), so I'm not sure why this file would fail during registration. You might try manually copying the SSUTIL.OCX from a computer that is working to this new Win2000 computer, and running the REGSVR command again to eliminate the possibility of a corrupted file.

Tony

Hi Tony,

They didn't have a copy of just REGSVR.EXE on their machine so I've sent them the same copy you sent me a while back. I believe they'd tried copying the OCX file from the good workstation.

Thanks for your help,

M@

View this thread on the forum...