This error indicates that Basecone is unable to open the linked company in AccountView. The issue is typically caused by one of the following:
Insufficient user permissions.
Missing access within the AccountView.NET environment.
A new fiscal year that has not yet been opened.
A company folder path that is inaccessible to web applications.
Cause 1: Insufficient Permissions
Verify Access in AccountView
The user should first confirm that they can:
Open the company in AccountView.
Post transactions within the company.
Access the company through the AccountView.NET environment.
Use the Basecone integration account with sufficient permissions.
How to Check User Access
Open AccountView.
Navigate to File > Companies.
Double-click the affected company.
Open the Users tab.
Verify whether the logged-in user has access to the company.
If applicable, also check the User Groups tab.
Check the Basecone Integration User
In some cases, the general user account used for the Basecone connection does not have sufficient rights on the company.
Verify that:
The Basecone integration account can access the company.
The account has authorization to create postings and perform synchronization tasks.
Review the AccountView Event Log
If permissions appear to be configured correctly:
Open the Event Log in AccountView.
Check for authentication errors or access-related messages.
Verify that neither the user account nor the integration account is being denied access.
Cause 2: New Fiscal Year Not Opened
Verify the Fiscal Year
A new fiscal year must be opened manually in AccountView for each company.
If a new fiscal year has not been opened, synchronization between Basecone and AccountView may fail with the error:
"Company {x}, could not be opened"
Resolution
Open the company in AccountView.
Verify that the current fiscal year exists and is available.
Open the new fiscal year if it has not yet been created.
Run the synchronization again from Basecone.
Cause 3: Company Folder Path Not Accessible
Verify the Company Folder Path
A common cause of this error is that the company files are stored in a location that is not accessible from web applications.
How to Identify This Issue
Open File > Companies.
Locate the Company Folder column.
Incorrect Configuration
The company folder path uses a local drive letter:
Plain Text
1
X:\ACCOUNTVIEW\ADM\2025\250
Meer regels weergeven
Correct Configuration
The company folder path uses a UNC network path:
Plain Text
1
\\SERVERNAME\Share\ACCOUNTVIEW\ADM\2025\250
Meer regels weergeven
UNC paths are required because web applications cannot reliably access mapped drive letters.
Changing the Company Folder Path
Open Edit > Change Company Folder.
Replace the mapped drive path with the corresponding UNC path.
Save the changes.
If You Receive "Folder Not Found"
When entering the new UNC path, you may receive the message:
"Folder not found"
Follow these steps:
Enter only the root UNC path first.
Example:
Plain Text
1
\\SERVERNAME\Share
Meer regels weergeven
When prompted:
"Should this folder be created?"
Select No.
Open Change Company Folder again.
Enter the remaining part of the path.
Example
Original path
Plain Text
1
SERVERNAME\Share\ACCOUNTVIEW\ADM\2025\250
Meer regels weergeven
First step
Plain Text
1
\\SERVERNAME\Share
Meer regels weergeven
Second step
Plain Text
1
ACCOUNTVIEW\ADM\2025\250
Meer regels weergeven
Troubleshooting Checklist
Before escalating the issue, verify the following:
The user can open the company in AccountView.
The user can post transactions in the company.
The user has access within AccountView.NET.
The Basecone integration account has sufficient permissions.
The AccountView Event Log does not contain access-related errors.
The current fiscal year has been opened.
The company folder uses a UNC path (
\\server\share) instead of a mapped drive letter.Synchronization has been retried after making any changes.
Support information
If the issue persists after completing all checks:
Contact:
Your organization's AccountView administrator.
Your Visma partner or Visma reseller responsible for the AccountView.NET environment.
Please include the following information:
The complete error message.
The company code or company name.
The company folder path.
Screenshots of any error messages.
The date and time when the issue occurred.
Summary
The "Company {x}, could not be opened" error is most commonly caused by:
Missing permissions for the user or Basecone integration account.
A fiscal year that has not yet been opened in AccountView.
A company folder path that uses a mapped drive letter instead of a UNC path.
By verifying permissions, opening the fiscal year, and ensuring the company folder uses a valid UNC path, the issue can usually be resolved without further escalation.