Re: Exchange tools

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I just tried to acquire the HKCRScan.exe tool via MS PSS and they wanted to
charge me the full $245 for a support call to acquire the tool - a tool
designed to find a known problem in a Microsoft product. Unacceptable.

Not only that, but the support technician had such a heavy Indian or Sri
Lankan accent I could barely understand her.
 
There is a difference between a hotfix (free) and a support case to obtain a
tool. The tool itself isn't a "hotfix", which is probably why they wanted
to charge you.

Have you checked Google?
 
You have already mentioned this KB
http://support.microsoft.com/kb/823159
You can always manually go through the HKCR yourself...but that is not fun.

You can always open the support call for the 503 error and not the tool
specifically. Then, Microsoft will work to resolve the 503 error and you
can request the tool as part of the process. I suggest asking for someone
in Canada, Los Colinas (Dallas), or Charlotte to assist you with the 503.

Some tools are free (rock) and some tools you have to buy (Hammer at Home
Depot). The rock and the hammer can both bang in a nail. Both require you
to be cautious with them. However, I have never turned my thumb purple from
a rock missing a nail. Then again, I have only done it with a hammer once.
The 2nd time it turned a deep red. Such is the norm for soft tissue
damage... Then again, a good hammer, like the Resource Kit, is less than
$30...and at $245, it better do the job itself.

Bob
 
Google wasn't any help. The only relevant info it pointed me to regarding
this tool was the posting I replied to.

This client is the local school district and they just don't have the funds
to fork over $245 for this. I guess I'm going to have to write a short
VBScript to parse the registry looking for values in excess of 259
characters.

As a side note, I have experienced this problem previously at a different
client (when the HKCRScan.exe tool was not even an option) and after
manually going through the registry myself, found there were no keys
exceeding the magic number so there very well could be another cause of the
issue.
 
Back
Top