PDA

View Full Version : PG error after installation



tig2020
06-22-2007, 11:20 AM
Installed the 4.1.037 version and when attempting to open the shredder get an error message as follows: "Runtime error 339:componet comdlg32.ocx or one of its dependencies not correctly registered: a file is missing or invalid." I have uninstalled and reinstalled the application and it does not correct the above error. The aforementioned ocx is in the system32 directory and is properly registered.

Please advise

AChen
06-23-2007, 08:37 AM
Hi tig2020,

Could you please attach a screenshot of the error message to this thread and we will investigate this further.

tig2020
06-25-2007, 04:49 PM
Hi tig2020,

Could you please attach a screenshot of the error message to this thread and we will investigate this further.

yep - here is the requested information

AChen
06-26-2007, 08:01 AM
Thanks for the screenshot.

We'll do some futher testing on this and I'll get back to you.

AChen
06-27-2007, 02:03 AM
I have been able to recreate the same problem as the error message you have provided. The problem occurs when COMDLG32.OCX is not installed/registered properly.

In order to resolve this issue, please try the following:

1. Uninstall PG (Make sure reboot is done if required), when asked to remove common components such as COMDLG32.OCX select 'yes'

2. Install PG (www.pctools.com/privacy-guardian/)

3. If there still is a problem could you please send us the COMDLG32.OCX version number. (C:\Windows\system32\COMDLG32.OCX)

tig2020
06-27-2007, 05:31 PM
I have been able to recreate the same problem as the error message you have provided. The problem occurs when COMDLG32.OCX is not installed/registered properly.

In order to resolve this issue, please try the following:

1. Uninstall PG (Make sure reboot is done if required), when asked to remove common components such as COMDLG32.OCX select 'yes'

2. Install PG (www.pctools.com/privacy-guardian/)

3. If there still is a problem could you please send us the COMDLG32.OCX version number. (C:\Windows\system32\COMDLG32.OCX)

As requested the version number is as follows: 6.0.84.18:)

AChen
06-28-2007, 03:05 AM
Thanks for the version number. Did the instructions resolve the error message?

tig2020
06-28-2007, 04:10 PM
Thanks for the version number. Did the instructions resolve the error message?


No, the error remains:confused:

AChen
06-29-2007, 12:36 AM
What you could try doing is either installing Registry Mechanic or Desktop Mechanic and then try re-installing Privacy Guardian. Before trying the following, uninstall Privacy Guardian first. RM and DM use the same runtime files as PG, let me know how you go.

tig2020
06-29-2007, 03:16 PM
What you could try doing is either installing Registry Mechanic or Desktop Mechanic and then try re-installing Privacy Guardian. Before trying the following, uninstall Privacy Guardian first. RM and DM use the same runtime files as PG, let me know how you go.

Installed RM prior to the installation of PG. Have uninstalled PG and reinstalled as previously instructed. Was file version I sent you the correct one. I am assuming it was not.:eek:

AChen
07-02-2007, 02:13 AM
Installed RM prior to the installation of PG. Have uninstalled PG and reinstalled as previously instructed. Was file version I sent you the correct one. I am assuming it was not.:eek:

The file version you have provided is the correct and latest version (6.0.84.18). We were able to replicate the error message you have received, but once we removed this file COMDLG32.OCX during the uninstallation and re-installed, the error message disappeared once we re-installed PG. When did you start receiving the error message? did it occur before, only only started appearing recently? Also what operating system are you running?

AChen
07-02-2007, 04:18 AM
Another possible thing to try, is to register the comdlg32.ocx manually.

1. Run command prompt as admin user
2. Navigate to Windows\system folder
3. Unregister the control regsvr32 /u comdlg32.ocx
4. Register the control regsvr32 comdlg32.ocx (Upon successful registration a confirmation message will be displayed)
5. Try running PG

tig2020
07-06-2007, 08:33 PM
Another possible thing to try, is to register the comdlg32.ocx manually.

1. Run command prompt as admin user
2. Navigate to Windows\system folder
3. Unregister the control regsvr32 /u comdlg32.ocx
4. Register the control regsvr32 comdlg32.ocx (Upon successful registration a confirmation message will be displayed)
5. Try running PG


Here is what I have done to fix the aforementioned problem. I uninstalled the PG program and unregistered the above captioned file as instructed. The uninstall feature of PG was not deleting the comdlg32.ocx file. I then located and renamed the the file to comdlg32.001. I then reinstalled the PG program and the problem has been corrected.:eek: