• Welcome to the Lightroom Queen Forums! We're a friendly bunch, so please feel free to register and join in the conversation. If you're not familiar with forums, you'll find step by step instructions on how to post your first thread under Help at the bottom of the page. You're also welcome to download our free Lightroom Quick Start eBooks and explore our other FAQ resources.
  • Stop struggling with Lightroom! There's no need to spend hours hunting for the answers to your Lightroom Classic questions. All the information you need is in Adobe Lightroom Classic - The Missing FAQ!

    To help you get started, there's a series of easy tutorials to guide you through a simple workflow. As you grow in confidence, the book switches to a conversational FAQ format, so you can quickly find answers to advanced questions. And better still, the eBooks are updated for every release, so it's always up to date.

MCPublishCache Error on 2015.3 Startup May be due to PhotoVia plugin

Quincy

New Member
Joined
Oct 13, 2015
Messages
1
Location
Toronto
Lightroom Experience
Intermediate
I just updated to 2015.3. When I opened the program, just after the splash screen I got the following error message:

attachment.php


The program still ran after clicking "OK", at least the Library and Develop modules. I didn't try any export or publish functionality, which ties into what followed.

I did some reading around several forums and the Adobe blogs and I came to suspect the PhotoVia plugin. I disabled that plugin and, so far, the error has not recurred.

I have not looked for an update to the plugin yet since i really don't use it that often. If anyone has further information on this error and how to solve it, that would be great.
 

Attachments

  • LR Error.jpg
    LR Error.jpg
    112.5 KB · Views: 377
Last edited by a moderator:
Joined
Sep 29, 2007
Messages
23,147
Location
Isle of Wight, UK
Lightroom Experience
Power User
Lightroom Version
Cloud Service
Hi Quincy, welcome to the forum!

If disabling the plug-in has fixed, then you're right, checking for an updated plug-in would be a great place to start. If that doesn't do the trick, then reporting it to the plug-in developers would be next in line.
 
Top