Current support cases

Performance fluctuations in the Cloud Suite in Germany

Due to problems with our hoster in Germany, there may be performance fluctuations in the Cloud Suite Germany at the moment.

The hoster is working hard to fix the problem so that the performance is stable again as soon as possible.

Vertec Outlook App together with Microsoft Viva can block connection to Exchange Server

You may have the problem that after sending an email, the connection to the Exchange Server is blocked.

Connection problems occur if the add-in Microsoft Viva or Viva Insights is activated at the same time as the Vertec Outlook App.

As a workaround, affected users can deactivate this add-in.

A correction, so that both add-ins can be used in parallel, will be made with the next Vertec version 6.7.0.7.

Error in fetchSharePointSites with Standard Sharepoint Extension.

A temporary Failure of the search function at Microsoft  with Sharepoint could lead to the standard SharePoint Online DMS extension in Vertec returned an error:

Error: method 'fetchSharePointSites’, 'Error fetching sites from domain abcd.sharepoint.com. Please check your configuration.'

In urgent cases, the following workaround could help:

1. In Vertec, create a script with the following script text: CustomSharePoint.py . Name of script is CustomSharePoint .
2. Register it as Custom Extensions . Once you have the extension ID CustomSharePoint.CustomSharePointExtension enter, the rest will appear automatically.
3. Now uninstall the standard Sharepoint Online DMS extension and install the one registered here instead.

Vertec Outlook App Web Edition

In a short period of time, Microsoft has changed the handling and installation of apps in Microsoft 365 several times. We are currently reviewing the prerequisites and installation process and the guide Installing the Web Edition to be adapted accordingly.

As a workaround until then, the Vertec Outlook App Web Edition can be installed in Microsoft 365 via the link https://aka.ms/olksideload.

Error message in Project Templates plug-in due to removed members.

With Vertec version 6.7.0.1, several members have been removed. Since when executing the script Projektvorlage wählen two remote fields are accessed, an error occurs:

Customers who are already using the plug-in can resolve the issue by doing the following:

Either you remove the corresponding rows in the script:

target.xResourcePlanPhases  = source.xResourcePlanPhases

and

target.relocation type = source.relocation type

Or you can install the latest version of the plug-in . However, self-made changes, such as adjustments to the list settings in the Project Templates folder, are lost.

Expansion of BESR can lead to error message when printing invoices.

With Vertec version 6.7, the Checkbox BESR verwenden on the Payment types removed – because now the use of BESR is activated automatically as soon as the Field Customer number a number is entered. Therefore, customers who deactivated the checkbox before version 6.7 but had entered a customer number can now receive an error message when printing invoices.

Specifically, the following error message is output:

Invalid QR code: Error: QR reference requires 27 digits

If you receive this error message while printing an invoice, check the customer number on the payment type used:

• If you do not want to use BESR, delete it.
• If you use BESR, enter the correct BESR customer number. This must always be 6 digits.

Correction of invoices that have already been settled and need to be reprinted:

For invoices that have already been settled and need to be reprinted, it is not sufficient to correct the customer number on the payment type as above, since the customer number is fixed during the charge. Therefore, the following options are available:

• After the correction of the corresponding invoices, the Verrechnen rückgängig and charge it again. The new, now valid customer number is entered.

• If this is not possible (for example, because the invoice has already been posted), the correct customer number must be entered in the attribute for affected invoices verrBESRKunde can be entered. This can be done either via Python Method SystemContext in a script entry with extended user rights or SQL.

Example code for correcting a single invoice with Python:

def fixCustomer(invoice):
    with vtcapp.SystemContext():
        invoice.verrBESRCustomer = “<richtige BESR Kundennummer>”

fixCustomer(argobject)

If BESR is not used, the number should be set to ““:

invoice.verrBESRCustomer = ““

Incorrect behavior in internal document saving on activities

If in the system settings General the Document storage on Intern and when executing a report, the Option Create activity is deactivated, an activity is still created and the report is saved on it.

Workaround: None in the report template File names So that no activity is created when the checkbox is deactivated.

Phone app: Expense tracking with an iOS device crashes:

The Phone app crashes at the Expense tracking with iOS devices via Foto machen ab. Andoid devices are not affected. Workaround: Download the photo from the gallery.

The problem has been fixed. The new version of the Phone app is available in App Store ready for download.

Button for scanning the QR code in the Android Phone app temporarily removed:

Fixing the problem with accessing the photo gallery with Android devices ( see below ) led to the Scanning the server address via QR code no longer works. As a result, the button for scanning the QR code with Phone app Version 1.0.28 for Android devices temporarily removed and will be available again once the issue is resolved.

Starting with version 6.6.0.3, only on-premises customers running SQL Server.

error message Unable to resolve root table when executing Office reports with MS SQL database:

The problem is caused by spaces being mistakenly interpreted as code. It was introduced in version 6.6.0.3 and only occurs in Office reports where there is no report-specific Python code.

Workaround: The spaces can be removed with the following script:

reports = vtcapp.evalocl(“report script”)

for report in reports:
    if len(report.scripttext) == 1:
        if ord(report.scripttext[0]) == 32:
            report.scripttext = ““

No access to photo gallery with Android 13 in the Phone app:

Due to changes in the permissions system starting with Android 13, no Expense pictures uploaded access to the photo gallery cannot be allowed. Also in the Phone app settings, access can only be granted to the camera and not to the gallery.

We are in the process of fixing this problem.

The problem has been fixed and the new version is available in Google Play Store ready for download.

Problems connecting to Webaccess:

When trying to connect to the Webacces, the error message Es konnte keine Verbindung zum Vertec Cloud Server hergestellt werden. Bitte versuchen Sie es in einigen Minuten erneut. occur.

It was discovered that the error occurred when trying to connect to the Webaccess using IPv6 Remote Port Forwarding (instead of IPv4). IPv6 support has been enabled and the connection problem has been resolved.

All information can be found in Vertec Forum and on the following Status page . If you are affected by the problem, please contact our support , or to your sales partner.

Problem fixed.

All information can be found here:
Status page / Vertec Forum .

Problem with OCL variables in OCL expression Editor:

Vertec from 6.6.0.8: Currently there is a problem in the OCL editor when creating expressions with OCL Variables ( varLogin , varContext etc.).

These are not recognized by the editor, an error of the type

0:varLogin Inf not a member of User Entry

Execution of expressions and normal operation are not affected, everything runs as usual. Only the display in the OCL editor is affected.

When re-creating such expressions in list settings or after the mentioned error message appears, the list must be reloaded afterwards.

The problem was introduced with Vertec 6.6.0.8. We will fix it as soon as possible.

Vertec from 6.6.0.3: Non-writable cells in lists:

In some cases, it is possible that list cells are not writable. Re-sorting the list (even if it returns to the original sorting) solves the problem ad hoc.

These are lists with controls (combo boxes or date pickers, etc.) in which there are also entries that cannot be written, e.g. services already charged on the same day, entries that fall into a block period, etc.

The issue was introduced in version 6.6.0.3 and affects the Cloud app and the Desktop App. The issue does not occur in the Web app.

We will fix this as soon as possible and deliver the fix with Minor Release 6.6.0.5 early next week.

Vertec 6.6.0.2/3: Possible error message when executing Legacy Office reports with graphics in the header:

Fehler beim Erstellen des Berichts. Data at the root level is invalid. Line 1, position 1.

In the course of resolving the issue with executing Legacy Office reports (see two rows below), which occurred due to a bug in a third-party component, we had to implement a workaround to get the reports executed.

Now, as a result of this correction, the problem with the graphics (so far only vector graphics, e.g. .svg The manufacturer of the third component has announced that the bug will be fixed in mid-December. We will release a Minor Release 6.6.0.4 as soon as it is available.

As a workaround, the graphic can be inserted in a different format (e.g. by inserting the image from the header with CRTL+ X cut out and in the row of the header by right-clicking and using the insert option Grafik einfügen reinserted). However, we only recommend this for reports that are urgently needed, as the issue will not persist with the next release.

Vertec 6.6 Resource Planning: User does not conform to Planningworker:

When you use the getTargetGroup() method on an user, the following error message appears:

vtcbold.OclError: 0:Projektbearbeiter does not conform to PlanningWorker

The problem is fixed and shipped with version 6.6.0.3.

Vertec 6.6: There is an issue when executing Legacy Office reports with version 6.6.0.1:

When executing the report with output Word an “invalid” Word File is created, which cannot be opened.

Workaround: As output PDF or let Word “repair” the file, then it will be shown.

Vertec On Premises: SSL certificate not found.

If when you start Vertec Cloud Server version 6.6 you get a message like:

A Certificate with Name “vertec.kundenname.de” Inf not registered in
the store at Vertec.CloudServer.Program.CertificateBind(Boolean startedByCommandLine)

appears that the certificate is not found, then as a workaround in the Vertec.ini – File the row Certificate Name="vertec.kundenname.de" without quotation marks:

Certificate Name=vertec.kundenname.de

We will correct that in the next Minor Audience.

Cloud Suite, Customer Portal and webaccess of Openssl vulnerability not affected.

There is currently an Openssl vulnerability X.509 Email Address Buffer Overflow, see https://www.openssl.org/blog/blog/2022/11/01/email-address-overflows/ .

The vulnerability affects OpenSSL versions 3.0.0 – 3.0.6. Vertec uses an earlier version and therefore the services offered by Vertec are not affected.

Basic Authentication via SMTP.

Microsoft deactivates authentication via Basic Authentication (Username / Password) for certain protocols in Exchange Online. However, this does NOT apply to SMTP Auth (the authentication as part of the SMTP protocol). Basic Authentication via SMTP is therefore supported until further notice.

Web app is Suddenly Slow to Operate with G DATA

It has been observed that the web app suddenly runs very slow when using G DATUM as a virus scanner. This could be related to an update of G DATA, we will investigate further.

An interim remedy is deactivating the checkbox Internetinhalte (HTTP) verarbeiten in the options of the G DATA Security Client:

On-premises customers without web access can alternatively run the Cloud Server on a different port.

Cloud Suite with locale German(Switzerland) shows all date values in US format

At the moment, customers with the region setting German(switzerland) or de-ch have the problem that all date formats in the Cloud Suite are shown in US format. The date also appears in US format on the printouts.

The purely manual input of date values works if the date is entered in US format. The performance tracking etc. also works because the date is automatically set there. Date queries bring an error message like VtcStrToDate: invalid date string 7/1/2022 (invalid german date string 7/1/2022)

A workaround, in order to print reports, invoices, etc., which are to be sent to customers, can be set to French (Switzerland) or fr-ch in the meantime, e.g. in a separate browser. The thousand separator as well as the date values are correct.

For on-premises installations from Version 6.5.0.18 the problem exists if the server is not set to German(Switzerland), but the clients are.

Version 6.5.0.19 with the hotfix was installed yesterday, 21.06.2022 on all Cloud Suite.

Missing CefSharp directory.

The following error message appears when the Cefsharp directory is missing:

Check the Vertec installation directory under C:\Users\YourUsers\AppData\Local\Vertec Cloud app to see if the directory exists.

• If No: Uninstall the Cloud app and reinstall it. Alternatively, the Cefsharp directory can also be copied from another computer.
• If Yes: Reinstall the Cloud app and see if the issue is resolved.

For on-premises customers only.

In some cases, after running the Desktop App Setup version 6.5.0.15, the following error message appears when starting the Vertec Desktop App:

The Firebird client library or one of its dependencies could not be loaded. 
Please make sure that the 64-bit Firebird client Inf installed correctly.

The reason for this is that under C:\Windows\System32 the file fbclient.dll does not exist.

We are working on this problem. In the meantime, you can Download fbclient.dll here and in the directory C:\Windows\System32. Then the Vertec Desktop App can be started.

When quickly typing a sequence of letters in combo boxes, as of version 6.5.0.11, it can happen that individual letters, especially from the second letter, are not applied as long as the combo box itself builds up a list. You have to wait until the list is there, so that the other letters are also accepted.

With the translation options introduced directly in Vertec with version 6.5.0.9, the language DD for “German Germany” came to the surface. In list settings etc. – i.e. wherever the program interface is translated – this is exactly the right thing. Unfortunately, this “multilingualism” has also slipped into the selection fields for addresses and projects. There it is about the translation of the data, and there of course there is only one “German”.

So you should NOT select “DD” at these points:

When updating to version 6.5.0.12, the already selected values at these locations are automatically reset to DE.

Solved with version 6.5.0.12

Problem with DB convert from versions before 6.1 directly to a 6.5 version: With the direct convert, the searchconfigurations not applied. The reason for this has been identified and will be fixed. Until then, you have to update to 6.4 and then to 6.5.

Information on the critical zero-day vulnerability in Log4j: This newly surfaced vulnerability has been in the press since Friday.

Vertec is not affected by this: The Vertec software does not use Java or the Log4j component. The servers and services that Vertec additionally uses for the operation of the Cloud Suite are also not exposed.

So there is no need for action when it comes to Vertec. But when it comes to security, it’s definitely worth staying up to date.

More information on this subject can be found in Vertec Forum .

Error message Property Handlesendemail when saving emails via Vertec Outlook Addin: Add-in Access will be adjusted. Until then, read permissions can be set to Property.propertyname and Property.bearbeiter as a workaround:

The Phone app has been temporarily blocked due to an issue in the Google Play Store. The issue has already been fixed and the app should be released again soon.

Already installed phone apps on Android will continue to run.

It has occurred that the Windows Executables (.exe) of Vertec, such as the Vertec Desktop App, get stuck after completing the apps. This is only visible in the Windows Task Manager, the app surfaces close.

The reason for this is the enabled option Malware Schutz AMSI in the G DATA Security Client. If this is disabled, the problem no longer occurs.

With version 6.4.0.21, the following errors occur when selecting objects:

Vertec.UI.ViewModels.SelectFolderDialogViewModel not found

Affects Desktop App and Cloud app in the following places:

• Object permissions, object selection ( eintrag )
• Query folder, Source Folder Selection
• Folder Property: IX folder References (Basic, Default)
• Skills object, Skills folder selection
• BI shows, selection of projection folders ( projectionfolder )
• Custom field items of type “folder” ( Name des Zusatzfelds )
• System settings of type “folder”

As a workaround, the values can also be set in some places via Python. For example, on a user right:

First, the Internal ID of the object you want to link to is determined. Right Click on the object > Property > Internal ID:

The assignment of the object then takes place in the Python console in the appropriate place, in our example on the object permission:

argobject.eintrag = vtcapp.getobjectbyid(31660)

• argobject = the current object being shown, in our example the object permission
• entry = the member to write. The member names are at the top of the list in rot noted.
• Id = The internal ID of the object to be linked, see above
• vtcapp.getobjectbyid: More information in the article Vertec Python Functions

The effect is that invoices that have been set to charge with Vertec 6.4.0.17 or later are not correctly displayed in the     BI evaluations appear.

Acronis Active Protection ( https://www.acronis.com/de-de/support/documentation/ATI2020/index.html#38019.html ) can slow down the Vertec Windows apps (Desktop App and Cloud app): It happened that running Acronis Active Protection caused both the Vertec Desktop App and the Vertec Cloud App to take a very long time to boot. The Vertec Web App, on the other hand, started noticeably faster.

Workaround: Turn off Acronis Active Protection. In most cases, Acronis is not used for this extra protection, but as a backup system. If you cannot use an alternative security suite and cannot do without this protection, we recommend using Vertec Web App.

It may be that in certain constellations the Vertec Phone App on iOS 14.2 or later does not open or exits immediately after start.

The problem occurs in the following situations (all must be met):

• iOS 14.2 or higher
• Deployment via Appstore and MDM Tool
• Device with arm64e processor

See also the forum entry at Apple:

https://developer.apple.com/forums/thread/666399

This is an issue in a component used by Vertec. The third-party vendor is working to fix this. We will be releasing a release shortly that will fix this issue.

Fixed with Phone app Version 1.0.18, available in the app Store.

Apple has fixed the underlying issue with iOS 14.4.

Creating Vertec reports in Cloud Suite instances currently takes a very long time when the output format is PDF, and the generated files are very large. The cause was identified as a problem with generating the PDF files on the server.

In the meantime, we recommend that you configure the Word output format for affected report templates.

Tonight, the Cloud Suite will be restarted. After that, the problem will be fixed.

When using MS SQL Server, if you update a Vertec version 6.2 and older directly to Vertec 6.4 and convert the database with the Vertec.Dbconvert.exe, the convert runs normally, but some things in Vertec no longer work, e.g. the list of report templates is empty.

Vertec version 6.4.0.5, which is expected to be released in calendar week 23, fixes the problem.

In the meantime, we recommend upgrading older Vertec versions to 6.3 first and then to 6.4, or waiting to update to 6.4.0.5.

If you have already converted your database from 6.2 and earlier to 6.4 and are experiencing problems, please contact your Vertec adviser.

It is possible that the Phone app with Vertec version 6.4 does not run (the Cloud app and the Web app, which are also Cloud Clients, does) and the error message appears:

An error has occurred on the server. Please contact your Vertec Administration.

Remember me in does not work in the web app when 2-factor authentication is turned on.

“Error: The object reference was not set to an object instance.” 
 
 
 

Until the problem is solved, it can be ensured as a workaround that Vertec is not maximized (i.e. not in full screen), then the problem does not occur.

 'charmap’ codec can’t encode character u’\ufffd’ in position 5: character maps to <undefined>

Fixed with version 6.4.0.10.

The error does not seem to occur with later versions of Sage

Payment import continues to work on individual invoices and lists of invoices. As a workaround until the resolution is resolved, the payment import can be performed on the individual invoice or the posted and unpaid invoices can be moved to a list and the payment import can be executed on them.

Starting with Vertec 6.3.0.11, the ExecuteFileReport() method reports the error “This path format is not supported” if no save path is specified.

Workaround: Make sure that the path contains at least one directory, for example: C:\Directory\Document.docx or SharePoint:\Directory\Document.docx.

A remedy in this case is to scroll down and up again in the list.