Let's take a look at the report on the options for correcting the pardon "Insufficient memory" in 1C 8.3.
Іsnuє obmezhennja at vidіlennі address ї міаіаі for software provision of operating system: for 32-bit system - 2 GB; for a 64-bit system - 4 GB.
To increase the size of the address memory, you need to do the following: run the command line with the rights of the Administrator:
We then used it in the dialog command line, then dial the command to increase the address memory. Enter in the command line BCDEdit /set increaseuserva xxxx, de zamіst хххх it is possible to specify the amount of virtual address space in megabytes. For example, 3072 MB is recommended for 32-bit systems:
Rezavantazhuemo computer. Zrobimo di in the program 1C 8.3, they did not come out earlier.
After the completion of the operation, it is better to turn the address memory of the value for locking. For which, enter BCDEdit /deletevalue increaseuserva on the command line:
Rezavantazhuemo computer.
The 1C 8.3 platform has a chance for additional regulatory tasks.
Visibility of marked objects allows:
Vidkrivaєmo point: administering - Adjustment of programs - Maintenance and service - Backup and update:
Nalashtovuєmo layout of automatic copying of the base and pressing Done:
For more details on how to make a backup copy of 1C 8.3, marvel at our video lesson:
Check the item Automatically see marked objects for the layout: split Administration - Adjustment of programs - Maintenance and service - Routine operations:
Nalashtovuєmo layout of automatic removal of marked objects in 1C 8.3 for the hour. For example, for an hour, interrupt and press on Done:
As a result, the bases change, the productivity of the pardon system and pardon 1C "Insufficient memory" is not guilty.
Pardon "Lack of memory" in 1C 8.3 and 8.2 is not so familiar. You can use it in the configurator (for example, when the configurations are balanced), as well as in the "1C: Enterprise" mode when working with labor-intensive processing: for example, when writing a large file to the base64 format.
This pardon can be used by the 1C program, and also by other programs of the Windows operating system.
On the right, in 32-bit operating systems for locking 2 Gigabytes on various programs and styles for the operating system. For 64-bit operating systems, the amount of memory, which is seen as add-ons, should be 4 Gigabytes.
Vyhodyachi from the foregoing, you need to increase the size of the seen address memory for supplements, like the 1C program. You can do this in two ways: change the transition from a 32-bit system to a 64-bit one, or increase the number of address memory.
Of course, the first way is the best and the best, but even at the present moment, otherwise you can’t speed up with him, you can speed up with others.
Days on the cob go to the command line of the operating system. For this, go to the "Start" menu and then in a row search for "cmd".
Before you z'appear poshuk programs. Choose the one called cmd.
Also, the command line can be opened for an additional combination of hot keys Windows + R.
At the beginning, type the next command and press “Enter” like this:
bcdedit /set increaseuserva 3200
In your case, you can increase the address memory up to 3200 megabytes.
Since everything is fine with you, it is recommended to restore a large amount of address memory. Timchasov's peace is given, so when you see the memory for additions, the operating system becomes smaller. For the account of which it is possible to damage the stability of Windows.
To restore the address memory, the value behind the lock can be accelerated with an offensive command, as it is entered in the command line like this:
bcdedit /deletevalue increaseuserva
To raise respect, that when pardoning “Nestacha memory” in 1C, which is often heard, it can help to remove the marked objects. Possibly, the programs have accumulated a lot of money, and the programs can easily make such obligatory data. If this method did not help, you should increase the capacity of the Windows operating system.
One of the widest pardons that is blamed on the process of work with 1C 8.3 is "Lack of memory". In fact, it can be seen after the richness of the subdivisions - updating, processing of great files, molding the sound, capturing data from those others. Tse means that, be it an administrator and a 1C retailer, he is guilty of understanding the essence of the problem and correcting it. Forgive the big ones operational memory PC or hard disk does not solve the problem.
The reasons for this pardon are not known in the 1C system, so you can apply the same pardon in other programs. The problem is that in the operating systems of the Microsoft family, there is a lot of memory for the skin program behind the mind. For 32-bit systems, the value is set at 2 GB, for 64 - 4 GB. If the program is revisiting this display, it will appear on the monitor with a pardon.
The simplest way to get around such reminders is to see the visibility of objects in the configuration. Tse help infrequently, but allow for zayvi koliva. Until then, the risk is minimal, the shards do not impair vtruchannya at the inside. customizing Windows. Even though the distance did not help, it happened to fight with other methods.
Another solution for 32-bit systems is the transition to the 64-bit version, or the increase in program memory. The first option is rather correct, but other than that, through various causes, the faults are impossibly. Then there is more than one option with the algorithm dіy, the indications are lower, but it can be more accurate - there may be problems with the practicality of the system.
The goal algorithm is simple:
This decision allows the operation to be vikonated, as it is impossible to vikonate through pardon 1C "Insufficient memory". You can only greet him in emergency jumps if the operation is necessary to vikonat directly at once. In other environments, it is better to try running 1C on a 64-bit platform and repeat the operation there.
More serious vartos are put up to inform about those who have insufficient memory on the server for the hour of updating or large-scale work. The problem may be in the untimely completion of the processes that are launched by the different software, after which there is a “disturbance” that accumulation of them in the virtual memory. Another dzherelo similar pardon - intensive work of various programs from the backup and memory. Іsnuє rіzne PZ for vyrіshennya tsikh problems, but practice pokazyuє, scho vono viklikає rozrivi z'єdna that fall 1C.
Podіbnі pardons zmushyuyut zamyslitsya, chi enough hard server 1C. The relief of yoga straining on the greed of the company, but for a moment, a similar pardon can be done in other ways, which do not require infusion of money.
Zvichayno, permanently zastosovuvat not varto, but stinks can help, if necessary, the terminology of the resource worker. Among the popular ways to help build a pardon for lost memory on the server, call:
Another extended pardon 1C blame, if there is not enough time on the hard drive on the server. Timetables take up a lot of time, and in times of incompetence, the administrator can pardon "Insufficient memory for vikonannya operation." In such a time, it is difficult to give exact reasons, the shards of the servers of the cluster can be sorted out in different options. Among the standard solutions that help in such cases, you can restart the server, increase the free space, optimize the consumption, update the version.
In companies with a large number of koristuvachivs, the pardon "Insufficient memory on the server 1C: Enterprise 8.3" is often blamed. The great problem of that rethinking is the insufficient analysis of the necessary productivity. To that, with the help of 1C, to attach great respect to the sufficient effort of servers, so that the future did not have a chance to achieve productivity at the expense of stability.
Tsya pardon є dosit typical for 1C 8.3, with it sticks a lot of coristuvachiv.
The reasons, through which you can blame the pardon "Insufficient memory 1C", really do it a lot. Even more often given a pardon vinikaє in case of incorrect updating of the configuration 1C Acceptance. It is not less rare before the vindication of a pardon to produce a fundraising volume of data, or try to collect even a great file.
So, as the reason for the blame for the pardon during these events, it is in the non-address memory, virishiti її modernizatsiyu obladnannya, on which the 1C program is installed, do not go into it.
Right in what the operating system gives software access to a shared address memory, as a rule, should be 2 gigabytes for thirty-two-bit operating systems and 4 gigabytes for sixty-two-bit operating systems.
Expanding the available address memory program 1C is awkward. For whom it is necessary to create a command line call. It is possible to create a kіlkom in ways, the simplest of which is to click the right mouse button behind the Start menu icon - "Command Row"
At the vіknі it is necessary to enter the step:
de numerical value - the need to obsyag memory and press the "Enter" key. If it will be necessary to restart the computer. If possible, you can try to repeat the operation, which ended with a pardon. As the pardon is repeated, it is recommended to turn to fakhіvtsіv.
Our programmers will be happy to advise you and help you.
Pardons are blamed. Let's take a look at one of them, dedicated to the topic "Insufficient free memory on the server 1C: Enterprise".
Methodology for the adoption of a pardon "Insufficient memory on the server 1C: Pіdpriєmstva".
Obsyag memory of working processes for an hour of work on the 1C agent server ceased to be inexhaustible. With yogo maximum zavantazhennі koristuvach bacheling in front of him a reminder to quiet his novelty - "Lack of good memory on the server 1C: Pіdpriєmstva".
A word about the causes of the blame for similar remembrance - why don’t you remember. Їx can be a sprat:
Yakshcho in the system works up to five osib - then it will be enough for one eight-gigabyte computer with two screws (on one - SERVER, on the other - SQL) and additionally installed chips. And on the right, there are thirty coristuvach people, thousands of first-hand documents. Here, SQL needs to be blamed on an okremy server, and you can’t get into one terminal server.
Typical configurations are trying to describe literally all the processes, so that you can find a retailer, trying to create a universal accounting record under the name 1C: Enterprise. Therefore, a specific coristuvach takes away additional baggage from looking at objects of metadata, additional SQL tables, details that are not victorious. Post-registration and re-indexation of all non-essential items in program loan registers long hour that rich mist.
The revantation of the server is blamed and in case of unreasonable (inode) programmers of certain processes and the introduction of their own "militia" by them, which zbіlshhuyt term vikonannya set zavdan (and the number of working processes is the same).
Crimson of a lesser, and often not the main reason - the 1C program may have a large number of internal pardons. Deyakі їх to be corrected at the next releases. A large number of forums are dedicated to this pardon, on some administrators, discussing black steps, it seems hot, that only Tajiks (Dzhamshut and Ravshan) work in one EU, singsongly.
Shards of the cause of the problem can be different, then the way out of the situation is also different:
Naishvidshim i in a simple way The solution is to restart the server service. From the Microsoft Windows command line (cmd): for the start, the command - net stop "1C: Enterprise 8.3 (or your version) Server Agent", and for launch - net start "1C: Enterprise 8.3 (depending on your version) Server Agent" . Such a solution does not know food again - most often the pardon is repeated. The frequency of repetitions to deposit depends on the number of clients and the number of working processes.
IMPORTANT. To be able to restart, you need a mother of all rights.
Sometimes you can create one working process, which is being worked out, it may not take up all the RAM. So the task is to build a way to increase the number of people in the cluster. Approximately one process is added for skin 15-30 coristuvacs.
Restart interval. Shortly before the completion of the front rose, a new process, rphost.exe, is launched. - On the new one, change the old one. Permissible memory limit - if the value is moved, a second timer will be started.
Interval for moving the boundary contract - when the timer moves to the given value, a new process will be launched. І on the new one, there are old ones. And the old one, by his blackness, is signified as inactive. Wimk. start the process after - after the value of this parameter, after the icon of the working process is inactive, it will be completed by the operating system. If this parameter is set equal to "0" - then all inactive processes will not be automatically terminated.
IMPORTANT. This setting is typical because it turns on the database only of that client, which launched an incorrect call. And the reshta - will be smoothly moved to new floors (without resurfacing from its base).
If rphost.exe is reconfigured with background tasks, and if new processes are created, it is necessary to reconfigure:
Max. obsyag memory of working processes - tse total obyag memory of all processes at once. Win by bytes. If an incorrect value is entered (inadequate normal operation), then the pardon "Insufficient free memory on the 1s server" will be removed.
Safe memory override for 1 call - control over memory overclocking when called by the server (in bytes). In case of victorious viklikom greater number, lower is assigned, in case of completion of the middle cluster. Restarting yoga did not work. And the cost of the session does not depend on other clients.
Obsyag memory for processes, until the server is considered productive by the system - when this value is reached, the cluster server stops accepting the call. The number of information bases per process - isolate IB for processes. After isolating infobases (when the value is entered - "1"), the problems begin to mount.
The number of days for one process - the value of "128" is set for the lock. As the flow base is already being challenged by the great challenges of the background tasks, you can change the quantity, for example, to “25”. With such adjustments, the trochs change and the alignment of the cluster:
Resilience to maturity - shows the number of servers, when exiting from the fret, there will be no abnormal completion of the work of clients. If so, it will automatically be launched in the required number of backup services.
The rozpodіlu navantagennya mode can have two possible options. If you set "Productivity Priority" - then the server memory will be used more to increase productivity. If you select "Memory Priority" - the 1C cluster will save memory.
To operate with the database, it is necessary to speed up with the help of MS SQL DBMS.
Possibly, the reason for the pardon is found in incorrect information, as if to be forgiven in the Configuration. For reverification, it is necessary to enter the command “Reverification of configuration”. (Do not stray from the tests!). Before the vicons, it is necessary to check the installed checkbox (ensign) - “logical integrity”. In times of inaccuracy, it will be corrected in the case of assistance. And pardons will be removed.
We looked at the reasons for the lack of free memory on the 1C server and the possible ways to use it. One of the ways to chantly allow the problem to be solved.
