Exporting Problem- End Point not initialized properly
I keep on receiving an error message when I attempt to upload expenses to my QB Desktop file. The export is uploading a select amount of entries and then failing on the remainder. Any idea what is causing this error message?
Answers
-
@Brucey, Can you share what the error message says? Do you have any expense reports that are negative from a refund to a credit card? This can make the import not work in some situations.
-
@tylerzoll The expense report does not have any refunds on it.
I have tried to reinstall the sync manager but this also does not resolve my issue either.
-
@Brucey, Sorry I'm not familure with this error, that will definently help someone else in the community or @Sheena Trepanier or @RachCHopkins help out.
-
Rachael Hopkins Expensify Success Coach - Admin, Expensify Team, Expensify Student Ambassador Posts: 904 Expensify TeamHi @Brucey , the most common reason for this issue is a QuickBooks Desktop modal dialogue box being open in the background.
Can you please check that there are no other windows open, minimised or hidden behind anything? It might even be worth closing and reopening QuickBooks Desktop to check.
If you are getting a partial export, my guess is that it's actually presenting an error and opening a dialogue box to tell you about it at the QuickBooks Desktop end, but that box is hidden. Sync Manager sees it has stopped and a box is open, but that's all it can see.
If reopening doesn't help, please let me know, and I'll email you directly to get the log files.
-
@RachCHopkins the latter of the two situations is occurring. I have closed all dialogue boxes and restarted QB several times and I am receiving a partial export.
You can reach me at [email protected] for the log files.
-
Rachael Hopkins Expensify Success Coach - Admin, Expensify Team, Expensify Student Ambassador Posts: 904 Expensify Team
Ok, just for anyone stumbling across this in future: This was caused by the Sync Manager being run in two locations simultaneously with the same token. One by Team A on a remote server, and one by Person B on a local workstation.
The solution was for Person B to remote onto the server and check the Sync Manager and QBD Company File were open, before triggering the sync in Expensify.
The key takeaway from this is that it doesn't actually matter where you hit the Sync Now or Export button from, as long as the Sync Manager and Company File are open on the linked location. You could be in Timbuktu for all Expensify cares, as long as the right stuff is running in the right place.
-
I am having this same issue, however the Sync Manager is only installed in one place. We have several policies and entities setup. I am able to export to one entity but not the other. However I still am getting the same error as above. Please email me, so we can send the log to you for resolution.
Dianne
-
@RachCHopkins can you please look at my comment above and respond? Thank you!
-
@dmcneese_123 I would recommend submitting through concierge. That way someone that is available can take a look at your account.
-
Thank you, I have done that also. Just trying to get someone to answer quickly. I have resolved to being patient.
-
That is very good advice @tylerzoll . Thank you :) When reaching out to Conci[email protected], it is also very helpful to include the logs.
@dmcneese_123Can you open the Expensify Sync Manager, double-click on the version number in the bottom left corner, and send the log file as an attachment in the message thread to Concierge?
