Hightower (19th June 2009)

We have some special software for DT called LJ_PLC_ROBOT or something similar. When trying to use PLC software on it it works for staff, but students on the same machine get a 339 error, something about a corrupt msflxgrd.ocx.
I have create a simple batch to unregister and re-register the OCX as follows:
I have ran this on the machines as systemadmin, logged off and logged on as a pupil and the software works fine (no 339 error now).Code:regsvr32 C:\Windows\System32\msflxgrd.ocx /u regsvr32 C:\Windows\System32\msflxgrd.ocx
Or so I thought - I did that yesterday, and a whole class of kids got on to the software fine. But today (possibly the restart that caused it) the same 339 error was reproduced on every machine when trying to run the software as a student.
How do I get this to stick so it works everytime? We're CC3.
You could add the batch file to the netlogon area of your server?
\\***-svr-001\netlogon\ then setup a GPO to run the batch file on each PC every time it boots up.
Hightower (19th June 2009)
Don't think so off the top of my head.
I use this method to roll out the .ini file for TestBase, ExamBase, ExamQuest etc, as we purchase a lot of these titles for a range of subjects and it saves packaging up the .ini file each time I just roll the latest version via batch file and GPO each time.
maybe use filemon and regmon on a test student account to see what the robot app is trying to do as far as permissions or changes etc
Am guessing its either permissions on the directory where the app is installed or because users dont have access rights to the system32 directory or a registry permissions issue ?
Had a DT app when working at the kingswood and it kept erroring out because it couldnt change a registry key.

I've just created a package for PICAXE (using their CC3 instructions), and when testing as a student it failed with a similar 339 error, only this time for WAVE32.OCX.
Logging on as SystemAdmin and unregistering/resgistering the OCX made it work for a student. Why have two packages created this similar error?

I'd be looking through other recent packages created/allocated to see whether any included these files and overwrote a previous version or so?

UPDATE: Checked every package in Q: and none have either of these OCX files in them.

Not sure ... open your new MSI and see whether it shows the registration for that particular ocx file?

@Hightower:
Don't want to seem patronising but have you ran the acl detective on the package, i find this helps.
Also as has been stated before regmon to see what access the software needs and to which directories or drives.
good hunting![]()
![]()
There are currently 1 users browsing this thread. (0 members and 1 guests)