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
- :
- Same problem with IS 2010 Standalone build
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
‎May 06, 2009
12:49 PM
ISDEV error -5045
Hi,
Our building group run into the following error (at compilation) when building a project (IS2009 InstallScript), using IS2009 Standalong version.
After that IS reported 0 errors at the end of compilation but 1 error at the end of build, the image seems being built ok.
end of compile
end of build
I never saw the error on my side with IS2009 Premier version during development.
Can anybody give help on how to remove/fix the error?
Thanks,
Yabing
Our building group run into the following error (at compilation) when building a project (IS2009 InstallScript), using IS2009 Standalong version.
ISDEV : error -5045: Could not preserve previous Build Logs
After that IS reported 0 errors at the end of compilation but 1 error at the end of build, the image seems being built ok.
end of compile
Linking...
Setup.inx - 0 error(s), 21 warning(s)
end of build
Default - 1 error(s), 6 warning(s)
I never saw the error on my side with IS2009 Premier version during development.
Can anybody give help on how to remove/fix the error?
Thanks,
Yabing
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 22, 2009
09:06 AM
I've been seeing this with IS12 lately and it's really wierd.
I'm using ESX VM's that get their snapshot reset before every build so the beginning state is always identical.
Without any sourcecode or build automation changes, a merge module solution will occasionally generate this error. Sometimes, but not always.
It's bizarre and really irritating.
I'm using ESX VM's that get their snapshot reset before every build so the beginning state is always identical.
Without any sourcecode or build automation changes, a merge module solution will occasionally generate this error. Sometimes, but not always.
It's bizarre and really irritating.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 24, 2009
01:55 AM
Hi,
Did you manage to solve that problem?
We have recently upgraded to IS 2010 Premier, and the same problem occurs when building the setup on our server using IS 2010 Standalone build.
It quite often works, but on occasion it doesn't and the log file shows the following error
Any idea?
By the way, I have opened a thread in the IS 2010 forum (http://community.acresso.com/showthread.php?t=189223).
Regards
Did you manage to solve that problem?
We have recently upgraded to IS 2010 Premier, and the same problem occurs when building the setup on our server using IS 2010 Standalone build.
It quite often works, but on occasion it doesn't and the log file shows the following error
Copying files from "\LogFiles\*.*" to "E:\BuildArea\SetupTemp\Output\MainPart\LogFiles"
ISDEV : error -5045: Could not preserve previous Build Logs
The system cannot find the path specified.
Any idea?
By the way, I have opened a thread in the IS 2010 forum (http://community.acresso.com/showthread.php?t=189223).
Regards
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 24, 2009
07:17 AM
Sorry, I've never found a solution. I did find a work around though... we are migrating all 700 of our merge modules to WiX.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 24, 2009
07:38 AM
Well, the solution is easy:
just make sure you don't have a "Logfiles" folder in the root of the drive you use to build your setup.
Or if you do have a Logfiles folder, make sure it is empty.
Regards
just make sure you don't have a "Logfiles" folder in the root of the drive you use to build your setup.
Or if you do have a Logfiles folder, make sure it is empty.
Regards
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)