Problem with Simply Accounting 2012, Windows 7, and Database Connectivity Issues

After virus removal on an infected PC, SA2012 was not working.  It looks to be ODBC connectivity issues as I get a timeout when trying to access local files.  I have done the following:

  • ensured all Windows 7 settings are back to default using Windows Repair (from tweaking.com)
  • SA2012 fully uninstalled
  • ODBC connections removed, ODBC files uninstalled
  • relevant registry entries removed (ensure ODBC is starting from scratch)
  • .NET 4+ uninstalled, .NET feature is removed and re-added from Windows 7 features
  • User account controls set to "no notifications" -- I assume this is admin all the time
  • Ensured install of SA2012 was done using admin rights (not sure if needed with above bullet)
  • followed KB articles to ensure latest mySQL ODBC is installed
  • Cannot open example company file or start a new file with either the old install or the fresh install -- same timeout issue
  • Verified that the connection manager is working and tried to stop/start this service
  • Tried to telnet to the port for connection manager but this failed
  • Windows is currently not activated -- not sure if this would cause an issue

What I notice is after I do the new, "clean" install that no ODBC connections are created.  There used to be entries in the ODBC control panel app, but since I've removed them, they are not added back with the fresh install.  I also don't know if I need to manually add these (and how) and whether this would help.

I am trying to avoid a fresh install of Windows, but I'm currently stuck thinking this is the only next step, however I don't want to impact my customer's personal/professional computer with this large an impact.

Any ideas/suggestions please?  As the person who helped with the virus removal, I am also feeling very responsible for breaking my client's computer and subsequent business tools.

  • 0

    Have you looked at the firewall on the workstation to make sure the proper programs are allowed through?  There is a Knowledgebase article on it but I usually start with mysqld-nt.exe and the Simply Accounting program first.

    Have you tried to open the sample file to see if it works and repopulates the ODBC DSN list?  Sounds like it might not work but worth a shot after you check the firewall.

    Once you see the Simply Accounting: Last Opened. DSN, can you click on configure and see the information?

  • 0 in reply to Richard S. Ridings

    Thanks Richard for your thoughtful reply.  I was initially troubleshooting antivirus and firewall issues before I did all of the above.  I didn't come back to it but will.  I am only running Microsoft's Security Essentials for antivirus and the built-in Windows firewall.  I did a quick test of killing the antivirus services and turning off the firewall.  Now that I did the whole reinstall thing, I'll validate the firewall rules as you suggest and add all the exceptions as given in the KB article.  As I'm opening the file locally, I also wondered if there would be less of an impact from a firewall perspective.  I wasn't sure if the firewall got involved in inter-process communication.

    I cannot open the sample file as it gives me the same error.  Are there instructions for populating the DSN entries  manually?

  • 0 in reply to MKD

    I don't remember when they show up as DSN's but I think they will only show up after opening a file properly, so start there.

    There are no instructions but if you can hit add and select the MySQL driver, you should be able to put anything in as a name and hit Ok.  If you can get it to save then the driver is installed correctly and you the program should create the rest as needed when the file is opened properly.