Rollback during the installation, logs available

To see what the setup has done or not, I have just killed the setup process when it started to process a rollback.
Then I was able to see the installed service and the dependencies inside the normal console (services.msc)
As this is leaving the system in a dirty state, it shouldn’t be performed on a producvtive system.

An alternative is to monitor the registry with the sysinternals procmon.exe. This will result in a huge list of accesses and changes to the registry. But it would be a hard work to find the failure on billions of entries.

@bitworld, thnx

@avast.de no not moved, installed…
i am not willing (actually refuse) to install a production product on a temporary computer because it fails to do what it should do, besides that i dont have the licenses to install a whole new server for unknown time.
I will not install sql express on a production machine for temporary use and on a machine that is not supposed to have a database engine on it.
:slight_smile:

so the new installer is very very welcome

I understand what you mean, I share your opinion, just trying to find a workaround for the time needed by AVAST to release a bugfixed installer. It seems that the problem here is the AD helper service, which only starts when it is needed. If the avast! installer starts it due to the dependencies and it stops immediately after that the calling service will not start either (in this case the avast! Mirror service). If I am right that is causing the rollback at the end.

Therefore it “may” be a solution to create it with a local database (without AD helper service), detach the database after the installation, attach to the production SQL, change the connection settings in the avast! SBC installation and use it with a remote DB. Of course this is just a theoretically thought and of course I also agree that this would not be a valid permanent solution. The installation itself should run properly in the first place.

Maybe some dev could confirm the cause and name an ETA for a new, fixed installer. Lukas…maybe you can jump in here.

i jumped ahead with thinking you would suggest running a complete server temporary, but your explanation is viable. Its too much hasle tho.

If i have time left over today i could see about testing the AD Helper service in my test environment. If i can test it ill let it know here

Hi wpn,

OK now we understand each other (hopefully) :slight_smile:

We are also running a test and discussing it in our forum, hopefully we will have some results ready soon. But at the moment I am not too positive about that we can handle the AD helper thing somehow, because it is only started by the SQL service itself on demand, therefore it may be possible that we need to wait for a fixed installer :confused: Well I will let you know if there are any news.

with the new installer i still receive the premature ending and roll back as i posted in the thread: http://forum.avast.com/index.php?topic=82941.0

I posted this (with the logfiles):

im still getting a premature ending with rollback

maybe im overlooking something in the logs but i dont see any error indicating any error causing a rollback, so i figure its still the same problem as before with the remote database server issue

Hi wpn,

we had one user who got his problem solved with the new installer, however we are still awaiting response from others, who experienced problems. At least one case hasn’t been solved, but I am still confirming that the user is using the latest version, since he mentioned that the version number remained the same.

Are you 100% sure that the customer that installed successfully didnt accidentally used the included express database?
The mistake is easily made i know from experience :wink:

I’m having the same experience with SP1 … finally got past the “installing service” screen but get the SMTP error during the process that downloads the mirror files. (see attached jpg) Which then when you click ok on the notification Window it rolls back.

This is becoming very disappointing – doesn’t Avast test these installers before publishing them?

I too cannot put this in my production environment using SQL Express … despite Avast support telling me that was the solution. It is not – this should work with a remote SQL server.

Please come up with a new installer very soon! My whole Windows 7 deployment project is on hold waiting for this solution.

@ HCI
i didnt fill in my exchange details because of the error, instead i filled in my gmail account.
This seems to work since i receive an email, except it still does the rollback

That too is highly disconcerting. I’m really disappointed that these kind of errors exist on a public “gold master” release (especially on SP1) … it appears as if the installer is not being tested properly.

I’m a long time business user of Avast going back around 8 years give or take – and have been a very happy and supportive customer and even evangelist (hopefully contributing to make Avast the #1 company on the consumer side it is today). But, I have felt abandoned as a business user the last year or so and hope they start to focus on us again.

I hope we get a working installer soon!

i hear ya

right now im scanning through the log file that the installer created with the command line logging option to filter my passwords…
hopefully it will be helpful for the Avast team