Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: hfm.exe
Problem Signature 02: 0.4.8.121
Problem Signature 03: 4b440cf8
Problem Signature 04: System.Configuration
Problem Signature 05: 2.0.0.0
Problem Signature 06: 4a275e0d
Problem Signature 07: 1a8
Problem Signature 08: 75
Problem Signature 09: IOIBMURHYNRXKW0ZXKYRVFN0BOYYUFOW
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 2057
Here's the Microsoft KB Article on what I think the problem is.
http://support.microsoft.com/kb/956762
Although on XP, I have reproduced an almost exact error signature by
mangling the user.config file as suggested in the above KB article.
Based on that information, let's do the following:
Find the following folder:
* XP: C:\Documents and Settings\<username>\Local Settings
\Application Data\harlam357
* Vista / Win7: C:\Users\<username>\AppData\Local\harlam357
And delete the user.config file found in it. This will wipe any user
settings and regenerate them from the defaults.
Restart HFM and see what happens. :-)
On Feb 3, 2:52 pm, harlam357 <harlam...@gmail.com> wrote:
> Hi Sir-Les,
>
> Here's the Microsoft KB Article on what I think the problem is.http://support.microsoft.com/kb/956762
> > Locale ID: 2057- Hide quoted text -
>
> - Show quoted text -
Here's a couple more error signatures that denote the problem:
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: hfm.exe
Problem Signature 02: 0.4.10.156
Problem Signature 03: 4ba1712b
Problem Signature 04: Castle.MicroKernel
Problem Signature 05: 1.0.3.0
Problem Signature 06: 46f2e4dd
Problem Signature 07: 1a
Problem Signature 08: e2
Problem Signature 09: WM0DLCLN0FFELNNYQUIWRCMEAUTRMMW2
OS Version: 6.1.7600.2.0.0.768.3
Locale ID: 4105
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: hfm.exe
Problem Signature 02: 0.4.10.156
Problem Signature 03: 4ba1712b
Problem Signature 04: Castle.MicroKernel
Problem Signature 05: 1.0.3.0
Problem Signature 06: 46f2e4dd
Problem Signature 07: 1a
Problem Signature 08: e2
Problem Signature 09: WM0DLCLN0FFELNNYQUIWRCMEAUTRMMW2
OS Version: 6.1.7600.2.0.0.256.1
Locale ID: 1033
On Apr 6, 9:14 am, harlam357 <harlam...@gmail.com> wrote:
> It also seems as if this issue is isolated to Windows 7...
So you haven't rebooted, but you have stopped HFM and then attempted
to start it again. Is this the first version you've installed, or
have you upgraded from previous versions?
I've just spent quite a bit of time looking into this... and again, I
can reproduce the error with an errant user.config file no sweat, and
I still believe that is the issue. For anyone who cannot get rid of
this start-up error, please find the following folder.
Find the following folder:
* XP: C:\Documents and Settings\<username>\Local Settings
\Application Data\harlam357\HFM.exe_Url_<randomstuff>
* Vista / Win7: C:\Users\<username>\AppData\Local
\harlam357\HFM.exe_Url_<randomstuff>
There may be several version folders beneath this folder. To be
absolutely sure you nuke all of the user.config files. Delete the
folder HFM.exe_Url_<randomstuff> itself. Now see if HFM will start
for you.
Description:
Stopped working
Problem signature:
Problem Event Name: CLR20r3
Problem Signature 01: hfm.exe
Problem Signature 02: 0.4.10.156
Problem Signature 03: 4ba1712b
Problem Signature 04: Castle.MicroKernel
Problem Signature 05: 1.0.3.0
Problem Signature 06: 46f2e4dd
Problem Signature 07: 1a
Problem Signature 08: e2
Problem Signature 09: WM0DLCLN0FFELNNYQUIWRCMEAUTRMMW2
OS Version: 6.0.6002.2.2.0.768.3
Locale ID: 1033
Please email me, I have an alternate build I'd like you to try. You
can find my e-mail address here in the Google Group. It's just my
screen name @ gmail.com. Once we're hooked up I'll send you a URL
where you can download the alternate build. It's the same R156 code
except I've put an error handler around the startup sequence, so it
should catch whatever is happening and at least give us a message box
with the stack trace. It's crude, but it's the best option I can
provide right now. Once I see the stack trace I'll be able to tell
where and what is going on.
Thanks for your help,
-H