PDA

View Full Version : Exception Encountered



William-Webb
07-12-2006, 09:58 AM
Hi All,

Why do bad things always have to happen when your working to a tight schedule?!

Anyway, I get an "Exception Encountered" error when building my project (Gets to the Building File Table and crashes EVERY time!)

This is the contense of the email sent to IS:


Exception ACCESS_VIOLATION (0xc0000005) at address 0x7818069c trying to read address 0x00000000.File : C:\Program Files\Macrovision\IS12\System\isdev.exeVersion : 12.0.0.49974Exception : c0000005Address : 7818069cAccess Type : readAccess Address : 00000000Registers : EAX=00000000 CS=001b EIP=7818069c EFLGS=00010202 : EBX=0911e324 SS=0023 ESP=0012d78c EBP=0911e324 : ECX=00000000 DS=0023 ESI=0a394054 FS=003b : EDX=01c80003 ES=0023 EDI=00000000 GS=0000Stack Trace : 00650065 00000000 00000000 00000000 : 00000000 00000000 00000000 00000000 : 00000000 00000000 00000000 00000000 : 00000000 00000000 00000000 00000000 : 00000000 00000000 00000000 00000000 : 00000000 00000000 00000000 00000000 : 00000000 00000000 00000000 00000000
Anyone have any idea's?

Regards,
Will

MichaelU
07-12-2006, 10:17 AM
On the off chance that it's the same problem, could you try backing up and replacing your iswiscanners.dll per http://community.installshield.com/showthread.php?p=356163#post356163?

William-Webb
07-12-2006, 10:31 AM
Nope, didn't solve the problem :(

Any other idea's?

We might have to go back to using ISX if we dont get it sorted soon :eek:

EDIT:: I've just deselected the .NET and J# options on the build, and it still thows the error and quits! :confused:

MichaelU
07-12-2006, 10:43 AM
No great ones. If you can send me your ISM file I can see if I can reproduce the behavior without your files, and that might allow us to address it directly. (You can see if this has a chance by renaming the folder that contains your files, or editing the relevant path variables until the build can't find your files. If it still crashes like above, it's probably worth a look).

You can also try binary searching to see if you can rip out something (a file, some redistributable, a setting) that will make it work, but definitely back up the current state of your project first. This is especially likely to be useful if you know what you changed since it last built successfully. But first try a quick test new project with a couple things in it to make sure it isn't a general problem on the computer that might be better resolved by running the InstallShield install through a repair.

MartinMarkevics
07-12-2006, 04:11 PM
Try creating a verbose log of the build. To do this, build the project from the command line:

<IS 12.0 Install Location>\System\IsCmdBld.exe -p <full project path> -v

This may give more detailed information about what the build is doing at the time it crashes and more importantly, what file\component it is failing on. That might give us a clue to how we could narrow this down.

William-Webb
07-13-2006, 03:46 AM
Ok, Done... I think i've found the problem looking at this, but I cant see anything wrong with the components listed, and this shouldn't crash when encountering errors like this...

Any idea's?


Loading File table
Building File table
Skipping .NET scan for component Data: KeyPath is not a file
Skipping .NET scan for component Database: KeyPath is not a file
Skipping .NET scan for component Info_Extentions_English: KeyPath is not a file
Skipping .NET scan for component DataMessagesEnglish: KeyPath is not a file
Skipping .NET scan for component PlanitMain: KeyPath is not a file
Planit Installer\14.1.0 - 0 error(s), 1 warning(s)
================= Logging stopped at 7/13/2006 09:16:59 AM ==================
Log file has been created: <file:C:\INSTALLSHIELD\INSTALLER PROJECTS\MAIN INSTALLERS\Planit Fusion Live Legacy\Planit Installer\14.1.0\LogFiles\7-13-2006 09-16-54 AM.txt>



The whole log file is attached...

William-Webb
07-14-2006, 08:40 AM
I am still getting this error...

Does anyone at InstallShield have any other idea's as this is starting to get to the "misson critical" stage :eek:

MartinMarkevics
07-14-2006, 12:08 PM
I definitely agree that it shouldn't crash...

I think it has something to do with the .NET scan. Not necessarily the PlanitMain component, but whatever component it builds\scnas next. I created a new version of iswibuild.dll which outputs a verbose message indicating which file\component it is currently trying to scan (in addition to outputting the files\components that it skips as it already does).

Replace the version of iswibuild.dll in <IS 12.0 Install Location>\System folder. Then run the command line build again with the verbose switch as you did before. This may give us more information to help track down the issue.

If not, send me your e-mail addres via a private message and we can deal with this offline in order to expedite figuring out this issue.

William-Webb
07-17-2006, 03:33 AM
Hi MartinMarkevics,

Thanks for the file, but it didn't seem to make a single bit of a difference :confused:

I've attached the new error log, but it looks identical to all of the others!

I have also sent you a Private Message.

Thanks for all the help so far!

Regards,
Will

scottd72
07-25-2006, 08:43 AM
I had the same issue in which the IDE would crash every single time during a build. I replaced the ISWIScanners.dll with the one presented in this thread and it worked for me. Keep us updated on how you're making out please.

bloomy13
11-01-2006, 04:34 PM
I recently upgraded to Version 12 - Premier and I am experiencing the same issues. Initially, the build failed every other attempt. I installed the hotfix and it fixed that problem.

However, I have an entirely different project that needs to be done "yesterday" and now it is failing EACH TIME I try to build it. It won't build...period.

My output is as follows:

Exception ACCESS_VIOLATION (0xc0000005)
at address 0x7818069c trying to read address 0x00000000.

File : C:\Program Files\Macrovision\IS12\System\isdev.exe
Version : 12.0.0.49974
Exception : c0000005
Address : 7818069c
Access Type : read
Access Address : 00000000

Registers : EAX=00000000 CS=001b EIP=7818069c EFLGS=00010202
: EBX=0500da2c SS=0023 ESP=0012c800 EBP=0500da2c
: ECX=00000000 DS=0023 ESI=0603cedc FS=003b
: EDX=00560001 ES=0023 EDI=00000000 GS=0000

Stack Trace : 002e0062 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000
: 00000000 00000000 00000000 00000000

Can anyone help?

William-Webb
11-02-2006, 04:23 AM
Try and strip everything from the project (files, dynamic links, everything), and run the build again via a batch file with verbose loggin on...

Post the log up once complete and i'll have a look! :)

MartinMarkevics
11-02-2006, 10:18 AM
Can you post the vebose build log?

iscmdbld.exe -p <project path> /v

MartinMarkevics
11-02-2006, 10:21 AM
William,

Did you ever get your issue resolved? Looks like I never replied to your last post some time ago? Sorry about that, it was not intentional.

bloomy13
11-02-2006, 10:34 AM
Thanks for your help. William-Webb, thanks to you as well. Here it is the verbose log:

================= Logging started at 11/2/2006 10:07:19 AM ==================
Creating path "C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Release 1\Reports"
Creating path "C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Release 1\DiskImages\DISK1"
Copying files from "C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Release 1.Bak\LogFiles\*.*" to "C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Release 1\LogFiles"
Copying files from "C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Release 1.Bak\Reports\*.*" to "C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Release 1\Reports"
Deleting folder "C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Release 1.Bak"
Creating path "C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Release 1\TestTools"
Removing read-only attribute for file "C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Interm\_IsIcoRes.Exe"
Copying from "C:\Program Files\Macrovision\IS12\Support\_IsIcoRes.Exe" to "C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Interm\_IsIcoRes.Exe"
Copying from "C:\Program Files\Macrovision\IS12\Support\0409\IsMsiPkg.itp" to "C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Release 1\DiskImages\DISK1\MSS_Install.msi"
Removing read-only attribute for file "C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Release 1\DiskImages\DISK1\MSS_Install.msi"
Created release folders
Deleting file "C:\InstallShield 12 Projects\MSS_Install\Script Files\Setup.inx"
Launching application: "C:\Program Files\Macrovision\IS12\System\Compile.exe" with command line: " "C:\InstallShield 12 Projects\MSS_Install\Script Files\Setup.Rul" -o"C:\InstallShield 12 Projects\MSS_Install\Script Files\Setup.inx" "C:\Program Files\Macrovision\IS12\Script\ISWi\Lib\iswi.obl" "C:\Program Files\Macrovision\IS12\Script\ISRT\Lib\isrt.obl" -v3 -w50 -e50 -g -i"C:\InstallShield 12 Projects\MSS_Install\Script Files";"C:\Program Files\Macrovision\IS12\Script\ISWi\Include";"C:\Program Files\Macrovision\IS12\Script\ISRT\Include";"C:\Program Files\Macrovision\IS12\Script\Include";"C:\Program Files\Macrovision\IS12\Script\SQLRuntime\Include";"C:\Program Files\Macrovision\IS12\Script\IISRuntime\Include";"C:\Program Files\Macrovision\IS12\Script\XMLRuntime\Include" -obsolete"C:\Program Files\Macrovision\IS12\Support\0409\obsolete.ini""
InstallShield Script Compiler
Version 12.0.0.49974
Copyright 1997-2006 Macrovision Europe Ltd. and/or Macrovision Corporation. All Rights Reserved.

Compiling...
Setup.Rul
Linking...
Setup.inx - 0 error(s), 0 warning(s)
Adding ISSetup.dll support file C:\InstallShield 12 Projects\MSS_Install\String1033.txt
Removing read-only attribute for file "C:\InstallShield 12 Projects\MSS_Install\String1033.txt"
Deleting file "C:\InstallShield 12 Projects\MSS_Install\String1033.txt"
AdminExecuteSequence table successfully built
AdminUISequence table successfully built
AdvtExecuteSequence table successfully built
AdvtUISequence table successfully built
InstallExecuteSequence table successfully built
InstallUISequence table successfully built
Directory table successfully built
Including feature VirtualDirectoryFiles
Feature table successfully built
FeatureComponents table successfully built
Component table successfully built
Loading File table
Building File table
Skipping .NET scan for component VirtualDirectoryComponent: KeyPath is not a file
Product Configuration 1\Release 1 - 0 error(s), 0 warning(s)
================= Logging stopped at 11/2/2006 10:07:25 AM ==================
Log file has been created: <file:C:\InstallShield 12 Projects\MSS_Install\Product Configuration 1\Release 1\LogFiles\11-2-2006 10-07-19 AM.txt>

William-Webb
11-02-2006, 10:38 AM
William,

Did you ever get your issue resolved? Looks like I never replied to your last post some time ago? Sorry about that, it was not intentional.

It's ok Martin, I know how easy it is to forget something when your constantly busy!

In the end I gave up and re-created the project from scratch. It still does it from time to time tho, it just goes bang!...

The company are planning on upgrading to Premier, hopefully this might solve some problems! :o

This seems to be almost "random", it crashes for almost no reason... Your software is almost as buggy as ours! :D

William-Webb
11-02-2006, 10:41 AM
bloomy13,

Click "Tools > Options > Validation" and turn off the bottom two validation options....

Also, Click "Tools > Options > .NET" and turn the .Net scanning off (none)...

Try to build it again and hopefully this should work! (It 'kinda' helped in my case! :rolleyes: )

James Zhu
01-03-2008, 02:52 AM
William-Webb, I encountered the exactly the same problem as you did.

Make sure there is only one dynamic folder in each of your components. You might have a component that links to two dynamic folders. If those two folders contain files of the same names, then the condition that filenames in each component are unique will break, hence exception (Suggested by Imre Lengyel).