I just ran into this problem today and solved it by systematically renaming all my Managed Site folders until it started up again. 

I found the solution at this site:

http://www.mikepadgett.com/technology/technical/dreamweaver-cs3-crashe s-and-wont-start-up-again/

Apparently Dreamweaver will crash if you edit a file to exactly a multiple of 8,192 bytes.  Renaming your folders,or editing the file outside of Dreamweaver so it is more or less than 8,192kb when saved fixes it.  I couldn't find the file causing the problem but I assume that I would find it in the last folder I tried renaming.

Leanne

dgrwebster wrote:

 

I'll check next time it opens.  About due for an opening in a day or so...

If the option is on - turn it off, close out all your open pages (if any) and restart DW.

Hi dgrwebster,

Man!  I hate to admit it but I'm at a loss for suggestions on this one.

You've either got a hardware problem, a DW installation problem or a software conflict problem.

I guess we can rule out hardware, since nothing else is going wrong on your system.

I guess we can rule out DW installation, since you've already reinstalled DW.

The only other thing I can think of is a software conflict.  Something else is running (occasionally) that interferes with DW.

The only thing you see when DW fails is the "blue circle" icon?  No DW window comes up at all?

This one's got me stumped.

Well, if you're going to do the "insane thing", here are a couple of suggestions:

Reboot the computer right after the uninstall.

Log in to your system with an administrator account.

Temporarily turn off your anti-virus program.

Then install DW, but not in the default directory - put it somewhere else like c:\DreamweaverCS3

None of this makes sense because you've had DW running for over a year.

But maybe, just maybe, that latest Win7 patch messed up something.

Checking the Windows Application event log reveals an error occuring upon execution of Dreamweaver.  The error text follows:

_microsoft.vc80.mfc_1fc8b3b9a1e18e3b_8.0.50727.163_none_0c187ef99ee1d2 5a\MFC80U.DLL". Dependent Assembly Microsoft.VC80.MFCLOC,processorArchitecture="x86",publicKeyToken="1fc 8b3b9a1e18e3b",type="win32",version="8.0.50608.0" could not be found. Please use sxstrace.exe for detailed diagnosis.

An option is given to link to the online event log, with url:

http://technet.microsoft.com/en-us/library/c688bfb1-6ffb-45b0-b8b0-294 675a693a9.aspx

The explanation given there would suggest that an incompatible version of the C runtime library was downloaded to the machine at some point.  The side-by-side  functionality appears to be compromised.  The article suggests that the runtime libraries be downloaded and re-installed, and gives a link for this purpose.  I have not tried it yet.  In my experience, it could also be an update to the .net framework that's screwing things up--this happens regularly.

So, I'm not alone. I began having this same problem today. I was working with DW CS3, likewise on the same Window 7 computer I've been using it on for over a year, when it suddenly crashed. I reopened it and after a minute or so, it crashed. Now it will not open at all, whether I try to run as Admin or not.

When I click on the icon, I get the little splash screen very briefly, then just as a full-size wondow starts to open, it all disappears. No process is left running. There have been no Windows updates in three weeks. I have not installed any new software.

Here's what I find in the Windows Application Event Log:

Faulting application name: Dreamweaver.exe, version: 9.0.0.3481, time stamp: 0x4600622f

Faulting module name: Dreamweaver.exe, version: 9.0.0.3481, time stamp: 0x4600622f

Exception code: 0xc0000005

Fault offset: 0x009b4df4

Faulting process id: 0x1964

Faulting application start time: 0x01cd2c59605f6cd3

Faulting application path: C:\Program Files (x86)\Adobe\Adobe Dreamweaver CS3\Dreamweaver.exe

Faulting module path: C:\Program Files (x86)\Adobe\Adobe Dreamweaver CS3\Dreamweaver.exe

Report Id: dce0047e-984c-11e1-8d39-78acc0985288

I'm reporting back to the team that my problem was actually caused by the famous 8k bug. I found a  jpg file that was exactly 65536 bytes in size. I reoptimized that and am now back up and running.

Don't overlook this possibility, no matter how unlikely it seems.

Hello All,

I recently had the same issue. I didn't believe that the 8K bug was responsible. I mean really? But it was. I've included a pic. The strange part was that I was using SpryTabbedPanels.css, but I hadn't modified it yet. Therefore it was the culprit - having a default size of 8,192 bytes. Perhaps Adobe should add a few characters to that default file. All the same, I just added a few characters to this file and Dreamweaver CS3 opened again. Odd but true. So just as a thought if you were using Spry you may want to check out the default files as well.

Finally, after trying all the more exotic ways, I found that it is the most reliable.  I open Photoshop first and a few projects there - then Dreamweaver obeys and opens very nicely.

It seems to need the PC to slow down in order to get itself open.  Also always works opening as an Administrator - also probably because that slows it down.

Weird, but I've been using this method and had no further problems.