Hashing function CryptAcquireContext Lib "advapi32" not working in new computer.

[Stephen Rasey]

I have a user function that creates a hash value from the contents of a
range. It uses the CryptAcqureContext and CryptCreateHash functions in the
advapi32 library. These have worked splendidly on a WinXP SP2, Office 2003
system. They have worked on several other systems without trouble.

I have a new computer using Windows Media Center. I loaded Office 2003,
then Office 2007 keeping the Office 2003 applications.

The CryptAcquireContext function returns a zero in the hProv argument
instead of some non-zero long integer. This tells me that the reference to
Lib advapi32 is mixed up, or there is some incompatibility between this
function and Windows Media Center (which I have trouble believing).

I have un-installed Office 2007,
Rebooted.
Repaired Office 2003 Prof.
Rebooted.
CryptAcquireContext hProv, ..... hProv = 0. wrong.
Un-installed Office 2003.
Reboot.
Install Office 2003 Prof. Complete.
Reboot.
CryptAcquireContext hProv,.... hProv = 0. Still not working.

checked advapi32.dll.
Version is the same as on the Winbook, WinXP SP2, Off 2003 where it works
well.
it is located in the same place: C:\Windows\System32\advapi32.dll.

Additionally, my Outlook will not remember my email passwords.

My feeling is the registry is a mess at this point. Anyone recommend a
good registry clean-up tool?

I'm about to implement KB290301 "Windows installer cleanup utility" to try
and go after some registration issues.

 

[JLatham]

You might look at CCleaner, www.ccleaner.com. FreeWare and highly praised
by those that have used it.

Another strong contender in the freeware category is RegSeeker from
Hoverdesk at: http://www.hoverdesk.net/freeware.htm

In the not so freeware category, there's Registry Mechanic, jv16PowerTools,
and TuneUp Utilities.

And we shouldn't forget Regedit and Regedt32 <g>

By the way, I don't think the Windows Installer Cleanup utility totally
wipes out the related registry entries. I had to use it once, and upon
reinstalling the product (it may have even been Office, don't recall right
now), it still showed up as and activated. Not a bad thing, just kind of
clued me in that not everything in the registry got trashed by it.

 

[Stephen Rasey]

I have no faith in the Windows Installer Cleanup utility. After
uninstalling office 2003 (after uninstalling Office 2007 earlier in the
day), I ran Installer Cleanup. It showed at least two dozen installations,
but none of them were related to office.

Regedit was littered with .12 references to Office components. A lot of
the .11 references were still there, but several instances of .12 without
..11. Realizing that I'm facing a wipe of the C: drive and reinstallation
of Windows, I deleted everything I could find in the registry related to
Office. I'm now reinstalling Office 2003 and waiting on the MS Update
(awful slow tonight).

I tried RegCure, but I cannot say I'm satisfied. I had to do 8 passes
before I got it down to three Empty Registry Keys. And it didn't fix my
problem. ErrorKiller, a product I downloaded in trial found 108 shared
program problems (where RegCure didn't fault them), but they are all
associated with a program I have not yet run and unrelated to Office.

I'll try your suggestions, at least for a test.

Stephen Rasey

 

[Stephen Rasey]

Reinstalled Office 2003. Waiting of Update, but the problem with
CryptAcqureContext from the advapi32 library remains. I'm still getting a
zero in hProv instead of a non-zero long integer.

Looks like a Windows Wipe on Christmas Eve.

Stephen Rasey

 

[Stephen Rasey]

The application runs fine on another computer running Media Center. So
there is no innate conflict between the CryptAcquireContext in lib
advapi32.dll and Media Center.

This Computer's windows installation appears hopelessly corrupted. I don't
know what happened. The only thing that I can blame is the installing of
Office 2003, then Office 2007 for a dual version Office Development Platform
caused all this grief. I don't know Office 2007 is the cause, but I don't
think I'll try it again anytime soon.

Stephen Rasey
Houston

 

[Stephen Rasey]

Performed a install of Vista32 onto the HP dv6000 laptop (that used to have
Media Center) and followed it with a clean install of Office 2003. The
application performed perfectly.

Loaded the application onto a Vista32 tablet running Office 2007. The
application performed perfectly. So it isn't Office 2007 that's at fault.

It had to be something in the original HP load, perhaps with a trial version
of Office that we ignored and installed another one on top of it followed by
Office 2007. Maybe it was the dual install. In any case, I have a
working laptop again and can get back to productive work. Santa Claus came
early.

Stephen Rasey