Startup errors
The database will not open, licences drop out, the server is not found, platform version conflicts.
The first action in any situation is a backup. Diagnostics and fixes come after that.
The database will not open, licences drop out, the server is not found, platform version conflicts.
Testing and repair, or restoring from a backup where the problem cannot be fixed.
Installing platform and configuration updates, tested on a copy with the option to roll back.
Diagnosing the cause: locks, the disk subsystem, insufficient memory, scheduled jobs.
Software and hardware keys, the licence server and problems after a hardware change.
When a file-based database can no longer cope with the number of users.
Emergency requests are taken on the day they arrive. Planned work is done outside working hours.
We take a backup of the database before doing anything. No exceptions.
We identify the cause from the logs and the symptoms rather than by trial and error.
We resolve it, working on a copy where needed and transferring the result afterwards.
We configure backups and scheduled jobs so the situation does not recur.
Updating a configuration without testing on a copy is the most expensive way to save time. If the configuration has been customised, an update can break those customisations, and that becomes apparent on the live database during the working day. The test takes a couple of hours; the recovery takes a day.
First establish what exactly is slow: one particular operation, all documents, or only at certain times. Common causes are locks under concurrent use, mechanical drives and scheduled jobs running during working hours. Diagnostics take a few hours.
File-based is acceptable up to 5 to 10 users and a modest volume. Beyond that the risk of corruption grows and speed falls. For 20 users and more, client-server is the only sensible option, not least for data safety.
We are responsible for the technical side: the platform, the server, the database, updates and speed. Configuration development and accounting methodology are handled by 1C specialists, and we work alongside them rather than trying to replace them.
Describe what is happening and when it started. In an emergency we respond the same day, starting with a backup.
Request received
We can already see it. We will reply within one business day, and for urgent matters we will bring in the on-duty engineer right away.
City not found. Please check the spelling.