Please don't forget to login! If you don't know your login details email us




The above error occurred when a user was processing a Batch with GL accounts

Found that there was an extra line on the Batch for AP which was blank.

-Checked the Vendor table, column exists
-Created a new Batch and selected Gl module as default
-Exported the corrupt batch and imported on the new batch and user was able to process with no errors.


Sales and Purchase orders not clearing the screen when placing order



Users may discover that the Purchase and Sales Order is not clearing the screen when placing an order.


For example:  

1. On the Purchase Order screen, a new order is captured and the Place Order button selected


 2. The screen is however not cleared afterward which may be exopected to occur here. The user is now forced to manually select the New button above to capture a new order which may be a nuisance, especially if a lot of orders need to be captured.




Invald Colimn Name "idCliClass"

Invalid Column Name "idCliClass"


When upgrading from any version to version 7.10.106 a company with Suppliers Group, you will face the following message:



There, please download the bpARAPXE.bpl file from the link below and replace it on every workstation.


If you are still having trouble please contact for further assistance.





An Error Occured While Processing This Transaction. All Processing Was Rolled Back

An Error Occured While Processing This Transaction.  All Processing Was Rolled Back

This error occurs when processing a Purchase Order.


Reason and Solution  

Check the Order defaults on the Purchase Order Tab the correct transaction types have been selected, however on the Inventory Defaults | Goods Received Vouchers Tab, the transaction types are blank as per screen shot below.  

Select the correct transaction types as per the order defaults, then process, should allow the process to go through with no errors.


Error- The service cannot be started either becuase it is disabled or becuase. . . .

When trying to start the Service of a specific SQL Database Engine in Configuration Manager, the following error message may be displayed:     



There may be various reasons for the above error but the following steps have proved to resolve the above error.


In Computer Manage Services or on Configuration Manager do the following:  

1. Set the Startup Type properties of the relevant SQL Server Agent to Manual and then Start it.


Evolution 7 Error: "qryARAccounts: Field ‘ubARF5mailer’ not found"

This error can occur when a User creates a User Defined Field (UDF) within the Customer section of Accounts Receivable and then deletes it.

The next time a user attempts to edit a customer record they will receive the following error message:



This error is caused because Evolution thinks the UDF is still active. While the created field may not appear in Evolution it still resides in the SQL tables.


To resolve this error:


1. Take a Backup

2. Delete the field from _rtblUserDict table in SQL

3. Check if the error persists


Alternativly you could make a copy of the company.


SQL Error: Incorrect syntax near 'len'

When trying to convert an Evolution database to a newer version of Evolution you may recieve the following SQL error message:

Eg. from Evolution  v6.81.48 to v6.82.69

Incorrect syntax near 'len'

CREATE function [dbo].[_efnSplitString] (

  @InputString varchar(max),

  @SplitChar char(1))

returns table

with encryption





Error: Cannot generate SSPI context


This section gives you the background information on why the "Cannot generate SSPI context" error message occurs and how to troubleshoot the error.

You may receive this error message if the following conditions are true:


  • You are connecting to Microsoft SQL Server.
  • You are using Integrated Security.
  • Kerberos authentication is used to perform the security delegation.


Verify the domain

Verify that the domain to which you log on can communicate with the domain to which the computer that is running SQL Server belongs. There must also be correct name resolution in the domain.