MSWINSCK.OCX dependency problem on Domain
Posted on 2005-04-20
This is driving me nuts! I've never had this problem and then all of a sudden poof!
I'm setting up a new windows 2000 pro computer. I then add it to my work domain. Then I re-login as Admin on the local account so I can install my VB6 program. When I test it, it works fine. I then select the folder from Program File and change the security settings for Users->Full Control. Then I login as a domain account and start the program. Now I get...
"Run-Time Error 339
Component 'MSWINSCK.OCX' or one of it's dependencies not correctly registered: a file is missing or invalid."
I checked the system. The mswinsck.ocx is in C:\winnt\system32 and I even re-registered it myself with regsvr32.exe just to be sure. The program opens fine when opened from Administrator (local), but when I try another users (doman) it won't work!!!
What really drives me crazy is that I got this program installed in about 20 locations and they all work fine with domain logins.
The only difference I can think of is that I remade the installer using the new Visual Studio Installer instead of the regular Package and Deployment Wizard. I don't want to remake the installer with the old wizard because I've already made many untested changes to the sourcecode and I don't have time to fully complete the changes and debug! This is turning into a disaster!
I thought maybe the Visual Studio Installer somehow didn't install the OCX in a domain-friendly manner, so I uninstalled my program and re-installed an older version packaged with the old deployment wizard. Even this won't run!!!!
So to repeat:
- I've done this fine about 20 times
- Now only the local accounts open the program. Accounts from the domain give the above error. (This only applies to fresh installations of Windows 2000. Old installations work no prob)
- MSWINSCK.OCX is properly installed and registered.
Anyone have any ideas??? I need to get this working today!