|
Good morning, the last build of SA17 for Mac OS does not install on Mac OS Catalina (10.15.1/2). I get an error: "Error. Internal error. Setup will exit." Will there be an update soon? Thanks, Axel |
|
May i ask once again? There are new builds for Windows and Linux... Well, apparently as just another customer, I can't tell - but you might have a look at the readme from the new Windows build to find out whether relevant OSX topics are documented.
(11 Mar '20, 09:43)
Volker Barth
We currently have an update in the QA process for that platform. I cannot estimate when that process will complete at this time. Note that we also had a very long cycle between patches for the most recent Windows and Linux patches.
(12 Mar '20, 09:27)
Chris Keating
Replies hidden
FWIW, we've noted that, too:)
(12 Mar '20, 10:19)
Volker Barth
For me SA for Mac OS is only nice to have. All of our customers work on Windows. But it would be nice to have a running software for the current Mac OS. ;-)
(12 Mar '20, 10:38)
Axel Siepmann
|
|
Hi Axel, This problem has explanation in following KBA. 2635376 - Internal error when install SQL Anywhere on Mac https://launchpad.support.sap.com/#/notes/2635376 Can you try Resolution? Install SAP SQL Anywhere 17.0 from command prompt: 1. cd ga1700 (the directory for SAP SQL Anywhere 17.0) 2. ./setup 3. follow the instructions as setup window shown Thansk, Atsushi Hi Atsushi, unfortunately does not work due to (new?) restrictions in Mac OS. I'd have to allow every single executed file (setup it self, *.dylib-files etc.) in system settings... Best regards, Axel
(22 Nov '19, 02:28)
Axel Siepmann
Replies hidden
Hi Axel, ok... You should ask SAP Support about this problem. Thanks, Atsushi
(22 Nov '19, 02:40)
asa
|
|
One more sign that SA is no longer a strategic product for SAP, i'm afraid... Would you share the other signs you have noticed?
(22 Nov '19, 04:02)
Volker Barth
1
My impression is that the software quality is decreasing gradually.
(22 Nov '19, 05:30)
Axel Siepmann
Replies hidden
1
Have you created any single support ticket with one of these crashes, or you asked questions on this forum only?
(22 Nov '19, 06:49)
Vlad
2
As Vlad has indicated, issues that you want SAP to address need to be pursued as technical support incidents. This forum is frequently by SAP staff but it is not a substitute for technical support. As an example, the crash involving the trigger had a discussion but the suggestions did not help. And without a dump or a repro, it can be difficult to determine root cause in this forum.
(22 Nov '19, 08:15)
Chris Keating
1
> SA is no longer a strategic product for SAP ...or, possibly, it indicates that OS X is no longer a strategic platform for SQL Anywhere 17. The SAP SQL Anywhere Supported Platforms and Engineering Support Status page lists 10.10 for OS X... ...maybe that's a typo, or maybe support for 10.15 (which was released one month ago) will take a while.
(22 Nov '19, 12:26)
Breck Carter
2
> My impression is that the software quality is decreasing gradually. That's certainly not my impression, or the impression of my clients. On the contrary, SQL Anywhere 17 is now stable, and I am no longer advising anyone to "stay with V16". That is a significant milestone in the very conservative world of production databases. Moving to a new RDBMS version (or OS version!) is a big decision, fraught with peril if done without careful consideration and preparation.
(22 Nov '19, 12:37)
Breck Carter
1
> The end of support in 2025 What's coming in 2025 is the end of mainstream maintenance for Version 17, which means no more fixes for freshly-discovered bugs. That's not the same as "the end of support". Technical support for SQL Anywhere 17 is no more likely to end in 2025 than it ended for version 16 in 2018 (it didn't). If you want SAP to do something for you, try calling SAP.
(22 Nov '19, 12:45)
Breck Carter
Just to add: When version 17 was released, the published EOL date was 12/2022 (*). In my limited understanding the date was later extended to 12/2025 because the release cycle has been modified (i.e. lesser new major versions, more minor versions, think of 17.0.0 to 17.0.10). I would except if SAP would not release a new major version (18 or whatever) in the coming years, the v17 EOL date might be extended again. My assumption, apparently... (*) This can be seen here when checking page history...
(22 Nov '19, 13:13)
Volker Barth
|
|
Hi Axel When receiving this error, I was with the following successful: Open the (Mac) Terminal Change to where the installer is, something like: cd /Users/<user>/Desktop/ebf27542/sqlany17/ if the path is correct, there is a setup file there. Now, start the setup file by: ./setup and follow the instructions. Hopefully this works for you as well. Regards, |
Support for Catalina is currently being completed. I do not have a timeframe for that work to be completed.
As Chris said, we are currently working on the notarization required for Catalina.
What version of macOS are you running exactly? The install works for me on 10.15 and 10.15.1. (I assume you're running 17.0.10.5853?)
Hi Tim i'm on 10.15.2 beta (19C64a). When i run setup from terminal i get "dbinstall can not be opened because the developer can not be verifyied." (Translated from German). I can allow this in system settings but then the next message is about "dbversion" and so on. BG, Axel
Okay, thank you Axel. That makes more sense.
> One more sign that SA is no longer a strategic product for SAP, i'm afraid..
> . . . i'm on 10.15.2 beta
Thanks for clearing that up: an Apple beta is not a strategic platform for SQL Anywhere :)
🙄..........