Author Topic: Plug-in not working with FileMaker 12 - QuickBooks already running.  (Read 1447 times)

andre.filemaker

  • Member
  • *
  • Posts: 1
Hi all!

I'm facing a very awkward situation. I have QuickBooks 2012 running on Windows 8. I'm using the plug-in demo file to connect FileMaker to QuickBooks. FileMaker 12 always returns an error when I press the test button saying that QuickBooks is already running. So far nothing special. The issue is that I'm able to run the plug-in just fine using FileMaker 11 on the same PC. It's probably not a configuration matter then. Productive Computing told me QuickBooks 2012 was not compatible with Windows 8 (despite having the plug-in running with FileMaker 11). I gave QuickBooks 2013 a try and still the same error. FM 11 works, FM12 does not. I re-installed FileMaker and QuickBooks. Updated both but no luck so far. Any thoughts?

Kevin Clemons

  • Member
  • *
  • Posts: 65
    • Productive Computing
Re: Plug-in not working with FileMaker 12 - QuickBooks already running.
« Reply #1 on: January 17, 2013, 01:37:35 PM »
Hi Andre, are you using the FileMaker 12 version of the demo or a converted FileMaker 11 demo?
If you are using a converted demo try with the Demo file made for FileMaker 12 and let us know if you get the same results.
Kevin Clemons
Products Support Specialist

950 Boardwalk, Suite 205
San Marcos, CA 92078
760-510-1200 xt.105 (voice)  760-510-1991 (fax)

Follow Productive Computing, Inc. on Twitter or FaceBook for the latest updates and product versions.

johnlewisdesign

  • Member
  • *
  • Posts: 81
Re: Plug-in not working with FileMaker 12 - QuickBooks already running.
« Reply #2 on: February 08, 2013, 04:46:57 AM »
It could also be that you have two versions of QuickBooks installed, say 2011 and 2012, as I just had the same thing. For instance I had 2012 open and it tried to open 2011.

Another thing to rule out - Ctrl-Alt-Del and go into task manager, and ensure QB has correctly quit. I still saw Quickbooks.exe (or whatever its called) was still running as a 32 bit process. I ended it, no more issues. This was after the version confusion of having 2011 and 2012 installed.

HTH