We’re moving our forums to a new platform.

You can still browse and search existing topics, but you can no longer create new topics or post replies.

For questions, technical issues, or feature requests, please don’t hesitate to contact our support team at support@advancedinstaller.com.

Thank you for your understanding!

mabs
Posts: 27
Joined: Tue May 08, 2012 10:04 am

Resuming installation after reboot and error 1622

Hi.

Well, I continue with my "reinstall-after-reboot" problem. The problem is not it appears is some cases, my problem is it apperas too many times, practically every time I install, update or repair, in all machines I tested, including several Windows XP SP2 and Windows 7 x32 and x64.

But now there is another new element to add to this problem: in some fow cases, when the installation resumes after reboot, it appears in screen an error message whit the text: "Server returned unexpected error 1622 attempting to install package C:\....\file.MSI".

I updated to AI 6.9.1 as you recommended, but the problem persists.

As you know, my problem is when the installer ends, it creates a registry entry in the "run" section to resume the installation when the computer reboots. In some cases, a task in the Windows Task Scheduler is created instead the registry entry.

I read a lot of log files, but I don't know why this occurs because the installer don't registers the cause. I don't find files in use nor errors registering COM components or fonts... I don't know. I spain we say "I'm lost as an octopus in a parking"...

I attach the last log file, created with the AI 9.6.1.

Regards.
Attachments
log.zip
(638.29 KiB) Downloaded 599 times
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Resuming installation after reboot and error 1622

Hello,
Well, I continue with my "reinstall-after-reboot" problem. The problem is not it appears is some cases, my problem is it apperas too many times, practically every time I install, update or repair, in all machines I tested, including several Windows XP SP2 and Windows 7 x32 and x64.
You can see my response from "Reinstall-after-reboot registry entries" thread.
But now there is another new element to add to this problem: in some fow cases, when the installation resumes after reboot, it appears in screen an error message whit the text: "Server returned unexpected error 1622 attempting to install package C:\....\file.MSI".
You could encounter this behavior if you don't have write permissions in the log file location. Please take a look on "System Error Codes (1300-1699) (Windows)" article.

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube
mabs
Posts: 27
Joined: Tue May 08, 2012 10:04 am

Re: Resuming installation after reboot and error 1622

Hi, people.

Referring to the 1622 error, the log file location is the temporary directory for the current user.

And referring to my "always-reinstal-after-reboot" beahviour problem, today I discovered the cause:

When the installation package contanis one or more feature prerrequisites which uses files on disk (not downloaded files) (in my case, a C# program which deletes other old files) the installer creates "by default" the registry entry or the scheduler task, and doesn't delete it when the installation process finishes correctly.

If the installtion package doesn't contains any file-on-disk based feature prerrequisite, the registry entry/task is not created.

Regards.
Daniel
Posts: 8283
Joined: Mon Apr 02, 2012 1:11 pm
Contact: Website

Re: Resuming installation after reboot and error 1622

Hello,
When the installation package contanis one or more feature prerrequisites which uses files on disk (not downloaded files) (in my case, a C# program which deletes other old files) the installer creates "by default" the registry entry or the scheduler task, and doesn't delete it when the installation process finishes correctly.
Can you please send us the .AIP (project file) and a download link for your installation package by e-mail to support at advancedinstaller dot com so we can try to reproduce the behavior and investigate this? Also, can you isolate the behavior on a sample project?

All the best,
Daniel
Daniel Radu - Advanced Installer Team
Follow us: Twitter - Facebook - YouTube

Return to “Common Problems”