I recently ran into a very annoying problem after copying a deployed OI application to my new Dell laptop running Windows 7. The programs vsprint7.ocx and vspdf.ocx do NOT load automatically the first time you run an OIPI report. An error message appears saying the programs were not loaded (I forget the exact message). I talked to OI support and found out how to manually load the programs: 1) Click on All Programs, 2) Click on Accessories, 3) Right click on the Command Prompt option, 4) Click on Run As Administrator, 5) Click Yes on message asking if you want to allow program to make changes, 6) navigate to location of ocx programs, 7) type regsvr32 vsprint7.ocx, 8) type regsvr32 vspdf.ocx.

Here's the problem: I would like to eventually sell this small application from a web site. The customer would download the zipped file and simply run a setup program to install the application. That's how it worked on windows xp. If I have to make new customers walk through the steps above each time it would be a real bummer!

Please tell me there is a simple way to automate the process.

Thanks,

Harold King

Harold,

Which version of OI? OI 9 has a client install that registers all the necessary client side programs. This must however run with administrative rights. So your install should have two parts. The first is to get the application on the server (server install) , the second should include a client install.

This is a common issue with Vista and Windows 7…

HTH,

John

Hi John,

I'm using version 8.07. My username on the laptop has administrator rights, but the 2 ocx files still don't load automatically (like they did on xp).

Thanks,

Harold

Harold,

You will need to run as Administrator not as someone with Administrator rights.

Sean

Hi Sean,

Is there a way to install the ocx files automatically after loading an RDK application on a stand-a-lone pc? I would hate to have to have to walk each customer through having to load the programs manually (as I described earlier).

Thanks,

Harold

Harold,

You can create a batch file to do the registration and then run this from each client.

regsvr32 vsprint7.ocx

regsvr32 vspdf.ocx

John

If you have a window or program that is always run on start-up, then you could add the following lines.

call utility("RUNWIN","regsvr32 VSPDF.OCX /s")

call utility("RUNWIN","regsvr32 VSPRINT7.OCX /s")

Windows 7 and Vista users will only need to run their shortcut once as Administrator.

Hi John,

Thanks for the suggestion. I had already experimented with using a batch file. It does make the process much simpler. It's still kind of annoying that the user can't simply run a setup program to extract the files, create the shortcut and be ready to run the app.

Thanks again,

Harold

If you get hold of SRP's NSIS install script for OI, you will see where it elevates to the highest Admin level and registers the OCXs in question (also adds to windows firewall).

I think you could strip this down for a workstation version.

Hi Barry,

That worked great! The /s (silent) parameter is cool, too. If I could figure out how to bypass the UAC message about running Oinsight.exe it would be even better! Do you have any ideas?

Thanks,

Harold

Right click your OInsight.exe program and click "Properties". Go to the compatibility tab and verify the state of "Run this program as an administrator". If it is checked you may get this UAC message. If so, un-check and test again.

If you are launching OInsight.exe from a shared network drive and the message is about trusting a shared network location you will need to adjust your IE security settings.

Hi Jared,

Thanks for the info. I tried your suggestion, but it didn't seem to work. I tried it with the box checked and unchecked. I still get the message "Do you want to allow the following program from an unknown publisher to make changes to this computer? Oinsight.exe".

This isn't a big issue for now. When I get to the point where I'm actually bundling the app in an install program we'll see what the options are. Hopefully the install program will have some options, too.

This Windows 7 security stuff must be a real pain for you guys are Revelation. I never used Vista which is where it looks like these issues started.

Thanks,

Harold

View this thread on the Works forum...