A short guide for error handling and limitations in the current implementation with
recommendations for solutions and workarounds.
Issues when enabling Master Data ManagementCould not enable Master Data Management. Please check
Visma.net settings
Check the following:
- Corresponding companies are existing in Visma.net
- Visma Cloud Gateway (tidl. Visma On
Premises Gateway) service is running and accessible
- The network connection is active.
Visma Business Services Host for SyncEngine
not starting at allCheck if the license is enabled in Visma Business
Visma Business Services Host for SyncEngine
reports a "no alter rights" error when startingThe user doesn't have the
proper rights to do the required changes on the Microsoft SQL Server.
Please log into Microsoft SQL Server with
an administrator user and enable Service Broker feature for
the Visma Business
system database manually. After that you need to restart the
Visma Business Services Host for SyncEngine in
order to start the monitoring of changes.
Master data is missing for companies in combination with common
tablesEnable Master Data Management for
the companies which are considered the master for a certain table.
Change of General ledger account number in Visma BusinessA change in general ledger account (using the Bytt kontonummer processing in the Hovedbokskonto table) is
currently reflected as a deletion of the existing general ledger account and an
insert of a new general ledger account as far as Master Data Management is
concerned.
Change of customer or supplier number in Visma BusinessA merge of more than one existing customer or supplier number (using the
Bytt kunde-/leverandørnummer processing in the Aktør table) to a new
customer/supplier no is currently not recognized as a change as far as Master Data Management is
concerned. It is treated as a deletion of all companies which are merged to the new
number.
If you change only one customer or supplier number by the time to a
new customer/supplier no then MDM will not consider it as a deletion; instead it will update the connected records
accordingly.
Error when synchronizing data from deleted companies in Visma BusinessThe MDM integration needs to be disabled for a company before it can be deleted from Visma Business. If a company has been deleted without disabling MDM integration then a restart of Visma Business Services Host for SyncEngine should
be performed in order to get rid of the error messages.
Log file error messages
Tabell 1. C:\ProgramData\Visma\Log\Business\Visma.BusinessHost.SyncEngineService
| Error message |
Explanation/suggested solution |
| The remote server returned an error: (500) Internal Server
Error. |
Restart Visma Cloud Gateway (tidl. Visma On
Premises Gateway) service |
| Invalid XML.Exception while trying to get the payload |
One of the entities which should be transferred to MDM contains a non-printable character in one of the Visma Business database fields. These characters are not allowed according to
the XML standard used for communication between the accounting
system and Master Data Management. |
| Incoming snapshotId x is smaller than current MDM snapshotId y |
- The Send på nytt til Master Data Management processing was initiated before the previous run of the
same processing was still in progress. Solution is to wait
until one process has ended and then restart the Send på nytt til Master Data Management if needed.
- A synchronization of a master data change was triggered
after an older version of the company data base has been
restored locally on the SQL Server. The solution is to run
the Send på nytt til Master Data Management processing for all master data types.
|