I am not sure what the existing version was, but I tried downloading and installing the latest version I could download from the website. I first tried installing over top, then uninstalling from windows and reinstalling, then uninstalling and removing all registry entries and folders (except what I found in the winsxs folder). Then I found a link to a newer version in a post by a guy with a similar system.drawing thing, but different problem, so I did the same things with that version. The error reports indicate the current version is eM Client (6.0.21151.0)
Yes, EM Client has worked correctly in the past. To be clear, I do not use windows so my primary email client is not em client, but I have some clients who use it so I keep it on a vm for testing. it has been several months since I last tried to use it, and I kind of think I couldn’t get it working then either, but I did have it working on this VM at one point, for sure.
the VM is virtualbox 4.2.26.
For grins and giggles, I fired up an old old VM of win7, downloaded EM Client, and it installed and worked just fine there. Unfortunately that provided zero enlightenment as to ow to fix it on this VM.
I have ensured all windows updates are in place, I have tried windows safe mode, I have tried running in elevated mode, I have tried all sorts of different compatibility modes, I have tried multiple screen resolutions. all produce the same error.
I get the feeling looking through the error that the problem is probably related to the .net framework, so I tried a repair on that and checked for updates, but that also did not fix the problem. it is currently 4.5.1.
Hi Bob, does the application keep showing this error while you’re using the application or is it displayed after an application crash?
Can you please make a screenshot of the error or copy the content of the error after the crash report window is shown?
The application will not open, all I get is an error report after checking the database:
eM Client (6.0.21151.0)Windows: Microsoft Windows NT 6.1.7601 Service Pack 1, Framework: 4.0.30319.18444
The following error has occurred:
System.ArgumentException: Parameter is not valid.
at System.Drawing.Font.GetHeight(Graphics graphics)
at System.Drawing.Font.get_SizeInPoints()
at System.Drawing.SystemFonts.FontInPoints(Font font)
at System.Drawing.SystemFonts.get_MessageBoxFont()
at MailClient.UI.Forms.ThemeForm…ctor(Boolean ignoreTheme)
at MailClient.UI.Forms.BorderlessForm…ctor()
at MailClient.UI.Forms.formMain…ctor(List1 arguments) at MailClient.Program.CreateMainForm(Boolean startupInit, List1 args)
at MailClient.Program.Main(String[] args)
Hi Bob, I’m sorry for my belated reply, however it seems like this issue is not actually related to eM Client rather than a system issue that might be related to use of some custom themes/fonts on your computer?
Are you aware of using such utility on your computer?
belated or not, thank you for taking the time to reply. I do appreciate it.
As stated before, I do not “use” this VM, it’s only real function is for testing and configuring software, such as em client, so I can do phone support and generally learn what I need to know before I show up to fix something for a client. As such, I have not installed any software on this machine that hasn’t also been installed somewhere else. Regardless, I take your point that something could have gotten installed somehow. The only thing in the programs list that I would identify as malware is outlook 2013, but to be sure I ran a scan with malwarebytes; it found a few things but removing them did not solve the problem.
I checked the themes in the control panel; the VM is running the default windows 7 basic theme and I see only three themes installed, and they all look like native default ones. I also checked the fonts; I am not sure how to identify any misbehaving fonts, but I found a button called restore default font settings and clicked it, but that also made no difference to the startup procedure or error message.
I would also mention that I am able to reproduce the problem when the VM is booted into safemode with networking. Same failure to start and same error. Perhaps my reasoning is flawed or lacks some bit of information, but I believe this to mean that the problem is not likely to be another program, and if it is due to a setting I have configured in windows, it is most likely something very fundamental in order for the setting to get loaded in safe mode.
One thing I can say that is different about this machine is that is is joined to a domain (also a testing thing). Given the nature of the error message and the fact that no other program fails to start, I don’t see how this could be the problem, but I would be remiss in not mentioning it…
Hi Bob, I have discussed the issue with the developers however what the crash report states is that system features are causing this crash on your device, which means we’re unable to resolve the issue from our side.
I’m sorry I couldn’t be more helpful in resolving the issue, however I personally still believe this might be related to the VM instance, did you come across this issue on any other computer where the application wasn’t installed on a virtual machine?
Can you try to setup a new database for eM client, if the issue persists or if it’s related to your current database? To setup a new database, please navigate to your local folder > app data > roaming and rename or remove the eM Client directory, next time you open the application a new database should be automatically setup.
Hi Bob, I have discussed the issue with the developers however what the crash report states is that system features are causing this crash on your device, which means we’re unable to resolve the issue from our side.
Is this the very top part that actually states the parameter is not valid, or is there some other clue in that pile of text that leads to the conclusion the problem is in the system and not the program? Maybe if I am pointed at what the problem actually is I can spend some time trying to figure it out…
I have not seen this particular error on other machines, no, but in another VM instance (a much older one I no longer use), using the same version of Virtualbox, a fresh install does not have this problem.
I have also tried deleting the folder in appdata, I found that as a possible fix before I posted the first time. I tried before and after installing, and again after removing all traces of em client from the registry after an uninstall and all folders that were not deleted by the uninstall.