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
- :
- ISDEV : error -6258 after Upgrade to Windows 8
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
‎Oct 16, 2012
09:41 AM
ISDEV : error -6258 after Upgrade to Windows 8
Hi,
I've updated my machine from Win 7 Ultimate (x64) to Win 8 Pro (x64). It has the Standalone Build of Installshield 2012 installed (18.0.0.329).
Now my Build gets the following errors:
ISDEV : error -6258: An error occurred extracting digital signature information from file "C:\Program Files (x86)\InstallShield\2012 SAB\Redist\Language Independent\i386\MSI3.1\WindowsInstaller-KB893803-x86.exe". Make sure the digital signature information provided in the IDE is correct.
ISDEV : error -6003: An error occurred streaming '\Interm\MSIEng.isc' into setup.exe
Then it signs my setup successfully but fails again:
ISDEV : error -6258: An error occurred extracting digital signature information from file "\.msi". Make sure the digital signature information provided in the IDE is correct.
ISDEV : error -6003: An error occurred streaming '\.isc' into setup.exe
The same ISM-File runs fine on a full Installation of Installshield 2012 on Win 7 (x64). It worked on my machine before so it seems to be related to Windows 8.
Any help would be greatly appreciated. Thanks in advance.
Uwe
I've updated my machine from Win 7 Ultimate (x64) to Win 8 Pro (x64). It has the Standalone Build of Installshield 2012 installed (18.0.0.329).
Now my Build gets the following errors:
ISDEV : error -6258: An error occurred extracting digital signature information from file "C:\Program Files (x86)\InstallShield\2012 SAB\Redist\Language Independent\i386\MSI3.1\WindowsInstaller-KB893803-x86.exe". Make sure the digital signature information provided in the IDE is correct.
ISDEV : error -6003: An error occurred streaming '
Then it signs my setup successfully but fails again:
ISDEV : error -6258: An error occurred extracting digital signature information from file "
ISDEV : error -6003: An error occurred streaming '
The same ISM-File runs fine on a full Installation of Installshield 2012 on Win 7 (x64). It worked on my machine before so it seems to be related to Windows 8.
Any help would be greatly appreciated. Thanks in advance.
Uwe
(4) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jan 07, 2013
07:58 PM
I tried replacing Signtool.exe with newer one from the Windows SDK. This did not fix the problem.
About half the time, InstallShield also just crashes.
I also tried creating a brand new simple project. Same issue.
Anyone?
About half the time, InstallShield also just crashes.
I also tried creating a brand new simple project. Same issue.
Anyone?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Feb 19, 2013
07:11 AM
I am getting the same issue Windows 8 Pro 64-bit, gives error -6258 and -6003, yet it happily signs the files and setup.exe, just refuses to sign the Windows Installer File msi file.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 16, 2013
03:13 PM
We're in the process of trying to set up our build environment on a 64-bit Windows Server 2012 system and are having the exact same problem but with the InstallShield 2010 SP1 Standalone Build module (16.0.0.400).
Did anyone ever figure out what's causing this or how to work around it?
Did anyone ever figure out what's causing this or how to work around it?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 20, 2013
05:21 PM
I opened a support incident with Flexera (SIOC-000144395) for my scenario (error 6258 when building IS 2010 source on Win Server 2012) and, as expected, they told me IS 2010 isn't supported on Win Server 2012 and I would have to upgrade to get support. After upgrading I no longer had this issue.