Dreamweaver CC 2014 crashes when updating site cache

Hi everyone,
I'm using Dreamweaver CC 2014 on the Mavericks operating system for mac. Dreamweaver attempts to update a site cache for one of my sites but then it pauses for a few minutes and then crashes. I thought it could have been a corrupted cache file so I deleted the MacFileCache-********.dat file inside the Dreamweaver configuration folder but this didn't work. I tested again and I got the same result.
I just wondered if anyone has had this problem or whether there's a workaround?
Appreciate any advice.

I do have one workaround that worked for MOST of my folders. It is NOT the best option--but it helped me get a little more of my website recognized. (This is working on a mac with the latest version of Mavericks. Who knows WHAT Yosemite will do!)
I dragged my biggest folders out of the larger 'site' folder and on to the desktop. I ignored them and just began with the dreamweaver site manager--creating my site by pointing to the first few folders that had been listed under 'site'. Then, I added the folders on the desktop a few at a time. It worked until I got to a larger, complicated folder...then it froze again. I worked on this all day-- and I'm done for now. But I'm not giving up. With Adobe, there is always a good outcome. Sometimes, it just takes a little longer.
If I get all the kinks out, I'll let you know. Meantime, the more people who ask the question, perhaps the more likely it is to get a little help.
THANKS.

Similar Messages

Crash when updating site cache? MM_Username1?

Hi,
All of a sudden, tonight, DW8.0.2 will no longer open or load
one of my
sites, crashing when "Updating Site Cache". The site is ASP
linked to an SQL
database.
Checking the file that the cache gets to, I notice that the
problem file is
within a sub-directory of the site, called "/admin". Thing is
though, it's
not always the same file, but it IS always a file within the
/admin
sub-directory.
Within this sub-directory I altered, by hand, the Login User
code and
Restrict Access to Page code to create and use the session
variable
MM_Username1 as opposed to the default MM_Username.
Could this be the reason for the sudden trouble with the site
cache? I am
puzzled because the site was working fine for a few weeks
now, with this
sub-directory included, and I didn't create the MM_Username1
issue today
either, it has also been working fine for a good few weeks
now. I've also
not added anything new to the site, that I am aware of.
When I remove the sub-directory from the site, the Updating
Site Cache works
fine, so I am 100% sure there is a problem with the files
within this
sub-directory. How will I know which one though?
I've tried this, as recommended by Adobe, but I still get a
freeze-up when
re-creating the cache:
1. Try renaming the Dreamweaver user configuration folder, so
that
Dreamweaver will automatically generate a new user
configuration folder the
next time Dreamweaver launches. The Configuration folder is
located here:
C:\Documents and Settings\<username>\Application
Data\Macromedia\Dreamweaver
8\Configuration
2. Recreate your Dreamweaver user settings in the registry as
follows:
Launch the Registry Editor by clicking the Start button,
choose Run, then
type "regedit". In the Registry Editor, navigate to this
folder:
HKEY_CURRENT_USER\Software\Macromedia\Dreamweaver 8
Rename the "Dreamweaver 8" key to "DreamweaverOLD", so that
Dreamweaver will
automatically generate a new user settings key the next time
you launch it.
3. Recreate your Dreamweaver site definitions in the registry
as follows.
The steps below will delete your site definitions in
Dreamweaver.
4. Launch the Registry Editor by clicking the Start button,
choose Run, then
type "regedit". In the Registry Editor, navigate to this
folder:
HKEY_CURRENT_USER\Software\Macromedia\Common\8\Sites
Rename the "Sites" key to "SitesOLD", so that Dreamweaver
will automatically
generate a new Sites key the next time you launch it.
Any further advice?
Regards
nath.

Found it! Jeesh.
I had a querystring value in my UPDATE redirect URL which was
coded
incorrectly!!!
I am frustrated that, rather than just highlighting the error
or, at the
very least, producing an error when opening the specific
file, this type of
thing crashed the entire DW programme.
The time I spent in Notepad today changing MM_Username1 back
to
MM_Username!! Turns out that was nothing to do with it.
<groan> Yeah,
that's right, laugh it up! :o)
Anyway, solved now. A misplaced ", %, ), (, <, >, &
etc can cause you no
end of grief! :o(
Nath.
"tradmusic.com" <[email protected]> wrote in
message
news:[email protected]...
> Hi,
> All of a sudden, tonight, DW8.0.2 will no longer open or
load one of my
> sites, crashing when "Updating Site Cache". The site is
ASP linked to an
> SQL database.
> Checking the file that the cache gets to, I notice that
the problem file
> is within a sub-directory of the site, called "/admin".
Thing is though,
> it's not always the same file, but it IS always a file
within the /admin
> sub-directory.
>
> Within this sub-directory I altered, by hand, the Login
User code and
> Restrict Access to Page code to create and use the
session variable
> MM_Username1 as opposed to the default MM_Username.
> Could this be the reason for the sudden trouble with the
site cache? I
> am puzzled because the site was working fine for a few
weeks now, with
> this sub-directory included, and I didn't create the
MM_Username1 issue
> today either, it has also been working fine for a good
few weeks now.
> I've also not added anything new to the site, that I am
aware of.
>
> When I remove the sub-directory from the site, the
Updating Site Cache
> works fine, so I am 100% sure there is a problem with
the files within
> this sub-directory. How will I know which one though?
>
> I've tried this, as recommended by Adobe, but I still
get a freeze-up when
> re-creating the cache:
>
> 1. Try renaming the Dreamweaver user configuration
folder, so that
> Dreamweaver will automatically generate a new user
configuration folder
> the next time Dreamweaver launches. The Configuration
folder is located
> here: C:\Documents and
Settings\<username>\Application
> Data\Macromedia\Dreamweaver 8\Configuration
>
> 2. Recreate your Dreamweaver user settings in the
registry as follows:
>
> Launch the Registry Editor by clicking the Start button,
choose Run, then
> type "regedit". In the Registry Editor, navigate to this
folder:
> HKEY_CURRENT_USER\Software\Macromedia\Dreamweaver 8
> Rename the "Dreamweaver 8" key to "DreamweaverOLD", so
that Dreamweaver
> will automatically generate a new user settings key the
next time you
> launch it.
>
> 3. Recreate your Dreamweaver site definitions in the
registry as follows.
> The steps below will delete your site definitions in
Dreamweaver.
>
> 4. Launch the Registry Editor by clicking the Start
button, choose Run,
> then type "regedit". In the Registry Editor, navigate to
this folder:
>
> HKEY_CURRENT_USER\Software\Macromedia\Common\8\Sites
>
> Rename the "Sites" key to "SitesOLD", so that
Dreamweaver will
> automatically generate a new Sites key the next time you
launch it.
>
> Any further advice?
> Regards
> nath.
>

Crash when update Dreamweaver 8 to 8.0.1 and 8.0.2 in MAC

Crash when update Dreamweaver 8 to 8.0.1 and 8.0.2 in MAC
PowerMac G5 Quad with Mac OS 10.4.7

You mean the people that that just 'send report to apple' and get on with it I presume? Like me most of the time. Well, as we all know, there are so many variables. The fact is, as far as I'm concerned right now is that Logic 8.0.1 needs some serious work. I can for sure say that I have noticed a snappier response as far as the graphics go. But as for overall performance, it needs an update. I'm trying not to be negative toward your positive thread however, do a search on overloads and, well, they will unfortunately outweigh this thread for sure. It does make me wonder mind how the price of a pro app like Logic tumbled when apple released the Logic studio box. It's £100 cheaper than Cubase 4. It just makes me think garage band ultimate edition right now.

Photoshop CC 2014 crash when opening or creating new files when running with Cintiq 13HD.

I have a problem where Photoshop CC 2014 crashes when trying to open or create a new file while the Photoshop window is being displayed on my Cintiq 13HD.
When Photoshop is being displayed on my main monitor it doesn't crash.
I'm running Windows 7 (64 bit) and have updated my graphics and wacom drivers to their latest versions and Photoshop is completely up to date. (I'm running the 30-day free trial)
Here's the event log of the crash:
Faulting application name: Photoshop.exe, version: 15.2.1.257, time stamp: 0x543dbc5e
Faulting module name: atig6txx.dll, version: 8.14.1.6398, time stamp: 0x54176130
Exception code: 0xc0000005
Fault offset: 0x00000000000122b7
Faulting process id: 0x23dc
Faulting application start time: 0x01d0030b1092334e
Faulting application path: D:\Program Files (x86)\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
Faulting module path: C:\Windows\system32\atig6txx.dll
Report Id: 61680f48-6efe-11e4-aeeb-bc5ff45851ea

As you can already see, your ATI/AMD video card drriver is crashing.
Update the driver from AMD's website to pick up all the bug fixes you are missing.

Indesign CC 2014 crashes when printing to Fiery server

This is to remind Adobe that issues printing to Fiery print servers from Indesign CC 2014 (10.0 or 10.1) on Mac have not been resolved.
A patch has been provided here: InDesign & Illustrator | Crash while printing to Fiery RIP | MacOS --- however, the problem persists after patching. I should note that the fix at that link only pertains to Indesign 10.0. If you download Indesign 2014 from Creative Cloud you would, at this time, receive 10.1. That script will break 10.1 completely. There is no fix for 10.1.
The original thread for this discussion is here: Indesign CC 2014 crashes when printing It's marked 'Answered' and methinks the ongoing conversation there has been over-looked.
I am bumping this topic to keep the conversation fresh. If anyone else has found solutions to printing to Fiery from Indesign 10.x either by updating Fiery directly or with additional scripts or workarounds, please share them here.
I could publish one of my 10.1 crash logs if I could be advised which pieces are most important, or how to post the unabridged without spamming the forum.
That's the constructive bit. Here's my rant...
After speaking to Adobe on the phone, they tell me this isn't resolved yet because it affects only a small subset of people. I called some peers at other agencies across my region and learned they all use Indesign with Fiery servers. We are not an isolated few! (those fortunate individuals I spoke to are still using CS6 -- and I received some jovial ribbing for having my on-going CC subscription.) I have a lot of printing to do on the Fiery now that these projects are finishing, but i'm held up while down-saving these projects to be used in CC (9.x). Its frustrating, its time-consuming, and its simply unacceptable to CC subscribers as we move in to 2015. I urge Adobe to work with EFI to solve this problem once and for all.

This is a user to user forum with "some" Adobe staff participation, report bugs at this link
https://www.adobe.com/cfusion/mmform/index.cfm?name=wishform for feature requests or bugs

PS CC 2014 crashes when I select print

PS CC 2014 crashes when I select print. I have updated all printer drivers as well as the graphics card. Any help is greatly appreciated.

Faulting application name: Photoshop.exe, version: 15.1.0.148, time stamp: 0x53d97a8f
Faulting module name: ntdll.dll, version: 6.3.9600.17114, time stamp: 0x53649e73
Exception code: 0xc0000374
Fault offset: 0x00000000000f87a8
Faulting process id: 0x1528
Faulting application start time: 0x01cfd5c2a647fe43
Faulting application path: C:\Program Files\Adobe\Adobe Photoshop CC 2014\Photoshop.exe
Faulting module path: C:\Windows\SYSTEM32\ntdll.dll
Report Id: ceaf0daf-41b6-11e4-8343-bcee7be34650
Faulting package full name:
Faulting package-relative application ID:

Dreamweaver CS 6 crashes when inserting images

Dreamweaver CS 6 crashes when I try to insert images into a webpage. This makes the app pretty much useless.
It crashes when the alt attributes window pops up.
How do I stop this from happening? I'd like to actually be able to use this VERY EXPENSIVE software.
version 12.0 Build 5842, OS X 10.7.4, 2.8GHz Intel Core 2 Duo, 8GB RAM

n8-zilla wrote:
version 12.0 Build 5842, OS X 10.7.4, 2.8GHz Intel Core 2 Duo, 8GB RAM
I'm not sure what the correct build number is for Dreamweaver 12.0.2, but it looks as though you have 12.0.1. Try getting the 12.0.2 updater from http://www.adobe.com/support/dreamweaver/downloads_updaters.html.

InDesign CC 2014 crashes when creating alternative layouts

InDesign CC 2014 crashes when creating alternative layouts. I successfully created alternative layouts in 3 documents, now I cannot create any at all, it just crashes the program.

I just taught a class using Alternative Layouts in InDesign CC 2014 without crashing.
Start by telling us what kind of computer and operating system you're running. Are you having any other problems in InDesign CC 2014? Have you try restoring your preferences?
Trash, Replace, Reset, or Restore the application Preferences

Indesign crashes when updating incopy content

I'm having a lot of bother with (Mac) Indesign CS6 crashing when updating Incopy content. The problem first appeared after upgrading from CS4 to CS6 on OSX 10.6.8.
I've since upgraded to Mountain Lion (10.8.2) and the problem still persists (with fully updated InDesign 8.01 and Incopy).
Incopy is Windows version if that has any bearing on the issue.
The crash occurs when opening an Indesign document with Incopy content that has been edited. I can open the document if I choose not to update content, but ID will subsequently crash if I choose to manually update the content from the assignments dialog. This doesn't happen with all my documents - perhaps about 1 in 4 with Incopy assignments.
I can place the ICML files in a new Indesign document without incedent. In other words the ICML files don't appear to be corrupt.
Suggestions anyone?
Ian

I got another crash. This time just on trying to launch inDesign.
Below is the report. If anyone can help it would be very appreciated.
Process:
Adobe InDesign CS6 [621]
Path:
/Applications/Adobe InDesign CS6/Adobe InDesign CS6.app/Contents/MacOS/Adobe InDesign CS6
Identifier:
com.adobe.InDesign
Version:
8.0.1.406 (8010)
Code Type:
X86 (Native)
Parent Process: launchd [172]
User ID:
505
Date/Time:
2013-02-14 13:25:08.237 -0500
OS Version:
Mac OS X 10.8.2 (12C60)
Report Version: 10
Interval Since Last Report:
3983 sec
Crashes Since Last Report:
2
Per-App Interval Since Last Report: 2270 sec
Per-App Crashes Since Last Report:   2
Anonymous UUID:
B8865CAA-B81B-3211-BACA-1F5C06EF8F47
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_INSTRUCTION (SIGILL)
Exception Codes: 0x0000000000000001, 0x0000000000000000
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   PublicLib.dylib
0x016c5372 ProtectiveShutdown::~ProtectiveShutdown() + 278
1   PublicLib.dylib
0x016c53f5 ProtectiveShutdown::~ProtectiveShutdown() + 17
2   ObjectModelLib.dylib
0x016082d2 ShuksanInit(IStartupScreen* (*)(), IPlugIn*) + 28162
3   ObjectModelLib.dylib
0x0160691c ShuksanInit(IStartupScreen* (*)(), IPlugIn*) + 21580
4   ObjectModelLib.dylib
0x015f70c3 0x15d6000 + 135363
5   ObjectModelLib.dylib
0x015f5742 0x15d6000 + 128834
6   ObjectModelLib.dylib
0x0160566f ShuksanInit(IStartupScreen* (*)(), IPlugIn*) + 16799
7   ObjectModelLib.dylib
0x016024ba ShuksanInit(IStartupScreen* (*)(), IPlugIn*) + 4074
8   com.adobe.InDesign
0x00001dc2 main + 82
9   com.adobe.InDesign
0x00001d55 start + 53
Thread 1:: Dispatch queue: com.apple.libdispatch-manager
0   libsystem_kernel.dylib
0x942f49ae kevent + 10
1   libdispatch.dylib
0x9a59ec71 _dispatch_mgr_invoke + 993
2   libdispatch.dylib
0x9a59e7a9 _dispatch_mgr_thread + 53
Thread 2:
0   libsystem_kernel.dylib
0x942f38e2 __psynch_cvwait + 10
1   libsystem_c.dylib
0x9374c289 _pthread_cond_wait + 938
2   libsystem_c.dylib
0x9374c512 pthread_cond_timedwait_relative_np + 47
3   com.apple.CoreServices.CarbonCore
0x99e496ad TSWaitOnConditionTimedRelative + 177
4   com.apple.CoreServices.CarbonCore
0x99d95b9b MPWaitOnQueue + 261
5   PMRuntime.dylib
0x005b9581 SetVSizeBaseline(unsigned long) + 1473
6   com.apple.CoreServices.CarbonCore
0x99e1ca7b PrivateMPEntryPoint + 68
7   libsystem_c.dylib
0x93747557 _pthread_start + 344
8   libsystem_c.dylib
0x93731cee thread_start + 34

Indesign crashes when updating incopy assignments!

Hi,
I've read through some forums and it appears others are having this problem.
When I open indesign and it says do you want to update links (referring to the incopy assignements) that need updated.
I click ok, and Indesign crashes!!!!
One thing I read could be the issue....
- anchored objects, (incopy can't handle all the anchored objects)
That is RIDICULOUS if that is the issue. If so, Adobe should have had a disclaimer....don't buy incopy if you plan on having more than text in your document.
There are no error messages that come up, the program just crashes. I'm using Indesign CS5 version 7.
A solution I read was to save the indesign file that keeps crashing when updating the assignments as an .idml file.
I tried this and it appeared to work, but what a joke!
This is very unreliable and has caused a lot of stress.
Anyone else have any solutions or can ADOBE come up with a solution???
Thanks

First question is are you fully patched to 7.0.4? If not, download and install that patch.
Second: Do you have Suitcase Fusion 3 installed? If so, try disabling the autoactivation plugin.
Bob

Itouch crashed when updating ios6 and now won't restore

My itouch crashed when updating to ios6 and now won't restore! Getting an error code (14). Any ideas?

Error 13, 14, 35 and 50 (or -50)
These errors are typically resolved by performing one or more of the steps listed below:
Perform USB isolation troubleshooting, including trying a different USB port directly on the computer. See the advanced steps below for USB troubleshooting.
Put a USB 2.0 hub between the device and the computer.
Try a different USB 30-pin dock-connector cable.
Eliminate third-party security software conflicts.
There may be third-party software installed that modifies your default packet size in Windows by inserting one or more TcpWindowSize entries into your registry. Your default packet size being set incorrectly can cause this error. Contact the manufacturer of the software that installed the packet-size modification for assistance. Or, follow this article by Microsoft: How to reset Internet Protocol (TCP/IP) to reset the packet size back to the default for Windows.
Connect your computer directly to your Internet source, bypassing any routers, hubs, or switches. You may need to restart your computer and modem to get online.
Try to restore from another known-good computer and network.
http://support.apple.com/kb/TS3694#error14

Dreamweaver 5.5 crashes on updating cache

I was going to upload my webpage to the server. Everything went ok untill Dreamweaver tried to update the site cache. Now it keeps on crashing, and I can't open the Dreamweaver without crashing on the startup. So I tried to find the most common problems, and tried to fix this thing. I'm using Windows 7 on my Acer computer. (desktop).
I've tried removing the corrupted cache file, restoring preferences, uninstalling and reinstalling Dreamweaver, checking my website for damaged files and restoring my operating system, but nothing helps. Everything that happens is that I get Dreamweaver to open properly, and then it crashes again on updating the site cache. And then I can't open the Dreamweaver at all. I have to empty the folder I was working on so I can get past the startup, but it doesn't remove the problem.
I have no clue what to do. I really need Dreamweaver for my schoolwork, but I can't find out what's the problem in here.
Any tips? Could somebody help me?

As I have never had the problem that you are describing, I can only make an assumption based upon the experience of others.
Their problem came about when the system clock was changed, for example for daylight saving time as described here http://foundationphp.com/blog/2007/10/29/dreamweaver-crashes-apparently-caused-by-corrupte d-cache-file/

Dreamweaver CS 5.5 crashes when saving Site settings.

Hey,
I'm working on a PHP website. I had it set up to test on a server. When I went to change the Site settings (I wanted to make a new version), Dreamweaver crashed when I saved the new settings. After that, Dreamweaver does not open unless I delete the Configuration file (a solution I found online). Also, any time I restart my computer Dreamweaver does the same thing – crashes on opening. The only thing that was saved that first time it seems is that Dreamweaver removed my server username and password, so I can no longer test the site that was working. Any ideas on how to fix this? Thanks,
-Taylor

Try restoring your preferences: Restore preferences | Dreamweaver CS4, CS5, CS5.5

Dreamweaver CC 2014 crashes every 3 to 5 minutes. Windows 8.1. Uninstalled and reinstalled again today, not any better.

I had the trial version for the last 30 days. I bought the product Sunday and entered the license code. The next day it started crashing every few minutes. I looked up similar reports in this forum and tried what has been recommended. I made sure Verdana and Tahoma fonts are set to "visible". I checked my CSS for open curly parenthesis. I uninstalled Dreamweaver and reinstalled. I rebooted. I cleared the cache.
I have a simple little site for a historical society. There are no extensions installed. I have one CSS file and no other files except for the few HTML pages that make up the site. There are no forms or javascript in use.
Val
I don't see anything broken in my CSS
body {
background-image: url(images/map.jpg);
margin-top: 50px;
margin-bottom: 10px;
#container {
width: 960px;
text-align: center;
margin: auto;
#top {
    height:83px;
    background-image:url(images/Top.jpg);
#middle {
background-image: url(images/Middle-1.jpg);
list-style-type: disc;
list-style-position: inside;
color: #9E221F;
font-family: Cambria, "Hoefler Text", "Liberation Serif", Times, "Times New Roman", serif;
font-size: 1.15em;
line-height: 150%;
#bottom {
height: 83px;
background-image: url(images/Bottom.jpg);
background-position: 0 -417px;
margin-bottom: 10px;
#container_foot {
font-family: Segoe, "Segoe UI", "DejaVu Sans", "Trebuchet MS", Verdana, sans-serif;
font-size: 0.7em;
line-height: 120%;
color: #663300;
border-top: 1px solid #663300;
width: 800px;
#container_site_nav {
font-family: Segoe, "Segoe UI", "DejaVu Sans", "Trebuchet MS", Verdana, sans-serif;
font-size: 0.8em;
line-height: 80%;
color: #663300;
border-top: 0px solid #663300;
border-bottom: 0px solid #663300;
padding-bottom: 8.5px;
width: 800px;
.nav_subtext {
font-family: Segoe, "Segoe UI", "DejaVu Sans", "Trebuchet MS", Verdana, sans-serif;
font-size: 0.86em;
line-height: 70%;
font-weight: 600;
margin-top: 0px;
.nav_text {
font-family: Segoe, "Segoe UI", "DejaVu Sans", "Trebuchet MS", Verdana, sans-serif;
font-size: 1.15em;
line-height: 120%;
    font-weight: 600;
margin-top: 0px;
    margin-bottom: 0px;
a:link {
color: #131266;
text-decoration: none;
a:visited {
text-decoration: none;
color: #131266;
a:hover {
text-decoration: underline;
a:active {
text-decoration: none;
h1 {
font-weight: normal;
h2 {
font-size: 1.3em;
line-height: 100%;
font-weight: 550;
padding-top: 22px;
padding-bottom: 6px;
color: #9E221F;
h3 {
font-size: 1.1em;
line-height: 170%;
margin-top: 0px;
margin-bottom: 0px;
color: #131266;
h4 {
font-size: 1.05em;
font-family: Cambria, "Hoefler Text", "Liberation Serif", Times, "Times New Roman", serif;
line-height: 100%;
margin-top: 22px;
margin-bottom: 2px;
color: #131266;
h5 {
font-size: 1.2em;
line-height: 100%;
margin-top: 32px;
margin-bottom: 12px;
/color: #131266;
.dropcap {
    float:left;
    color: #131266;
    font-size:82px;
    line-height:70px;
    padding-right:15px;
    padding-top:2px;
    font-family:Constantia;
    /text-shadow:1px 1px 1px #444;
p2 {
font-size: 0.85em;
font-family: Cambria, "Hoefler Text", "Liberation Serif", Times, "Times New Roman", serif;
line-height: small;
color: #9E221F;
margin-top: 0px;
margin-bottom: 0px;
font-style: oblique
p3 {
font-size: 0.85em;
font-family: Segoe, "Segoe UI", "DejaVu Sans", "Trebuchet MS", Verdana, sans-serif;
line-height: 80%;
color: #9E221F;
font-weight:600;
word-spacing:-1px;
margin-top: 0px;
margin-bottom: 0px;
font-style: oblique;
p4 {
font-size: 0.85em;
font-family: Segoe, "Segoe UI", "DejaVu Sans", "Trebuchet MS", Verdana, sans-serif;
line-height: 100%;
color: #9E221F;
font-weight:600;
margin-top: 0px;
margin-bottom: 0px;
font-style: oblique

OK I will remove the Ps. The crashes started before I created those, but I will remove them. Here is one of the crash reports.
Log Name:      Application
Source:        Application Error
Date:          11/18/2014 12:15:27 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Muffin
Description:
Faulting application name: Dreamweaver.exe, version: 15.0.0.6947, time stamp: 0x5423eb8a
Faulting module name: Dreamweaver.exe, version: 15.0.0.6947, time stamp: 0x5423eb8a
Exception code: 0xc0000005
Fault offset: 0x00000000004fa27e
Faulting process id: 0x2324
Faulting application start time: 0x01d00352ce09bc96
Faulting application path: C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe
Faulting module path: C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe
Report Id: 7cf25798-6f46-11e4-8288-a0886943af3e
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-11-18T17:15:27.000000000Z" />
    <EventRecordID>123445</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Muffin</Computer>
    <Security />
</System>
<EventData>
    <Data>Dreamweaver.exe</Data>
    <Data>15.0.0.6947</Data>
    <Data>5423eb8a</Data>
    <Data>Dreamweaver.exe</Data>
    <Data>15.0.0.6947</Data>
    <Data>5423eb8a</Data>
    <Data>c0000005</Data>
    <Data>00000000004fa27e</Data>
    <Data>2324</Data>
    <Data>01d00352ce09bc96</Data>
    <Data>C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe</Data>
    <Data>C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe</Data>
    <Data>7cf25798-6f46-11e4-8288-a0886943af3e</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>
This is what the DETAILS tab on the error report says:
Log Name:      Application
Source:        Application Error
Date:          11/18/2014 12:15:27 PM
Event ID:      1000
Task Category: (100)
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      Muffin
Description:
Faulting application name: Dreamweaver.exe, version: 15.0.0.6947, time stamp: 0x5423eb8a
Faulting module name: Dreamweaver.exe, version: 15.0.0.6947, time stamp: 0x5423eb8a
Exception code: 0xc0000005
Fault offset: 0x00000000004fa27e
Faulting process id: 0x2324
Faulting application start time: 0x01d00352ce09bc96
Faulting application path: C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe
Faulting module path: C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe
Report Id: 7cf25798-6f46-11e4-8288-a0886943af3e
Faulting package full name:
Faulting package-relative application ID:
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Level>2</Level>
    <Task>100</Task>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2014-11-18T17:15:27.000000000Z" />
    <EventRecordID>123445</EventRecordID>
    <Channel>Application</Channel>
    <Computer>Muffin</Computer>
    <Security />
</System>
<EventData>
    <Data>Dreamweaver.exe</Data>
    <Data>15.0.0.6947</Data>
    <Data>5423eb8a</Data>
    <Data>Dreamweaver.exe</Data>
    <Data>15.0.0.6947</Data>
    <Data>5423eb8a</Data>
    <Data>c0000005</Data>
    <Data>00000000004fa27e</Data>
    <Data>2324</Data>
    <Data>01d00352ce09bc96</Data>
    <Data>C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe</Data>
    <Data>C:\Program Files\Adobe\Adobe Dreamweaver CC 2014.1\Dreamweaver.exe</Data>
    <Data>7cf25798-6f46-11e4-8288-a0886943af3e</Data>
    <Data>
    </Data>
    <Data>
    </Data>
</EventData>
</Event>

Dreamweaver CC 2014 won't save site server passwords

Since updating to Dreamweaver CC 2014, it asks for a site server password every time I try to upload files. Even though I toggle the "Save" checkbox on, it will remember the passwords as long as I keep DW running. If I quit DW, it asks for the password again when I try to connect to a site's server. I'm really hoping there's a fix other than recreating all of my site FTP connection info. I do multiple sites.

Sounds like a permissions problem. Try this:
Rename the Preferences folder on your computer:
On Mac : ~/Library/Application support/Adobe
On Windows7 : \Users\<user name>\AppData\Roaming\Adobe
Rename “Dreamweaver CC2014.1” to “Dreamweaver CC2014.1_old”
Re launch Dreamweaver.

Dreamweaver CC 2014 crashes when updating site cache

Similar Messages

Maybe you are looking for