Command line options to specify startup options. Command line parameters for specifying launch parameters Batch files for launching 1s

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

The following parameters are defined for the client-server option:
Srvr - 1C:Enterprise server name;
Ref - name of the infobase on the server;
SQLSrvr - SQL server name;
SQLDB - SQL database name;
SQLUID - SQL username;
SQLPwd - SQL user password. If a 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. Can take values ​​0 or 2000. This parameter is not required to be specified. If not specified, the value 0 is accepted.
Locale - language (country), (similar to the file version).

For all options the following parameters are defined:
Usr - username;
Pwd - password
/AddInList - parameter indicating under what name to add the database to the list; if not specified, the database will not be added to the list. If a name is not specified, the default is used, similar to the interactive creation of an infobase.

Simultaneous use of keys is not allowed.

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

/N<Имя>-Username. Must 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 - prohibits the use of Windows authentication when starting an Enterprise or Configurator
/WA+ setting the mandatory use of Windows authentication when starting 1C:Enterprise or Configurator. If the /WA switch is not specified, the /WA+ command line option is assumed to be used.
/AU - prohibits the display of a question about updating the current version of 1C:Enterprise from an administrative installation
/AU+ setting to display a question about updating the current version of 1C:Enterprise from an administrative installation. If the /AU switch is not specified, the /AU+ command line option is assumed to be used.
/Out<Имя файла>[-NoT_runcate] - setting the file for outputting service messages. If the –NoT_runcate switch is specified (separated by a space), the file is not cleared
/L<Каталог>- indicates the directory of localized interface resources (for example, “RU”)
/DisableStartupMessages -Suppresses startup messages: “The database configuration does not match the saved configuration. Continue?"; “Your computer's capabilities are not sufficient to edit the configuration help. To edit the help, you must install Microsoft Internet Explorer version 6.0 or higher.”; “Your computer’s capabilities are not sufficient to edit HTML documents, including help topics. To edit HTML documents, you must 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 configurator batch mode:
/DumpIB<Имя файла>-uploading the information base in command mode
/RestoreIB<Имя файла>- loading the information base 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 correct the infobase
ReIndex - reindexing tables
LogIntergrity - logical integrity check
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

In case of partial loss of objects:
BadDataCreate - create objects
BadDataDelete - delete objects

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

Batch mode command line options for creating delivery and update files:
/CreateDistributionFiles [-cffile<имя cf файла>] [-cfufile<имя cfu файла>[-f<имя cf файла>|-v<версия дистрибутива>]+] - Create delivery and update files
-cffile<имя cf файла>- instructions to create a distribution kit
-cfufile<имя cfu файла>- instructions to create an update
-f<имя cf файла>- the distribution 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<версия дистрибутива>is repeated as many times as distribution files are included in the update.

Command line parameters for working with the configuration repository:
/DepotF - storage directory
/DepotN - storage username
/DepotP - storage user password
/DepotDumpCfg<имя cf файла>[-v<номер версии хранилища>] - save configuration from storage to file (batch mode)
-v<номер версии хранилища>
v - version number, if the version number is not specified or is 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 storage, then the parameter is ignored
-revised - receive captured objects, if required. If the configuration is not connected to the storage, the parameter is ignored.

Command line parameters for batch mode registration of 1C:Enterprise 8.x as an Automation server:
/RegServer - application registration
/UnregServer - deleting application registration
After execution, closes the 1C:Enterprise 8.x system.
If parameter values ​​include spaces (for example, a path or file name), the values ​​must be enclosed in quotation marks.

Below are command line examples for starting the 1C:Enterprise 8.x system:
C:\1CV8\BIN\1CV8.EXE ENTERPRISE /FDB
The given command line means that the 1C:Enterprise 8.x system will be launched in “1C:Enterprise” mode, and the infobase is located in the “\DB” subdirectory of the “C:\1CV8\BIN” directory.

C:\1cv81bin\1cv8.exe enterprise /s Serv06\ZUP /L RU
And this command line below means that the 1C:Enterprise 8.x system will be launched in the “1C:Enterprise” mode, the address of the ZUP infobase stored on the 1C:Enterprise server Serv06 and the Russian interface

To remove the blocking of connections to the infobase, you need to:
Log in to the infobase using the "/UC" launch parameter with the same access permission code that was specified when setting the lock. Start this processing by specifying “Unblock connections” as the blocking action. Click the "Run" button.
in cmd
start C:\Progra~1\1cv81\bin\1cv8.exe /UC<код доступа>
in the label
"C:\Program Files\1cv81\bin\1cv8.exe" ENTERPRISE /F"D:\Configurations\Typical\UprTorg" /N"Username" /P"Password" /UC 456743

DOS Batch File Code
echo off
cls
"C:\Program Files\1cv81\bin\1cv8.exe" ENTERPRISE /S"server\ESKM" /N"Admin" /P"ESKM" /DisableStartupMessages /C"StopUsers"
"C:\Program Files\1cv81\bin\1cv8.exe" CONFIG /S"server\ESKM" /N"Admin" /P"ESKM" /DisableStartupMessages /UpdateDBCfg /UC"IB Configuration Batch Update"
"C:\Program Files\1cv81\bin\1cv8.exe" ENTERPRISE /S"server\ESKM" /N"Admin" /P"ESKM" /C"Allow Users to Work" /UC"BatchUpdateIBConfiguration"

In this article I will talk about possible parameters and launch 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 possible parameters, but I will describe those points that, in my opinion, ordinary users of the program may need.

On the 1C 8.1 platform there was only one option for launching the 1C application - a thick client. Let me 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 greater demands 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 advantages and limitations; many articles have already been written about this, and I will not go deeper into this. I will note only the main points.

• Configurator only works in thick client mode.
• Fat client the most demanding of computer resources.
• Thin client is not demanding on the resources of the user’s computer in client-server mode, because all the load goes to the server.
• Web client Requires only a browser and an Internet connection. You can work in the program from anywhere in the world. Comfortable work depends only on the speed of your Internet connection. The entire load falls on the web server.

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

I’ll also note that by default in the database launch settings it’s “Select automatically” and you don’t need to think about which client and which database you need to launch.

1C launch options 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 not a single user was created in the 1C database.

To fix it, you had to create and log in, clicking OK each time in the user selection window. And this is, in principle, correct: if there are several users working in the database, each should log in under their own account.

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

If you don’t 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 Windows operating system user, then you can do the following:

We launch the information base in configurator mode. Select Administration => Users. Find your user in the list and click edit:

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

Select your user and save all changes:

If you have only one user with full rights, and you try to give him OS authentication, the program will display a warning. In this case, you should create another user with full rights. I think this was done for security reasons, so that if the OS malfunctions, they can still log into 1C with full rights.

Using additional parameters for launching the 1C information base. No matter how scary it may sound, there is actually nothing complicated about it. There is no need to go into the configurator for this, except to look at the possible parameters for launching in the help. You need to specify the Username and Password as parameters.

From the 1C help:

• /N<имя>- Username. Must 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 can we register them? Select the desired database in the list and click edit:

Scroll Next to the last page of settings and see the line we need “Advanced launch options”. 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 “Done” button. If you make a mistake with the password in the parameter, the user selection window will also pop up. Make sure everything is entered correctly.

If you want to change your username and password, you will need to make corrections to the parameters.

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

For example, you don’t 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'll need one more launch parameter. From the 1C help:

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

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

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

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

First, let's create a shortcut for the executable file 1cestart.exe. The easiest way is to copy the 1C Enterprise shortcut you already have and rename it, for example, to 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 separated by a space we write the parameters:

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

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

We save it and now when you start from this shortcut, it will launch exactly the database whose path you specified.

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 1C database\Trade management (demo) for the site” /N “Fedorov (administrator)” /P “ 131".

Now, when you start from the shortcut, the database you need will be launched under the specified user and password. If there is no password, this option is removed.

Keys and parameters for launching the 1C database when starting Windows

Let's say you want that when you turn on your computer and start Windows, the 1C database you need will automatically start under your user 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 right button and click Open. Copy the created shortcut into the Startup folder that opens and the next time you start Windows 1C it will start with the parameters specified in it.

Selecting different versions of the platform for launching 1C databases

For example, you simultaneously use platforms 8.1 and 8.2 to run different databases and you want to launch them from one 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 specified a certain version of the platform in the database launch settings and after updating the platform, the launch still occurs with the old version. To change the launch platform version, select the 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 a recording, 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 run this database.

By default, when adding a database to the list, the value is set to 8.2 or 8.3. I think this article may be useful when switching to version 8.3, when everyone in the database settings will have the version to run 8.2 and no one will see the result of the update and switch to 8.3, because the databases will still be launched on the 8.2 platform.

I launch it, but it doesn't start. What does he write? Doesn't write anything. Well, if he doesn’t write anything, this doesn’t happen! Well, he writes something in yellow in English. How is this yellow??? Well, the letters here are all non-Russian, come and figure it out yourself!

When you click on the 1C shortcut on the Windows desktop, you are not launching 1C, but a completely different program :)

Catalog 1C

In the catalog of installed 1C 8.2 (especially for those familiar with version 8.1), you can break your legs.

So, it is usually installed at:

C:\Program files\1Cv82\

Inside there are directories with [sub]versions of 1C. 1C executable files of each version are located in the bin directory of each version. Every time you update the platform, instead of updating, this beauty adds another new catalog!

Size 1C. It eats up about 250MB of disk space for each version. You can imagine what will happen if you update it for a couple of years :)

In the “Common” subdirectory there is a 1C “launcher” file - the 1cestart.exe program, a shortcut to which is located on your desktop.

The launch of 1C begins with this executable file. So, we have already launched one program!

It is this program, with the help of artificial intelligence built into it, that chooses which version of 1C to launch and how to do it.

Files of different versions of 1C!

Now you can enter each database with a specific version of 1C 8.2, one of those installed in this directory. This is what everyone was waiting for and what should be installed by default, and there’s not even anything to say except words of gratitude.

Of course, by default, 1C is included in the database as the latest installed version, but otherwise you need to make a small number of settings.

You can see these settings in the instructions for this lesson.

Corporate launch

If we are an organization, then everything can be even cooler. 1C no longer needs to be painfully and time-consuming to install (and update) on “all the company’s computers..”.

She can now do this herself (the question remains unclear to me - what about local admin rights, friend?).

It is organized like this:

1) We distribute among users a shortcut to launch the 1C starter program, which is physically located on the network, surrounded by distribution kits of 1C versions/updates. Where the distributions are - of course, is indicated in the configuration file.

2) When launched, this program analyzes what is installed on the user’s computer and installs what is needed.

3) And then everything happened like magic! Profit!

Have we already launched?

So we settled on the fact that the user launches the 1C starter program file. And she is already launching 1C itself. Right?

No! Not true

After performing a simple experiment - by clicking on the 1C shortcut file - you will see a window with a choice of the database you want to enter.

This window is also a separate 1C program, the file 1cv8s.exe, which is located in the bin directory of each version of 1C 8.2.

The launch of 1C continues by launching the program to select the 1C database. So, we have already launched two programs!!

And after selecting a specific database, 1C itself will be launched - file 1cv8.exe (thick client) or file 1cv8c.exe (thin client), with the parameters specified on the command line.

The launch of 1C ends with the launch of 1C itself. So we have already launched three programs!!!

If you are very cunning and try to launch the thick client directly without specifying parameters on the command line, it will launch the 1cv8s.exe file back.

Find ways to beat 1C and speed up the launch of 1C three times further in this lesson!

Creating a 1C database

Mode selection command line options:

CONFIG
launching the 1C:Enterprise 8 system in the “Configurator” mode

ENTERPRISE
launching the 1C:Enterprise 8 system in the “1C:Enterprise” mode

CREATEINFOBASE
creating delivery and update files

a line specifying 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 a value contains whitespace, it must be enclosed in double quotes (").

File Mode Options

File information base directory;
Locale is the language (country) that will be used to create the information base. Valid values ​​are the same as for the Format method parameter. The Locale parameter is not required. If not specified, the regional settings of the current infobase will be used.

Client-server mode parameters

Srvr 1C:Enterprise server name;
Ref name of the infobase on the server;
SQLSrvr SQL server name;
SQLDB SQL database name;
SQLUID SQL username;
SQLPwd SQL user password. If a 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. Can take values ​​0 or 2000. This parameter is not required to be specified. If not specified, the value 0 is accepted.
Locale - language (country), (similar to the file version).

For all options the following parameters are defined:

Usr Username;
Pwd password

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

Command line options to specify startup options:

/@
command line parameters are written in the specified file

/F
path to the infobase, if it is stored in a file (the file name does not need to be specified)

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

/N
Username. Must 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 when starting an Enterprise or Configurator

/WA+
setting the mandatory use of Windows authentication when starting 1C:Enterprise or Configurator. If the /WA switch is not specified, the /WA+ command line option is assumed to be used.

/AU-
prohibiting the display of a question about updating the current version of 1C:Enterprise from an administrative installation

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

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

/L
indicates the directory of localized interface resources (for example, “RU”)

/DisableStartupMessages
Suppresses startup messages: “The database configuration does not match the saved configuration. Continue?"; “Your computer's capabilities are not sufficient to edit the configuration help. To edit the help, you must install Microsoft Internet Explorer version 6.0 or higher.”; “Your computer’s capabilities are not sufficient to edit HTML documents, including help topics. To edit HTML documents, you must install Microsoft Internet Explorer version 6.0 or higher. In this launch, editing html documents will not be available."

/C
passing a parameter to the configuration

Batch mode

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

Using command line parameters, an administrator can specify:

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

In addition, all launch 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 launch parameters, the 1C:Enterprise configurator closes.

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

Configurator batch mode command line parameters:

/DumpIB
unloading the 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
perform syntax check

/UpdateCfg
updating a supported configuration

/IBCheckAndRepair [-ReIndex]
[-LogIntergrity] [-RecalcTotals]
[-IBCompression]
[-TestOnly | [-BadRefCreate |
-BadRefClear | -BadRefNone]
[-BadDataCreate |
-BadDataDelete] ]
perform testing and correction of the information base

ReIndex
table reindexing

LogIntergrity
logical integrity check

RecalcTotals
recalculation of results

IBCompression
table compression

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

BadRefCreate
create objects

BadRefClear
clear objects

BadRefNone
don't change

In case of partial loss of objects:

BadDataCreate
create objects

BadDataDelete
delete objects

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

Batch mode command line options for creating delivery and update files:

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

Cffile
instructions to create a distribution

Cfufile
instructions to create an update

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

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

Note: the group of parameters -f |-v 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
storage username

/DepotP
storage user password

V
v - version number, if the version number is not specified or is 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 storage, then the parameter is ignored

Revised
receive captured objects if necessary. If the configuration is not connected to the storage, the parameter is ignored.

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

/RegServer
application registration

/UnregServer
deleting application registration

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

Examples

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

C:\Program Files\1cv8\bin\1cv8.exe" ENTERPRISE /F D:\Configurations\Typical\Trading Control /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\Trading Control /N Username /P Password

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

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

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

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

How to test and correct an infobase without checking referential integrity automatically

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

How to perform a configuration check automatically and output 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 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 modules of an application solution 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

In this article I will tell you about 1C launch parameters and how to use them. I will give several examples of how to use these parameters. After reading the article, you will be able to automate some everyday processes.

When starting 1C:Enterprise, you can use the launch parameters, which can be specified in the settings or in the shortcut that you use to launch 1C.

Launch mode 1C

CONFIG— 1C will start in Configurator mode.
ENTERPRISE— 1C will start in Enterprise mode.

1cestart.exe- a file for launching the 1C program, usually located in the “1cv8\common” folder. When launched, it automatically detects the required version of the client. When installing 1C, shortcuts on the desktop and in the Start menu refer to this file.

1C launch parameters for automatic user selection

• /N"Username"
• /P"User Password"

The username and password must match the username and password specified in the list of users in the Configurator. Users can be viewed in the Configurator, go to the top menu: Administration > Users. If the password is empty, then this field can be omitted.

These parameters can be specified in the settings when editing a database in the list of databases. In the "Advanced launch options" field.

Launch 1C and go to the infobase settings, the following window should appear:

Enter the parameters as shown in the figure, indicating your username and password, then click “Finish”. If you did everything correctly, then when you enter this database, you will not be asked for your username and password.

1C launch parameters for automatic database launch

• /F “address” - the address to the database, if it is stored in a file version.

If your database is stored on a server, you need to set the launch parameters differently:

• /S “address” - specify the address as follows: “Name of the server (infobase cluster)” \ “Name of the infobase on the server”

These parameters must be specified in the shortcut that you use to launch 1C:Enterprise. Go to the shortcut properties, at the end of the “Object” field, add the parameters you need.

If everything is done correctly, when you launch the shortcut, the database that you specified in the parameters should start.

For convenience, you can create a new shortcut, or copy the one you use.

Autoload 1C at system startup

If you need to launch 1C Enterprise when the system starts with the necessary parameters, you need to copy the 1C shortcut to the Startup folder.

If it contains 1C startup parameters, they will work when the system starts.

You can combine any 1C launch parameters. To do this, simply write down the necessary parameters in the 1C settings or in the shortcut.

Additional launch parameters 1C

• /LogUI— recording user actions in the log. (Writing will be done in the user directory, in a file called “logui.txt”)
• /DumpIB " Upload file address « — unloading the database. Suitable for creating automatic database archiving.
• /Execute " External processing address” - the parameter is intended to automatically start external processing after system startup.
• /C“String parameter” - passes the parameter to the configuration. You can access it through the global context in the “Launch Parameter” configurator.
• /DisableStartupMessages– the parameter removes system messages when starting 1C Enterprise.

When editing the infobase. You can specify the version of 1C through which to launch (suitable if you have several databases installed running under different versions of the client)

An example of using parameters for automatic archiving of an infobase.

"C:\Program Files (x86)\1cv8\common\1cestart.exe" CONFIG /F"С:\Base_Buh" /N"user" /P"111″ /DisableStartupMessages /DumpIB C:\Arhiv\Buh.dt / Out" C:\Arhiv\log_arhiv.txt" -NoTruncate

If you enter these parameters into the shortcut for launching 1C in the “Object” field, an archive of the database will be created, which is located “C:\Base_Buh” in the folder “C:\Arhiv” under the name “Buh.dt”. An entry will also be made to the log file “C:\Arhiv\log_arhiv.txt”. Indicate your paths, where the database is located, and where you want to create archives.

Configuring Application Debug Launch Options

When developing applications, it is often necessary to launch the 1C debugger under a specific user; to do this, go to the configurator: Help > Options

On the “Launch 1C:Enterprise” tab, in the “User” group, the current user is set by default (under which you logged into the configurator). You can change it to whatever you need. And debugging will start under the selected user.

Also, here you can specify which client to run the application under.

With these simple steps you can implement useful functions in the 1C:Enterprise program.