Owner: SupportLast updated: Jul 16, 2026Status: LiveReviewed by: DanHub: v3.5
LiveNetwork Edition / Multiuser Issues
Fast triage for lock files, host/workstation access, FileConnect browsing/update prompts, one-user-at-a-time multiuser symptoms, NE connectivity/firewall/antivirus troubleshooting, plus a dedicated FileConnect troubleshooting section (crashes on launch, won't stop, connection errors, reinstall/uninstall).
Lock file issue2 items
Error upon opening CF "Someone with this user ID is already signed in"
What to do
Solution will be the same for ALL lock file issues. 1. Have all users log out of AE and close AE completely 2. Go into where the CF is located and delete any access01.flk or lock0001.flk files 3. Have the user who couldn't log in before, log in first. 4. Have the rest of the users log back in.
Error upon opening CF "File may be locked or in use or access privileges may be incorrect"
What to do
Another option is to have all users log out and restart the host machine. Once host is restarted lock files should be gone but incase they aren't, delete them.
NEX/Win NE issues1 item
WS receives the message upon clicking Browse that they should update their File Connect version
What to do
They have a firewall that's blocking internal connections on that workstation. They either need to turn the FW off or make an exception within the firewall - no we dont touch the firewall, their IT needs to do that.
Connectivity, firewall & antivirus troubleshootingMac & Windows
Antivirus or firewall software can block a workstation from connecting to the host, or block the host from opening its own files -- typically by blocking FileConnect's local network access. This can also happen if the network itself changed recently (loop in IT if so).
FileConnect Troubleshooting
Issues with the FileConnect utility itself -- crashing on launch, refusing to stop, connection errors, and clean uninstall/reinstall. For everyday setup and installation of NE/FileConnect, see AccountEdge Network Edition -- Setup.
FileConnect closes/crashes after launchMac
1. Verify file permissions
Full Disk Access (macOS): System Settings > Privacy & Security > Full Disk Access -- ensure AccountEdge NE is enabled.
Local Network Access (macOS 15 and above): System Settings > Privacy & Security > Local Network -- ensure both AccountEdge NE and FileConnect Browser are enabled.
2. Check for background instances using Activity Monitor
Attempt to launch FileConnect. If it still shuts down:
- Open Activity Monitor (magnifying glass, top right > search Activity Monitor).
- From the top menu, click View > All Processes.
- Use the search bar (top right) to search for FileConnect.
- If found, select FileConnect from the list and click the "X" icon in the top menu bar.
- Select Force Quit to terminate any background instance occupying the required socket.
3. Restart FileConnect
Launch FileConnect again and check whether it now stays open and functions as expected.
4. Configure a custom port (if the issue persists)
- Go to System Settings > AccountEdge > FileConnect > Port Number.
- Enter a value between 0 and 65535 (e.g. 49745) and click Apply. The port can't already be in use by another app on the Mac.
- Restart FileConnect.
- Once FileConnect is running: open AccountEdge, click Browse, and when the FileConnect window appears, manually enter the IP address and the custom port just configured, then click Connect.
- Log into the company file and confirm the data is now accessible.
FileConnect could not be stoppedMac
If FileConnect can't be stopped and the message "FileConnect #### could not be stopped" appears, possible causes include: users still connected to a company file on this machine, a user has their Company File Browser open with this host highlighted, or AccountEdge Network Edition crashed or quit abnormally.
Things to try
- Make sure everyone is out of all accounting files located on the machine running FileConnect.
- Make sure no user has the open-file window open with this host computer selected in the list.
- Restart the host computer once everyone is confirmed logged out -- this typically resolves it.
NoteAdministrator rights are required to start or stop FileConnect.
If System Preferences won't turn it off: quit via Activity Monitor
- Ensure all users have quit AccountEdge Network Edition.
- Applications > Utilities > Activity Monitor.
- Choose All Processes from the top dropdown.
- Find FileConnect or AccountEdge File Connect in the list and select it.
- Click Quit Process (top left), then Quit. If it doesn't quit, repeat and choose Force Quit instead.
- Go to System Preferences > AccountEdge and click Turn on FileConnect to restart it.
Error connecting to hostMac -- firewall/port
"An Error Occurred While Trying to Connect to This Host" is most often caused by a firewall blocking the port FileConnect is using.
- On the host, open the AccountEdge pane in System Preferences and click the Port Number tab. If it shows 0, FileConnect is dynamically choosing a port -- either disable the firewall on the Macs involved, or assign a specific port number and open that port on every Mac's firewall.
- To configure a Mac's firewall: System Preferences > Security > Firewall tab. Check whether the firewall is on, and if so, confirm the port number from the AccountEdge preference is open on it.
Reinstalling / uninstalling FileConnectMac & Windows