jeffrey.andrew
Adobe Employee
jeffrey.andrew
Adobe Employee
Activity
Adobe Employee
in Lightroom ecosystem (Cloud-based) Discussions
Jan 29, 2018
09:08 AM
1 Upvote
Jan 29, 2018
09:08 AM
1 Upvote
Lightroom CC 1.2 ( the version with the potential fix for this issue ) has not yet been released. Though we're hoping to release it soon, we are taking the time to make sure it's right.
... View more
Adobe Employee
in Lightroom ecosystem (Cloud-based) Discussions
Jan 18, 2018
09:35 AM
3 Upvotes
Jan 18, 2018
09:35 AM
3 Upvotes
Darn, I'm sorry to hear that. There's a slight chance that your Windows 10 firewall is blocking IPv6 traffic; potentially you could check the "Outbound Rules" section in the firewall settings to see if there's a rule that's explicitly blocking IPv6. This would be tedious and it's only a theory, but you might be able to find an offending rule and disable it. The next version of LrCC (1.2) moves away from IPv6 for local network communication, so it's possible that it will fix this issue for you. I really hope you stick with LrCC and try out the next version when it's released. It just might do the trick. Sorry again for the frustration. Thanks, Jeff
... View more
Adobe Employee
in Lightroom ecosystem (Cloud-based) Discussions
Jan 17, 2018
10:33 AM
2 Upvotes
Jan 17, 2018
10:33 AM
2 Upvotes
Hi David, We've never seen this issue before, and unfortunately we cannot reproduce the behavior you've described. Something you could try is adding an exception to the Windows firewall for the Lightroom CC executable: Open the Windows Firewall from the control panel. Click on the “Advanced Settings” link on the left pane. Windows Firewall with Advanced security UI opens up. Click on the “Inbound Rules” option. On the left pane, click on “New rule”. Under “Rule Type” select the option “Program” and click next. Select the option “This Program path”. Browse to the Lightroom CC executable location: C:\Program Files\Adobe\Adobe Lightroom CC\lightroomcc.exe Select the option “Allow the connection”. Click Next, do not change any option here and click Next again. Specify a name for this rule. Click Finish. If the above does not resolve the issue, you could try repeating these steps for lightroomcchelper.exe which is found adjacent to the Lightroom CC executable. Hopefully this resolves your issue. Thanks, Jeff
... View more
Adobe Employee
in Lightroom ecosystem (Cloud-based) Discussions
Jan 05, 2018
01:30 PM
1 Upvote
Jan 05, 2018
01:30 PM
1 Upvote
The issue "Unable to setup wf rtmfp notify pipe." occurs when Lightroom CC is unable to initialize communication between the various Lightroom CC processes. Some users experience this issue when using a VPN because certain VPN services block all local network traffic that uses IPv6 (a type of internet protocol used by Lightroom CC). Most VPNs can only route IPv4 network traffic, and so many VPNs disable IPv6 to ensure that no IPv6 traffic leaks out over your normal internet connection when you are connected to the VPN. For users that encounter this issue and are using a VPN, there are two workarounds. 1.) Disable the VPN or 2.) If it exists then disable "IPv6 Leak Protection", or any similarly worded setting, in the VPN preferences. With this setting disabled, LrCC should work just fine.
... View more
Adobe Employee
in Lightroom ecosystem (Cloud-based) Discussions
Jan 05, 2018
01:27 PM
2 Upvotes
Jan 05, 2018
01:27 PM
2 Upvotes
The issue "Unable to setup WF RTMFP Notify Pipe" occurs when Lightroom CC is unable to initialize communication between the various Lightroom CC processes that run simultaneously on a user’s machine. Some users experience this issue when using a VPN because certain VPN services block all local network traffic that uses IPv6 (a type of internet protocol used by Lightroom CC for local process communication). Most VPNs can only route IPv4 network traffic, and so many VPNs disable IPv6 to ensure that no IPv6 traffic leaks out over your normal internet connection when you are connected to the VPN. Unfortunately, some VPNs have implemented this leak protection in such a way that it also erroneously blocks local network traffic that uses IPv6. This can prevent any app that uses IPv6 locally, even when not communicating with outside servers, from working properly. For users that encounter this issue and are using a VPN, there are two workarounds: Disable the VPN If it exists, then disable "IPv6 Leak Protection", or any similarly worded setting, in the VPN preferences. With this setting disabled, LrCC should work just fine. For users that are not using a VPN, it's likely that they have some other software installed that is preventing IPv6 network traffic. Likely candidates are firewall and anti-virus software. If you have such software installed, I'd advise you to disable it and then try launching LrCC. If this fixes the problem, then you will need to add some sort of exception to the anti-virus software for LrCC.
... View more