Jump to content

Recommended Posts

Hi,

Does anyone know what error code 4101 means? It just started happening when I try to push an invoice to QuickBooks Desktop using the FM Books Connector plugin v12.0.0.2 (64 bit). The script was pushing invoices fine yesterday.

The error messages appear when initiating a new request and also when adding related record requests (for the invoice lines). The plugin step returns the result 0, as does FMPA 18 if I do a Get ( LastError ), so neither FMPA nor the plugin seem to think there's an error.

Also, I'm seeing a progress bar I've never seen before (see below). It displays for about 20 seconds. I never saw that before today.

This is on Windows 10, QuickBooks Pro 2017, FMPA 18. All are up to date.

I rebuilt the QB data file, ran the QB file doctor (which said no errors found).

Any help is greatly appreciated.

-Kent

178656505_ScreenShot2020-03-05at10_01_36.png.c4db9cdca0b4fbd4735fcd260f62e8ec.png980666452_ScreenShot2020-03-06at11_16_48.png.e3d96b121be69f1fca4b023e37cbe1ef.png

Link to comment
Share on other sites

Hi Kent,

This error indicates a FileMaker or system error generated by FileMaker. The best recommendation is to review and walk through the scripts to find where the error is occurring. As a general rule of thumb, if the dialog box or error box has a red X icon, (i) symbol, or an <!> icon it is a system generated error.

Thanks,

PCIPal

  • Like 1
Link to comment
Share on other sites

Hey PCIPal,

Thanks for the reply. I fixed the problem and think I figured out where the problem was (although I'm not 100% certain). If you don't mind I'd like to run this by you so I have a better understanding of how plugin/QB sessions are handled.

I was beginning the Connector session in a parent script 2 stack calls away from the script that primed the data fields and then posted the request. When I moved the session opener step to a parent script just 1 stack call away from the subscript that executes the post  the problem disappeared.

Does this behavior make any sense to you? All the scripts called were in the same file. Does a session not realize it exists if the post is more than 1 script stack call away? Or is something else going on you can think of?

Thanks again. I appreciate your help.

-Kent

 

Link to comment
Share on other sites

Hi Kent,

As long as the session to QB is opened the number of stacks should not have an effect. There is a chance that something within the stack in between could have caused the connection to end early, or interfere with the data. It is great to hear you got it working though! If you wish to investigate it further, then I suggest closely looking at the second call stack to see if you can spot anything that may cause one of these issues. Also, another option is to view the Windows event logs and, if you are lucky, it could show a bit more information about the error.

Thanks!

PCIPal

  • Thanks 1
Link to comment
Share on other sites

  • 11 months later...
  • Newbies

In case anyone else goes googling this error, I ran into it today, too. This afternoon, everything worked perfectly. Tonight, error 4101. Same FM, same QB, same record, same script, same everything. Except ... in the script I was running, I made a couple edits from a Mac that, of course, can't see all the PCQB functions because it's a PC only plug-in. I didn't touch any lines that referenced the FM Books Connector plug-in, just wrapped a few lines in an If/End If.

I solved the problem by going back into the same script from a PC and editing the script step that triggers the 4101 error (PCQB_RqNew-EstimateAdd) and saved it and voila ... no more 4101. I'm guessing my problem was due to editing from the Mac.

Gordon Shewach

Link to comment
Share on other sites

  • 1 year later...

Thanks @Gordon Shewach. I ran into the 4101 error as well. Like you, I was editing on the Mac side while running on a PC (via Bootcamp on another machine).

For others, here is what happened to me:

This caused the 4101 error

PCQB_RqNew [Select; Results: $rqNew_itemInventoryQuery; Request Type: "ItemInventoryQuery"]

So I commented it out

//PCQB_RqNew [Select; Results: $rqNew_itemInventoryQuery; Request Type: "ItemInventoryQuery"]

And replaced with this:

PCQB_RqNew [Select; Results: $rqNew_itemInventoryQuery; Request Type: "ItemInventoryQuery"]

If it looks the same to you, that's because it is. I did create a new variable and start from scratch, but I think it would be interesting if I had duplicated the line to see if that worked. If it didn't, my next test would be to duplicate the line and make one minor edit (e.g. delete the last "y" and replace with a "y" in Request Type: "ItemInventoryQuery".

@Productive Computing, Inc. seems like there might be enough info here for you to test to see if modifying a script on a Mac results in this error.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
 Share

×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.