Logo TCMB Rates Documentation

Support

FAQ and troubleshooting

The questions that come up most often in the field, and what the error texts on the screen actually mean. If you cannot find your case here, write to support with the log file for the day in question.

Licensing

The screen says "Waiting for licence assignment". What should I do?

It means the installation has announced itself to the licence centre but has not yet been attached to a licence. Pass the short setup code shown on the screen to ERP; once the administrator has matched the customer and the product, the state changes on its own. At this stage the application still fetches rates and the panel works; only the step that writes to Logo is closed.

Is there a trial version?

No automatic trial licence is issued. Every installation is attached to a licence centrally; trial terms are agreed commercially and assigned the same way.

The licence server cannot be reached. Will the application stop?

No. The application keeps the last valid signed decision in its cache and carries on through a network outage. It locks in three cases only: the licence has been revoked with a signed revocation, it has expired, or the offline allowance has run out.

I got a "seat limit exceeded" warning.

The product has been installed on more machines than the licence allows. Either the unused installations have to be removed centrally or the licence has to be widened — tell ERP.

If I reinstall the machine, is the licence lost?

No. The licence and the device identity are kept outside the application folder, under %ProgramData%\ERP\Lisans\TCMBKUR; the uninstall script preserves that unconditionally and an automatic update does not touch the folder either.

Rates and the calendar

The rate written for today came from yesterday's bulletin. Isn't that wrong?

It is correct. The TCMB bulletin is published every business day at 15:30 and is valid for the next business day; that is why target day D uses the D-1 bulletin. If a weekend or a holiday falls in between, the source bulletin comes from further back. Details: the TCMB bulletin calendar.

No rates were written at all today.

Check in this order: was the machine switched on at that hour, is the ERP TcmbKur service running, is there a record for that day on the Runs screen, and if there is, what was its result. If no bulletin was published for the target day at all (a holiday), writing nothing is the expected behaviour.

The rates are incomplete, some currencies are missing.

If the fetch ran before the publication hour, early-fetch protection blocks the incomplete data. Beyond that, XDR is excluded by default and currencies not selected in the wizard are not written — check the selection in the rate-fetching step.

I corrected a rate by hand in Logo. Will the next run overwrite it?

No. Rows that were changed by hand are skipped, and the report says they were skipped.

Can I have rates written for a past day?

Yes. Pick the date on the Rates screen and start the fetch by hand; the application finds the correct bulletin for that day itself.

Are numbers written with a comma or a dot?

The screen uses Turkish formatting (dot for thousands, comma for decimals). The value written to the database is a numeric type; it is not affected by the display format.

I get "INSERT permission was denied ... LG_EXCHANGE_xxx".

The service runs as LocalSystem and connects to the Logo database as NT AUTHORITY\SYSTEM. That account has no write permission on the exchange-rate tables of the company concerned. On the SQL Server side, grant NT AUTHORITY\SYSTEM the necessary permission in the Logo database and restart the service. Since 1.5.0 the application also keeps its own tables there (dbo.TCMBKUR_*), so the expected role is db_owner; the installer grants it for you.

Which rate is written into which Logo field?

RATES1 foreign exchange buying, RATES2 foreign exchange selling, RATES3 banknote buying, RATES4 banknote selling. RATES1 is the active rate Logo uses in transactions — talk to accounting before changing the mapping. Table: Logo rate fields.

I wrote with the wrong settings. Can I undo it?

Yes. Select that run on the Runs screen and undo it; only the rows written by that run are reverted.

The JPY rate looks 100 times too large.

TCMB quotes some currencies per 100 units. Turn on the "Divide by unit" option in the rate-fetching step.

Access and passwords

I cannot open the panel from another computer.

That is the expected behaviour: the panel opens only from the machine it is installed on, over http://127.0.0.1:<port>. If you need to look at it remotely, connect to the machine over RDP; do not open the service port outbound in the firewall.

Where do I find the port number?

It is written in C:\ERP\TcmbKur\listen-url.txt.

I forgot the administrator password.

Reset it on the machine from an administrator command prompt: .\TcmbKur.App.exe reset-admin admin. If you do not supply a password, the tool generates one and prints it on the screen. Details: Password reset.

Error messages

MessageWhat it means and how to fix it
Error occurred during a cryptographic operation. The encrypted settings cannot be opened with the key that protects them. This usually happens when the database is restored from a backup without the keys folder being restored with it. Restore the backup together with keys; if that is not possible, enter the encrypted fields (SQL password, SMTP password) again from the wizard.
INSERT permission was denied ... LG_EXCHANGE_xxx The NT AUTHORITY\SYSTEM account has no write permission in the Logo database — see above.
Licence server cannot be reached A temporary network problem. The application does not lock; it carries on with the cached decision. Check access to lisans.erp.tr over port 443.
Seat limit exceeded The device count on the licence is full. Either the unused installations have to be removed centrally or the licence has to be widened.
Bulletin not found No bulletin was published within the back-walk window for the target day. During long holidays, increase the number of days searched.
Service failed to start / /healthz does not respond A port conflict or the SQL connection. Check the port in listen-url.txt and that day's log file.