First run of SnowieApp causes SQL error when using MPN screenname. HEM crashes.

[arty smokes]

Hi,

I just did the HEM auto-update and wanted to have a look at the new SnowieApp, but when I clicked the box to start the 15 day trial, I got a pop-up error "Holdem Manager has encountered an internal SQL error". Clicking 'Cancel' just shuts down HEM. If I restart the program, the same error message comes up and none of the standard HEM features are accessible.

I'd guess one possible cause for this is that the screenname I was using when I booted up was one for MPN (aka Prima/Microgaming) which I don't think is supported by the SnowieApp. The problem is I can't switch to my Pokerstars or 888 screenname, because HEM pops up the same SQL error message every time I reboot it.

Do I have to roll back to an earlier version of HEM and then reinstall again, but make sure I'm on a compatible site/screenname when I next try and start the trial?

[fozzy71]

Please try to vacuum/analyze and reindex (http://hm2faq.holdemmanager.com/questions/5/Database+Manager+%28Ribbon%29#maintenance) your database.

If you continue to have problems, try the following:

Try creating a new DataBase and import a small portion of your \HM2Archive (http://hm2faq.holdemmanager.com/questions/3091/How+to+create+a+new+database+and+import+previously +played+hands) so you can see if the problem exists in the new DB.

If the new database seems to work properly, it sounds like your database might be corrupt. Please continue to use the new database and import the rest of your hands using the steps above. This is why regular backups are a good idea. If your database becomes corrupt you can restore a backup and only have to import the most recent hands (that were played after the backup was created) and edit any tournament results if necessary. I recommend keeping at least the most recent 2 or 3 backups in case the most recent one does not restore properly you can try the previous backup.

Here is a FAQ (http://hm2faq.holdemmanager.com/questions/1471/How+does+Backup+and+Restore+Database%2C+Settings+a nd+HUD+configs+work%3F) explaining how to backup your database and all settings in one easy step.

If you continue to have problems please zip and email the problem hand histories, with a link to this thread and your forum name, to us using the 'Contact Support (https://support.holdemmanager.com/support/product/1)' link.

All original hands that are auto-imported get moved to an archive for performance reasons. Your \HM2Archive is in C:\HM2Archive by default, but you may have put it anywhere. The archive should be organized by \Month\DayOfMonth e.g C:\HM2Archive\2009\07\31 or if it was auto-imported with v7283+ it would be in C:\HM2Archive\SiteName\YYYY\MM\DD.

When sending any files please zip them (right-click > send to > compressed folder) before attaching them to an email. If the attachment is larger than 10MB please upload them to a file hosting site like dropbox, then 'copy public link' and paste the download link directly into the support ticket via the 'Contact Support (https://support.holdemmanager.com/)' and if there is a forum thread with additional information please link to this thread and let us know your forum name if there are several people in the thread.

Also include the following log files:

SnowieApp only supports NL Hold'em cash games. Please make sure that such hands are showing in your active HM2 database.

SnowieApp will automatically attempt to import hands from your HM2 database every 5 minutes.

If after 5 minutes hands from your HM2 database don't show inside SnowieApp, please follow these steps:

1) Open HM2, go to Settings > Featured Logging and enable the HMApps option and increase number of saved log files to 10. Click OK and restart HM2.

2) After restart go to SnowieApp tab and click Resend hands button. Please wait 10 minutes to let SnowieApp attempt to analyze the hands.

3) If hands will not show up after 10 minutes, close your HM2 and submit the log files - https://support.holdemmanager.com/

4) If hands show up you can disable logging that was enabled in Step 1.