Main > Forum > 1C:Enterprise Platform > 1C:Enterprise – Business applications platform > Error : Load New Configuration From File and Update DB on CentOS 7.

Forum

Search UsersRules
Error : Load New Configuration From File and Update DB on CentOS 7.
#1
Just came
Points:: 0
Joined:: May 25, 2017

Version 1C: 8.3.8.1652
Version OS: CentOS 7
DB : Oracle 12.1.0.2.0 - 64 bits

Load new configuration from file. After that, i make the update of the database configuration.

Profile
#2
Active user
Points:: 0
Joined:: Nov 3, 2011

Onofras Ioan,

in most cases, clearing the cache helps. To clear the cache, do the following:

Method 1.

1. In the list of infobases, click your infobase, then click Settings.
2. In the Configuration template and update directories field, find a path that looks like this: C:\Documents and Settings\username\Application Data\1C\1Cv8\tmplts\1c.
3. The path to the cache folder will look like this: C:\Documents and Settings\username\Application Data\1C\1Cv8\. Open this folder.
4. You will see a lot of folders with names like this: 0a3fb881-abde-4208-839d-0f80874cb3cb. Delete them all.

Method 2.

Remove the infobase from the list, then add it back. This does not actually delete the old cache files, it simply assigns a new cache folder to the infobase.

Method 3 (thin client only).

Run the platform with /ClearCache parameter.

If clearing the cache does not help, verify and repair the infobase. In Designer, on the Administration menu, click Verify and repair.

Please let me know if this helped.

Profile
#3
Just came
Points:: 0
Joined:: May 25, 2017

That it is a newly created base in which we are trying to load an existing configuration and i tried all the methods. After i update, i can not access the designer to do a repair.

Profile
#4
Active user
Points:: 0
Joined:: Nov 3, 2011

Onofras Ioan,

try the following methods that do not require running Designer.

- If it is a file infobase, verify and repair it using chdbfl.exe utility, which is located in C:\Program Files (x86)\1cv8\<version>\bin.

- If you have a client/server infobase with SQL server, try "delete * from configsave" query.

Profile
Subscribe
Users browsing this topic (guests: 1, registered: 0, hidden: 0)



© 1C LLC. All rights reserved
1C Company respects the privacy of our customers and visitors
to our Web-site.