Lightroom 4: Server is busy message when first entering the develop module

  • 1
  • Problem
  • Updated 7 years ago
The message is only shown when selecting the develop module for the first time after starting the application. Goes away after 15-20 seconds clicking on retry in the dialog box. After that, everything is working fine (switching back and forth between library and develop).
OS is Win7 pro 64bit, Lightroom 4.1 RC2 although this problem was already showing in earlier versions of LR4.
Tried some of the suggestions on the forums (repairing/reinstalling LR, disabling indexing services and so on). Anybody have any idea where to look for the culprit?
I remember that this behaviour started at some point after upgrading to LR4, can't say exactly when it happened, but certainly not from the getgo.
Like I said, I'd appreciate any ideas to where to start looking - it must some application I installed or maybe the catalog is broken? Tried that, too by the way, optimizing the catalouge and changing the camera raw cache location to another HD. Thanks in advance
Photo of Christoph Kühne

Christoph Kühne

  • 2 Posts
  • 0 Reply Likes

Posted 7 years ago

  • 1
Photo of jdv

jdv, Champion

  • 728 Posts
  • 56 Reply Likes
Please get a screenshot of the message in question. Lightroom doesn't, as far as I know, have a "server" component of any kind.
Photo of Christoph Kühne

Christoph Kühne

  • 2 Posts
  • 0 Reply Likes
That's true, it is some kind of Windows problem. The thing is, it only happens with LR4, only when entering the develop module for the first time. CameraRaw from Photoshop opens without a hitch.
I have searched the web for quite a while now and was not able to find anything specific.
The error message is in German, so I don't know if anybody here will benefit from it. The English version reads like this:

Server Busy
This action cannot be completed because the other program is busy. Choose 'Switch To' to activate the busy program and correct the problem.

Buttons read "Switch To" and "Retry", "Cancel" is greyed out.

I guess I'll try shutting down various processes through the task manager to try to find the source problem.