What's Happening
If you're seeing Error Code 1130 when your orders try to sync into Fishbowl, don't worry - this one's pretty straightforward. It means all of your Fishbowl user seats are currently in use, so the system can't log in to write the order.
How Do I Know This is the Error I'm Encountering
You'll be notified of this failure by email with a subject as follows:
"Order #WEB12345 failed to sync successfully for {Your Company Name}"
The body of the email is where the specific error (statusCode 1130) will be indicated.
Why This Happens
Fishbowl licenses are tied to a set number of concurrent user seats. Every person logged into Fishbowl (and every integration that connects to it, including Kinein) takes up one of those seats. When they're all occupied, anything trying to write data into Fishbowl - like an order coming through your portal - gets turned away with error 1130.
Think of it like showing up to a bar and every seat is taken - you can't place your order until someone frees up a spot. Nothing's broken - you just need a seat to open up.
This tends to pop up during your busiest times, which is exactly when you don't want it. Common triggers include everyone on your team being logged in at once, or old sessions that didn't close properly still holding onto seats in the background.
How to Resolve It
- Free up a seat. This could be as simple as asking someone to log out.
- Ask a team member to log out, or log out of your own session.
- If neither of those is an option:
- Check who's currently logged into Fishbowl. Open the Fishbowl Server program and head to the Connections tab. You'll see a list of everyone (and everything) currently using a seat.
- Look for sessions that shouldn't be there. Sometimes a user closed Fishbowl but their session didn't disconnect cleanly. If you see someone listed who isn't actually working in Fishbowl right now, that's your culprit.
- Disconnect the inactive session from the server. Select the user in the list and click the red trash can on the right.
- Resync the order. Once a seat is available, head back to your Kinein dashboard and resync the order that failed. It should process through without the error this time.
The Scribe below walks you through the resync process step by step:
How to Prevent It Going Forward
- Keep an eye on your seat count. If you're regularly bumping up against your limit, it might be time to review how many licenses you actually need - or consider adding one for integrations specifically.
- Make sure users log out when they're done. Stale sessions are the most common reason seats get "stuck." Encourage your team to close Fishbowl properly rather than just closing the window.
- Set up a session timeout on your Fishbowl server. This automatically clears out sessions that have been idle too long, so ghost sessions don't eat up your seats. You can configure this under Server Menu > Settings.
Still Stuck?
If you're still running into this after working through the steps above, shoot us an email at support@kinein.com and we'll dig into it with you.