Error messages on startup

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

Invalid object name 'dbversion’

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

• For a description when using Firebird, see Update vertec on-premises premises.
• The description when using MS SQL Server (from Vertec 6.4 is used instead of the parameter /DC the aid programme Vertec.DbConvert.exe used) 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, for example, it is transferred from a CD to the HD. 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 the Properties feature. In the dialog that appears, under “General,” you can set the file attribute “read-only” to inactive (this may vary slightly depending on the Windows version).

The path in Vertec.ini is incorrect. The database is not located at 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.

In Vertec.ini, no database is specified in the corresponding 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:

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

Change the database name and also specify the new name in Vertec.ini.

1. Verify that Firebird Server is started.
2. Check if the settings in the Vertec.ini – file are correct.
3. Make sure that the driver is capitalized in Vertec.ini (e.g. INTRBASE, MSSQL etc.)
4. Ping server (same name as specified in Vertec.ini). If that doesn’t work, try using the IP number. If that works, use the server’s IP number instead of the server name in Vertec.ini.
5. Via IBOConsole, start the Communication Diagnostics 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 corresponding 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. Starting 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 is using which port.
2. There is an obsolete GDS32.dll file in the Vertec directory. For a description of how to do this, see Firebird .

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

Solution: Create a Backup with the previous version of Firebird. Then perform a restore of this 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 is missing. For information about this, 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 because of a setting in Microsoft SQL Server. For more troubleshooting information, see here.

This error message appears because of 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

There are several reasons for this message:

1. The problem may be that the firewall on the server blocks access from the clients. In this case, the solution is to define new rules on the server for incoming connections to ports 3050, 8091, 8095, 8096 and VertecServer.exe. Info: If you install Vertec on a server that also has a firewall for the internal network, the Notification and 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 also VertecServer.exe.
   The 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 has 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 deactivated, everything worked fine again.

If you receive an error message when you start Vertec on the clients:

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, 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 is operated with the local system account. However, you can also specify a different account:

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

Invalid connection string

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

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

Unsuccessful execution caused by an unavailable resource. Unavailable Database.

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

OCL Expression: ->size

When you start Vertec, the following error message appears:

This is due to a misconfigured wrapper link type on project user – one role is the project user, the other role is empty. This error must be fixed so that Vertec can start again. 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. Contact your Vertec advisor for this.

On the Terminal Server immediately after double-clicking on Vertec the message appears

Vertec Desktop App funktioniert nicht mehr

This affects all users who want to open Vertec on the terminal server.

Remedy

The cause of this problem is a “stuck” Vertec Desktop. Several open Vertec Desktop Apps are visible in the Task Manager on the Terminal Server. One of them does not work if you want to view the properties (via right mouse button). Mark them and click Task beenden. After that Vertec can be started normally.

When starting the Vertec desktop app, the error may occur

dbConfig is empty

A possible reason for this may be an incorrect encoding of the Vertec.ini file. This can happen, for example, if it is edited and saved 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 again 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.