Self Registration Error

[jmcmh]

When I attempted to load Pub 5 Ultimate on my laptop (after removing Pub4) everything went perfectly until the end, then I got this message:

SELF REGISTRATION ERROR
The following files did not self register or unregister
1. c:\WINDOWS\System 32\Gstctrl.ocx
This application has failed to start because the application configuration is incorrect. Re-installing the application may fix the problem

Re-installing didn't help - tried several times.
Used system restore and it still wouldn't load.
I tried copying that file from the desktop and replacing the one in the laptop - no use.

I was using the CD produced at the installation on the desktop.

Any suggestions?

[Singyteach]

Hi,

I have exactly the same problem
Sorry I can't help as yet, but if I discover anything will get right back to you.

[Bart]

The controls library is not wanting to register for some reason.

If you open the Command Line (From the Start menu under Programs -> Accessories -> Command Line, if you are on Windows Vista or 7 you should right click on the shortcut to Command Line and choose "Run as administrator").

Type into the command line (with the quotes left in):
"<path to where Publisher is installed>\Publisher5.exe" /register

(e.g. "C:\Program Files\greenstreet\Publisher\Publisher5.exe" /register)


Hopefully this should return without showing any error messages and should have fixed the problem.
If not typing into the command line:
regsvr32.exe gstctrl.ocx


If this works it will tell you it registered the ocx successfully, otherwise it sounds like you are missing one of the other libraries it depends on.
The easiest way of finding out which library it is missing is to download the Microsoft tool - Dependency Walker http://www.dependencywalker.com/ and then run it on the library "C:\WINDOWS\System 32\Gstctrl.ocx"

[jmcmh]

Thanks Bart

However the first 2 suggestions brought no results.
I then tried Depenency Walker which apparently found 4 errors.
I tried replacing Gstctrl.ocx with the same file from the desktop but DW returned the same errors
(I attempted to add an image showing findings but couldn't work out how to do so.)

The errors were apparently in these files: MFC90, MSVCR90, DWMAPI, & EFSADU.DLL

What now?

[I also tried to load Nokia Suite program with a similar result - "windows installer not correctly installed"]

[Bart]

MFC90 and MSVCR90 are part of the Visual C++ 2008 Redistributables. They are normally installed as part of the install, but it is nice and easy to install them separately. You can download them from http://www.microsoft.com/downloads/details.aspx?FamilyID=9b2da534-3e03-4391-8a4d-074b9f2bc1bf&displaylang=en and then just install them.

If you then run regsvr32.exe Gsctrls.ocx as I said in my previous post, hopefully this should now work. At which point Publisher should then be fine.


The other two don't matter as they are delay linked libraries, so they are only exist and are loaded if they are needed (DWMAPI is used for the Areo interface on certain versions of Windows Vista and 7, EFSADU is used for handling encrypted hard disk drives on certain version of Windows).

[jmcmh]

Sorry Bart, same problem.
I followed your instructions and downloaded and ran "vcredist_x86" which produced:

"The following error occurred during setup:
Windows Installer service could not be accessed. Contact your support personnel to verify that the Windows Installer service is properly registered."

I also tried installing "MSI30-KB884016" with this result:

"Setup has detected that the Service Pack Version of this system is newer than the update you are applying. There is no need to install this update."

Running "regsvr32.exe Gsctrls.ocx" brought no results.
John

[Bart]

It definitely sounds as if the Microsoft Installer on your computer is having some problems (especially as you were saying that running the Nokia Suite install was reporting the same sort of problems).

I'd suggest following the Microsoft knowledge base article on the problem - http://support.microsoft.com/kb/315353 and see if that fixes the Microsoft Installer.

If it does then try what I suggested in my last post.

[jmcmh]

Bart - you're a star!!!
Everything now working perfectly
Thanks again
John

(hope "error1935" who apparently had the same problem has got his sorted too)

[Sponsored content]