Jump to content

Error Message help


avmad

Recommended Posts

I've had some pc probs lately and fixed most. I've been running sfc scannow, and XP manager repair, disk check and cleaning of useless files etc. :rolleyes:

Now when I try to run Mailwasher Pro I get an error. It starts and checks,displays my emails but as soon as I try and click on them I get this error.

The type initializer for 'system.windows.automation.invokepatternidentifiers' threw an exception

I've tried searching but didn't come up with much that seemed relevant :blink: Replies were completely different depending on the software. Most of which I didn't understand anyway.

Anyone have any clue on how to fix it? I can only think maybe some system file wasn't installed correctly, or something was removed. No idea :s

Link to comment
Share on other sites


  • Replies 7
  • Views 2.7k
  • Created
  • Last Reply

Try this for info.. http://msdn.microsoft.com/en-us/library/system.windows.automation.invokepatternidentifiers.pattern%28v=VS.85%29.aspx

Seems that part of the UI automation is not working properly could have been a folder or registry entry that was cleaned or something like you said.. Have you tried reinstalling the application after cleaning it and all parts of it from your computer?

EDIT: This link.. http://msdn.microsoft.com/en-us/library/system.windows.automation%28v=VS.85%29.aspx Seems to point to .Net Framework problems.. In XP you are in luck... as you can uninstll and reinstall them... and I have accidentally screwed up .Net in XP before trying to cleanup what I thought were duplicates and useless installations.. which some were.. but.. you get the point.. LOL

Link to comment
Share on other sites


Thanks for the suggestions. I tried uninstalling all Net Frameworks and reinstalling, damn things why have so many different versions and updates and service packs lol.

Now windows update keeps telling me to install 2 more but they keep failing to instal.

This didn't fix it though.

Im not bothered about Mailwasher but I thought maybe if that won't work there may be other more important software that won't also.

Link to comment
Share on other sites


Well if your .Net Frameworks are spotty.. you can BET on having redundant cataclysmic failures in programs.. The one that had the death of .Net Framework 2.. would not open MMC, anything event viewer related and I received nothing but errors on trying to open any program that relied on or was indirectly reliant upon another component relative to it.. I tried everything to repair it. in Windows Vista and Windows 7 however .. you can't just reinstall.. or uninstall and reinstall... they are part of the OS.. integrated.. something goes wrong there ( like messing around with IIS ).. You cause almost complete system failure.. It may boot and run some things but you are limited on what... I even tried re-registering all DLL's and .Net's.. files were present and original.. but it wasn't having it..

My thoughts came down to doing upgrades with the WebPlatform Installer for IIS 7.5.. which changes a few things in areas concerning them and not really knowing enough yet to properly secure or program for them.. So a guess.. Next was in Local Security or Group Policy.. changes here could deny access to them.. However.. the problem with that is to even apply a change or template alteration... You have to be able to run it ( LSP/GP ) guess what it relies upon? That's right.. the 100 dollar question.. .Net Framework and Components.. so you wind up in a place not good..

The first thing that happened to mine by surprise was the disappearance of the list of accounts on my Login Screen... All Pictures disappeared.. and the only one large Account box remained.. where you had to enter in an Account Name and Account Password.. I thought maybe I had done it until I did a little digging.. and found that these settings were in the LSP... I adopted it into both systems.. because I liked the idea... Worked for me.. not only would someone have to find a password name they would also have figure out a account...

I would try once more with the packages.. start with 1.1.. I believe.. and install the first packages of 2,3 and possibly 4..( introduction of 4 was when I started to have issues in XP, I don't know why.. ) then run Microsoft Update and see what happens... The only complication I could see coming from that is having any updates that effect them.. that are not directly listed as service packs or updated for them.. My tired coding eyes in this sort of thing always tell me to just pull my files and reinstall.. wipe the drive.. that sort of thing and start fresh... Just like the problem I am recovering from now.. after you spend three days trying to fix something that may or may not fix.. its just time to let it go...

There are some areas which would be nice for MS to 'improve' along these lines.. A lot of people always say, ' Why would they mess with it and what could go wrong.. ' but I am sure that's what they said about the Titanic.. oh wait.. they said that about MACs.. :o and ... wait for it.. Linux :o .... a component should not be able to cripple a system the way it does.. and if so imperative should have a ready fix..

Sometimes I think its an exploitation... that has come into play either remotely.. or otherwise. possibly even through other programs not really intended to make the mistake... But the last thing I need is to be running around thinking I have been hacked... ( Possibly even the last thing the rest of the planet needs too..LOL )

Link to comment
Share on other sites


Finally fixed the issues. :o Mailwasher started working again, only thing that happened was an xp security update, maybe it did the trick.

Still couldn't get the 2 updates done for .Net Framework. Was thinking about reinstalling again but found Microsoft Fix It, (little guy with the spanner) :D didn't think it would help but I ran it and tried the updates again, went straight in :o

Hoping it stays fixed for a while now, trying to put off upgrading to 7. Hoping I can afford a new pc before I have to do that (doubt it) lol.

Thanks for the help HX1 B)

Link to comment
Share on other sites


  • Administrator

O.T.

You don't "really" need a new PC to run Windows 7. :)
Link to comment
Share on other sites


I know but this ones dying slowly :blink: I don't want to speed up its death :D 2005 I think lol. Besides, I like XP :P

Link to comment
Share on other sites


Yeah there have been some major changes since then.. Just like the one I am using now... Even with supposedly powerful enough hardware... ( which I don't have really IMO ) there are aspects that need support for to really enjoy and get the most out of Windows 7.. BUT.. I mean I installed Windows 7 Ultimate on a 2001 HP 360n.. it runs... and does most things just fine.. BUT.. LOL ( and is slow in a few areas )

Good to know you got it worked out Microsoft Fix-it sometimes can be a life saver.. :thumbsup: always good to remember.. :)

Link to comment
Share on other sites


Archived

This topic is now archived and is closed to further replies.

  • Recently Browsing   0 members

    • No registered users viewing this page.
×
×
  • Create New...