New Lightroom CC install Errors

[rperisho_tmcrv]

I work for a company as a commercial photographer on staff & naturally we have network servers. Since I've been here, installing & updating any software contained in the Creative Suite ( and I have the full suite access) has never been a problem; until now.  Apparently your company decided to change the coding that makes Lightroom (and only Lightroom)  decide to require access to a file in my documents folder that is actually stored on our company's secure server. So it is being denied. And I get something like the following:

Exit Code: 156

-------------------------------------- Summary --------------------------------------

- 2 fatal error(s), 0 error(s), 4 warnings(s)

FATAL: Error (Code = 156) executing in command 'CreateSymlinkCommand' for package: 'AdobeLightroom-mul', version:7.0.1.1142117

FATAL: Error occurred in install of package (Name: AdobeLightroom-mul Version: 7.0.1.1142117). Error code: '156'

WARN: Unable to delete directory "C:\Program Files\Adobe". Error 32 The process cannot access the file because it is being used by another process.. Check and correct folder & parent directory permissions and then try again.

WARN: Warning (Code = 149) executing command DeleteDirectoryCommand

WARN: Unable to delete file at "\\****.local\private\home\****\..\Desktop\Adobe Lightroom Classic CC.lnk". Error 5 Access is denied.

WARN: Unable to create symlink at "\\tmcrv.local\private\home\rperisho\..\Desktop\Adobe Lightroom Classic CC.lnk"

-------------------------------------------------------------------------------------

(the row of "****" is just redacted info.)

Now we found a silly work around for the new install that requires our tech to do a private login on my computer, do the install into his private admin folder & then move the document to my area in order for everything to work. I figured that would be the end of it. But no, apparently now this has to be done even for your updates. Because as of this morning, Lightroom failed to update & is now unusable. And it is adding another lovely fail code "Error: 5". And please don't recommend the "cleaning tool". I've been down that road & it doesn't help.

Now I know the vast majority of users work on private computers, hell, I have the new Lightroom on my home system; flawless install. But this needs to be addressed for larger institutions that use your product.  

[Jeff A Wright]

Rperisho_tmcrv sorry that you have been facing difficulties with your Lightroom Classic CC installation.  What version of Windows are you utilizing Lightroom Classic CC on?

From the error you posted it appears that there was a failure to create the Lightroom Classic CC shortcut on the desktop.  From your description it appears you are using Roaming User Profiles/Accounts which store the contents of your User folder on a local network server?  Is this correct?

What type of a Creative Cloud membership do you have Rperisho_tmcrv.  There are a number of options, to deploy a successful installation of Creative Cloud applications in a restricted environment, for Creative Cloud for Team or Enterprise memberships.  If you can confirm the type of membership you are using it would be appreciated Rperisho_tmcrv.

[rperisho_tmcrv]

Thanks for responding Jeff.

Windows are you utilizing Lightroom Classic CC on?

• Windows 10 Pro  64bit

... using Roaming User Profiles/Accounts which store the contents of your User folder on a local network server?  Is this correct?

• I'm not in I.T. but that sounds about right considering our techs described the temporary resolution as follows:

             Adobe was looking for access to Robert's documents for a final part of the installation. Possibly for a log file or something                          related. Because the documents are a network location and he is not a network admin, that specific part of the install

              couldn't be run as an administrator (not even by me because I don't have access to his documents either), so I was able to                        install it under all users by logging in under my UA account and going from there.

As for the membership, I'm listed under the Creative Cloud for Teams.

In regards to the error potentially based around a failure to write a shortcut to my desktop; would you care to elaborate on this? Because it absolutely makes no sense to me, since every other piece of your company's software has no issue doing this.  And as I previously stated, this issue has never occurred during past installations & updates of Lightroom.  Is this just a known bug or will this be something down the road that is going to be implemented into other pieces of your software. The reason I bring this up is simply to be able to alter my I.T department as well as my colleagues who's workflow is paramount to the Creative Suite software not disrupting their production.

[Jeff A Wright]

Thanks for the update Rperisho_tmcrv. 

Since you have a Creative Cloud for Team account I would recommend asking your I.T. department to open a request to speak with an Expert within the Admin Console.  We have guided assistance available to help with installation deployment errors such as the one you have discussed in this discussion.

Rperisho_tmcrv in answer to your question it will be greatly dependent on how the software is being deployed/installed to the computer.  Whatever method is currently being utilized is not treating the Roaming Profile the same as if the User folder was stored locally.

I will also move this discussion to the Deployment for Creative Cloud for Team, Enterprise, & CS forum.  The community in this forum may have additional suggestions. 

Please do not hesitate though to have the request raised within the Admin console as previously discussed Rperisho_tmcrv.

[rperisho_tmcrv]

Addendum:

Since other people have been coming to this thread, I figured I should give an update.  To clear up my previous response, my company is not on a "roaming profiles" network due to our size & the issues that structure can have with our volume of users logging in from multiple access points throughout the day.

Our IT department has run a few tests & will be contacting Adobe to share their findings with a few solutions that will be beneficial to both parties.

[Jeff A Wright]

Thanks for the update Rperisho_tmcrv!

[itp71225311]

Hi Jeff,

My name is Jason and I'm posting on behalf of the IT department for rperisho_tmcrv. We have been exploring many different solutions but unfortunately we seem to be at an impasse. Previously updates have been pushed without hiccups through the Creative Cloud client but this simple issue with the code used to run the update is incompatible with our Redirected Folders.

• WARN: Unable to delete file at "\\****.local\private\home\****\..\Desktop\Adobe Lightroom Classic CC.lnk". Error 5 Access is denied.
• WARN: Unable to create symlink at "\\tmcrv.local\private\home\rperisho\..\Desktop\Adobe Lightroom Classic CC.lnk"

Where the “\..\” is listed, the installer is attempting to look for the Desktop in a location it doesn’t exist, and even if it did, the installer likely wouldn’t have permissions there even when run as an administrator, as this is a network location, not a local path.

Currently our network is set up such that the Desktop, Downloads, and Favorites are local directories on the computer, but other user folders are redirected to be stored on the network. Thus, it will not find the Desktop where it is looking. Were our network set up with Roaming Profiles, this would work, but to switch to this would be a huge undertaking that is, quite frankly, not worth the effort compared to what it would take to change a few lines of code in the installers.

Solutions we have looked into:

• Temporarily change the group policy for redirected folders and change it back once the install is complete. However, to do this for every update would be ridiculous, and requires that a technician has to work on it each time.
• Installing for all users through a network administrator account. However, once the update tries to push it goes right back to the same error, looking at the same path.

Most options we have involve, (in one way or another), moving all user files, changing the way our network policies treat these files, running the update, and moving everything back including the old network policy. These workarounds temporary, time consuming, and risky, as we may lose users’ files in the process.

These updates should be simple and automated for our users. We cannot afford to babysit each update and installation, so we propose these potential solutions:

1. 1. Do not search for the Desktop at username\..\Desktop.

As noted by user arjenth  in thread https://forums.adobe.com/message/9946718#9946718, the install scripting is using the My Documents location as retrieved from the registry and adding “\..\Desktop” to the path rather than using the Desktop’s own registry key.  Arjenth notes that, “Going up a folder from My Documents in some cases is not possible” such as our case of Redirected Folders.

1. 2. Do not require the creation of a Desktop shortcut (or a symlink to said shortcut) to complete the installation. It appears that all necessary files to run the program are present on the computer at the time of this error, but because the installation is viewed as not properly finishing, running the .exe directly from the install directory renders an error that—as you may guess—the install did not finish properly. This solution, while functional, does require intervention after each update. It is simpler intervention where all that is required is that we create a shortcut ourselves, but is still not ideal. Not requiring a shortcut and giving a simple alert that one could not be made would suffice. A path to the .exe could even be provided in this alert.

If this same install scripting is applied to all future Creative Cloud updates/installs, I imagine there will be a lot more issues like this popping up for clients with similar network configurations. Looking forward to your reply.

-Jason

[Jeff A Wright]

Thanks for the update Jason.  There are additional options available to deploy CC applications.  What type of membership does your organization have?

[itp71225311]

What do you mean by membership? We have the Creative Cloud (all apps) for teams, if that's what you're asking.

And the issue isn't with deploying the software, it's specifically with updating it. Right now it only affects the AdobeLightroom-mul Version: 7.0.1.1142117, but I suspect similar code will be implemented for future updates of your other apps and potentially affect thousands of users.

[Jeff A Wright · Accepted solution]

Yes Jason you will want to deploy any updates to the affected computers.  I would recommend reviewing https://helpx.adobe.com/content/dam/help/attachments/cct_onboarding_guide.pdf​ and Packaging User Guide which discusses how to get started with creating deployment packages.

If you would like direct assistance with the process then please submit a request through the Admin Console.  You can arrange a time to speak with a deployment specialist who can assist you with deploying Lightroom Classic CC, and any available updates, successfully.