Error messages on startup

Here is a description of the most important error messages when starting Vertec On-Premise:

Invalid object name 'dbversion’

This error message means that the login is correct and the Vertec database exists, but it is probably empty. The Vertec database converter can be used to create table structures and convert databases.

• For descriptions when using Firebird, see Update vertec on-premise.
• The description when using MS SQL Server can be found in the article about Convert with ms sql server.

Vertec only runs with a valid license code. You can retrieve this in the Customer Portal.

Vertec’s database is read-only. This error often occurs when it is transferred from a CD to the HD, for example. In the Vertec installation directory, go to the subdirectory \DB. Here, right-click on the database file (usually Vertec.fdb). In the menu that appears, select Property. In the dialog that appears, under “General,” set the file attribute “read-only” to inactive (may vary slightly depending on the Windows version).

The path in Vertec.ini is incorrect. The database is not below the specified path.

The password or user name for Firebird specified in Vertec.ini does not match the Firebird itself. Open IBOConsole directly in the Firebird program group and log in with the known user name and password. If this works, encrypt the database password in the Customer Portal and enter the corresponding information in Vertec.ini.

Vertec.ini does not specify a database in the appropriate section or the section is missing altogether. Correct the information in Vertec.ini and then restart Vertec.

Database names must not start with a number, otherwise you will receive this error message. On MSSQL servers, the following symbols must not appear in the database name:

• Spaces
• Special characters (e.g. $,§,% etc.)
• Hyphens (-) or underscores (_)

Change the database name and specify the new name in Vertec.ini as well.

1. Check if Firebird Server is started.
2. Check if the settings in the Vertec.ini – file are correct.
3. Make sure the driver is capitalized in Vertec.ini (e.g. INTRBASE, MSSQL etc.)
4. Ping server (same name as specified in Vertec.ini). If this does not work, try to go over the IP number. If this works, specify the IP number of the server in Vertec.ini instead of the server name.
5. Start the Communication Diagnostics via IBOConsole and try to establish a tcp/ip connection to the server.
6. Check the Services file to see if port 3050 is registered: (C:\Winnt\Drivers\etc.)
7. For firewalls, make sure port 3050 is open.

This error message appears when the connection is denied at the network level. Typically, the client request to the appropriate port is rejected by the server because the port is not approved.

1. Check the Services file to see if port 3050 is registered: (C:\Winnt\Drivers\etc.)
2. For firewalls, make sure port 3050 is open.

It is also possible that for some reason the Firebird service is not running. Then you get the same message. Start the Firebird Guardian service should fix the problem.

This error message appears when the connection is denied at the network level. This can be caused by:

1. Port 3050 is used by another application or is otherwise unavailable.
   1. Check the Services file to see if port 3050 is registered: (C:WinntDriversetc.)
   2. For firewalls, make sure port 3050 is open.
   3. Use an external tool to check which program uses which port.
2. There is an outdated GDS32.dll file in the Vertec directory. For descriptions on how to do this, see the Firebird article.

The Vertec database is accessed with a newer version of Firebird than before.

Solution: Create a Backup with the previous version of Firebird. Then restore the backup with the new version of Firebird. After that, you can work normally with the new version of Firebird.

The required Firebird client library gds32.dll does not exist. For information on this topic, see the Articles about firebird.

This error message may occur due to a setting in Microsoft SQL Server. For more troubleshooting information, see here.

This error message appears due to a setting in Microsoft SQL Server. For more troubleshooting information, see here.

This error message appears due to a setting in Microsoft SQL Server. For more troubleshooting information, see here.

When starting Vertec on the clients, the error message appears:

Can’t format message 13:98 -- message file firebird.msg not found

This message can have several causes:

1. The problem may be that the firewall on the server blocks access from the clients. The remedy is to define new rules for incoming connections on ports 3050, 8091, 8095, 8096 and the VertecServer.exe on the server. Info: If you install Vertec on a server that also has a firewall for the internal network, the Notif port 3050 (TCP) and the Firebird port 3050 (TCP) and possibly the XML port must be explicitly enabled for this to work. To do this, you should enable the port and VertecServer.exe in addition.
   Information about what is running on which ports can be found in the Vertec.ini configuration file, which is located in the Vertec installation directory.
2. The client is having trouble resolving the name on the internal network. In this case, you should use the IP address instead of the hostname in the Vertec.ini file.
3. In one case, the activity monitor of an anti-virus program blocked. After it was disabled, everything worked fine again.

When you start Vertec on the clients, the error message:

Can’t format message 13:98 -- message system code -4
Cannot attach to password database

appears, it may run out of disk space on the server. Approving disk space on the server will help.

If you want to start Vertec, from a client or directly on the server, and the following error message appears:

no permission for read-write access - Datenbankname -

Then this is because the account with which Firebird is operated does not have full access to the Firebird files.

Normally, Firebird runs with the local system account. However, another account can be specified:

It is important that this account has access to the drive where the Firebird files are located:

Invalid connection string

This error message occurs when the MS SQL Server database connection information in Vertec.ini is incorrect.

Check and correct the information in your Vertec.ini file.

Unsuccessful execution caused by an unavailable resource. Unavailable Database.

If this error message appears when starting Vertec, it is probably because the Firebird service is not running. Go to Services and start Firebird Guardian.

OCL Expression: ->size

The following error message appears when starting Vertec:

This is due to a misconfigured wrapper link type on user – one Role is the user, the other Role is the expression empty. This error must be fixed in order to restart Vertec. If you have a Vertec Desktop App, you can start it and fix the error there. Otherwise, the appropriate link type must be searched in the database and set to inactive. Please contact your Vertec advisor.

When starting the Vertec Desktop App, the error may occur

dbConfig is empty

a possible cause of this can be an incorrect encoding of the Vertec.ini file. This can happen, for example, if it is edited and saved again with a different encoding.

Remedy

Open the Vertec.ini file in a text editor and save it with the ANSI (or Windows-1252) encoding.

Vertec Cloud Server starts and stops after a short time with the following error:

Method not found: 'Newtonsoft.Json.JsonSerializerSettings System.Net.Http.Formatting.BaseJsonMediaTypeFormatter.get_SerializerSettings()'.

The problem is a conflict of assemblies on the system. It occurs only in rare cases and in certain constellations.

Remedy

Copy the Vertec.CloudServer.exe.config file to the Vertec installation directory. The Cloud Server should then restart.

The amount must not be a negative number

If the following message appears when launching a Vertec full-featured app:

Session settings were probably saved at a time when Vertec was open on a different screen and/or monitor resolution.

Remedy

Remedy is to delete the Session Settings.

On the Terminal Server, the message appears immediately after double-clicking on Vertec.Desktop.exe

Vertec Desktop App funktioniert nicht mehr

This applies to all users who want to open the Vertec Desktop App on the Terminal Server.

Remedy

The cause of this problem is a “stuck” Vertec Desktop App. In the task manager on the terminal server several open Vertec Desktop App are visible. One of them is not running if you want to view the properties (via right mouse button). Mark it and click Task beenden. After that, Vertec can be started normally again.