Skip to main content

12.5 Registration failed - urgent

Forum Member
Posts: 9
Comments: 17

After an upgrade from 12. 12,5 we always had backup problems.

Exchange backup is hanging at 98%.

So we made a repair installation as described in the FAQ

No we get the error message:

failed to register the following components on the management server:

-Backup Agent

For details, view the installation log.

Any fast help is very appreciate

Forum Star
Posts: 22
Comments: 2643

Top

Hi,

It's hard to advise without checking the actual log file, but what you can quickly try is to re-install Agent for Windows component on the machine, e.g. uninstall it using Acronis Backup installer (instead of repair installation and without using Control Panel), and then re-install back. If this doesn't help then you can check the .msi installation log and search for "return value: 3" entry (may be localized depending on Windows locale) to see messages above this entry which will show what the problem is.

Thank you.

Forum Member
Posts: 9
Comments: 17

Top

Thanks Vasily, I will test this on the weekend and post here

Take care

Forum Member
Posts: 9
Comments: 17

Top

Dear Vasily, after re-installing the same situation happen.

How can I perform a total de-installing and a total new installing without any old components and backup plans?

 

Thanks for your help in advance

Stefan

Forum Star
Posts: 22
Comments: 2643

Top

Hi Stefan,

In order to advise I'll need to check the .msi installation log from the failed attempt (all logs are stored in C:\ProgramData\Acronis\InstallationLogs folder) + Windows system information outputs (Win+R->msinfo32->File->Save). Please upload these details to FTP link which I'll send you in a private forum message shortly.

Thank you.

Forum Member
Posts: 9
Comments: 17

Top

Dear Vasily i put now all files to your FTP including a text file with some informations.

Many thanks for your help - honestly. No backups makes me nervous.

Take care

Stefan

Forum Star
Posts: 22
Comments: 2643

Top

Hi Stefan,

Thank you for providing diagnostic data. According to the log files the problem occurs when trying to append incremental backup to existing archive on the X:\ drive. To localize the issue, can you please try creating some folder on the X:\ drive and use it as backup destination? Please let me know if backup to new folder would complete successfully or not. If not, then I'll need to check the latest activity log (you can upload it to the same FTP).

P.S. the problem is not related to installation/reinstallation, but rather to Exchange application processing (there was also 1 Exchange VSS writer failure).

Thank you.

Forum Member
Posts: 9
Comments: 17

Top

Dear Vasily, I was formatting a new RDX cartridge now. So lets see what will happen with the backups.

tc

Stefan

Forum Member
Posts: 9
Comments: 17

Top

Dear Vasily, many thanks for your help - now its working fine - except one small problem with one SQL database. We get always a warning.

If you are able to help me again, here is the log file.

Thanks in advance

Stefan

 

2017-09-20T23:02:19:483+01:00 14208 I0135003A: Der Benutzer '' (clientProfileID=; clientSessionID=AA435D29-9273-4EC7-8BFC-D6CA18A13D87) führt gerade den Befehl 'Backup' aus.
2017-09-20T23:02:19:484+01:00 14208 I00000000: Collecting metadata for 'BMD' MsSql database starts
2017-09-20T23:02:19:904+01:00 14208 I00000000: Start backup of file #1: F:\BMDDataBase\BMD_DATA.MDF
2017-09-20T23:02:21:662+01:00 14208 I00000000: Start backup of file #2: F:\BMDDataBase\BMD_LOG.LDF
2017-09-20T23:02:21:933+01:00 14208 I00000000: Start backup of file #3: F:\BMDDataBase\BMD_IND.IDX
2017-09-20T23:02:22:822+01:00 14208 I00000000: Collecting metadata for 'BMD' MsSql database ends
2017-09-20T23:02:22:823+01:00 14208 I00000000: Collecting metadata for 'BMDRESTORE' MsSql database starts
2017-09-20T23:02:22:847+01:00 14208 I00000000: Start backup of file #4: F:\BMDDataBaseRESTORE\BMD_DATA.MDF
2017-09-20T23:02:23:024+01:00 14208 I00000000: Start backup of file #5: F:\BMDDataBaseRESTORE\BMD_LOG.LDF
2017-09-20T23:02:23:069+01:00 14208 I00000000: Start backup of file #6: F:\BMDDataBaseRESTORE\BMD_IND.IDX
2017-09-20T23:02:23:081+01:00 14208 I00000000: Collecting metadata for 'BMDRESTORE' MsSql database ends
2017-09-20T23:02:23:082+01:00 14208 I00000000: Collecting metadata for 'master' MsSql database starts
2017-09-20T23:02:23:122+01:00 14208 I00000000: Start backup of file #7: F:\BMDSoftware\DBMGR\MSSQL12.BMD\MSSQL\DATA\master.mdf
2017-09-20T23:02:23:193+01:00 14208 I00000000: Start backup of file #8: F:\BMDSoftware\DBMGR\MSSQL12.BMD\MSSQL\DATA\mastlog.ldf
2017-09-20T23:02:23:216+01:00 14208 I00000000: Collecting metadata for 'master' MsSql database ends
2017-09-20T23:02:23:217+01:00 14208 I00000000: Collecting metadata for 'model' MsSql database starts
2017-09-20T23:02:23:232+01:00 14208 I00000000: Start backup of file #9: F:\BMDSoftware\DBMGR\MSSQL12.BMD\MSSQL\DATA\model.mdf
2017-09-20T23:02:23:274+01:00 14208 I00000000: Start backup of file #10: F:\BMDSoftware\DBMGR\MSSQL12.BMD\MSSQL\DATA\modellog.ldf
2017-09-20T23:02:23:303+01:00 14208 I00000000: Collecting metadata for 'model' MsSql database ends
2017-09-20T23:02:23:304+01:00 14208 I00000000: Collecting metadata for 'msdb' MsSql database starts
2017-09-20T23:02:23:318+01:00 14208 I00000000: Start backup of file #11: F:\BMDSoftware\DBMGR\MSSQL12.BMD\MSSQL\DATA\MSDBData.mdf
2017-09-20T23:02:23:535+01:00 14208 I00000000: Start backup of file #12: F:\BMDSoftware\DBMGR\MSSQL12.BMD\MSSQL\DATA\MSDBLog.ldf
2017-09-20T23:02:23:555+01:00 14208 I00000000: Collecting metadata for 'msdb' MsSql database ends
2017-09-20T23:03:21:949+01:00 14208 I00000000: Logs truncating starts for 'BMD' instance
2017-09-20T23:03:21:983+01:00 14208 I00000000: TruncateLogOf: master start
2017-09-20T23:03:21:990+01:00 14208 I00000000: TruncateLogOf: master skipped because database has Simple recovery model
2017-09-20T23:03:21:991+01:00 14208 I00000000: TruncateLogOf: model start
2017-09-20T23:03:22:081+01:00 14208 I00000000: TruncateLogOf: model done
2017-09-20T23:03:22:082+01:00 14208 I00000000: TruncateLogOf: msdb start
2017-09-20T23:03:22:090+01:00 14208 I00000000: TruncateLogOf: msdb skipped because database has Simple recovery model
2017-09-20T23:03:22:091+01:00 14208 I00000000: TruncateLogOf: BMD start
2017-09-20T23:03:22:209+01:00 14208 I00000000: TruncateLogOf: BMD done
2017-09-20T23:03:22:211+01:00 14208 I00000000: TruncateLogOf: BMDRESTORE start
2017-09-20T23:03:22:307+01:00 14208 I00000000: TruncateLogOf: BMDRESTORE done
2017-09-20T23:03:22:309+01:00 14208 I00000000: Logs truncating ends for instance 'BMD'
2017-09-20T23:03:22:311+01:00 14208 I00000000: MS-SQL instance 'BMD' successfully backed-up
2017-09-20T23:03:22:319+01:00 14208 I00000000: Collecting metadata for 'BMD' MsSql instance ends
2017-09-20T23:03:22:320+01:00 14208 I00000000: Collecting metadata for 'MICROSOFT##SSEE' MsSql instance starts
2017-09-20T23:03:22:322+01:00 14208 I00000000: Start backup MS-SQL instance: 'MICROSOFT##SSEE'
2017-09-20T23:03:22:323+01:00 14208 I00000000: Create truncate logs operation for instance 'MICROSOFT##SSEE': '1'
2017-09-20T23:03:22:324+01:00 14208 I00000000: Logs truncating transaction creation starts for 'MICROSOFT##SSEE' instance
2017-09-20T23:03:26:402+01:00 14208 W00570227: Fehler 0x570227: Restore of database 'master' (SQL Server instance: 'MICROSOFT##SSEE') to the point of failure may become unavailable.
| Ablaufverfolgungsebene: Warnung
| Channel: tol-activity#D1345FDB-85F8-490D-BB95-2441A1FC7625
| Zeile: 0x7357c1fc25258e1f
| Datei: k:\13\enterprise\applications\mssql\archiver\src\engine\db_backup_visitor.cpp:857
| Funktion: `anonymous-namespace'::TruncateLogsGuard::TruncateLogsGuard
| $module: ArsAgentProvider_vsa64_7970
|
| Fehler 0x570010: Ausführen der SQL-Anweisung 'CREATE TABLE dbo.B1600106C07E4DA19D9C7F1A89B3CDD1 ( column_1 varchar(30) )' ist fehlgeschlagen.
| Zeile: 0xb19b368b2754d2e3
| Datei: k:\13\enterprise\applications\mssql\archiver\sqldmo_provider\impl\db_service_odbc_impl.cpp:1147
| Funktion: OdbcDbServiceImpl::QueryResultImpl::Create
| $module: ArsAgentProvider_vsa64_7970
|
| Fehler 0x570800: 42000 (33003): [Microsoft][ODBC SQL Server Driver][SQL Server]DDL statement is not allowed.
| Zeile: 0xb19b368b2754d2e4
| Datei: k:\13\enterprise\applications\mssql\archiver\sqldmo_provider\impl\db_service_odbc_impl.cpp:1148
| Funktion: OdbcDbServiceImpl::QueryResultImpl::Create
| $module: ArsAgentProvider_vsa64_7970
2017-09-20T23:03:30:411+01:00 14208 W00570227: Fehler 0x570227: Restore of database 'model' (SQL Server instance: 'MICROSOFT##SSEE') to the point of failure may become unavailable.
| Ablaufverfolgungsebene: Warnung
| Channel: tol-activity#D1345FDB-85F8-490D-BB95-2441A1FC7625
| Zeile: 0x7357c1fc25258e1f
| Datei: k:\13\enterprise\applications\mssql\archiver\src\engine\db_backup_visitor.cpp:857
| Funktion: `anonymous-namespace'::TruncateLogsGuard::TruncateLogsGuard
| $module: ArsAgentProvider_vsa64_7970
|
| Fehler 0x570010: Ausführen der SQL-Anweisung 'CREATE TABLE dbo.B1600106C07E4DA19D9C7F1A89B3CDD1 ( column_1 varchar(30) )' ist fehlgeschlagen.
| Zeile: 0xb19b368b2754d2e3
| Datei: k:\13\enterprise\applications\mssql\archiver\sqldmo_provider\impl\db_service_odbc_impl.cpp:1147
| Funktion: OdbcDbServiceImpl::QueryResultImpl::Create
| $module: ArsAgentProvider_vsa64_7970
|
| Fehler 0x570800: 42000 (33003): [Microsoft][ODBC SQL Server Driver][SQL Server]DDL statement is not allowed.
| Zeile: 0xb19b368b2754d2e4
| Datei: k:\13\enterprise\applications\mssql\archiver\sqldmo_provider\impl\db_service_odbc_impl.cpp:1148
| Funktion: OdbcDbServiceImpl::QueryResultImpl::Create
| $module: ArsAgentProvider_vsa64_7970
2017-09-20T23:03:34:441+01:00 14208 W00570227: Fehler 0x570227: Restore of database 'msdb' (SQL Server instance: 'MICROSOFT##SSEE') to the point of failure may become unavailable.
| Ablaufverfolgungsebene: Warnung
| Channel: tol-activity#D1345FDB-85F8-490D-BB95-2441A1FC7625
| Zeile: 0x7357c1fc25258e1f
| Datei: k:\13\enterprise\applications\mssql\archiver\src\engine\db_backup_visitor.cpp:857
| Funktion: `anonymous-namespace'::TruncateLogsGuard::TruncateLogsGuard
| $module: ArsAgentProvider_vsa64_7970
|
| Fehler 0x570010: Ausführen der SQL-Anweisung 'CREATE TABLE dbo.B1600106C07E4DA19D9C7F1A89B3CDD1 ( column_1 varchar(30) )' ist fehlgeschlagen.
| Zeile: 0xb19b368b2754d2e3
| Datei: k:\13\enterprise\applications\mssql\archiver\sqldmo_provider\impl\db_service_odbc_impl.cpp:1147
| Funktion: OdbcDbServiceImpl::QueryResultImpl::Create
| $module: ArsAgentProvider_vsa64_7970
|
| Fehler 0x570800: 42000 (33003): [Microsoft][ODBC SQL Server Driver][SQL Server]DDL statement is not allowed.
| Zeile: 0xb19b368b2754d2e4
| Datei: k:\13\enterprise\applications\mssql\archiver\sqldmo_provider\impl\db_service_odbc_impl.cpp:1148
| Funktion: OdbcDbServiceImpl::QueryResultImpl::Create
| $module: ArsAgentProvider_vsa64_7970
2017-09-20T23:03:34:442+01:00 14208 I00000000: Logs truncating transaction creation ends for 'MICROSOFT##SSEE' instance
2017-09-20T23:04:59:841+01:00 14208 I00000000: Write MS-SQL instance 'MICROSOFT##SSEE' to archive
2017-09-20T23:13:35:163+01:00 14208 I0135003B: Befehl 'Backup' wurde erfolgreich abgeschlossen.
 

Forum Star
Posts: 22
Comments: 2643

Top

Hi,

First of all sorry for the late reply. As I've discovered the warning shown in the log can be safely ignored and the root cause of the problem is that we didn't hide this warning properly (we've submitted a new bug for this issue to be fixed in future updates). What is the the exact purposes of these queries which give failures I can't say right now - it will require further investigation.

Thank you.