Using Mac OS X. iWeb crashes when I try to publish, after 8 years of problem free updating, gives following error
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000088
Crashed Thread: 18
Have tried everything forums suggest.; repaired hard disc, added 1TB, deleted photos, blogs etc.
Desperately need to update our charity's website. Please help.
Jan
null-OTHER, Mac OS X (10.6.8), iWeb 3.0.4
I don't know as I've not created nor used a blog site. Do you have a backup of the Domain.sites2 file that resides in your Users/Home/Library/Application Support/iWeb folder that was made before you attempted the move of pages?
Replace the current file with the backup file and launch iWeb again. That should return the blog to it's previous situation. Keep the current Domain.sites2 file just in case. Move it to the Desktop.
Hi OT thanks for responding. Feel I know you already, having read many of your threads to others on the above subject!
Just tried publishing to folder on desktop, but crashed again with following error.
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
As I am a complete amateur could you keep suggestions simple. Many thanks
Jan
Sorry for delay had to work out how to find reports! This is a learning curve for me.
This is the last report from trying to publish to folder on desktop - different to trying to publish to FTP server, which says Crashed Thread 18?
Process: iWeb [749]
Path: /Applications/iWeb.app/Contents/MacOS/iWeb
Identifier: com.apple.iWeb
Version: 3.0.4 (304)
Build Info: iWeb-6010000~1
Code Type: X86 (Native)
Parent Process: launchd [106]
Date/Time: 2018-05-29 21:04:05.214 +0100
OS Version: Mac OS X 10.6.8 (10K549)
Report Version: 6
Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 com.apple.CoreFoundation 0x01a3068d _CFArrayReplaceValues + 573
1 com.apple.CoreFoundation 0x01a89f1b -[NSMutableArray addObjectsFromArray:] + 219
2 com.apple.iWeb 0x00033312 0x1000 + 205586
3 com.apple.iWeb 0x0000e53a 0x1000 + 54586
4 com.apple.iWeb 0x000109ed 0x1000 + 63981
5 com.apple.iWeb 0x00010924 0x1000 + 63780
6 com.apple.iWeb 0x0014249e 0x1000 + 1315998
7 com.apple.iWeb.sfstyles 0x02824776 -[SFSStylesheet(PersistenceAdditions) encodeWithXMLArchiver:node:version:] + 812
8 com.apple.iWeb.sfarchiving 0x02148ad5 -[SFAXMLArchiver encodeObject:asChildOf:withName:xmlNamespace:] + 469
9 com.apple.iWeb 0x00026027 0x1000 + 151591
10 com.apple.iWeb 0x00025e4b 0x1000 + 151115
11 com.apple.iWeb.sfarchiving 0x02148ad5 -[SFAXMLArchiver encodeObject:asChildOf:withName:xmlNamespace:] + 469
12 com.apple.iWeb 0x0007070c 0x1000 + 456460
13 com.apple.iWeb 0x00025d41 0x1000 + 150849
14 com.apple.iWeb.sfarchiving 0x02148ad5 -[SFAXMLArchiver encodeObject:asChildOf:withName:xmlNamespace:] + 469
15 com.apple.iWeb 0x0000d267 0x1000 + 49767
16 com.apple.iWeb 0x000727cd 0x1000 + 464845
17 com.apple.iWeb.sfarchiving 0x02148ad5 -[SFAXMLArchiver encodeObject:asChildOf:withName:xmlNamespace:] + 469
18 com.apple.iWeb 0x0003496b 0x1000 + 211307
19 com.apple.iWeb.sfarchiving 0x02148ad5 -[SFAXMLArchiver encodeObject:asChildOf:withName:xmlNamespace:] + 469
20 com.apple.iWeb 0x0000fe1e 0x1000 + 60958
21 com.apple.iWeb.sfarchiving 0x02148632 -[SFAXMLArchiver encodeObject:asRootNodeNamed:xmlNamespace:] + 370
22 com.apple.iWeb 0x001b0a49 0x1000 + 1768009
23 com.apple.iWeb 0x00098795 0x1000 + 620437
24 com.apple.iWeb 0x0024098f 0x1000 + 2357647
25 com.apple.iWeb 0x00006606 0x1000 + 22022
26 com.apple.AppKit 0x009e121a -[NSDocument saveToURL:ofType:forSaveOperation:error:] + 201
27 com.apple.AppKit 0x009e4459 -[NSDocument _saveToURL:ofType:forSaveOperation:delegate:didSaveSelector:contextInfo:] + 71
28 com.apple.AppKit 0x009e1568 -[NSDocument saveToURL:ofType:forSaveOperation:delegate:didSaveSelector:contextInfo:] + 788
29 com.apple.AppKit 0x009e5d51 -[NSDocument _saveDocumentWithDelegate:didSaveSelector:contextInfo:] + 879
30 com.apple.AppKit 0x009e191d -[NSDocument saveDocumentWithDelegate:didSaveSelector:contextInfo:] + 354
31 com.apple.AppKit 0x009e19ef -[NSDocument saveDocument:] + 58
32 com.apple.iWeb 0x000051b4 0x1000 + 16820
33 com.apple.iWeb 0x0000543a 0x1000 + 17466
34 com.apple.iWeb 0x00239a93 0x1000 + 2329235
35 com.apple.iWeb 0x00164486 0x1000 + 1455238
36 com.apple.iWeb 0x001417b4 0x1000 + 1312692
37 com.apple.iWeb 0x0023b6ce 0x1000 + 2336462
38 com.apple.iWeb 0x0023b73d 0x1000 + 2336573
39 com.apple.iWeb 0x00238f8f 0x1000 + 2326415
40 com.apple.AppKit 0x006c3a26 -[NSApplication sendAction:to:from:] + 112
41 com.apple.sf.sfapplication 0x0203d794 -[SFAppApplication sendAction:to:from:] + 610
42 com.apple.AppKit 0x006c38d9 -[NSMenuItem _corePerformAction] + 435
43 com.apple.AppKit 0x006c35ca -[NSCarbonMenuImpl performActionWithHighlightingForItemAtIndex:] + 174
44 com.apple.AppKit 0x006c34b6 -[NSMenu performActionForItemAtIndex:] + 65
45 com.apple.AppKit 0x006c3469 -[NSMenu _internalPerformActionForItemAtIndex:] + 50
46 com.apple.AppKit 0x006c33cf -[NSMenuItem _internalPerformActionThroughMenuIfPossible] + 97
47 com.apple.AppKit 0x006c3313 -[NSCarbonMenuImpl _carbonCommandProcessEvent:handlerCallRef:] + 336
48 com.apple.AppKit 0x006b7a55 NSSLMMenuEventHandler + 404
49 com.apple.HIToolbox 0x04ec9c2f DispatchEventToHandlers(EventTargetRec*, OpaqueEventRef*, HandlerCallRec*) + 1567
50 com.apple.HIToolbox 0x04ec8ef6 SendEventToEventTargetInternal(OpaqueEventRef*, OpaqueEventTargetRef*, HandlerCallRec*) + 411
Thanks so much for taking the time to help me
Jan
I'm not proficient at reading crash reports but don't see anything obvious in it. As a test, create a new site, put in a couple of pages similar to what you have and see if that can be published to a folder on the Desktop.
One of the pages that you edited the last time is damaged somehow. I'd run these tests;
1 - move the last page you edited out of the site to a holding site and publish to the folder. If it publishes OK then you'll need to redo that page and put it back in your site and republish.
2 - if necessary repeat Step one for each page you've edited recently until you find the culprit.
On another note: it might be time to start thinking of migrating to another web design app that is still supported and maintained by the developers. One that many have migrated to is EverWeb because it has a GUI very similar to iWeb and has iWeb's drag and drop feature. Also it's much more powerful than iWeb as it is compatible with all the current HTML features.
Thanks OT. This could take a while as I've been adding pages since the 'crash' in the hope I'd be able to publish soon.
At least I now know how to check pages. Much appreciated. Will let you know if I succeed.
I have been looking into moving to Everweb already, but you will see from the website (innersense.org.uk) that it contains hundreds of photos, so think I may have to start again and cut down content!
Thanks again for sharing your time and knowledge.
Jan
Think I've just made a big 'faux pas'. Was doing as suggested....dragging most recently edited pages one at a time into a new testing site to see if they would publish to folder on desktop (hence find damaged file), then dragging them back into original website successfully. However, having recently edited the blog, tried the same thing, it published to folder ok, but now won't drag back into original website 😟 Does this mean I am now not able to return several years of blogs? Aaaaaggghhhh!
Kern Protection Failure usually indicates a damage data file. See if you an publish your website to a folder on your Desktop. Can you?
Post the first 50 lines of the crash report. Be sure to include the crashed thread - 0.
Ok, I'll try that, once I've worked out how.
Thankyou
Ok, that worked ok 😕
So what does that mean for my original website please?
I'm not sure as I've not used EverWeb much but you may be able to copy and paste items from your iWeb page to an EverWeb page. Work a try with the demo mode.
Yes, I'll have a go, thankyou.
Shame, as I've enjoyed using iWeb. Don't understand Apple sometimes 😟
Jan
Ok, I'll try to do that 😕
Thanks
iWeb crashes when I try to publish
