Rollback during the installation, logs available

[avadas.de]

Hi,

another user with a rollback, logs are attached. He tried to install on "Server 2008 R2 Foundation" and as an alternative on "Win7SP1 32-bit". In both cases he gets a rollback.

Logs: Click here

[wpn]

can you reattach the file?
i cant open it since you have played with the extensions and renaming doesnt work

[avadas.de]

Check the link

[wpn]

manager2716 log

Code: [Select]

08-03 12:37:14,264 [9] INFO  MirrorWrapper - Building Setup.
08-03 12:37:14,264 [9] INFO  MirrorWrapper - Calling setifaceMirrorBuildSetup(abp,  /edition 9, , C:\ProgramData\AVAST Software\Administration Console\Mirror\Packages, True, 0).
08-03 12:37:35,838 [9] ERROR LogExceptionHandler - Unhandled exception!
System.ServiceModel.CommunicationObjectAbortedException: Das Kommunikationsobjekt "System.ServiceModel.Channels.ServerSessionPreambleConnectionReader+ServerFramingDuplexSessionChannel" kann nicht für die Kommunikation verwendet werden, da es abgebrochen wurde.
   bei System.ServiceModel.Channels.CommunicationObject.ThrowIfDisposedOrNotOpen()
   bei System.ServiceModel.Channels.OutputChannel.Send(Message message, TimeSpan timeout)
   bei System.ServiceModel.Dispatcher.DuplexChannelBinder.DuplexRequestContext.OnReply(Message message, TimeSpan timeout)
   bei System.ServiceModel.Channels.RequestContextBase.Reply(Message message, TimeSpan timeout)
   bei System.ServiceModel.Dispatcher.ImmutableDispatchRuntime.Reply(MessageRpc& rpc)
08-03 12:37:35,838 [9] INFO  MirrorService - Retrieving mirror status.
08-03 12:37:35,901 [9] INFO  MirrorService - Retrieving mirror error data.
08-03 12:45:55,105 [11] INFO  ManagerServiceWrapper - Monitoring service stopped.

To me it looks like one of the module is not propperly installed for which the installation fails because it apperently depends on it.
But this goes in too deep for my knowledge of the product and only Avast crew can answer i believe



installer 5364 log

Code: [Select]

08-03 12:08:48,286 [SchedulerWorker0] WARN  ConfigurationDatabase - Problem reading out the process/elapsed time reader for the service. This is OK during install.
System.InvalidOperationException: Instance 'Avast.Sbc.Service' does not exist in the specified Category.
   at System.Diagnostics.CounterDefinitionSample.GetInstanceValue(String instanceName)
   at System.Diagnostics.PerformanceCounter.NextSample()
   at System.Diagnostics.PerformanceCounter.NextValue()
   at Avast.Sbc.Service.Database.ConfigurationDatabase.LoadStatistics()
08-03 12:18:49,888 [SchedulerWorker0] INFO  UpdateJobBase - Building setup file.
08-03 12:37:35,932 [SchedulerWorker0] ERROR Scheduler - Error during server side job execution.
Avast.Sbc.UpdateEngine.Iface.UpdateEngineException: Unable to communicate to mirror service!
Call result: 0
Return code: 0 (Unknown value!)

   bei Avast.Sbc.UpdateEngine.Iface.RemoteMirrorWrapper.TransformException(Exception e)
   bei Avast.Sbc.UpdateEngine.Iface.RemoteMirrorWrapper.BuildSetup(String product, String edition, String additionalSwitches, String destPath, Boolean detached)
   bei Avast.Sbc.UpdateEngine.Iface.UpdateEngine.BuildSetup()
   bei Avast.Sbc.UpdateEngine.Iface.UpdateJobBase.BuildSetup(Int32 lowerBound, Int32 upperBound)
   bei Avast.Sbc.UpdateEngine.Iface.DefinitionsUpdateJob.Execute(Job job, IPluginContext context)
   bei Avast.Sbc.Scheduler.Core.Scheduler.RunServerSideJob(Job job, ScheduleItem triggerItem)
Call result: 0
Return code: 0 (Unknown value!)

08-03 12:37:35,932 [SchedulerWorker0] INFO  SbcServiceInstaller - Job @L0675 finished execution.
08-03 12:37:35,932 [SchedulerWorker0] ERROR Scheduler - Error encountered while processing tasks.
Avast.Sbc.Scheduler.Iface.TaskException: Task execution error ---> Avast.Sbc.UpdateEngine.Iface.UpdateEngineException: Unable to communicate to mirror service!
Call result: 0
Return code: 0 (Unknown value!)

   bei Avast.Sbc.UpdateEngine.Iface.RemoteMirrorWrapper.TransformException(Exception e)
   bei Avast.Sbc.UpdateEngine.Iface.RemoteMirrorWrapper.BuildSetup(String product, String edition, String additionalSwitches, String destPath, Boolean detached)
   bei Avast.Sbc.UpdateEngine.Iface.UpdateEngine.BuildSetup()
   bei Avast.Sbc.UpdateEngine.Iface.UpdateJobBase.BuildSetup(Int32 lowerBound, Int32 upperBound)
   bei Avast.Sbc.UpdateEngine.Iface.DefinitionsUpdateJob.Execute(Job job, IPluginContext context)
   bei Avast.Sbc.Scheduler.Core.Scheduler.RunServerSideJob(Job job, ScheduleItem triggerItem)
   --- Ende der internen Ausnahmestapelüberwachung ---
   bei Avast.Sbc.Scheduler.Core.Scheduler.RunServerSideJob(Job job, ScheduleItem triggerItem)
   bei Avast.Sbc.Scheduler.Core.Scheduler.SchedulerWorkerThread()
08-03 12:37:35,979 [1] INFO  Scheduler - Stopping the scheduler thread...
08-03 12:37:35,979 [SchedulerWorker4] INFO  Scheduler - Worker received shutdown signal.
08-03 12:37:35,979 [SchedulerWorker2] INFO  Scheduler - Worker received shutdown signal.
08-03 12:37:35,979 [SchedulerWorker0] INFO  Scheduler - Worker received shutdown signal.
08-03 12:37:35,979 [SchedulerWorker3] INFO  Scheduler - Worker received shutdown signal.
08-03 12:37:35,979 [SchedulerWorker1] INFO  Scheduler - Worker received shutdown signal.
08-03 12:37:35,979 [SchedulerCacheMediator] INFO  CacheMediator - Scheduler cache received shutdown signal. Flushing...
08-03 12:37:35,979 [1] INFO  SbcServiceInstaller - Startup jobs finished run.
08-03 12:37:36,088 [1] WARN  SbcServiceInstaller - Could not verify email sending, incorrect data specified.


[avadas.de]

Hi,

sorry...the customer gave the client deployment logs to me. Here is the SBC log. It seems he has a problem with an SQL server:

Code: [Select]

08-03 14:09:13,884 [1] ERROR SbcServiceInstaller - Problem while installing the service.
System.Data.SqlClient.SqlException (0x80131904): A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: SQL Network Interfaces, error: 26 - Error Locating Server/Instance Specified)
   at System.Data.SqlClient.SqlInternalConnection.OnError(SqlException exception, Boolean breakConnection)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning()
   at System.Data.SqlClient.TdsParser.Connect(ServerInfo serverInfo, SqlInternalConnectionTds connHandler, Boolean ignoreSniOpenTimeout, Int64 timerExpire, Boolean encrypt, Boolean trustServerCert, Boolean integratedSecurity)
   at System.Data.SqlClient.SqlInternalConnectionTds.AttemptOneLogin(ServerInfo serverInfo, String newPassword, Boolean ignoreSniOpenTimeout, TimeoutTimer timeout, SqlConnection owningObject)
   at System.Data.SqlClient.SqlInternalConnectionTds.LoginNoFailover(ServerInfo serverInfo, String newPassword, Boolean redirectedUserInstance, SqlConnection owningObject, SqlConnectionString connectionOptions, TimeoutTimer timeout)
   at System.Data.SqlClient.SqlInternalConnectionTds.OpenLoginEnlist(SqlConnection owningObject, TimeoutTimer timeout, SqlConnectionString connectionOptions, String newPassword, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlInternalConnectionTds..ctor(DbConnectionPoolIdentity identity, SqlConnectionString connectionOptions, Object providerInfo, String newPassword, SqlConnection owningObject, Boolean redirectedUserInstance)
   at System.Data.SqlClient.SqlConnectionFactory.CreateConnection(DbConnectionOptions options, Object poolGroupProviderInfo, DbConnectionPool pool, DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionFactory.CreatePooledConnection(DbConnection owningConnection, DbConnectionPool pool, DbConnectionOptions options)
   at System.Data.ProviderBase.DbConnectionPool.CreateObject(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.UserCreateRequest(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionPool.GetConnection(DbConnection owningObject)
   at System.Data.ProviderBase.DbConnectionFactory.GetConnection(DbConnection owningConnection)
   at System.Data.ProviderBase.DbConnectionClosed.OpenConnection(DbConnection outerConnection, DbConnectionFactory connectionFactory)
   at System.Data.SqlClient.SqlConnection.Open()
   at Avast.Sbc.Service.Installer.DatabaseInstaller.CreateDatabase()
   at Avast.Sbc.Service.Installer.DatabaseInstaller.ClaimDatabase()
   at Avast.Sbc.Service.Installer.DatabaseInstaller.Install()
   at Avast.Sbc.Service.SbcServiceInstaller.Install(IDictionary stateSaver)

[avadas.de]

Hi,

the strange thing about this is that we now got two customers with the same issue.

Unfortunately it differs from the case described here very often...login failure for the SQL server. In this case (as you can see from the log excerpts) it is not a logon failure, but a failure that the installer can't find the instance. Strange thing is...in both cases the customers describe that the installer created the database and tables and also a new installation attempt finds this database, removes it and creates it again (that you can also see from the log files, when trying an installation again).

Both customers report that the rollback immediately occurs after they get a warning that the SMTP settings are not correct, but both are also 100% sure that they match. But from the SMTP failure you can see nothing in the log files.

Therefore I am not sure what is causing the real issue here...a SQL problem or a SMTP problem?

[wpn]

aah i have had the roll back today too while installing on a remote server
but i intentionally left out the e-mail details.
I got an error telling me the test mail couldnt be send and the rollback happend deleting all but the logfiles

i didnt have the email set because in my test environment i didnt restore the mailserver, which i have now tho because of this error.

over the weekend or monday i will test again

[avadas.de]

Hi,

I think that the installer should be more detailed in debugging or less strict about the SMTP details. You can't expect a working SMTP (at least for 'external' applications) in every environment anyway.

[lukas.hasik]

Hi,

I think that the installer should be more detailed in debugging

Agree, "ended prematuraly" message isn't enough

or less strict about the SMTP details. You can't expect a working SMTP (at least for 'external' applications) in every environment anyway.

SMTP page of installer can be "skipped" and the install shouldn't fail even with "wrong" SMPT settings (like unreachable SMTP server, etc.). Would it be possible to get "exact" SMTP settings used by your customer? Exact=>I don't need login/passwd but wjat properties were used - e.g. server, user, passwd, authentication=No, SSL=No ...)

[wpn]

this roll back seems only to happen when using an external database server.
Since i have installed the SBC product in my test environment several times skipping the SMTP settings while using the sql express setup that avast installer installs.

the whole database/email connection during installing should be redesigned in my opinion

the database section should contact a search button (like now) but detecting the servers + instances, a test connection button and a possibility to set a different username then the SSPI login that SBC is getting installed with since that is probably not the database user for the databse it gets installed on.

the email section should at least contain a check button for the settings and a report section telling which emailserver software is used for example Exchange 2010 or 2003 or .... 

[avadas.de]

Hi Lukas,

SMTP page of installer can be "skipped" and the install shouldn't fail even with "wrong" SMPT settings (like unreachable SMTP server, etc.). Would it be possible to get "exact" SMTP settings used by your customer? Exact=>I don't need login/passwd but wjat properties were used - e.g. server, user, passwd, authentication=No, SSL=No ...)

I asked the customer again, but another one replied in the meanwhile that he left the SMTP settings completely alone ("skipped") and he receives the error message anyway, that it is not possible to send the testmail, because the SMTP settings are incorrect. Shortly after that, the installation is rolled back. Maybe the SMTP setting thing is not the problem and just needs another rework of the message itself (seems confusing to the users), but some problem with contacting the SQL instance. Strange thing is that the instance has been found by the avast! installer before, therefore I am out of ideas what the real cause could be. It seems to happen with local AND remote SQL Server instances.

[wpn]

good to know that at your client it also happend when using a local express installation.

at the moment of writing i am installing the SBC again using an dedicated db server and my exchange server. The mirror is downloading as we speak (although really slow according to the indication).
Cancelled the mirror download, was stuck at a file which i could download on the server by manually entering the url in the browser.
Started again...and waiting

edit:
Got the message that the SMTP settings are invalid, while im 100% sure it is correct and immediately the rollback starts.
in the logs i can see everything was configured already (like the nodes detection in AD) no strange errors about e-mail server or so....


edit:
instead of using my own mailserver i set my gmail account to the SMTP settings.
I received a nice e-mail, which arrived at the same time the rollback started.
One line particularly in the e-mail p*sses me of right now
"Let avast! take the stress out of managing your network!"
So far its been only creating stress

At this point im restoring again my server where avast has to get installed on....
when im out of a meeting ill continue the test with gmail (since that seems to work better) and a dedicated db server and if that fails a local database, keep you posted

[avadas.de]

Hello,

I also could re-produce the rollback issue on a test system. At the moment I would say that you have to be lucky to get it installed right, tough some customers said that they also did some successful installations already.

For now I would like to have some official statement, if we could expect some bug-fixed version soon, which also features a more robust installer with more debugging details.

[wpn]

well i have deployed successfully several times, but all was with the local express database, but skipping the e-mail settings...

so to me it still seems to be the connection to the remote database server
Before the rollback tho everything is downloaded and the database is created, i have seen it in my sql manager.

[bitworld]

In my case, the problem is, that the installer of the SBC is configuring false dependencies on the service:
MSSQL$SBSMONITORING
MSSQL$SHAREPOINT
MSSQLFDLauncher
MSSQLFDLauncher$SBSMONITORING
MSSQLFDLauncher$SHAREPOINT
MSSQLSERVER
MSSQLServerADHelper100
MSSQLServerOLAPService
ReportServer
avast! Administration Console Monitor

When at least one dependend service is not running the setup will fail, because the avast service couldn't be started.

avast is already knowing this. They told me it will be changed in the next release of SBC. But I'm still waiting.
Also you can't determine which release is online, as there is no version number included in the download.

I'm not sure if this will be the only problem but it is the first showstopper.

Hope this helps, and avast is making a new release imediately.

Severin