[resolved] TOS_DI-macosx-cocoa is damaged and can't be opened
I've been running versions of Talend Open Studio on my Mac for a long time and can still launch v5.3.2. I need to upgrade to at least v5.4.2, but I get this error when I try to run TOS_DI-macosx-cocoa:
"TOS_DI-macosx-cocoa" is damaged and can't be opened. You should move it to the Trash.
I get this message with v5.4.2, v5.6.0, and v5.6.1. No log file gets created. I have Mountain Lion (10.8.5) and JRE 1.7:
$ java -version
java version "1.7.0_51"
Java(TM) SE Runtime Environment (build 1.7.0_51-b13)
Java HotSpot(TM) 64-Bit Server VM (build 24.51-b03, mixed mode)
Thanks for any help -- I'm getting pretty desperate because I'm supposed to take over some jobs developed by another programmer!
Hi, All your studios are not working well in your MAC after upgrading? Can you open a new installed studio? No error log is located in <Talend Studio installation path>/workspace/.metadata/.log ?
Hi Sabrina, thanks for your reply! My v5.3.2 studio is still working fine. I've tried installing new TOS versions multiple times (v5.4.2, v5.6.0, and v5.6.1 from the download site). All of those fail in the same way. No .metadata directory is created in the workspace directory. Only .JETEmitters exists.
Hi Sabrina,
Yes, I downloaded the .zip file and unzipped it successfully. I've been using TOS since version 4.2. I'm asking some colleagues to try and install newer Mac versions to try and confirm that this is a problem with my Mac rather than with the build process itself.
Thanks,
Chris
Ugh, apparently my Mac OSX security changes have been changed. This article tells you how to allow apps from "other vendors" to run on the Mac platform.
Apple shouldn't just give a bogus "corrupt file" message when the app is not from one of its trusted vendors! However, I'd suggest that Talend consider becoming a trusted vendor. Thanks for your help!
Hi,
i'm trying to launch it on Mac OSX Yosemite, i get the error message to check log file but I cant find the log.
The error is,
An Error has occurred.
See the log file
null