The maximum number of users permitted by your

The maximum number of users permitted by your registration code has
been reached
The following error message may be received when trying to open a Sage Evolution company:
Solution
The first thing to check for is if the maximum number of users permitted by your registration
code has been reached. For instance, 5 users are registered and currently the 6th Sage
Evolution user now wants to access a company.
If the above reason is not the cause of the problem and it’s not possible to simply open
Management Studio and restart the relevant SQL Database Engine (after ensuring all users are
logged out of all Sage Evolution companies), then do the following:
1. Ensure all Sage Evolution agents are completely logged out.
2. Run the following SQL script on the relevant Sage Evolution Common database to identify
the Sage Evolution agents stuck on the database:
select * from dbo._tSessions
3. Then run the following script to completely remove them from the Sage Evolution Common
database:
delete from dbo._tSessions
An unknown error occurred initializing the extended MAPI subsystem
The following error message may be received when mailing out of Sage Evolution:
Solution
One of the many reasons for the above error message could be the following:
The client might be using an internet based e-mailing package such as Thunderbird or
Windows Mail. Since upgrading to version 6.80 or version 6.81 the client will then be
complaining about receiving the above error message.
Please consider that if mailing in MAPI mode out of Sage Evolution (the System Wizard | email tab’s top-half fields for Server, Account Name and Password are thus not completed),
Sage Evolution is offering both Simple and Extended MAPI as required by the specific mailing
application (since version 6.80).
Therefore, if you’re e-mailing application is Thunderbird or Windows Mail it is not supported on
either Simple or Extended MAPI and thus the above error message can be expected.
The client will therefore be forced to start using SMTP (completing the Server, Account Name,
Password and other relevant fields) in order to resolve this.
Sage Evolution version 6.81.48 SMTP e-mailing clients can now make use of the Bcc Address
field option making it easy for customers to track mailers sent using Sage Evolution.
Could not import row 1 error message
The following error message might be received on the Branch Accounting Sync Monitor:
Solution
We discovered on a recent incident that the branch and head office MS SQL server instances
were not quite 100% the same and this gave rise the above error.
This was evident on the numerical number that displays to the right of the SQL engine instance
within the Management Studio as seen below:
On the one server, the numerical value was 10.50.1600 and on the other is was 10.50.2550.
Therefore always ensure that these values are the same (e.g. by using the same install disk on
both servers), in addition to this also use the same collation on them.
Missing lines on the bank recon screen for unposted cashbook batches
What could cause transaction lines from unposted cashbook batches to be missing on the
Bank Recon screen in accordance to the specific Bank Account, date range and other display
parameters specified?
You might have ensured that the correct options as below are selected, but still none of the
transaction lines of an unposted cashbook batch display, for the same Bank Account selected
on the Bank Recon screen. (Not really sure of this part)
Solution
It may be that in the unposted cashbook batch, the first transaction line didn’t have a Tax Type
selected and the other lines did. The Cashbook batch Properties might also have been set to
Always Calculate Tax (see below).
When a Tax Type has been selected on that line and the batch saved, the Bank Recon screen
showed all open cashbook lines as expected.
General ledger account not found
The following error message may be received when converting a Partner company to Sage
Evolution using the new Trew Solutions conversion utility.
43 General ledger account(s)...
12:55:43 - In document line(s)...
12:55:43 GL Account: [1000207] not found
12:55:43 GL Account: [1101000] not found
12:55:43 GL Account: [2000106] not found
12:55:43 GL Account: [2001105] not found
[Error]
Solution
In the Partner company simply create these general ledger accounts and re-convert. The
account type will be determined by the existing main account when sub-accounts are being
created. If it’s a new main account select any account type.
Report starts to run and then hangs
When a user runs a report or tries to preview any document in Sage Evolution it might start and
then suddenly hang and no end report / document preview result is available.
Solution
1. In certain cases this problem might be a result of temporary PC performance issues. Shut
down the PC and try again.
2. If the above fails, test with another agent. It might be that the new agent is able to
successfully run the report. In that case, simply close Sage Evolution on the local PC and
delete the relevant agent report key (failing that the whole agent’s Registry key) in the PC
Registry.
Purposefully displaying only a specific number of characters of a specific
field on a report or document
How do you set up a customised field in Report Writer to display only e.g. the first 10
characters? This kind of request was recently received from a client in order to prevent
displaying the full field values for all the records.
Solution
1. On the Document / Report Design screen, insert a new Variable.
2. When the variable is placed, then right click on it and select Calculations
3. Enter the following syntax for the new variable on the newly opened CALC tab
Value := Copy(ReportData['AccDesc'], 1, 10);
AccDesc = Field name example that you want to be cut off
1 = starting position
10 the number of characters allowed, in your case 25
The following error message may received unexpectedly when working anywhere in an
Evolution company, on any workstation/s.
INVALID USER SESSION. THE APPLICATION WILL NOW LOG OFF OR TERMINATE IN 1
MINUTE - ERROR MESSAGE
Sometimes this might occur very soon/immediately after a new agent has logged on and it
seems as if his new login somehow could have caused this error message.
Solution
1. Get all Sage Evolution agents to physically log out of all Sage Evolution companies
2. Run the following SQL script on the relevant EvolutionCommon database
select * from dbo._tSessions
3. It may give you one or more records indicating those agents are still ‘stuck’ on the sessions
table, while this table was supposed to be clear when all agents are logged out of all
companies.
4. Then run this SQL script:
delete from dbo._tSessions
5. The agents can log on again but the situation should still be closely monitored from here.
It might be caused by possible erratic network behaviour and if this error occurs again,
suspected network instability should be closely diagnosed and resolved by a professional
IT/network expert.
Viewing the actual agent who processed a document or transaction
When a transaction such as an Invoice has been allocated to e.g. a payment or credit note,
then you’ll see the agent who processed the actual allocation under the User Name column on
the AP / AR Enquiries screen, and not the original transacting agent.
How do you see the original agent that actually processed the above documents?
Solution
Simply double click on the relevant transaction above and on the Audit Trial screen you’ll see
the actual transacting agent.
Error updating system function information – invalid column name
“blssystemrule”
The following error message may be received when trying to upgrade a Sage Evolution
company.
Solution
1. Cancel the upgrade process.
2. Shut down the PC and restart.
3. Restore the backup that was made before the upgrade process started.
4. Try again to upgrade. This solution worked for a recent support query client.
Tender types no cash tender type defined – retail error message
The following error message may be received when selecting a relevant transaction menu
option on the main Retail POS screen, for example the ‘Sales invoice, Credit Notes or Order’
and Till Transactions.
Solution
It could be that you don’t have any Tender Types in the relevant Sage Evolution company with
a Type of Cash.
Therefore go to: Retail POS | Maintenance | Tender Types and ensure the above rule is
adhered to.
On version 6.81 the screen looks like this:
On older versions the Tender Type screen looked like this:
Unable to get the add property of the workbooks class
The following error message may be received when running a BIC report (normally occurring
during the DATA OUT report running phase).
The second error message is the reason behind why you get the first one. It comes up when
you go to the MS Excel and try and open a macro enabled workbook, so you might not
necessarily see it but it is the cause of the above problem.
Solution
Close all MS Excel workbooks on the local workstation where the error occurs.
From the workstation, browse the network for the relevant BIC Excel template file from where it
is located (on the server, another workstation or the local machine) i.e. \\server\evobicmetadata
and open it.
On the workstation open Report Manager.
Right click on the report on the left and select Create and Link Template (noticed some options
are greyed out).
The below screen will pop up showing all the currently open Excel workbooks. Select the
template for the report (the reason why you have to close all Excel workbooks first is for easy
selection of the template).
You might also be getting the screen below and will therefore select the relevant version of MS
Excel.
Select Yes on the following screen:
Then select Ok on the following screen:
You might be getting this message (where relevant). Select Yes as recommended:
Select Yes on the following screen:
The following confirmation message will then be received while the opened Excel template will
be closed automatically:
MS SQL profiler not available or missing even when running full SQL server
Why would you not be able to find/access MS SQL Profiler even though full MS SQL Server
(2005/2008/2012) and Management Studio are installed?
Solution
You previously might have had MS SQL Express with its own Management Studio installed.
The problem is that when installing full MS SQL 2008 Server with tools that includes
Management Tools: Management Studio, Profiler etc, these new tools can’t be properly
installed over the previously MS SQL Express edition’s Management Tools (e.g. Management
Studio for Express) and as a result you won’t have MS SQL Profiler available afterwards.
Therefore, do the following to keep your new full MS SQL Server instance (no need to uninstall):
1. Close Sage Evolution and all instances of MS SQL (and backup your companies just in
case).
2. On Control Panel | Programs and Features, select the relevant instance of MS SQL Express
and the Uninstall/Change option.
3. Then select the Uninstall option on the next screen. At this point it will start preparing the
uninstallation wizard but nothing will be uninstalled yet.
4. Follow the wizard until you reach the screen below (Remove SQL Server 2008 R2 or relevant
version indicator) and select the Management Tools options below. Then continue with the
wizard and complete the uninstallation process.
After this your new MS SQL Server engine instance should still be there.
5. Restart the PC and then install again and select the option below. You will not install a new
SQL instance, simply adding the Management Tools to it.
6. When reaching this screen, select the option below and continue with the wizard
Duplicated transactions
What could be one of the obvious causes of duplicate transactions that somehow seem to get
randomly posted?
For example, a client may complain about duplicate POS payment transactions as evident in
the POSTAR table, as well as on the front end in the AR Enquiry screen for the relevant
customer.
Solution
1. Always check for foreign triggers and third party integrations that may be the culprit.
2. For interest sake, also investigate to see if there are different audit numbers between the two
receipts (transation type in this case).
For example:
select cauditnumber, txdate, debit, credit, description from postar
where txdate = '2012-11-27' and AccountLink = 4808 and Reference = 'INV69790'
Different Audit Numbers between the two POS Receipts!
3. Check to see if deadlock errors were perhaps occurring, by running the SQL script below, as
this is a known cause of duplicate transactions.
select * from _btbllogdetails
where cDetails like '%deadlock%'
In an actual incident we found a lot of deadlock errors that occurred and this could therefore be
linked to the duplications on the client’s database.
4. Fortunately there is a SQL script available that might be able to resolve this issue - see
article below.
Also ensure the client’s local IT consultant are running on a stable network with no unexpected
network drops as this might also be linked to possible duplicated transactions.
How to prevent deadlock errors
In order to prevent deadlock errors:
1. Get all users out of the Evolution company.
2. Make a company backup.
3. On the Evolution server PC, open MS SQL Management Studio and connect to the
correct SQL server instance name.
4. Expand the Databases section on the left, right click on the relevant company database
and select New Query.
5. Paste the following script on the right hand side of the screen:
ALTER DATABASE Pastel
SET ALLOW_SNAPSHOT_ISOLATION ON;
ALTER DATABASE Pastel
SET READ_COMMITTED_SNAPSHOT ON;
6. Replace the Pastel word (used as example in my case) in the above script with your
exact database name. For example:
ALTER DATABASE FLIGHT
SET ALLOW_SNAPSHOT_ISOLATION ON;
ALTER DATABASE FLIGHT
SET READ_COMMITTED_SNAPSHOT ON;
7. Press F5 on the keyboard and wait a couple of minutes until you see results at the
bottom of the screen.
8. When done, only then may the users again log back into the Evolution company.