Dreamweaver CS5 will not open

[freicook]

I just downloaded Adobe CS5 Design Premium and installed. Every application opens without problem except Dreamweaver which will not open at all. I tried installing again and that didn't work. I even tried removing all of my preference files, old Application Support files and even Library Application Support files. Uninstalled CS4 and CS5 and installed a fresh copy of CS5.

Dreamweaver CS5 will not open. It gets to just before the splash screen and stops. It's not hanging either, I can click the dock and quit the app without a force quit. It appears that the open sequence is missing something.

Mac OS X 10.6.3

[Guest]

Can you please talk me through the permission thing that you did to get t to work the third time?

[Örongodis]

I did what Nohl Lyons and other suggested:

1. In Finder, navigate to <your username>:Library:Application Support:Adobe:Dreamweaver CS5.
2. With the Dreamweaver CS5 folder selected, choose File > Get Info (Cmd+I).
3. If necessary, expand Sharing and Permissions.
4. Click the lock icon at the bottom right of the panel to make changes. Enter your Mac password when prompted.
   
5. Click the plus button at the bottom left of the panel, select your name in the dialog box that opens, and click Select.
6. Change the privilege for your name to Read & Write.
7. Click the lock icon to lock the Sharing and Permissions section.

Additionally, I selected "Use for included objects" (or whatever it's called on an English system).

[Grimm_nl]

yep, did that too; no joy.

even de-installed and re-installed dreamweaver, to no effect. then I de- and re-installed the entire CS5 suite (took me an hour), again to no effect.

I can only get DW working again when I create another account and log in under that one.

this can NOT be right guys!..

[Grimm_nl]

I got a brand new Macbook pro on tuesday (my first Mac!), already had the CS5 for Mac. Immediately installed CS5 web premium when I got it home, and it worked like a charm for 2 days.. this afternoon DW CS5 quit on me, showing the exact symptoms described here (no splash screen, only "dreamweaver" top left).

- I'm not running file vault

- I tried to set the permissions as described

- I downloaded and installed the html5 pack

- I restarted the system

no joy whatsoever...

WHY IS ADOBE NOT FIXING THIS???

sorry for shouting, but I'm frustrated.. DW is my main working tool, and now I can't use it. going back to CS4 means going back to Windows, as I only have CS4/Win. not doing that in THIS lifetime.

Adobe, do what we all pay you for and fix this TODAY! thanks.

[Guest]

Right, just spent ANOTHER few hours trying to sort it and still DOESN'T launch!!! My wife is nearly as angry at Adobe as I am!!

I'm going to start charging Adobe my time at this rate!!!!! Why is nobody from Adobe replying on this thread? When can we expect a patch / update!? This problem is not solved, so someone better be looking into it as there are a number of VERY unhappy clients here!!!

[Grimm_nl]

Could become expensive for them, as I am already tracking time spent on this nonsense.. as long as the Adobe guys & gals are too lazy/disinterested/stupid to fix this, charging our time is a viable option.

3 years ago I had trouble installing CS3, eventually found the solution and gave it to:... Adobe

[Guest]

Yeah this is a real bummer, I was looking forward to trying out the new html5 extension pack.

[Guest]

Strange it does load on a standard account I just created.

[dlandfan1]

I have done the same thing.  I deleted the new install, first just dreamweaver, then the whole suite!  then I created a new account, re-downloaded just dreamweaver, installed and still didn't work. 

Adobe told me to go into safe mode and try to open the program.  LOL  like that's gonna work! 

[Grimm_nl]

just received a Dreamweaver update through the adobe application manager, but does it solve anything? nooooooooo..... Is it just me, or am I dealing with amateurs here?

[Guest]

Do you guys also have CS4 installed?

[Nevegal]

cayennecode wrote:

Do you guys also have CS4 installed?

Yes, I also have CS4 installed along side of CS5.

[Guest]

I also have CS4 installed at the moment, but have tried with it installed, without it installed, everything

....

[creacog_-]

+1, wishform filled - IMO this is a serious backward step for Dw.

I consider use of FileVault a best practice for MacBooks at least - those project files need protection should the device gets lost or stolen.

And sorry, but I am a little disappointed with the dismissive nature of responses from the CPs on this thread and lack of any engagement so far from Adobe.

[David_Powers]

creacog - wrote:

I am a little disappointed with the dismissive nature of responses from the CPs on this thread and lack of any engagement so far from Adobe.

Adobe Community Professionals tend to have expertise in how to use one or more Adobe programs. They are not software engineers with an intimate knowledge of how Adobe installation programs interact with different configurations of operating systems.

I fully sympathize with people who are having installation problems, but I don't have the technical expertise to resolve the issue. What I can tell you is that the Dreamweaver engineers have been informed by myself and at least one other ACP. But as far as I know, it's not so much a Dreamweaver issue as a problem with the installer. The installer is a separate program created by a separate team.

I can also tell you that a high proportion of beta testers were using Mac OS X, and testing involved installing and uninstalling new builds of Dreamweaver several times a month. Occasionally, testers did have installation problems. These were invariably caused by incompatible components from a previous build that had not been removed successfully. Uninstalling and then running the CS5 Clean script before reinstalling always fixed the problem.

I don't know what proportion of beta testers were using FileVault, if any, but it doesn't seem to be directly related, because some people are reporting problems even though they don't use FileVault. Nailing the cause of software failure is notoriously difficult. Unless you can identify steps to reproduce the problem 100% of the time, it means there are unknown factors affecting the situation. Until those factors can be identified, it's impossible to offer a solution.

[creacog_-]

@David: thanks for the reply. You time is appreciated, and there is certainly no expectation on my part for you to personally resolve an issue that is as far beyond your control as it is ours. I was just concerned that your previous replies did not seem to appreciate how important/critical FileVault is for those who are using it.

There seems to be a mix of problems. From this thread, it appears a core problem of permissions and some process required by Dw not having the right permissions to access the user's Application Support directory. Consistently, if your FileVault is on, there's nothing you can do other than turn it off at the moment to get Dw CS5 working. Which is undesire-able/impossible in the use case I mentioned previously. Additionally some people are clearly experiencing the same symptoms without FileVault in use.

I have Dw CS5 running fine* on my Mac Pro. And the FileVault problem on my MacBook Pro - just loaded with files for a week away from the office.

* Very occasionally Dw CS5 shows this symptom on my Mac Pro (no FileVault). But force-quit and re-launch clears it.

So there's one or more bugs at play. My main concern and hope is to find some indication that Adobe are working to fix it, and that inability to use FileVault does not become a permanent feature or precedent for the rest of CS.

thanks

[craigalyn]

The CPs & Adobe's response reminds me of  BP's response to the Deepwater Horizon disaster. Blame everyone else and don't take resposibilty for their own failings.

And why isn't someone from Adobe monitoring these forums These forums and others are where the problems are discussed and where praise would be issued by their users  to Adobe if they knew someone was listening. After sale service or lack thereof is what can bring down a company or make the company a hero with it's customers.

[David_Powers]

craigalyn wrote:

The CPs & Adobe's response reminds me of  BP's response to the Deepwater Horizon disaster. Blame everyone else and don't take resposibilty for their own failings.

Why do you think that I or any other community professional should take responsibility for an installation failure? Perhaps you're under the impression that ACP = Adobe employee. Community professionals are not Adobe employees. They are unpaid volunteers with expertise in one or more Adobe programs. I can help you with coding problems and understanding how to use Dreamweaver, but I'm not part of Adobe Technical or Customer Support.

It's also a bit rich to say that Adobe is blaming everyone else. As far as I can tell, there hasn't been an official Adobe response.

And why isn't someone from Adobe monitoring these forums

I agree that it would be helpful if Adobe did so. However, there are about 100 forums. Monitoring the posts in all of them would be a big undertaking.

The official forum monitored by Adobe staff is http://forums.adobe.com/community/general/adobedotcom_feedback.

[Grimm_nl]

This morning I posted a link to this discussion in the forum you mentioned, so now we wait (and in the meantime use Coda instead (and maybe stick with it)).

[Grimm_nl]

YAY! solved it! that is to say, I solved my own issue, so maybe it will solve (some of) yours.

it's like this:

- quit Dreamweaver.

- In Finder, go to: Macintosh hd/users/<your username>/library/application support/adobe/dreamweaver cs5/en-US/

- here you will find the folder "configuration". rename it to configuration-old and restart Dreamweaver

tadaaaa...

of course, you will have to configure DW all over again..

but..

[dmntx]

this fixed it!!!!

it's like this:

- quit Dreamweaver.

- In Finder, go to: Macintosh hd/users/<your username>/library/application support/adobe/dreamweaver cs5/en-US/

- here you will find the folder "configuration". rename it to configuration-old and restart Dreamweaver

[PatriceAnn]

renaming configuation file finally did it for me...

[meeps]

I'll be away for the week of the 22-27th but will respond to your e-mail as soon as I return.

Garry

[PatriceAnn]

This happened again today. So frustrating. Fix was to rename config file.

Why isn't a patch out yet for this?

[AlexBerryLibrary]

I've been through all of the suggested permission fixes and added the patch. DWCS5 still not working on my OS 10.6.4 machine.