For a long time I wanted to find a similar cheat sheet, which contains the main commands and parameters for starting 1C from the command line. It finally happened, thanks to Infostart 🙂

For versions 1C 7.7 and 8 (8.1, 8.2, 8.3), the parameters are different. Let's consider them in more detail

Teams 1C 7.7

1cv7.exe MODE [/ M | / D | / U | / N | / P ],

where MODE- launch mode, can take only one of several values:

• config- configurator mode;
• debug- debugger mode;
• enterprise- normal (working) mode;
• monitor- "Monitor" mode.

The following keys are optional:

• / M- launching the program in exclusive mode;
• / D- database directory;
• / U- user's working directory (directory from the list of users is ignored);
• / N- Username;
• / P- user password;
• / T<путь> - path to temporary files;
• /@<ИмяФайла> - for the configurator mode with the indication of the batch launch file;
• / W- Web extension initialization;
• / L- Interface language: ENG - English, UKR - Ukrainian.

Example: 1cv7 enterprise / Dc: \ 1c \ mainbase / NIvanov / P123,

In this case, the program will start without displaying dialogs about choosing a base and operating mode, as well as without prompting for a username and password.

Commands for 1C 8.3 and 8.2

Additional options for choosing the launch mode

Simultaneous use of parameters from the table below is not allowed.

DESIGNER(CONFIG in 8.0) Start in the Configurator mode.

ENTERPRISE Run in Enterprise mode.

CREATEINFOBASE<СтрокаСоединения> ] Creation of an information base.

• StringConnection - required parameter, see below.
• / AddInList [IBName] - the name under which the base is added to the list. If this parameter is not specified, the database will not be added to the list. If IBName is not specified, the default name will be specified (as when creating a database interactively).
• / UseTemplate- the creation of an infobase is carried out according to the template specified in<template file name>. Configuration files (.cf) or infobase dump files (.dt) can be used as templates. If no template is specified, the parameter is ignored.

Parameter ConnectionString is formed from pairs ParameterName = Value separated by semicolons ( ; ). If the Value contains spaces, it must be enclosed in double quotes. Possible connection string parameters:

The parameter is defined for the file variant:

File Information base directory.

For the client-server version, the parameters are defined:

Srvr 1C: Enterprise server name.

(8.1 and higher) If the command line for launching an executable file contains several parameters describing the path to the infobase (File and Srvr), then the last of the specified parameters is used.

(c 8.2 and 8.3) To ensure the smooth operation of client applications, it is possible to specify several cluster addresses. For this:

• The value of the Srvr parameter can be a comma-separated list of cluster addresses,
  For example: Srvr = "Server1, Server2" or Srvr = "Server1: 1741, Server2: 1741";
• In the dialog for adding an infobase in a client application, the value of the "Enterprise Cluster" property can be a comma-separated list of cluster addresses, for example: Server1, Server2 or Server1: 1741, Server2: 1741;

Ref Name of the infobase on the 1C: Enterprise server

DBMS(from 8.1) type of database server used:

• MSSQLServer- Microsoft SQL Server (default);
• PostgreSQL- PostgreSQL;
• IBMDB2- IBM DB2;
• OracleDatabase- Oracle Database (c 8.2).

DBSrvr(SQLSrvr in 8.0) The name of the SQL server.

DB(SQLDB in 8.0) The name of the SQL database.

DBUID(SQLUID in 8.0) SQL server username.

DBPwd(SQLPwd in 8.0) SQL server user password. If a password is not specified for the database server user, then this parameter can be omitted.

SQLYOffs Date offset used for storing dates in SQL server (for client / server version). Valid values ​​are 0 or 2000. The default is 0.

CrSQLDB(from 8.1) Create a database if it is absent ("y" - create a database if it is absent, "n" - do not create).

SchJobDn(since 8.1.11, before that it was as a general parameter) for the created infobase, prohibit the execution of routine creations (Y / N). The default is N.

SUsr The name of the cluster administrator where the initial image is to be created. This parameter must be specified if administrators are defined in the cluster and for them operating system authentication is not installed or is not suitable.
SPwd Cluster administrator password.

Parameters are defined for all variants:

• Usr Username.
• Pwd User password.
• Locale Language (country). Valid values ​​are the same as for the method Embedded language format(for example, "ru_RU"). By default, the regional settings of the current infobase are used.

General startup parameters in Enterprise or Configurator mode

• /@<ИмяФайла> The path to the file with command line parameters.
• / F<ПутьИБ> The path to the file infobase (excluding the file name).
• / S<ИмяКомпьютера\ИмяИБ> The address of the infobase on the 1C: Enterprise server.
• / Ws (from 8.2) String ws-connection.
• / IBName<имя информационной базы>Z launching an infobase by the name of the base in the list of infobases. The name must be enclosed in double quotes if necessary. Moreover, if the name contains double quotes, then you need to replace each double quotes with two double quotes. If more than one database with the specified name is found in the lists of databases, an error will be displayed to the user.
• / IBConnectionString allows you to specify the entire infobase connection string, in the form in which it is returned by the function InfoBaseConnectionString(). Parts of the connection string can be overridden by pre-existing parameters. For this it is necessary that / IBConnectionString was on the command line before them. When passing the connection string as a command line parameter, remember that the connection string contains quotes. Therefore, it is required to enclose the entire string in quotes, and double the quotes contained within.

Additional parameters of the connection string in the mode:

• wsn- username for authentication to;
• wsp- user password for authentication on the web server;
• wspauto- use automatic proxy server settings;
• wspsrv- proxy server address;
• wspport- proxy port;
• wspuser- username for proxy with authorization;
• wsppwd- password for proxy with authorization.

/ N<ИмяПользователя> Username as specified in the Configurator.

/ P<ПарольПользователя> The password for the user whose name is specified in the / N parameter. If the user does not have a password, this parameter can be omitted.

/ WSN<имя> (from 8.2) Username for authentication on the web server.

/ Wsp<пароль> (from 8.2) Password of the user, whose name is specified in the / WSN parameter, for authentication on the web server.

/ WA- Preventing the use of Windows authentication at startup.

/ WA + Mandatory use of Windows authentication at startup. If / WA is not specified at all, / WA + is assumed.

/ SAOnRestart Indicates that a password must be requested when the system is restarted from this session (not used in the thin client). By default, no password is requested.

/ itdi(from 8.2.14) Opening forms in the main window and using bookmarks to switch between open forms (working with bookmarks).

/ isdi(from 8.2.14) For working with separate windows.

/ LogUI Logging user actions.

/ Out<ИмяФайла>[-NoTruncate] Sets the file for displaying service messages. If NoTruncate is specified, the file is not cleared.

/ SchJobDn(since 8.1, since 8.1.11 appeared as a connection string parameter) Controls the execution of scheduled tasks. Possible values: "Y" or "N". "Y" - the created infobase will be prohibited from performing scheduled tasks.

/ AppAutoCheckVersion BUT automatic selection of the required version for each infobase.

/ AppAutoCheckMode BUT automatic determination of an application based on infobase data (main launch mode for configuration and launch mode for user).

Mode selection command line parameters:

CONFIG
launch of the 1C: Enterprise 8 system in the "Configurator" mode

ENTERPRISE
launch of the 1C: Enterprise 8 system in the "1C: Enterprise" mode

CREATEINFOBASE
creating delivery and update files

a string that specifies the infobase parameters, each of which is a fragment of the form
,
where Parameter Name is the name of the parameter, and Value is its value. Fragments are separated from each other by ";" symbols. If the value contains whitespace characters, it must be enclosed in double quotes (").

File mode options

File infobase directory;
Locale language (country) to be used when creating the infobase. The valid values ​​are the same as for the Format method parameter. The Locale parameter is optional. If not specified, the regional settings of the current infobase will be used.

Client-server mode options

Srvr server name 1C: Enterprise;
Ref name of the infobase on the server;
SQLSrvr SQL server name;
SQLDB is the name of the SQL database;
SQLUID SQL username;
SQLPwd SQL user password. If the password for the SQL user is not specified, then this parameter can be omitted.
SQLYOffs is the date offset used to store dates in SQL Server. It can take values ​​0 or 2000. This parameter is optional. If not specified, the value 0 is accepted.
Locale - language (country), (similar to the file variant).

Parameters are defined for all variants:

Usr Username;
Pwd password

/ AddInList parameter showing under what name to add the base to the list; if not specified, the base will not be added to the list. If a name is not specified, a default is used, similar to the interactive creation of an infobase.
Simultaneous use of keys is not allowed.

Command line parameters for specifying startup parameters:

/@
command line parameters are written in the specified file

/ F
path to the infobase, if it is stored in a file (you do not need to specify the file name)

/ S
the address of the infobase stored on the 1C: Enterprise 8 server is as follows:

/ N
Username. Should be specified in the same way as in the list of users created in the Configurator

/ P
the password of the user whose name is specified in the / N parameter. If the user does not have a password, this parameter can be omitted

/ WA-
prohibiting the use of Windows authentication at the start of the Enterprise or the Configurator

/ WA +
setting the mandatory use of Windows authentication at the start of 1C: Enterprise or the Configurator. If the / WA switch is not specified, it is assumed that the / WA + command line parameter is used

/ AU-
prohibition of displaying the question about updating the current version of 1C: Enterprise from the administrative installation

/ AU +
setting the output of the question about updating the current version of 1C: Enterprise from the administrative installation. If the / AU switch is not specified, it is assumed that the / AU + command line parameter is used

/ Out
[-NoTruncate]
installation of a file for displaying service messages. If the NoTruncate key is specified (separated by a space), the file is not cleared

/ L
a directory of localized interface resources is specified (for example, "RU")

/ DisableStartupMessages
Suppresses startup messages: “The database configuration does not match the saved configuration. Proceed?"; “Your computer is not powerful enough to edit the configuration help. To edit the Help, you need to install Microsoft Internet Explorer 6.0 or higher. "; “Your computer's capabilities are not enough for editing html-documents, including help topics. To edit html-documents, you need to install Microsoft Internet Explorer version 6.0 or higher. In this launch, editing html-documents will not be available. "

/ C
passing parameter to configuration

Batch mode

Using command line parameters, the administrator can run the configurator in batch mode to perform the following actions:

The administrator can use command line parameters to specify:

• launching the 1C: Enterprise 8 system in the Configurator mode;
• infobase parameters: user, password; for the file version - directory, language; for the client-server version - server name, infobase name, SQL server name, SQL database name, SQL username and password, date offset.

In addition, all startup parameters can be generated in an external file, the name of which is specified in the command line parameters.

After completing the actions specified in the startup parameters, the 1C: Enterprise configurator is closed.

Using the configurator batch launch mode allows you to automate the infobase maintenance process by launching the corresponding command files on a schedule.

Configurator batch mode command line parameters:

/ DumpIB
unloading an infobase in command mode

/ DumpCfg
saving configuration to file

/ UpdateDBCfg
[-WarningsAsErrors]
updating the database configuration. If the Warnings-AsErrors key is specified (separated by a space), then all warning messages will be treated as errors

/ DumpDBCfg
saving database configuration to file

/ RollbackCfg
return to database configuration

/ CheckModules
do syntactic control

/ UpdateCfg
updating a supported configuration

/ IBCheckAndRepair [-ReIndex]
[-LogIntergrity] [-RecalcTotals]
[-IBCompression]
[-TestOnly | [-BadRefCreate |
-BadRefClear | -BadRefNone]
[-BadDataCreate |
-BadDataDelete]]
test and fix the infobase

ReIndex
re-indexing tables

LogIntergrity
logical consistency check

RecalcTotals
recalculation of totals

IBCompression
compress tables

TestOnly
only testing when there are references to non-existent objects:

BadRefCreate
create objects

BadRefClear
clear objects

BadRefNone
do not change

With partial loss of objects:

BadDataCreate
create objects

BadDataDelete
delete objects

The simultaneous use of keys within a subgroup of parameters is not allowed. If the command is successful, it returns a return code of 0, otherwise 1 (101 if there are errors in the data).

Command line parameters for batch mode for creating distribution and update files:

/ CreateDistributionFiles
[-cffile]
[-cfufile
[-f | -v] +]
Create delivery and update files

Cffile
instruction to create a distribution

Cfufile
instruction to create an update

F
the distribution included in the update is specified by the name

V]
the distribution included in the update is specified by the version

Note: the -f | -v parameter group is repeated as many times as the distribution files are included in the update.

Command line parameters for working with the configuration repository:

/ DepotF
storage directory

/ DepotN
repository username

/ DepotP
vault user password

V
v - version number, if no version number is specified, or equal to -1, the latest version will be saved.

/ DepotUpdateCfg [-v] [-revised]
Update storage configuration from file (batch mode)

V
version number, if the version number is not specified, or is equal to -1, the latest version will be saved, if the configuration is connected to the repository, then the parameter is ignored

Revised
get captured objects if required. If the configuration is not connected to the repository, then the parameter is ignored.

Command line parameters for batch mode registration of 1C: Enterprise 8 as an Automation server:

/ RegServer
application registration

/ UnregServer
remove app registration

After completion, it closes the 1C: Enterprise 8 system.
If parameter values ​​include spaces (for example, path or file name), the values ​​must be enclosed in quotation marks.

Examples of

How to start 1C: Enterprise 8 from the command line

C: \ Program Files \ 1cv8 \ bin \ 1cv8.exe "ENTERPRISE / F D: \ Configuration \ Typical \ ControlTorg / N Username / P Password

C: \ Program Files \ 1cv8 \ bin \ 1cv8.exe "ENTERPRISE / S Server \ Base / N Username / P Password

C: \ Program Files \ 1cv8 \ bin \ 1cv8.exe "CONFIG / F D: \ Configurations \ Typical \ ControlTorg / N Username / P Password

How to force 1C: Enterprise to unload the database from the command line

C: \ Program Files \ 1cv8 \ bin \ 1cv8.exe "CONFIG / F D: \ ControlTorg / N Username / P Password / DumpIB c: \ name.dt

How to update changes to the current configuration in the database configuration from the command line

C: \ Program Files \ 1cv8 \ bin \ 1cv8.exe "CONFIG / F D: \ ControlTorg / N Username / P Password / UpdateDBCfg

How to test and fix an infobase without checking referential integrity in automatic mode

C: \ Program Files \ 1cv8 \ bin \ 1cv8.exe "CONFIG / F" C: \ DemoTrd2 "/ N" Fedorov (administrator) "/ P" "/ IBcheckAndRepair -LogIntegrity

How to perform a configuration check in automatic mode with the output of the check results to a file

C: \ Program Files \ 1cv8 \ bin \ 1cv8.exe "CONFIG / F" C: \ DemoTrd2 "/ N" Fedorov (administrator) "/ P" "/OutD:\my\log.txt / CheckConfig -ClientServer -Client -ExternalConnectionServer -ExternalConnection -Server -DistributiveModules -IncorrectReferences -ConfigLogicalIntegrity -UnreferenceProcedures -HandlersExistence -EmptyHandlers

How to shorten the log file programmatically

C: \ Program Files \ 1cv8 \ bin \ 1cv8.exe "CONFIG / F" C: \ DemoTrd2 "/ N" Fedorov (administrator) "/ P" "/OutD:\my\log.txt / ReduceEventLogSize 2004-12- 26 -saveAsC: \ OldLog.elf

How to unload application modules as text files from the command line

C: \ Program Files \ 1cv8 \ bin \ 1cv8.exe "CONFIG / F" C: \ DemoTrd2 "/ N" Fedorov (administrator) "/ P" "/ DumpConfigFiles" D: \ 1 \ 11 "-Module

How to load help files saved in htm format into an application solution

C: \ Program Files \ 1cv8 \ bin \ 1cv8.exe "CONFIG / F" C: \ DemoTrd2 "/ N" Fedorov (administrator) "/ P" "/ LoadConfigFiles" D: \ 1 \ 11 "-Help

Often, when working with 1C, it is necessary to carry out some of the same type of operations, which are repeated systematically in time and simply distract from the main work. These can be various downloads and unloads, the formation of some kind of data for external analysis, etc. There is a fairly simple way to automate these operations and actually forget about them, periodically receiving log files by mail for control.

It's great if you have already written these operations with external processing, no problem, if this is not the case, create and transfer everything there. Further, to check the functionality, I recommend testing all this in manual mode and then, if everything works as it should, rewrite the main processing code so that when external processing is loaded, it starts automatically, without pressing the button, execute, and the like. The simplest thing is to move the code into the procedure OnOpen ().

The next step is to automatically close the program after performing the external processing that we have created and it is already working for us. To do this, in the procedure OnOpen () at the very end, insert the following command: EndSystemWork (False); in this case the parameter RequestOpportunity we pass the value "False" to cut off various options for additional system questions when closing, thereby initiating an unconditional shutdown of 1C after performing this external processing. To be sure, we run the program again and perform processing and make sure that it worked and the program closed itself.

"C: \ Program Files (x86) \ 1cv8 \ 8.3.5.хххх \ bin \ 1cv8.exe" ENTERPRISE / DisableStartupMessages / FС: \ path to database / N "Username" / P "UserPassword" / Execute c: \ path to processing \ self-processing.epf

Let's decipher:

1. "C: \ Program Files (x86) \ 1cv8 \ 8.3.5.хххх \ bin \ 1cv8.exe" ENTERPRISE - the 1C engine itself in this case is 8.3, check the path yourself, it differs depending on the version and engine including do not forget to edit it after updating the last one.

2. / DisableStartupMessages - disable all messages at system startup.

4. / N "UserName" / P "UserPassword" - respectively / N username, also immediately without a space and / P password.

5. / Execute c: \ path to processing \ self-processing.epf - / Execute starts our processing, the path and name must follow this key.

Now that's all, it remains only to add our cmd file to the task scheduler: avtozapusk1c.cmd by specifying the schedule for its launch.

To track the work of external processing, I recommend creating a separate user for it, it is still optimal that the processing itself creates a log file, which also periodically falls to your mail.

These are not clever tools that help automate everyday routine operations, good luck to you!

In this article I will talk about the possible parameters and startup keys for 1C 8.3, 8.2 and 8.1. For the convenience of users, you can use some of the presented features. I will not go deep and describe all the possible parameters, but I will describe those moments that, in my opinion, may be needed by ordinary users of the program.

On the 1C 8.1 platform, there was only one option for launching the 1C application - this is a thick client. I will decipher this concept a little. 1C is a client-server software and client applications are used to run it.

The concept of a thick client did not exist before the concept of a thin client appeared, and it means a great demand on the resources of the end user's computer.

With the release of the 1C 8.2 platform, it became possible to use a thin client and a web client. All these client applications have their own advantages and limitations, many articles have already been written about this, and I will not go into it deeply. I will only mention the main points.

• Configurator works only in thick client mode.
• Fat client the most demanding on computer resources.
• Thin client not demanding on the resources of the user's computer in the client-server mode of operation, since all the load goes to the server.
• Web client only requires a browser and internet connection. You can work in the program from anywhere in the world. Comfortable work depends only on the speed of the Internet connection. All the load falls on the web server.

The most common launch option so far, in my opinion, is a thick client with a file infobase. Although the future is undoubtedly with the web client.

I also note that by default, in the database launch settings, it is set to “Select automatically” and think about which client and which database you do not need to launch.

1C launch parameters from the command line with automatic user selection

In my work, I often encountered errors in the operation of the 1C Accounting program, for example, some document logs were not displayed if no user was created in the 1C database.

To fix it, it was required to create and go under it, clicking OK each time in the user selection window. And this is, in principle, correct if several users work in the database, each must go under his own.

But in some cases, when only one user always works with the program, for example, in the basic versions, it seems impractical to confirm his choice each time by pressing the OK button if the user does not have a password to enter. After all, it is clear that he is alone.

If you do not want to select a user every time you start 1C, there are several ways to do this.

If you always work in the 1C 8 program from the same computer, under the same user of the Windows operating system, then you can do the following:

We launch the infobase in the configurator mode. Choose Administration => Users. We find your user in the list and click change:

Uncheck the "1C: Enterprise Authentication" checkbox and check the "Operating system authentication" checkbox. Press select, a window for selecting an operating system user appears. In my case, the “Domains” list contains the name of my computer, the “Users” list contains the existing users of my Windows OS.

We select our user and save all changes:

If you have only one user with full rights, and you are trying to provide him with OS authentication, the program will display a warning. In this case, create another user with full rights. I think this was done for security reasons, so that in the event of a malfunction of the OS, you can still enter 1C with full rights.

Using additional parameters for launching the 1C infobase. As scary as it sounds, in fact, there is nothing complicated about it. To do this, you do not need to climb into the configurator, unless you look at the help for the possible parameters for starting. You need to specify the parameters Username and password.

From the 1C help:

• / N<имя>- Username. Should be specified in the same way as in the list of users created in the Configurator.
• / P<пароль>- password of the user whose name is specified in the / N parameter. If the user does not have a password, this parameter can be omitted.

We know our username and password, but where do we put them? Select the required base in the list and click change:

Scroll further to the last page of settings and see the line we need “Additional launch parameters”. Here we write / N “your username” / P “your password”. If there is no password, then this parameter and its value are not written. Save with the "Finish" button. If you made a mistake with the password in the parameter, then the user selection window will also pop up. Make sure everything is entered correctly.

If you want to change the username and password, then you need to make corrections in the parameters.

Launching a specific 1C database without selecting from the list of databases

For example, you do not want to select a database from the list every time you start 1C Enterprise, but create a separate shortcut on the desktop for each database. We need one more launch parameter. From the 1C help:

• / F<путь>- path to the infobase, if it is stored in a file (you do not need to specify the file name).

Let's take a look at the example of the 1C file base. Do the same for all other bases from the list if necessary.

And those who have a database on the server should use another parameter to indicate the path:

• / S<адрес>- the address of the infobase stored on the 1C: Enterprise 8 server is as follows:<Имя компьютера, работающего сервером приложений>\ <Ссылочное имя информационной базы, известное в рамках сервера 1С:Предприятия 8>

First, let's create a shortcut for the 1cestart.exe executable file. The easiest way is to copy the 1C Enterprise shortcut you already have and rename it, for example, in UT 10.3, so that it is clear which database it will launch:

Now go to the properties of the shortcut and in the object field, after the quotes, write the parameters through a space:

First, we write the ENTERPRISE parameter, it means that at startup, the Enterprise launch mode will be selected. If it is necessary to start the configurator, then the DESIGNER parameter is written.

• "C: \ Program Files (x86) \ 1cv82 \ common \ 1cestart.exe" enterprise / F "D: \ 1C \ Demo base 1C \ Trade management (demo) for the site".

We save and now, when starting from this shortcut, exactly the base will be launched, the path to which you have registered.

You can add the user authentication parameters described above to this shortcut:

• "C: \ Program Files (x86) \ 1cv82 \ common \ 1cestart.exe" enterprise / F "D: \ 1C \ Demo base 1C \ Trade management (demo) for the site" / N "Fedorov (administrator)" / P " 131 ”.

Now, when you start from a shortcut, the base you need will be launched under the specified user with a password. If there is no password, this parameter is removed.

Keys and parameters for starting the 1C database at Windows startup

Let's say you want that when you turn on the computer and start Windows, you automatically start the 1C database you need under your username with a password. To do this, you need to create a shortcut with launch parameters as described above and put it in the Startup folder. Go to Start => All programs see the Startup folder, click on it with the other button and click Open. In the opened Startup folder, copy the created shortcut and the next time you start Windows 1C will start with the parameters specified in it.

Selection of different versions of the platform for launching 1C databases

For example, you simultaneously use platforms 8.1 and 8.2 to run different bases and you want to run them from the same list. For each database, it is possible to specify which version of the platform will run this database. People often encounter a problem when someone has registered a specific version of the platform in the launch settings of the database, and after updating the platform, the launch still occurs with the old version. To change the version of the platform to run, select a base from the list and click "Change". In the last window, specify the required version of the platform, just keep in mind that it must be installed on your computer.

With such an entry, the latest version of the 8.1 platforms installed on your computer for the selected database will be launched.

With such an entry, platform 8.1.15.14 will be selected to launch this database.

By default, when adding a database to the list, the value 8.2 or 8.3 is set. I think this article can come in handy when switching to version 8.3, when everyone in the database settings will have a version for launching 8.2 and no one will see the result of the update and transition to 8.3, tk. the bases will still be launched on the 8.2 platform.

When launching the 1CV8.EXE file, the following parameters can be specified in the command line:
Mode selection command line parameters:
CONFIG - launch of the 1C: Enterprise 8.x system in the "Configurator" mode; ENTERPRISE - launch of the 1C: Enterprise 8.x system in the "1C: Enterprise" mode;
CREATEINFOBASE ] - creating an infobase (
a string that specifies the infobase parameters, each of which is a fragment of the form<Имя параметра=><Значение>, where Parameter Name is the name of the parameter and Value is its value.
Fragments are separated from each other by ';'.
If the value contains whitespace characters, it must be enclosed in double quotes (“).

The parameter is defined for the file variant:

File - infobase directory;
Locale - language (country) that will be used to create the infobase. Valid values ​​are the same as parameter<Форматная строка>method Format. The Locale parameter is optional. If not specified, the regional settings of the current infobase will be used.

For the client-server version, the parameters are defined:
Srvr - 1C: Enterprise server name;
Ref - name of the infobase on the server;
SQLSrvr - SQL server name;
SQLDB is the name of the SQL database;
SQLUID - SQL username;
SQLPwd - SQL user password. If the password for the SQL user is not specified, then this parameter can be omitted.
SQLYOffs is the date offset used to store dates in SQL Server. It can take values ​​0 or 2000. This parameter is optional. If not specified, the value 0 is accepted.
Locale - language (country), (similar to the file variant).

Parameters are defined for all variants:
Usr - username;
Pwd - password
/ AddInList - a parameter showing under what name to add the base to the list, if not specified, the base will not be added to the list. If a name is not specified, a default is used, similar to the interactive creation of an infobase.

Simultaneous use of keys is not allowed.

Command line parameters for specifying startup parameters:
/@<имя файла>- command line parameters are written in the specified file
/ F<Путь>- path to the infobase, if it is stored in a file (you do not need to specify the file name)
/ S<Адрес>- the address of the infobase stored on the 1C: Enterprise 8.x server is as follows:
<Имя компьютера, работающего сервером приложений>\ <Ссылочное имя информационной базы, известное в рамках сервера 1С:Предприятия 8.x>

/ N<Имя>-Username. Should be specified in the same way as in the list of users created in the Configurator
/ P<Пароль>-password of the user whose name is specified in the / N parameter. If the user does not have a password, this parameter can be omitted
/ WA - prohibiting the use of Windows authentication at the start of the Enterprise or the Configurator
/ WA + setting the mandatory use of Windows authentication at the start of 1C: Enterprise or the Configurator. If the / WA switch is not specified, it is assumed that the / WA + command line parameter is used
/ AU - prohibition of displaying the question about updating the current version of 1C: Enterprise from the administrative installation
/ AU + setting the output of the question about updating the current version of 1C: Enterprise from the administrative installation. If the / AU switch is not specified, it is assumed that the / AU + command line parameter is used
/ Out<Имя файла>[-NoT_runcate] - setting the file for displaying service messages. If the –NoT_runcate switch is specified (separated by a space), the file is not cleared
/ L<Каталог>- the directory of localized interface resources is indicated (for example, "RU")
/ DisableStartupMessages -Suppresses startup messages: “The database configuration does not match the saved configuration. Proceed?"; “Your computer is not powerful enough to edit the configuration help. To edit the Help, you need to install Microsoft Internet Explorer 6.0 or higher. "; “Your computer's capabilities are not enough for editing html-documents, including help topics. To edit html-documents, you need to install Microsoft Internet Explorer version 6.0 or higher. In this launch, editing html-documents will not be available. "
/ C<Строка текста>- passing the parameter to the configuration Command line parameters of the batch mode of the configurator:
/ DumpIB<Имя файла>- unloading the infobase in command mode
/ RestoreIB<Имя файла>- loading the infobase in command mode
/ DumpCfg<имя cf файла>- saving the configuration to a file
/ LoadCfg<имя cf файла>- loading configuration from file
/ UpdateDBCfg [-WarningsAsErrors] - update the database configuration. If the WarningsAsErrors key is specified (separated by a space), then all warning messages will be treated as errors
/ DumpDBCfg<имя cf файла>- saving the database configuration to a file
/ RollbackCfg - return to database configuration
/ CheckModules - perform syntax check
/ UpdateCfg<имя cf | cfu файла>- updating the supported configuration
/ IBCheckAndRepair [-ReIndex] [-LogIntergrity] [-RecalcTotals] [-IBCompression] [-TestOnly | [-BadRefCreate | -BadRefClear | -BadRefNone] [-BadDataCreate | -BadDataDelete]] - test and fix the infobase
ReIndex - re-indexing tables
LogIntergrity - check logical integrity
RecalcTotals - recalculation of totals
IBCompression - table compression
TestOnly - testing only

If there are references to non-existent objects:
BadRefCreate - create objects
BadRefClear - clear objects
BadRefNone - do not change

with partial loss of objects:
BadDataCreate - create objects
BadDataDelete - delete objects

The simultaneous use of keys within a subgroup of parameters is not allowed.
If the command is successful, it returns a return code of 0, otherwise - 1 (101 if there are errors in the data).
After completion, it closes the 1C: Enterprise 8.x system.

Command line parameters for batch mode for creating distribution and update files:
/ CreateDistributionFiles [-cffile<имя cf файла>] [-cfufile<имя cfu файла>[-f<имя cf файла>| -v<версия дистрибутива>] +] - Creation of delivery and update files
-cffile<имя cf файла>- an instruction to create a distribution kit
-cfufile<имя cfu файла>- an instruction to create an update
-f<имя cf файла>- the distribution kit included in the update is specified by the name
-v<версия дистрибутива>] - the distribution included in the update is specified by the version
Note: parameter group -f<имя cf файла>| -v<версия дистрибутива>repeats as many times as distribution files are included in the update.