Platform: 1C:Enterprise 8.3 (8.3.14.1694)
Configuration: Solucion contable para peqenas y medianas empresas (2.7.12b) (http://www.abaco.com.ec/index.php?id=16)
Abaco Soluciones S.A. 2011-2018
(www.abaco.com.ec)
Mode: File (without compression)
Application: Thin client
Localization: Infobase: Spanish (Argentina), Session: English
Interface mode: Taxi

Errors:
--------------------------------------------------------------------------------
5/30/2019 12:23:40 AM
Invalid value of function argument
--------------------------------------------------------------------------------
5/30/2019 12:23:24 AM
{CommonModule.XMLFunc.Module(74)}: Error calling context method (Read)
While XMLReader.Read() Do
, reason:
XML parsing error:  - [1,1]
Fatal error:
Extra content at the end of the document
SystemId: file://C:/Users/agera/AppData/Local/Temp/v8_EA01_f.xml
--------------------------------------------------------------------------------

Before 8.3.14 it just showed empty XML, but you could still continue to work with 1C:enterprise.

The error is triggered by
While XMLReader.Read() Do

Dear Alexey,

Please verify that my understanding of the way you reproduce the issue is as follows:

- you changed nothing in your infobase's configuration
- you switched to 1C:Enterprise platform 8.3.14.1694
- you simply ran the infobase in Enterprise mode
?

If positive, please:

- let us know the 1C:Enterprise platform version you switched from
- try using the latest 1C:Enterprise platform 8.3.14 version: 8.3.14.1779 and inform us about the results
- if the issue persists, send us the infobase configuration (.cf)

Best regards,
Vladimir Gurov

I changed some parts of configuration, but not related to the problem at all
Yes, I have switched to 8.3.14.1694
I ran with debug enabled from designer

ok, I will test with another version later. This error is not critical for me, because I made a workaround to never receive empty XML, but still it is not very good that the platform closes when it is not necessary.

Update:
bug fixed in 8.3.14.1779

Dear Alexey,

<<bug fixed in 8.3.14.1779>>

Thank you for the notification.

Best regards,
Vladimir Gurov