Critical error (executing database script)

katbert · February 26, 2015

I'm trying to install ERA Server 6.1.28.0 on Windows 2008 R2 SP1 (Russian) domain controller

I install SQL 2008 R2 Express SP2 manually without errors, and can connect to SQL using Management Studio

I opened 1433 port

https://forum.eset.com/topic/3805-remote-administrator-install-odbc-error/

Setup can connect to database using "SQL Server" ODBC driver and sa SQL account

But setup stop with critical error in the step "executing database scripts - installing new database"

If connect to SQL using Management Studio before setup rollback - I see database era_db

Setup rollback delete database

In the install log I see this error:

INFO: Custom action 'DbCreate' successfully initialized.
INFO: Successful GET property 'P_PRODUCT_NAME' with value - Server
INFO: Successful GET property 'P_PRODUCT_GUID' with value - 8863923d-9052-44de-8941-dc611f0a7a4a
INFO: Successful GET property 'P_DB_SCRIPTS_DIR' with value - C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\
INFO: Successful GET property 'P_DB_CONNECTORS_DIR' with value - C:\Users\836D~1\AppData\Local\Temp\EsetRemoteAdminServer\
INFO: Successful GET property 'P_DB_TYPE' with value - MS SQL Server
INFO: Successful GET property 'P_DB_DRIVER' with value - SQL Server
INFO: Successful GET property 'P_DB_HOSTNAME' with value - localhost
INFO: Successful GET property 'P_DB_PORT' with value - 1433
INFO: Successful GET property 'P_DB_NAME' with value - era_db
INFO: Successful GET property 'P_DB_ADMIN_USERNAME' with value - sa
INFO: Successful GET property 'P_DB_ADMIN_PASSWORD' with value - **********
INFO: Successful GET property 'P_DB_USER_USERNAME' with value - era_user
INFO: Successful GET property 'P_DB_USER_PASSWORD' with value - **********
INFO: (GetDatabaseServerConnectionStringWithoutEscape) Created connection string: 'Driver=SQL Server;Server=localhost,1433;Uid=sa;Pwd={******};CharSet=utf8;'
INFO: Entering function: void __cdecl Era::Setup::Common::CustomActions::CDatabaseWrapper::DropAndCreateDatabaseForDBServer(const class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > &,const class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > &,const class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > &,const class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >)
INFO: (DropAndCreateDatabaseForDBServer) Skipping file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\version.ini
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\1_create_schema_without_views.sql
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\2_create_log_tables.sql
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\3_create_views.sql
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\4_init_data.sql
ERROR: (DbCreate) Statement execution failed. Error: @5>1@07>20=85 B8?0 40==KE varchar 2 B8? 40==KE datetime ?@825;> : 2KE>4C 7=0G5=8O 70 ?@545;K 480?07>=0.. File: C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\4_init_data.sql. Statement: INSERT INTO tbl_security_users (user_id, user_uuid, user_login, user_comment, password_change_timestamp, change_password_on_next_logon, password_expiration_interval_in_days, auto_logout_time_in_minutes, user_full_name, user_email, user_phone, user_state, disabled, native, removed, user_password_hash, user_password_salt) VALUES
	(5, dbo.ufn_uuid_str_to_binary('00000000-0000-0000-7002-000000000001'), 'system', '', '2012-01-26 12:00:00', 0, 1500, 10, 'System user', '', '', 0x, 0, 1, 0, 0x20, 0x20),
	(6, dbo.ufn_uuid_str_to_binary('00000000-0000-0000-7002-000000000002'), 'Administrator', '', '2011-10-12 12:00:00', 0, 1500, 10, 'Administrator', '', '', 0x, 0, 1, 0, 0x0FCF62F35B4D4A5C1D733280F9D476E73FCBD029, 0x75A308F8F28B096A5ADFE94A07DBE5C4555E1CD3D7E43D2D23F850B5ECDEDFB56D13A85BCEE4F13D2C5E9ACB8E685D5FB6ADA597A7A22FA3E874ED65D5A6A55B);


INFO: Successful GET property 'P_SILENT' with value - 
Error 30000. A critical error occurred. Please see the installation log for more information. Enabling the log is described at the ESET knowledge base website:
kb.eset.com

Issue ID: SOLN406
    
MSI (s) (68!F8) [18:35:49:692]: Product: ESET Remote Administrator Server -- Error 30000. A critical error occurred. Please see the installation log for more information. Enabling the log is described at the ESET knowledge base website:
kb.eset.com

Issue ID: SOLN406

Edited February 26, 2015 by katbert

katbert · February 27, 2015

In test environment I installed ERA Server on member server 2008 R2 SP1

Setup install and configure bundled SQL express - and comleted successfully

How about KB article about configuring manually installed SQL instance?

vfiuchcikicshuusrch · February 27, 2015

hi.

I have the same error.

Katbert, you need to change file

C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\4_init_data.sql

this

2012-01-26 12:00:00

to

20120126 12:00:00

and second line too.

and try reinstall again.

when software installing, you need fast replace file 4_init_data.sql with correct datetime format.

and after this error was fixed, but installation also failed.

I can see this error in my log:

INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\6_cleanup_operations.sql
MSI (s) (40!5C) [11:46:50:193]: Closing MSIHANDLE (392) of type 790531 for thread 5724
MSI (s) (40!5C) [11:46:50:193]: Creating MSIHANDLE (393) of type 790531 for thread 5724
ERROR: (DbCreate) @5>1@07>20=85 B8?0 40==KE varchar 2 B8? 40==KE datetime ?@825;> : 2KE>4C 7=0G5=8O 70 ?@545;K 480?07>=0.
MSI (s) (40!5C) [11:46:50:209]: Closing MSIHANDLE (393) of type 790531 for thread 5724
MSI (s) (40!5C) [11:46:50:209]: Creating MSIHANDLE (394) of type 790531 for thread 5724
INFO: Successful GET property 'P_SILENT' with value - 
MSI (s) (40!5C) [11:46:50:209]: Closing MSIHANDLE (394) of type 790531 for thread 5724
MSI (s) (40!5C) [11:46:50:209]: Creating MSIHANDLE (395) of type 790531 for thread 5724
Error 30000. A critical error occurred. Please see the installation log for more information. Enabling the log is described at the ESET knowledge base website:
kb.eset.com


Issue ID: SOLN406

what is it ?

please help us.

p.s. sorry for my english.

katbert · March 2, 2015

Successfully installed ERA Server on test domain controller (Windows Server 2008 R2 SP1 Russian)

Difference from the first post:

1. Manually installed version of SQL 2008 R2 Express SP2 is English, not Russian (SQLEXPRWT_x64_ENU.exe, ver 10.50.4000)

2. Install SQL as default instance, not SQLEXPRESS

ERA installer stop with critical error (executing database script) - when using Russian SQL Express and/or using named SQL instance SQLEXPRESS

Edited March 2, 2015 by katbert

katbert · March 2, 2015

Next try - to install ERA 6.1.28.0 on domain controller Windows Server 2008 R2 SP1 Russian,

with manually installed SQL 2008 R2 Express SP2 Russina, configured as default instance.

Critical error (executing database script) againt

ERA Server installer is not compatible with Russian SQL Express (installed with default settings)

katbert · March 2, 2015

vfiuchcikicshuusrch, which is your SQL version and lang?

vfiuchcikicshuusrch · March 2, 2015

MS SQL 2010 Russian.

Peter Randziak · March 4, 2015

Hello,

I have reported this as a support ticket for our Dev team, we will check it.

It seems like an issue on our side.

Thank you for reporting this, I will keep you posted.

P.R.

Peter Randziak · March 10, 2015

Hello,

we have a response from the Dev team, it is an confirmed issue on our side.

This issue will be addressed in future releases of the product.

Workaround for this issue is to change default language for the user which you use to connect to the database from your default to English via Management studio.

Please let us know how it went in case you decide to try this workaround.

Thank you.

P.R.

technika · March 12, 2015

I'm having a similar problem. Using Windows Server 2012 R2 with MySQL Server 5.6 all english.

...
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\MySQL\CreateScripts\3_create_views.sql
MSI (s) (F4!8C) [19:35:36:925]: Closing MSIHANDLE (676) of type 790531 for thread 2188
MSI (s) (F4!8C) [19:35:36:925]: Creating MSIHANDLE (677) of type 790531 for thread 2188
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\MySQL\CreateScripts\4_init_data.sql
MSI (s) (F4!8C) [19:35:36:925]: Closing MSIHANDLE (677) of type 790531 for thread 2188
MSI (s) (F4!8C) [19:35:38:926]: Creating MSIHANDLE (678) of type 790531 for thread 2188
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\MySQL\CreateScripts\5_reports_interface.sql
MSI (s) (F4!8C) [19:35:38:927]: Closing MSIHANDLE (678) of type 790531 for thread 2188
MSI (s) (F4!8C) [19:35:40:119]: Creating MSIHANDLE (679) of type 790531 for thread 2188
ERROR: (DbCreate) Statement execution failed. Error: This function has none of DETERMINISTIC, NO SQL, or READS SQL DATA in its declaration and binary logging is enabled (you *might* want to use the less safe log_bin_trust_function_creators variable). File: C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\MySQL\CreateScripts\5_reports_interface.sql. Statement: 
CREATE FUNCTION `ufn_create_hour_interval`(`timeParam` DATETIME)
    RETURNS TIMESTAMP
    LANGUAGE SQL
    NOT DETERMINISTIC
    CONTAINS SQL
    SQL SECURITY INVOKER
BEGIN
    return FROM_UNIXTIME(UNIX_TIMESTAMP(timeParam)- UNIX_TIMESTAMP(timeParam)%%(60*60));
END;
MSI (s) (F4!8C) [19:35:40:119]: Closing MSIHANDLE (679) of type 790531 for thread 2188
MSI (s) (F4!8C) [19:35:40:122]: Creating MSIHANDLE (680) of type 790531 for thread 2188
INFO: Successful GET property 'P_SILENT' with value - 
MSI (s) (F4!8C) [19:35:40:123]: Closing MSIHANDLE (680) of type 790531 for thread 2188
MSI (s) (F4!8C) [19:35:40:123]: Creating MSIHANDLE (681) of type 790531 for thread 2188
Error 30000. A critical error occurred. Please see the installation log for more information. Enabling the log is described at the ESET knowledge base website:
kb.eset.com

Issue ID: SOLN406
    
MSI (s) (F4!8C) [19:35:43:521]: Product: ESET Remote Administrator Server -- Error 30000. A critical error occurred. Please see the installation log for more information. Enabling the log is described at the ESET knowledge base website:
kb.eset.com

Issue ID: SOLN406
...

Is there a workaround for this too?

katbert · March 13, 2015

Workaround for this issue is to change default language for the user which you use to connect to the database from your default to English via Management studio.

Please let us know how it went in case you decide to try this workaround.

I'm trying to install ERA using sa SQL account, and allow to create eradb account at the next step

For which user change default language?

Peter Randziak · March 13, 2015

For the user you specify for the ERA to connect to the database.

P.R.

roald · April 9, 2015

Hi,

I'm am also having an issue at the same place, here is the log where it failed:

INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\1_create_schema_without_views.sql
ERROR: (DbCreate) Statement execution failed. Error: Incorrect syntax near '100'.. File: C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\1_create_schema_without_views.sql. Statement: ALTER DATABASE SET COMPATIBILITY_LEVEL = 100
INFO: Successful GET property 'P_SILENT' with value -
Error 30000. A critical error occurred. Please see the installation log for more information. Enabling the log is described at the ESET knowledge base website: kb.eset.com

I am choosing to use SQL on another server and the SQL account being used is using English as a default language.

joaotiago81 · May 5, 2015

Hi,

I'm am also having an issue at the same place, here is the log where it failed:

INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\1_create_schema_without_views.sql

ERROR: (DbCreate) Statement execution failed. Error: Incorrect syntax near '100'.. File: C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\1_create_schema_without_views.sql. Statement: ALTER DATABASE SET COMPATIBILITY_LEVEL = 100

INFO: Successful GET property 'P_SILENT' with value -

Error 30000. A critical error occurred. Please see the installation log for more information. Enabling the log is described at the ESET knowledge base website: kb.eset.com

I am choosing to use SQL on another server and the SQL account being used is using English as a default language.

I had the same problem and found out it was due to SQL Server Express 2005 edition. After installing 2008 edition the instalation completed.

JT

antoineL · May 20, 2015

Same problem here, with Server-6.1.365.0_x64. SQL server is 2008R2 Express running on Spanish locale, using Windows authentication, I changed the default locale from Spanish to English of the login used without any visible effect.

I spent some time on the SQL error, was able to repro the problem and found it is in fact a conversion error, as vfiuchcikicshuusrch described in https://forum.eset.com/topic/4213-critical-error-executing-database-script/?p=24318. So I designed a patch (below and 4_init_data.sql.patch.txt) which allowed me to perform the initialization of the data.

--- 4_init_data.orig	Wed May 20 19:32:18 2015
+++ 4_init_data.sql	Wed May 20 19:30:32 2015
@@ -73,8 +73,8 @@
 GO
 
 INSERT INTO tbl_security_users (user_id, user_uuid, user_login, user_comment, password_change_timestamp, change_password_on_next_logon, password_expiration_interval_in_days, auto_logout_time_in_minutes, user_full_name, user_email, user_phone, user_state, disabled, native, removed, user_password_hash, user_password_salt) VALUES
-	(5, dbo.ufn_uuid_str_to_binary('00000000-0000-0000-7002-000000000001'), 'system', '', '2012-01-26 12:00:00', 0, 1500, 10, 'System user', '', '', 0x, 0, 1, 0, 0x20, 0x20),
-	(6, dbo.ufn_uuid_str_to_binary('00000000-0000-0000-7002-000000000002'), 'Administrator', '', '2011-10-12 12:00:00', 0, 1500, 10, 'Administrator', '', '', 0x, 0, 1, 0, 0x0FCF62F35B4D4A5C1D733280F9D476E73FCBD029, 0x75A308F8F28B096A5ADFE94A07DBE5C4555E1CD3D7E43D2D23F850B5ECDEDFB56D13A85BCEE4F13D2C5E9ACB8E685D5FB6ADA597A7A22FA3E874ED65D5A6A55B);
+	(5, dbo.ufn_uuid_str_to_binary('00000000-0000-0000-7002-000000000001'), 'system', '', '2012-01-26T12:00:00', 0, 1500, 10, 'System user', '', '', 0x, 0, 1, 0, 0x20, 0x20),
+	(6, dbo.ufn_uuid_str_to_binary('00000000-0000-0000-7002-000000000002'), 'Administrator', '', '2011-10-12T12:00:00', 0, 1500, 10, 'Administrator', '', '', 0x, 0, 1, 0, 0x0FCF62F35B4D4A5C1D733280F9D476E73FCBD029, 0x75A308F8F28B096A5ADFE94A07DBE5C4555E1CD3D7E43D2D23F850B5ECDEDFB56D13A85BCEE4F13D2C5E9ACB8E685D5FB6ADA597A7A22FA3E874ED65D5A6A55B);
 
 
 GO

(basically, changed the format of the datetime constants to include the ISO8166-mandated 'T'.) Then I inserted at installation time. That trick worked.

However, the installation stopped a little later, as the log now shows:

MSI (s) (EC!60) [19:34:57:546]: Creating MSIHANDLE (646) of type 790531 for thread 4960
INFO: (GetDatabaseServerConnectionStringWithoutEscape) Created connection string: 'Driver=SQL Server;Server=MYSQLSERVER,12345;Trusted_Connection=yes;CharSet=utf8;'
MSI (s) (EC!60) [19:34:57:546]: Closing MSIHANDLE (646) of type 790531 for thread 4960
MSI (s) (EC!60) [19:34:57:546]: Creating MSIHANDLE (647) of type 790531 for thread 4960
INFO: Entering function: void __cdecl Era::Setup::Common::CustomActions::CDatabaseWrapper::DropAndCreateDatabaseForDBServer(const class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > &,const class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > &,const class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> > &,const class std::basic_string<char,struct std::char_traits<char>,class std::allocator<char> >)
MSI (s) (EC!60) [19:34:57:546]: Closing MSIHANDLE (647) of type 790531 for thread 4960
MSI (s) (EC!60) [19:34:57:733]: Creating MSIHANDLE (648) of type 790531 for thread 4960
INFO: (DropAndCreateDatabaseForDBServer) Skipping file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\version.ini
MSI (s) (EC!60) [19:34:57:733]: Closing MSIHANDLE (648) of type 790531 for thread 4960
MSI (s) (EC!60) [19:34:57:733]: Creating MSIHANDLE (649) of type 790531 for thread 4960
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\1_create_schema_without_views.sql
MSI (s) (EC!60) [19:34:57:733]: Closing MSIHANDLE (649) of type 790531 for thread 4960
MSI (s) (EC!60) [19:35:09:832]: Creating MSIHANDLE (650) of type 790531 for thread 4960
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\2_create_log_tables.sql
MSI (s) (EC!60) [19:35:09:832]: Closing MSIHANDLE (650) of type 790531 for thread 4960
MSI (s) (EC!60) [19:35:30:632]: Creating MSIHANDLE (651) of type 790531 for thread 4960
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\3_create_views.sql
MSI (s) (EC!60) [19:35:30:632]: Closing MSIHANDLE (651) of type 790531 for thread 4960
MSI (s) (EC!60) [19:35:30:632]: Creating MSIHANDLE (652) of type 790531 for thread 4960
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\4_init_data.sql
MSI (s) (EC!60) [19:35:30:632]: Closing MSIHANDLE (652) of type 790531 for thread 4960
MSI (s) (EC!60) [19:35:31:084]: Creating MSIHANDLE (653) of type 790531 for thread 4960
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\5_reports_interface.sql
MSI (s) (EC!60) [19:35:31:084]: Closing MSIHANDLE (653) of type 790531 for thread 4960
MSI (s) (EC!60) [19:35:31:536]: Creating MSIHANDLE (654) of type 790531 for thread 4960
INFO: (DropAndCreateDatabaseForDBServer) Processing file C:\ProgramData\ESET\RemoteAdministrator\Server\SetupData\Database\SQLServer\CreateScripts\6_cleanup_operations.sql
MSI (s) (EC!60) [19:35:31:536]: Closing MSIHANDLE (654) of type 790531 for thread 4960
MSI (s) (EC!60) [19:35:31:552]: Creating MSIHANDLE (655) of type 790531 for thread 4960
ERROR: (DbCreate) La conversión del tipo de datos varchar en datetime produjo un valor fuera de intervalo.
MSI (s) (EC!60) [19:35:31:568]: Closing MSIHANDLE (655) of type 790531 for thread 4960
MSI (s) (EC!60) [19:35:31:568]: Creating MSIHANDLE (656) of type 790531 for thread 4960
INFO: Successful GET property 'P_SILENT' with value - 
MSI (s) (EC!60) [19:35:31:568]: Closing MSIHANDLE (656) of type 790531 for thread 4960
MSI (s) (EC!60) [19:35:31:568]: Creating MSIHANDLE (657) of type 790531 for thread 4960

"La conversión del tipo de datos varchar en datetime produjo un valor fuera de intervalo." means in English "Conversion of data type varchar into datetime produced an out-of-range value." I do not know if this is the same error message as reported in vfiuchcikicshuusrch's message (in Russian), but I highly suspect it is... Unfortunately, there is no helpful INFO hint just above to explain where the failed conversion took place.

I had a look at the tbl_security_groups_to_users table, and found that the "user_password_xxx" values for user 6 ("Administrator") were changed to strings of ? (0x3F3F3F3F3F3F3F3F3F3F for _hash, 0x3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F3F for _salt), while the datetime values were apparently correct.

[ Edit: credit vfiuchcikicshuusrch's research on the subject, which I apparently repeated. ]

Edited May 20, 2015 by antoineL

michalp · May 21, 2015

Please try again with released hotfix release.

antoineL · May 21, 2015

Please try again with released hotfix release.

Yeah, it works much better now! (I used Server_x64 v.6.1.440.0) Thank you very much Michal.

@katbert: Perhaps this topic could be marked as solved then?

Sign In

Critical error (executing database script)

Recommended Posts

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Link to comment

Share on other sites

Recently Browsing 0 members

Quick search

FAQ

Topics