This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- ProtectionProcessorCleanup.0001 hanging
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Dec 10, 2010
03:49 AM
ProtectionProcessorCleanup.0001 hanging
Hello,
our build machine runs InstallShield 2010 Standalone Build. When the SABuild is started from the build tool, it also starts a ProtectionProcessorCleanup.0001 process. This process does not terminate, so at the end of the build process (which is some steps after the SABuild), the build tool does not terminate because of this hanging process.
This behaviour has occurred regularly for a few days on a Windows 7 build machine (we have been building with InstallShield 2010 Standalone Build and the same build tool for some months on XP and for some weeks on Win7).
Are there any ideas about why this process hangs and what it is supposed to do anyway? Would it be safe to just kill it at the end of the build script (even though I would do that only as a last resort)?
Best regards
Matthias
our build machine runs InstallShield 2010 Standalone Build. When the SABuild is started from the build tool, it also starts a ProtectionProcessorCleanup.0001 process. This process does not terminate, so at the end of the build process (which is some steps after the SABuild), the build tool does not terminate because of this hanging process.
This behaviour has occurred regularly for a few days on a Windows 7 build machine (we have been building with InstallShield 2010 Standalone Build and the same build tool for some months on XP and for some weeks on Win7).
Are there any ideas about why this process hangs and what it is supposed to do anyway? Would it be safe to just kill it at the end of the build script (even though I would do that only as a last resort)?
Best regards
Matthias
(1) Reply
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
Jan 05, 2011
06:53 AM
Just check whether the build process is completing successfully before terminating ur batch or other script file.
Or try to build manually through iscmdbld.exe in command prompt and observe.
Or try to build manually through iscmdbld.exe in command prompt and observe.