MW error on start: Cannot create instance of 'FiltersPreview

[ErikRad]

After upgrading, installing and starting MWPro, I receive the following error message:

Cannot create instance of 'FiltersPreview' defined in assembly 'MailWasherPro, Version=1.0.10.0, Culture=neutral, PublicKeyToken=null'. Exception has been thrown by the target of an invocation. Error at object 'System.Windows.Controls.Grid' in markup file 'MailWasherPro;component/spamtoolsidebar/spamtoolsidebar.xaml'.

I'm running Windows 7 x32 and upgraded from MW6.5.
The DotNet framework is up-to date to release 3.5.

Please advise.

Kind regards,

Erik.

[Sidewinder]

After upgrading, installing and starting MWPro, I receive the following error message:

Cannot create instance of 'FiltersPreview' defined in assembly 'MailWasherPro, Version=1.0.10.0, Culture=neutral, PublicKeyToken=null'. Exception has been thrown by the target of an invocation. Error at object 'System.Windows.Controls.Grid' in markup file 'MailWasherPro;component/spamtoolsidebar/spamtoolsidebar.xaml'.

I'm running Windows 7 x32 and upgraded from MW6.5.
The DotNet framework is up-to date to release 3.5.

Please advise.

Kind regards,

Erik.

Did you install in the same folder as the old version or did you let MWP2010 choose the location?

[nobodyspecial]

Did you install in the same folder as the old version or did you let MWP2010 choose the location?

I don't think that's the problem - I think you need to install SP1 for .net framework 3.5

[ErikRad]

Did you install in the same folder as the old version or did you let MWP2010 choose the location?

I've first chosen a specific location (because I do not want the old Mailwasher to be overwritten yet), de-installed and let Mailwasher choose a location. Both times without any luck.

regards,
Erik.

[ErikRad]

I don't think that's the problem - I think you need to install SP1 for .net framework 3.5

I've got .Net 3.5 SP1 installed. In fact, it's version 3.5.30729.4926 to be precise.

Regards,
Erik

[stan_qaz]

I've first chosen a specific location (because I do not want the old Mailwasher to be overwritten yet), de-installed and let Mailwasher choose a location. Both times without any luck.

The default locations (program, registry or data) of v6 and 2010 do not impact each other so as long as you make no changes to the settings that cause a collision both should be happy to run together.

[rusticdog]

I would try repairing .NET, sadly it's not easy to do in Windows 7

http://blogs.msdn.com/b/astebner/archiv ... vista.aspx


It says Vista, but it's the same process.

Repairing .NET Framework 2.0/3.0 files on Windows Vista

You can use the following steps to repair the files that are a part of the .NET Framework 2.0 and 3.0 on Windows Vista and Windows Server 2008:

1. Click on the Start menu, choose All Programs, then Accessories, then right-click on the Command Prompt item and select Run as administrator
2. Click Continue to authorize opening a command prompt with administrative privileges
3. Run this command in the cmd prompt: sfc /scannow
4. The cmd prompt should list text stating "Beginning system scan. This process will take some time."
5. Wait for the scan to complete (this can take several minutes so be patient). This command will scan all protected system files and replace incorrect versions with correct Microsoft versions
6. When the scan completes, the SFC tool will indicate whether or not it found any problems and whether or not it was able to fix them

[ErikRad]

I would try repairing .NET, sadly it's not easy to do in Windows 7

Code: Select all

Microsoft Windows [Version 6.1.7600]
Copyright (c) 2009 Microsoft Corporation.  All rights reserved.

C:\Windows\system32>sfc /scannow

Beginning system scan.  This process will take some time.

Beginning verification phase of system scan.
Verification 100% complete.

Windows Resource Protection did not find any integrity violations.

C:\Windows\system32>

No error's found. Any other options?

Regards,
Erik.

[rusticdog]

If you can zip and email me your C:\Users\[username]\AppData\Roaming\Firetrust\MailWasher\ folder, will take a look.

[rusticdog]

My layman understanding says this is a problem loading the Language file.

If you place this file in C:\ProgramData\Firetrust\MailWasher\Languages then restart....does that work ? .....if not I'll wait to hear from someone smarter

[rusticdog]

If you haven't done this yet, can you first make a copy of your old Language.xml file


Thanks

[rusticdog]

Ah. Now if the language file doesn't work, go into C:\Users\[username]\AppData\Roaming\Firetrust\MailWasher\ and delete startup.xml, then try again.

[ErikRad]

Ah. Now if the language file doesn't work, go into C:\Users\[username]\AppData\Roaming\Firetrust\MailWasher\ and delete startup.xml, then try again.

The language file did not work, but the solution above got me at least a bit further. Unfortunately (after importing old whitelist) I receive this message:

Cannot create instance of 'MWPMainWindow' defined in assembly 'MailWasherPro, Version=1.0.10.0, Culture=neutral, PublicKeyToken=null'. Exception has been thrown by the target of an invocation. Error in markup file 'MailWasherPro;component/MWPMainWindow.xaml'.

[rusticdog]

Interesting. Send me the MailWasher folder again like you did earlier, again remove your account.xml file.


Many thanks

[ErikRad]

Done