Thanks for replying. First I delected the *.dat file as recommended by that post. Didn't work. Then I deleted the whole configuration folder as he recommended. Didn't work either. Now there is nothing under the Dreamweaver 9 folder. Any other suggestions?
Should I put that config folder back?
Now it opens occasionally. I try it every day and once in a while it will open. Very very strange. I try to just keep it open but invariably, I forget and close it. then no luck for days!!!
I had the same problem. Solved by opening through right click and opening in administrator mode. I then set the program to open automatically in administrator mode and will hopefully set a rule so it doesn't ask me if it is ok everytime I open it.
Thank you so much! It worked perfectly!
How is it possible that this worked for 2 days and suddenly it won't open again?? I was able to open and close the app multiple times for those 2 days no problem. Now, doesn't work. Software is not supposed to be temperamental!! I tried cold boot, restart, deleted the config folder. It is set to run as administrator.. but today it just doesn't feel like opening. Will try again tomorrow . Just can't figure out what setting could be causing all this variability! Any suggestions will be welcome.
A few ideas:
- A recent Windows Update?
- A computer virus?
- Hard drive failure?
- Memory problem?
- Conflict with Anti-Virus software?
- Is Dreamweaver shutting down all the way when you close it? Check your task manager.
Thank you so much for replying. I checked back to find the last day when it worked well and it was right before I installed TaxCut. Several folks in my family are still working on their taxes so I do not want to do a restore to that point. BUT, I was thinking about that after they are done with taxes…I would.. No other software shows any signs of problems – FireWorks, Word, browers, iTunes, PPT, Quicken, etc. No memory, viruses, hard drive problems. IT might be related to a windows up date around the time TaxCut was installed. I’ve been checking the task manager all along. Every time I try to open it, it does leave behind a Dreamweaver.exe file open in the process. I delete those. I tried, restarting the computer after deleting the Config folder, cold starting, etc. No go.
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:
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.
Thank you, I will try this.
Tried this and no luck. I'm completely mystified. It continues to open several days a week. But on the other days, it just plain doesn't work.
Hmmmm. The fact that it works for a couple of days, then stops, leads me to think you may have something else running (sporadically) that conflicts with DW.
(Though, I can't imagine what that could be.)
You mentioned you tried a cold boot. Did you launch anything else?
Since you mentioned a recent TaxCut install, does TaxCut have any processes running in the background when DW crashes?
Also, what specifically happens when DW fails to open?
Does it open and then just blank-out? No DW window at all?
There are no Taxcut processing running that are identifiable. I haven't opened it in days. When DW fails to open nothing happens but that circular blue dot which runs a second or two then stops. And of course it leaves behind a Dreamweaver.exe file running in the Task Manager. I've tried deleting that, cold boot, try again. No luck. Sometimes I try at the end of the day and it works.
When I do a cold boot, I try to open DW first, but that does not seem to work.. I am running in administrator mode for this program and that doesn't seem to work either.
I can't imagine what could be conflicting that wouldn't be running all the time. A true mystery!
Oh man. This one's got me stumped.
Do you have your preferences set to "Reopen documents at startup"?
I'll check next time it opens. About due for an opening in a day or so...
Thanks for this discussion, I'm googling about this problem and found this post.
I think the problem occur after install window 7 updates.
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.
DW just opened today for the first time in days. I checked and the preferences are not set to "reopen documents at startup". I tried starting DW 3 times this am, and no luck. Deleted the Dreamweaver.exe file in Task Manager each time. Inexplicably, this evening I clicked on the shortcut 5 times in a row (in a fit of annoyance) and it opened. I need to use it so I will do my work then keep it minimized and hibernate my PC for as long as I can. Unfortunately sometime in the next day or so I will inadvertently close it :-? just out of habit.
I have been using computers for 30 years now and have never had this bizarre behavior from any software.
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.
Yes, all that happens when I click on the icon is the blue circle for about 2 seconds then it disappears, leaving the Dreamweaver.exe open. I have uninstalled and reinstalled it once, maybe I'll try that again....(though I am remembering the definition of insanity...doing the same thing expecting difft results!)
I may also try a restore to my pre TaxCut days since that installation seems to mark the beginning of when the trouble began.
Thank you for your replies.
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.
I have the EXACT same problem.
Dreamweaver CS3 has been working fine for years. I've run it on Windows 7 since I got this machine - about 1 year ago. And suddenly it won't open. I bet it is a Windows7 patch because I don't have that Tax program on my machine and I can't think of any software I've loaded down recently.
I can open it as Administrator - so far. I'm in the middle of a project with a deadline and don't want to try anything that would make it worse (not open at all).
I'll keep checking back to see if others find a solution. I'm stumped.
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_0c187ef99ee1d25a\MFC80U.DLL". Dependent Assembly Microsoft.VC80.MFCLOC,processorArchitecture="x86",publicKeyToken="1fc8b3b9a1e18e3b",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:
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.
@Ruth105_364 - Oh man, this gets uglier and uglier. Back to the old "DLL-Hell" days.
Did a quick G-search on piece of that error text you posted.
Some folks are getting this error when a trial version of DW CS3 is (or has been at some point) involved.
Ruth, can you describe the exact behavior when you do not run as Admin?
i.e. from the time you click the shortcut to launch Dreamweaver CS3, a step-by-step of what you see/observe. (If you see nothing happening, not even the splash screen, let me know that. However, if you see anything at all, it would be helpful in identifying what may be causing this.)
I click on the application (either the shortcut or the icon on the desktop) and the hourglass appears, turns around a few times and goes away. The application does not open.
Your help would be most appreciated. As I said, I've used DM for years and have a project on it right now.
This is not a fix, but when my Dreamweaver is not working correctly I can always resort to my laptop where I also have it loaded and for some reason, though it too is Windows 7, this problem does not occur. You do need good backups for this method, especially the site manager.
I do have a laptop and it does still seem to be working fine - it's not on Windows 7, though. I think it has to have been some Windows 7 update - although I tried to restore - to no avail.
My PC is more convenient to work on and that's where I am working - because I opened the application by running as Administrator and have not closed it.
As long as it stays open, it works fine.
Strange, right? I hope Carey from Adobe can help us.
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: 220.127.116.1181, time stamp: 0x4600622f
Faulting module name: Dreamweaver.exe, version: 18.104.22.16881, 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
This might be a different issue. I've kept Dreamweaver opened and it hasn't crashed (yet). It never did. When it doesn't open, there is no Spash Screen - just nothing. And I've been able to open in Administrator mode (so far).
I'm sorry this is happening - but there might be something else going on on your computer.
I hope that Adobe answers soon - Carey Burgess posted on May 2nd and nothing since then.
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.
I checked the CSS files and the html files and found nothing that size. Where else should I look for this? And in my case.. why would it only happen some of the time?
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.
Looks like the culprit.
I had just started using Spry for a drop-down menu - probably why it just started happening.
Thank you SO MUCH!!!!!
I hope Adobe is paying attention.
Just thought I'd give you an update on my quirky problem and the only solution that seems to work. I have discovered that if I open a bunch of programs in succession and try to open Dreamweaver in between, eventually it opens. Sounds crazy and I have tried to figure out if a particular program needs to be open (or not!) and nearly drove myself crazy with that bit of research. Bottom line, is if I open 6-10 programs and keep them open, eventually Dreamweaver will open. Sometimes it delays and opens "late" 30 seconds later... A little like jumpstarting and old car....
Appears to be a possible conflict with Windows Aero, at least it was on my workstation. I was finally able to get it to work by changing the following settings ....
- Right-click on the Dreamweaver shortcut and select Properties.
- Switch to the Compatability tab.
- Under the Settings section, select 'Disable visual themes' and 'Disable desktop composition'. (It typically worked without disabling the visual themes, but another time it didn't so I just left it checked. I'm pretty sure all settings are restored when you close DReamwevaer anyway.)
I guess you could disable Windows Aero altogether, or at least the Aero Peek feature, but I like both and really didn't want to see them go. This option gave me the best of both worlds. Hope this helps!
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.
Tried everything on this thread, without success.
Found this page:
via this thread:
The instructions are:
1. Run CMD as administrator
2. Enter command: sfc /scannow
[This may take 20-40 mins to run]
3. Try Dreamweaver again.
This worked first time for me, but I had tried all the other suggestions in this thread first, so I am unsure if it was a combination, or just the sfc /scannow action.
Thank you to all suggestions above and the community support.