on 2012 Jun 14 10:01 AM
The "Check for Updates" is returning a "Could not check for updates" message.
I am not sure if this makes any difference but I have tested this via Sybase Central and ISQL.
From a command line dbsupport -iu
shows that www.ianywhere.com is down.
Request clarification before answering.
Ok, so for what its worth and in the interest of being as open as we can be, the check-for-update system was unexpectedly down for quite a while due to some network restructuring.... but as it has been noted by others, it is now up (as of Wednesday evening/early Thursday morning).
While the system was down a number of new EBFs were posted and the info about these new EBFs needed to get pushed out to the check-for-updates system... which has now been done (as of Thursday afternoon).
Hopefully everything should now be back to normal!
Thank you for your patience.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Thanks for that "Info update service" - much appreciated, Mark:)
I just tested it again and the Check for Updates service seems to be back up. No upgrades found for the options I have installed for the SA 12.0.1.3726 version (for Windows).
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Volker, I recall seeing in another place that a new EBF was to be released. Does 3742 show for you as available for download?
This is a known issue and IT is working to resolve it. I am unsure how quickly IT will have it back up?
I will post back here when IT has it fixed.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
@Volker, I didn't have any issues accessing the forum today.
But I had, around 10am, for about an hour or so. Pinging sqlanywhere-forum.sap.com failed.
Yes, that's about the time I tried, too (MEST/CEST).
FWIW, pinging that address (and 192.138.151.252) still fails for me with timeout - but I guess the server simply doesn't generally respond to ICMP requests for reasons of security...
...We might wait for some book keeping in the bottom line:
User | Count |
---|---|
82 | |
29 | |
9 | |
8 | |
7 | |
7 | |
7 | |
6 | |
6 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.