Greg

You can use the bat file and then schedule this, however, that will just shrink the log file - it won't optimise the database as the patches would Both of these patches are still available in SOLUS, if you don't see them then ask whoever you get your SIMS support from to release them

We have it on multiple test systems, no problems yet

Patch 24836 has just been released to fix the issue

Patch 24836 has just been released to fix the issue

Capita have announced the rerelease of the Spring 2019 update https://myaccount.capita-cs.co.uk/Notifications/sims-spring7186-release/ Have fun...

SLG report publishing is split into two jobs in SharePoint, upload and permissions If the upload is ok but you can't access them then make sure the permissions job is running successfully I've had that fail for some schools before

It can be recorded in Dietary Needs in Parent App the Student record in SIMS If it's not there to select then add it on Lookups, along with Dietary Preferences It should then appear in Parent App so long as it's been selected as visible in Parent App Admin Ha, we must have been typing the same thing at the same time

Ha, it was supposed to say SIMS on SQL 2012 is supported...

Ask your LA as your support contract is with them SIMS is now supported by Capita until 2022, it was changed from Summer this year Your LA may be changing the SQL versions that it supports or it may be a doc that needs updating

As long as you can still access it as you can't still upgrade SIMS post support contract - Phil, feel free to correct, this is what we have always been told You'd need to ensure that it is on a version of SQL/Windows/Office that works with that SIMS version - perhaps a VM that can be accessed when needed

Is this via a SQL maintenance plan This is usually related to write problems - check space, permissions, etc Have you checked the full error log Try the backup manually to a different location

We haven't got the same setup as you but if it helps We point all of our SIMS.ini's to SIMSDotNetDirectory=C:\Program Files\SIMS\SIMS .net SIMSDirectory=H:\SIMS Connect.ini is just Redirect=H:\SIMS H is mapped for the user when they log on so all users get the appropriate H drive and their correct connect.ini to access SIMS

No problem Glad to help

That's a VB component, it should be in C:\Windows\SysWOW64 Try rebooting the SIMS Server Failing that check Windows Updates installed or try reregistering it if it exists using Regsvr32 (Usual backup caveats before you start...)

Make sure you have recoverable backups first Find the Doc Server location on the SIMS Server eg C:\Program Files\SIMS\SIMS .net Document Server Open SIMSDocumentServer_.config in Notepad This will tell you where SIMS thinks the Docstorage folder should be Confirm the physical location of the Docstorage folder If it's wrong, stop the Document Server service Copy the contents of the existing DocStorage folder to the new DocStorage folder Restart the Document Server service again to update this Make sure everything is correct and working in SIMS | Tools | Setups | Document Management Server

This can be an Office issue when Office is opening the merge document in read only mode Open a Word document. Go to File | Options On the bottom of the General tab uncheck the box that says “Open e-mail attachments and other uneditable files in reading view.” This will prevent Word from opening in read only view and the data will merge. * Just noticed you've already tried this, try the suggestion above to recreate users profile

When you're back in SOLUS3 check what account is set to authorise upgrades in Environment | Targets | Databases and Environment | Targets | Services If it's the SA account then you'll need to change the password there too

The SA password is stored separately in the SOLUS3 database You can uninstall and then reinstall the Deployment Service and the SOLUS3 UI with the correct account Make sure you have everything you need to reinstall these before you start and are ok doing it, there is an instillation guide, contact your support provided for it

There was a Capita change request (1412-1349499 ) opened for this in 2015 but it didn't get enough votes to impliment

Don't forget to change it back when you've finished

That import is to import an authorised SOLUS3 patch or upgrade file that you had to download manually, it can't import a regular Patch that has not come from SOLUS3 as it needs to be in a .pkg format

The SIMS Summer 2018 Release is now available. 1st test system upgraded without issues. Have fun all...

How are your backups created, the SIMS passwords are not stored in the SIMS database by default. You can transfer them into the SIMS database by running the following in SSMS EXEC sims.sims.db_p_transfer_login You can add an OSQL command to your backup script to transfer them daily to cover any changes, otherwise the passwords stay with the SQL instance - not good for DR OSQL -S YourSIMSServerName\Uour SIMSDatabaseName -E -Q "EXEC sims.sims.db_p_transfer_login"

Capita advise the following on p6 in the technical roadmap Capita SIMS will support SQL Server 2012 Service Pack 4 until Spring 2022, in line with Microsoft Extended support

The Student App is on it's way, that may give what you're looking for