What the hell is ioibmurhynrxkw0zxkyrvfn0boyyufow?!!!

[FunkyDexter]

OK, I develop a telemarketting app that comes in two parts. There's a Telemarketting app and an Admin app.

I recently changed the development enviroment from VS 2005 to VS 2008 and when I did the last roll out the Admin app installer popped up a message saying that it now required the 3.5 framework. I'm really not sure what introduced the new dependency because the only change in the new version was an additional checkbox on a form along with the ammended code to read and write the assosciated value back to the DB - nothing that isn't done a thousand times already elsewhere in the app.

I didn't particularly let that worry me though because the whole point of upping to 2008 was to use some of the new features and that means sooner or later we'd need to upgrade the framework on the target machines anyway. So the IT Support guy here grabbed the 3.5 framework download. He installed it on our test machine and everything was peachy and extracted the contents and deployed the msis through group policies. Immediately he did this the telemarketting app (which is a bit business critical) started keeling over and refuses to start. We've got round the problem for now by reverting the target machines back to 2.0 so there's no panic but this does leave me unable to roll out the admin app.

The error we get when trying start the telemarketting app reads:-
EventType clr20r3, P1 telemarketing.exe, P2 1.0.0.75, P3 48bfec57, P4 system.configuration, P5 2.0.0.0, P6 471ebf00, P7 27b, P8 a, P9 ioibmurhynrxkw0zxkyrvfn0boyyufow, P10 NIL.
I don't have experience of reading these but from googling a bit I gather that the error message is contained in P9 - so the error is:
ioibmurhynrxkw0zxkyrvfn0boyyufow

That looks like garbage to me but I was surprised to see that googling it returns lots of results and the general theme seems to be that it's a corrupt config file. We've grabbed a config file from a target machine and put that on the test machine and it worked fine - which implies that the config isn't the problem.

At this point I'm stumped. can anyone suggest what we should be checking next?

[.paul.]

Telemarketting?

[JuggaloBrotha]

I would help, except telemarketing is the most annoying this about having a home phone, which unfortunately DSL requires. So in the name of my internet connection... good luck.

[mattwise40175]

Look to see if .UseCompatibleStateImageBehavior = True or False and comment the line out and see if that fixes it.

[dbasnett]

from Microsoft

Cause
The user.config file may be corrupted. This file is generally found in the folder
"...\Documents and Settings\<user>\Local Settings\Application Data\<application_name>\...\user.config"

Resolution
Delete the user.config file and let the application recreate it.

[kmoorman]

FunkyDexter,

I don't have a solution to your particular problem.

But I will point out that with VS2008 you can target a particular framework. It sounds like your app could target the 20.0 framework and not need to deal with the 3.5 framework at all, if that is the source of the problem.

Kerry Moorman

[RParkes]

The guy at this link:
http://jimbobmcgee.wordpress.com/200...rvfn0boyyufow/

Fixed his error by checking his syntax in the appSetting entry. There was an ampersand (&) in it, which is a reserved character in XML.

I don't know if this will help you...

[FunkyDexter]

Yeah, I knew I was taking the devil's sovereign when I took the job but, honestly, I'm trying to bring the system down from within. Thanks to my unflagging efforts to introduce ropey code, bad practices and general managerial malaise, you are now considerably less likely to be successfully phoned by this application than when I picked it up a year ago.

.UseCompatibleStateImageBehavior

I haven't come across this previously so I'll have a google and see if it'll be useful. Thanks.

@DBasnett and RParkes. I'd found both those pages on my initial search and they prompted me to get a copy of the config from one of the machines that was failing and try it out on the test machine. On the test machine the app works fine even with the config file from a failing machine so I actually don't think the config file is the problem. Thanks for the input though - I'll see if I can get to a failing machine today and delete the existing config so it can be recreated on the off chance.

with VS2008 you can target a particular framework

That may not solve the underlying problem but it does provide me with a good fall back position and I hadn't thought of it. I'll put a bit more time into trying to sort out the underlying problem I think but if I can't find a good solution by the end of the today I'll probably do as you suggest so I can get the roll out done. Thanks.



edit>MattWise, .UseCompatibleStateImageBehavior seems to be a property on a list view from what google tells me. I'm not sure I understand what you're getting at with this. Could you explain a bit further please? Thanks