DW CC 2014 Server Busy

[Hedge]

Every time I launch DW CC 2014 on my Windows 8.1 machine I keep getting a Server Busy message where I can switch to the application or try again. Eventually it goes away but it really delays the start up time on my DW application. I have added DW to the trusted applications list for Kaspersky so I don't think that is the issue. Never had this problem with the previous version of DW CC. Anybody else running into this?

[TwoSuits]

Well, if you are certain that the SATA drive or it's controllers are not going offline for any reason then your problem must be different to mine. Seems strange that your setup is so similar to insitemotions and my own though.

[bluehaus]

Hey TwoSuits (or anyone else who has solved this issue)

Thanks for your reply and solution that sounds like it's working for you. I'm interested in trying this out however I'm a little unsure where/how to check when my external drives are sleeping or not? Would you be able to shed a little more light on this for me please?

Also, please excuse my ignorance if this is a blatantly obvious thing that I'm missing.

Thanks in advance

(PRAYING there could be some light at the end of this tunnel)

[insitemotion]

Click on the Start button in your taskbar and type "sleep" (without quotation marks) in the search programs and files box. Choose "Change when the computer sleeps". That will bring up a control panel window. Click on "Change advanced power settings". Toggle Hard disk and type Never or click the down arrow to the very bottom and it will be the option below 1 minute. Click Apply and OK. Click Save changes. That should do it. This solution worked for me.

[TwoSuits]

Exactly as insitemotion said for any internal drives.

External drives, card readers and possibly even network drives (maybe even more) becoming unavailable for any reason may also be causing this issue. There could be a large number of reasons for any of those being temporarily inaccessible so I would probably start by removing any non essential connected devices in the short term. If this resolves the issue you can then reinstate them one by one to find out which is the offender.

Sorry I cannot be more specific.

[bluehaus]

Thanks insitemotion! I was more worried about the external, but still went through the steps to turn off my internals sleeping after 20mins. *fingers crossed

Also thanks for the additional information TwoSuits! I keep all my client info on an external drive so every time I need to launch DW it'll be reading from those drives. Not plausible for me to knock them off and turn them on one by one to see if that's the error. Well more impractical than anything. And really, I shouldn't have to for any program especially DW. Completely understand where you're coming from though. And I still find it sad that it's a community that's solving these issues instead of Adobe's brains. Perhaps we are all the testing group. 😕

[bookoflife_org]

I cannot on many days too. It sux paying for something, hug monthly money and nothing works consistently. I liked my old MS FrontPage, it was stable and consistent  - they just shut down support.- extensions.  Cannot even get support or turn off sync that is hijacking all my personal files. Is Abose the NSA or something?

[ben-erwin]

Well, I have additional hard drives.
Even If that is the case, I'm not going to change my settings.
Dreamweaver should not be checking the status of my hard drives or having a prompt pop up.

PLEASE
FIX
THIS
NOW

[TwoSuits]

Almost 24 hours now and not a single error message, whereas normally I would have had it at least once and hour!! I am so glad to be rid of this problem as it has seriously affected my productivity.

I agree it needs fixing properly but at least I have a workaround until it gets resolved. I would hope that now they are clear what the problem is it will be fixed in the next update (although I won't hold my breath!).

[insitemotion]

Yes, I haven't seen a single error either after I changed my hard drive sleep settings. I also agree this issue needs to be fixed by Adobe.

[subhadeep_banerjee]

Thanks for sharing your solutions TwoSuits.

We've taken note of it & will surely help us investigate further. I'll post back as soon as I have an update.

Thanks,

Subhadeep

[TwoSuits]

Just a quick update to this in order to confirm that, for me, the problem is 100% fixed by the workaround. Now I just hope they fix the code so I can let power management power down my drives when appropriate.

[Hedge]

For me the problem is still not fixed. I have no additonal drives that are spinning down. DW still does the Switch To and Retry thing and then still crashes about half the time when I launch it or come back to it after being AFK for a bit.

[bluehaus]

Unfortunately, I'm still in the same boat with Hedge . Thanks for your update though TwoSuits and glad it's all fixed for you now. Hopefully we'll be next!

[k_randolph]

If they were actually serious about fixing this, they would look at the code and find each of the areas that make a call for the cloud service to validate the license.  In a special build/patch, in each place the code exists in, they would add an unique value. Then, in the object that displays the error message we are reporting, they would add a bit of code that outputs the value.  Then, in a pure stroke of genius, they would give this code to a few people that get the error reliably.  In short order, the users report what unique value showed up in the error message.  Low and behold, they would then know EXACTLY which call to the cloud service is triggering the issue.  Then they could compare that bit of code with how it is done in ANY of their other applications to see how it should be done (since this only occurs with Dreamweaver, it seems obvious that the Dreamweaver team messed up).

Yes, this would require some people to actually do something that doesn't fit their particular Agile or Waterfall schedule, but so what?  They could fit it in IF THEY CARED.

It seems pretty obvious that they don't.

Lets put it this way.  How about we create a single post demanding that they respond with information that tells us that they have X number of engineers working on the issue, what they are doing to resolve the issue and what their expected time line is for a resolution and then we all vote up the post to show how much we want this resolved?  Then share links to the post with others we suspect might be having the issue. . .

[cbrinks]

Yes, this is a known issue with sidebyside and creative cloud.  Here's the error you will likely find in your Event Viewer.

Activation context generation failed for "c:\program files (x86)\Adobe\adobe creative cloud\Utils\Creative Cloud Uninstaller.exe".Error in manifest or policy file "" on line . A component version required by the application conflicts with another component version already active. Conflicting components are:. Component 1: C:\Windows\WinSxS\manifests\x86_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_41e6975e2bd6f2b2.manifest. Component 2: C:\Windows\WinSxS\manifests\amd64_microsoft.windows.common-controls_6595b64144ccf1df_6.0.7601.17514_none_fa396087175ac9ac.manifest.

And the culprit for Adobe to look at (in my case, i've seen other adobe apps crash it) ..

c:\program files (x86)\Adobe\adobe creative cloud\Utils\Creative Cloud Uninstaller.exe

If you guys think this x month response is slow, here's a thread from sept, 2013 regarding the same thing.  Very little has changed.  I suspect both of the proposed solutions are right - the application checks status of hd and cloud connectivity from time to time and the error isn't handled properly and so the user experience is rudely interrupted.  The response time on this is atrocious.  We deserve a press release apology and a free box of ho-hos at this point.

https://forums.adobe.com/thread/1304813

My suggestion: coda.

[ben-erwin]

At this point, I'm pretty disgusted at the neglect of this issue and I'm prepared to take this to my contacts Adobe over the heads of the techs that have been handling/neglecting this issue.
Looking at this thread posted by cbrinks really hits home. https://forums.adobe.com/thread/1304813 <- is outrageous.

I fell like our (we the users on the thread) ruminating about this is not helping and there is no real effort being made to fix this.
I feel like the team working on this is wasting a lot of our time and not prioritizing a real solution.
I reject any requirement for effort on our part to spend our logging this. Dreamweaver's QA team is neither delivering Quality, nor Assurance.
I reject the idea that there are any settings that need to be changed or uninstalled, or rolled back on our machines in order to make this issue go away.
The problem is something that Dreamweaver is responsible to fix, and that we the users should only have to run an update and that's it.

If this speaks for you and you have my back, please like this post and I will include your name when I reach out to Adobe management about the pathetic response to this obviously widespread and massively frustrating problem.

[TwoSuits]

Hi Ben

I am happy to add my voice to yours on this as I agree wholeheartedly with everything you say in your above post. The fact that I have managed to resolve my problem, entirely through my own efforts, does not alter the fact that I should not have had to do that. Many others are still suffering with this issue, as well as numerous other problems, which should have been resolved long ago.

I am no stranger to software development and I am not naive enough to believe that applications should have no bugs whatsoever, but this problem (and many of the others that appear regularly on these forums) is taking to long to resolve. Especially considering that, for many, it significantly degrades productivity.

I sympathise with the developers working on DW to some extent, as I am sure the code base must be a lumbering behemoth with a huge number of legacy issues. There are probably large sections that date back to the Macromedia days. Since the programs inception there have been massive changes to web development and, by and large, DW has done a great job of keeping up with those changes. Unfortunately this has largely been done by simply patching existing modules to add new features. This is fine in the short term but causes problems in the long term as it leads to inefficient, clunky code that is incredibly difficult to diagnose as all the different sections and patches (and patches on patches) affect each other in unforeseen ways. IMHO DW is long overdue for a complete rewrite, but I now think that is highly unlikely to happen. I would be highly surprised if the Edge group of applications are not Adobes vision of web developments future, with DW eventually retired or aimed more toward the hobbyist. I am not saying this will happen for a few years/versions yet but I can see it heading that way. Nor am I saying that this is a bad thing as often multiple specialised tools are better than one large 'jack of all trades'. It certainly makes the tools easier to update and keep in line with changes in technology. Unfortunately, at the moment, the 'Next Generation' is not ready and the 'Incumbent King' is starting to look quite jaded.

With all that said, Adobe still owes a quality working product to it's paying customers and at the moment, for many, it does not seem to be delivering that with DW.

These are just my thoughts on the matter. Sorry for the tl;dr post. I did not intend to post as much but once I got going I found the process quite cathartic.

[ben-erwin]

Thanks Two Suits,
You're absolutely right. The politics of what you speak of with Edge Suite vs. Macromedia legacy was thick at Adobe MAX 13.
The Dreamweaver team are great guys and they care about the product.

I have given up neither on my loyalty to Dreamweaver nor Creative Cloud, but at $50/month and daily Dreamweaver use gives me the right when not a Dreamweaver core bug, but the damn activation component that only afflicts Dreamweaver and it doesn't have to be that way, and it's only on Windows.

[BeggarSo]

I'm on Windows 8.1 and get this Server Busy issue as well.

I guess you are right and the writing is on the wall for DW. It is amazing how far it has come, but it seems like it's going the way of the dinosaurs now.

I have since swapped to PhpStorm and it's improved my workflow in many ways (it has it's own set of issues but they are pretty quick to sort them out usually).  The one thing I really miss, and about all I ever open Dreamweaver for these days, is its ability to understand content pasted from Word or other Office docs. Saves hours of htmlizing work from clients.

[ben-erwin]

I can't believe this is still going on. And I don't think this should be that hard to fix.
1) It is sleeping hard drives. When get the error, I can go to the hard drive, click on it and the error message goes away

2) The reason it is the sleeping hard drive is because of the path on the local machine

3) The fix is for Dreamweaver to access the sleeping hard drive like any file

We KNOW what it is. Yes, Windows may throw the error, but that's because Dreamweaver fails to communicate to windows to say HEY WINDOWS! My files are here. Please let me access them.
Problem solved. You're welcome.
Now, will somebody on the Dreamweaver team stop jacking us off and fix this please?
Can I get an amen?

[bluehaus]

Amen ben-erwin!

[davidamdur]

Same problem as everyone else. Only started when the cloud system upgraded to DW 2014.1. There was not a problem like this previously. I'm running Windows 7 ultimate 64 bit. DW often takes a long time booting up, and the server message shows up regularly, but I'm able to update my various websites.

[jamie8848]

I have the same error, and it affects Lightroom and Photoshop as well as Dreamweaver. For me it is simple. I have 4x hard drives in my computer (an SSD is the main, operating system drive), 3 high capacity drives of photos. When all four drives are powered up, spinning, then no error when i start any CC app. If even one drive is idle, not spinning, then i get the error until the drive spins up.

Adobe, your response time for this says YOU REALLY DON'T GIVE A TOSS about this, about your customers. You are wasting my time ($$) and the only way you will stop me complaining every time I have to call customer service for the next 3 years is if you actually apologize, and since you have not for MONTHS, you need to apologize with a free month or some good deal. Otherwise I will happily waste more of your time when dealing with customer service. Why is it so difficult for companies to at least admit they have a problem? You reputation is getting closer to MS, and I assure you started a lot higher.

[studiogulo]

I just had the same problem.

Started to Google for aswers and ended up here.

Restarted, same issue. Read some more. Went back to Dreamweaver and clicked 'try again'. Dreamweaver crasched, then I could restart it without the problem.
Weird.

[Hedge]

Don't feel bad I started this thread and I still continue to have the problem.