The objects from the .fob file were imported, but they contain schema changes that cannot be synchronized to the database with the Microsoft Dynamics NAV Server instance. Contact your system administrator with the following information: Server Name: %1 Server Instance: %2 Management Port: %3 Microsoft Dynamics NAV Development Environment will detect a running server automatically. Check that: 1. The Microsoft Dynamics NAV Server is running 2. The management service is configured 3. The firewall is open for the management port if remote 4. Microsoft Dynamics NAV Development Environment is running as Administrator, or 5. UAC is turned off.
The NumberSequenceDeployment table contains the running sequence of numbers for all sequences that are configured in a multi-deployment ...
The object ID range of the entitlement is not valid: Entitlement Set ID={0}, Type={1}, ID Range Start={2}, ID Range End={3}. ...
The object \%1 does not contain all of the fields that are required to build a unique index. The resulting dimension may ...
The objects from the .fob file were imported, but they contain schema changes that cannot be synchronized to the database ...
The objects from the .fob file were imported, but they contain schema changes that cannot be synchronized to the database ...
The objects in %1 could not be imported because the worksheet settings in the import file cannot be applied to the objects ...
The objects in %1 could not be imported because there are objects already in the database with conflicting versions. Choose ...
The OData data request cannot be serviced because the following dimension name does not comply with .Net property syntax: ...
The OData query page size must be greater than zero. Open the 'ax32serv.exe.config' file and insert the XML element ' ' into ...