limawhiskey

That's really impressive @Moohorse. Do you plan to publish the code / app?

Another option is to contact Mathswatch, tell them your external IP and they make a change that runs the video from their servers instead.

Thanks, got it. I enjoyed the Monkey Island remasters a lot so I'm looking forward to re-playing this. It's been a very long time since I played the original! For info, according to the countdown the giveaway ends tomorrow at 2 pm (GMT).

This seems to be related to files which have the alternate data stream to indicate they have come from an untrusted Zone (i.e. files whose properties have the Unblock button). Normally you would see the Enable editing security banner in Office programs, but we seem to be getting this same error instead (added the text for anyone searching): We're sorry, something went wrong that might make PowerPoint unstable. Please save your presentations and restart PowerPoint. If you 'unblock' the file it opens fine, which is why the measures @hardtailstar mentioned work too. It seems to have happened over the last couple of days which points to a Windows update, but this is even happening for us on machines that have not restarted to apply updates. So all this points to some issue running Protected View or transitioning from Protected View to normal editing, but only in PowerPoint - other Office apps are not affected. As an aside, I agree the Protected View security is there for a reason but in realistically can anyone say that they don't just hit the Enable editing button to get on with their tasks?!

Saw the same error here yesterday, nothing to do with File Stream but this powerpoint had been saved from an email to a network drive. Copying it to the local drive resulted in the same error message. On opening another working powerpoint file we got the 'Powerpoint has opened in safe mode' message. Next time opening the 'problem' file it worked fine.

No problem. Credit to the tech support folks at Scholar - they turned that around quickly. The Jisc certificate service uses QuoVadis so it might be worth adding all the intermediate certs anyway if you can. I checked our Smoothwall and they are included in the 'built-in' installed CA list.

Holy thread resurrection, Batman! Did this ever materialise as a SIMS component or did anyone find a good alternative? We're looking for a way to take extra curricular attendance and then do some number-crunching with the data on a termly basis.

Looks like your proxy system doesn't like it as the site's HTTPS certificate chain is badly configured: https://www.sslshopper.com/ssl-checker.html#hostname=scholar.hw.ac.uk https://whatsmychaincert.com/?scholar.hw.ac.uk https://www.ssllabs.com/ssltest/analyze.html?d=scholar.hw.ac.uk&hideResults=on&latest Adding the intermediate CA cert (QuoVadis Global SSL ICA G2) to your proxy system should allow connections: https://www.quovadisglobal.com/QVRepository/DownloadRootsAndCRL.aspx

How did I miss that?!

What OS are you using on the pi? I know you said it doesn't exist, but on my install of Raspbian Stretch, /etc/dhcpcd.conf is definitely the config file to use for IP configuration. Sorry if it sounds patronising but maybe double check that you're not making a typo in the filename / path. Look for the the following lines, copy and/or remove the comment delimiters (hashes: #) and edit as appropriate: # Example static IP configuration: #interface eth0 #static ip_address=192.168.0.10/24 #static ip6_address=fd51:42f8:caae:d92e::ff/64 #static routers=192.168.0.1 #static domain_name_servers=192.168.0.1 8.8.8.8 fd51:42f8:caae:d92e::1

Just sent you a PM with the details of a contact.

I don't know if it's recorded elsewhere, but you can find it in your SIMS database in the db_update_log table by reading the row for patch 24229. SQL query - you may need to update the SIMS database name (in italics) to match yours: SELECT [error_description] FROM [[i]sims[/i]].[sims].[db_update_log] WHERE patch_id = 24229

Thanks, that was really useful and helped me confirm that we had not applied patch 22527. So unless the Capita advice changes we appear to have been lucky enough that our data manager stopped importing CTFs at the right time.

We definitely have CTF imports that were done just prior; towards the end of the 2016/17 academic year and at the start of 2017/18. All the sources I have seen imply that the bug came in with the Autumn upgrade; the Capita guidance states: So @Banjo see what you are saying but I don't believe we have applied patch 22527. Does anyone know how can I check which patches have been applied for certain? Confusingly, "Workstation Patch 1" is not even visible for me in SOLUS3 unless I select "Show all updates". What's more, the release date conflicts with Capita's guidance. I do have "Consolidated Workstation Patch 1" but that doesn't even tie in properly with Capita's information as it was released to us on 16 August. I'm with everyone that thinks Capita have handled this appallingly - I have read so many conflicting bits of advice since the CTF issue came up that I'm struggling to understand the truth of the matter!

I don't think we are affected, but can someone check my logic please? 24 Jan 2018 - Autumn release applied 12 Jul 2018 - Summer release applied There is no record in SOLUS3 of patch 22527 being applied. Between the above dates, we had no CTF files imported (looking at Routines > Data In > CTF > View Import History Log) , therefore no contacts should have been adversely affected by the CTF import problem. Am I correct? However, diagnostic check 99 has come back with 46 "Possible contact link issues" and one "no current address". I'm guessing these could be general contact issues in the database that are not necessarily related to the CTF bug. I'd welcome other opinions