DW CC 2017 Now Crashes?

[jeffery wright]

I've been using this for weeks on my new Win10 machine, suddenly today it crashes every time I save html files I am working on.

Again, I have tight deadlines and an Adobe product I am relying on is letting me down, what could the problem be?

Killing these tasks does nothing:

This never seems to happen with notepad...

I have had to create a new html file, open my existing file in notepad, copy the code and paste it into the new file in DW, then save it, over-writing my original, which works a few times but it's a roulette... my next save might be the one that crashes DW!

Is anyone else having this issue? Thanks!

[Jon Fritz]

Have you tried any of the standard troubleshooting steps like clearing the program cache or restoring preferences yet?

Clear Program Cache - https://forums.adobe.com/thread/494811

Rename Personal Configuration Folder - https://forums.adobe.com/thread/494812

Restore Preferences (CS4-CS6) - https://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver-cs4-cs5.html

Restore Preferences CC Versions - https://helpx.adobe.com/dreamweaver/kb/restore-preferences-dreamweaver.html

[jeffery wright]

Thanks, but why would I do any of that? I just want to get work done, why does Adobe expect their customers to become software debuggers and have to tweak all these system parameters?

I use DW to create web sites for instance, not so I can have an excuse to fiddle around with system configurations to trick their product into working.

All I want to do is my job, not chase down wild geese... I did delete the cache to no avail, if this is such a common issue with Adobe products, why don't they include a menu entry in their software interface to do that instead of making their customers hunt down obscure forum solutions so we then must dig through our machines to manually perform these tasks?

Now my CC is unable to connect to Adobe servers... are they down? Could this be the cause of DW crashing every time I open a simple HTML file? I hope not, because that would be insane.

Thanks, again!

[Jon Fritz]

You're preaching to the choir here.

I'm not an Adobe employee and don't know their motives for anything they do with DW. Some of these troubleshooting steps go back to the Macromedia days as the software has always seemed prone to corruptions in the cache and preferences files.

If you're just here to vent, vent away this is my final response to this thread. If you want more ideas, let the contributors here know. They'll no doubt offer things like "validate your code" or "verify you don't have Lavasoft's Web Companion installed" and "as a last resort, run Adobe's Cleaner Tool during a reinstall".

If you want to talk directly to Adobe, you're going to have to contact their Customer Care center and, hopefully, get a technician on their Live Chat.

For what it's worth, I have no connectivity issue with the CC Desktop App, so that's going to be localized to your machine, network or ISP it appears.

Good luck.

[jeffery wright]

Not vent, I want to know how to fix this issue.

This issue has plagued me all morning, and now has evaporated as mysteriously as it appeared, everything is working fine now and I do not know why...

Is it a Win10 issue? And Adobe issue? My other programs were working just fine; browsers, Lotus Notes, Skype etc...

I would like to know what happened and even more, what made everything work again?

Thanks for weighing in, if it occurs again, I will document it here.

[Nancy OShea]

<Thanks, but why would I do any of that?>

As responsible computer users, that's the protocol we use when we encounter problems.  

Incidentally. have you scanned your system for viruses and spyware lately?

Nancy

[jeffery wright]

My machine is a weapons grade HP Z840, I work for a very large government contractor and our machines are constantly monitored for intrusions and suspicious software activity, this machine is also brand new, in addition to the CC suite, very few other programs have been installed.

I would say as a responsible software vendor, things considered "standard troubleshooting steps" should be built into the product, as opposed to turning multimedia production people into computer engineers via frenzied desperation.

So far no sign of any trouble, I am hoping it stays that way. Software and computers sometimes eerily sense a tight deadline looming and do things to make life a little more interesting, like not working as expected. I am hoping someone else who experiences this problem and discovers the cause and solution might find this post and share it with us.

Again, thanks everyone for taking a shot at this, I really do appreciate it.

[Preran]

I am glad that you are back to working normally again. I am not an Engineer, and cannot speak to your wish of having a wizard run through the troubleshooting process. You can make your request heard using Adobe Dreamweaver CC: Feature Ideas or by participating in the Dreamweaver prerelease forum. If you are interested in participating, send me your Adobe ID, location, and phone number over a private message.

We document most issues that we have seen on the forum. DIY troubleshooting kit for Dreamweaver Many users prefer to do their troubleshooting on their own before they reach out to the support center.

On Windows 10, we have seen instances of DW crashing when Web Companion is installed because of an issue with the Lavasoft DLL (my understanding at least). Uninstalling Web Companion has helped avoid these crashes.

Thanks,

Preran

[jeffery wright]

If only it was working properly, just when I think everything is back to normal and just want to complete a new task...

I am still having this issue: When I open a file I created in Dreamweaver CC 2017, it crashes/freezes Dreamweaver CC 2017.

If I copy the HTML in the file and place it into a New file in Dreamweaver CC 2017 and save it, everything is just fine... until I close it and try to open it again. Really, no one else is having this problem? See for yourself in this handy video I made of me trying to get some work done today:

I have no Lavasoft products installed on this computer.

[Webmation]

Make sure your anti-virus and firewall settings aren't blocking the program and traffic. Also, if you have a mapped network drive try using the actually network address instead of the mapped directory letter. CC2017 was completely unusable for me until I made that change - It would take 20-30 minutes to open a file and then lock when trying to edit. I could see the same issues when trying to save.

Example:

S:/Websites/ClientDirectory

Use the full network path:

//DriveDeviceName/Clients/Websites/ClientDirectory

[jeffery wright]

Thanks for that, it does sound interesting but I wonder how one would configure the Windows Explorer to use Network Paths instead?

I would also wonder why Adobe's product would not be able to cope with such a common system setup; a feature of most professional workflow environments - mapped network drives? That would be concerning.

Especially since it hasn't been an issue in previous versions. I am sure that can't be the case.

Could it?

[ALsp]

You won't get an answer. I've had the same issue, along with startup and shutdown issues since I began testing Dreamweaver CC versions. I've spent hours on the phone with Adobe support, and they are totally clueless. The only logical conclusion, based on my particular situation, is my primary defined site has 70,000 files. I dare say that none of the "experts" on this list have that large a site. If I work in a test site, with a couple of hundred files, everything works fine. If I log into my computer with the hidden admin account, then things are better... but only marginally. This leads me to believe that part of the problem is sloppy programming (imagine that) with regard to things Adobe is doing that require full permissions, to do things that Adobe did not do in CS6 (and under). Why? Because I have CS6 installed, along with CC 2015, on two different Windows 10 machines, with the same result:

CS6 has no problem saving files, starting up, or shutting down on either system, while CC 2015 is nearly crippled.

It would be great if you got an answer from Adobe here, but this is a weird forum. On Adobe's phone system, it claims this is a support forum manned by Adobe employees and a "vibrant" community of users, which would lead someone of average intelligence to assume this is an official support forum. But the civilian community experts here habitually claim otherwise -- that this is not an official support forum, that it's strictly a user-to-user community with no accountabilities for providing answers to all questions.

Perhaps you'll get lucky.

If not, you can use your Creative Cloud app to install CS6. Not a big deal as CC 2017 has removed far more valuable features than they've added.

[pziecina]

ALsp  wrote

The only logical conclusion, based on my particular situation, is my primary defined site has 70,000 files. I dare say that none of the "experts" on this list have that large a site.

You want to bet on that AL

My recommendation would be to use Visual Studio Pro, which is not what anyone wants to hear, as I don't know of a solution to the problem if someone is using Dw.

[ALsp]

Adobe claims in their voice mail system that this is a support forum. It's a bit unusual to recommend another company's product

CS6 works great.

[pziecina]

ALsp  wrote

CS6 works great.

If the OP has a copy, then yes, (recommended) though I am no longer happy developing in JS with CS6 personally

[ALsp]

We use Aptana for script. We would never use Dreamweaver CC 2017 or Brackets. In our opinion, they are horrible. We write CSS manually, so Dreamweaver is our tool for editing content and automating various tasks with our extensions. .

We're quite happy with CS6, as are many of our customers.

[pziecina]

ALsp  wrote

We would never use Dreamweaver CC 2017 or Brackets. In our opinion, they are horrible.

They do appeal to a limited audience, who are mainly beginners or are happy building sites the Dw way, (sass/bootstrap).

[ALsp]

pziecina  wrote

ALsp   wrote

CS6 works great.

If the OP has a copy, then yes, (recommended) though I am no longer happy developing in JS with CS6 personally

CS6 is available via the Creative Cloud, no? I have an original license, but it doesn't reference it in the CC app. I also have it running on 3 different computers. One installed via the original DVD and the other 2 from a single CC license.

[pziecina]

ALsp  wrote

Adobe claims in their voice mail system that this is a support forum. It's a bit unusual to recommend another company's product

Just thought I would reply to this, after thinking about it.

My thoughts are that my responsibility lies with helping the user when I can, not with being 'loyal' to Adobe. If I don't think Dw is the program that should or could be used, then I will say so, (this goes for any product, not just Adobe's).

I know that one or two may not agree with me doing so, but I cannot recommend Dw if I think it does not match the users requirements, and if I think another program would be better, so be it. Trouble is that is happening more often

I don't expect an Adobe employee to do, or agree with this, as their further employment would then I think be in doubt.

[jeffery wright]

Bloody hell... a new way to crash?

I am editing simple, basic html files... or trying to.

[Nancy OShea]

Restore Preferences

Unusual behavior in Dreamweaver? Try restoring preferences.

[Preran]

Hi Jeffery,

If Nancy's solution did not help, can you let us know if you are trying to access files from a remote drive? That is one of the primary reasons for Dreamweaver crashes when opening files. If you are OK with using the sledgehammer method, try uninstalling the software using the CC cleaner, and reinstalling the software (Use the Creative Cloud Cleaner Tool to solve installation problems )

If you still need help, I suggest getting in touch with customer care Contact Customer Care for further investigation.

Thanks,

Preran

[Nancy OShea]

Open your Windows Event Viewer.  Which faulting module is causing DW to crash?

As Preran said earlier, Lavasoft is a known conflict with several Adobe products including Photoshop & After Effects.  Removing Lavasoft & related DLL files fixes the problem.

Photoshop crashes with Lavasoft Chrome extension installed

Nancy

[jeffery wright]

Thanks!

I have no Lavasoft products installed, I am not in the business of rooting through program directories, searching for and opening tools like Windows Event Viewer (?), I simply wish to design and develop web pages, which is what I am paid for and the Adobe Dreamweaver brand promises to facilitate, yet delivers only hindrance after baffling hindrance.

All my web pages are simple; not very complex... yet bring Dreamweaver to its knees just by tasking the program with opening the file for editing, waiting an hour so far:

Good thing I don't have any deadlines I need to meet. Oh, wait. I do, lots of them.

Hey look, another weekly update to DWCC17 to download and install instead of getting work done, again!

I better close the program before installing, which I did and somehow I am greeted with this un-helpful error:

DW is not running, pressing Continue freezes the CC program... this just gets better and better.

So even though I force closed the crashing DW program, it was apparently still running processes for some reason, I shut them down manually and installed the new, amazing update that hopefully feature the cutting edge ability to open html files to edit and...

And it appears they did in fact thoughtfully include the ability to open up html files without crashing, just like the good old days.

So, it appears that after all this, I can finally get to the work I originally intended to do in the first place all is good!

At least for now... 

Thanks for all your help, everyone!

[Preran]

Thank you for letting us know that Dreamweaver is now working for you. I apologize for the frustration you faced previously.

Do let us know if you run into issues again, and we will do our best to help you.

Meanwhile, happy designing and happy weekend.

Thanks,

Preran