lollettuk

For anyone search for an answer to this old problem - We just had this with one of our schools getting "Could not find file ....\census_output.xml" quickly flashing at the bottom of sims. Every time we run a create and validate census it wrote the following error to c:\users\[username]\SREngine.log (might sometimes save to c:\program files (x86)\SIMS\SIMS .net\ folder). ----- SREngine.exe exception raised 06/10/2021 at 13:32:33 Message : Could not find stored procedure 'sims.sre_pix_datapackage_census_GetFamDetails'. Source : .Net SqlClient Data Provider StackTrace : at SIMS.Processes.Database.RetrieveDataSet(IDbCommand command, Boolean AsCP320) ... ------------------- Additional Data (as key/value pairs) ------------------- ... -------------------------- Parameters passed to SREngine.exe -------------------- ... ------------------------------- End of Exception -------------------------------- When compared to other SIMS databases this stored procedure was indeed missing from the SQL database. Problem was due to SIMS Summer 2021 - Consolidated Workstation Patch 1 This comes in two parts - "SIMS .Net client update files" and the "database patch". The clients had been updated to 7.200.35.1 But the database patch hadn't been applied for some reason. Note: SIMS doesn't seem to whinge "database mismatch" for these consolidated workstation patches. So applying the database patch and re-running the create and validate census then worked

Ran into this problem today: Could not find method 'CreateManagedTask' for type... I believe the version of DBAttach in SIMSSQLApplicationSetup.exe included with SQL Migration is out of date. Simple fix: Overwrite the SIMSSQLApplicationSetup.exe in the SQLMigration folder with your latest version from the SIMS Setups folder.

Many thanks for all your help Matt and good luck with the new job!

We do! SIMS .net shortcuts go to pulsar.exe but oddly if you set C:\WINDOWS\SIMS.INI (and the Users Profile SIMS.INI) - SIMSSetupsDirectory=[something that doesn't Exist] pulsar take 30sec (instead of 6-10secs) to load and various parts inside SIMS are very slow??!?!?!?!

Found the issue: C:\WINDOWS\SIMS.INI - SIMSSetupsDirectory pointing to a location no longer available! Updated, but you also have to delete any profile C:\Users\[username]\Windows\Sims.ini as it doesn't seem to pickup the WINDOWS\SIMS.INI changes.

Tea / Coffee tray? Sure you can get 6 - 8 mugs to take to managers everyday???

SQL default port is 1433... Not "TCP Dynamic ports" setting, but the one below "TCP Port" But Matts answer is correct your SIMSINST is out of date, so running SIMSSQLApplicationSetup.exe manually should do the trick

In SQL Server Configuration Manager: Is TCP/IP/IP Addresses/IPALL set to 1433?

Can SQL management Studio connect to the instance? Did you install SQL in mixed mode authentication? Can SQL Mgnt studio login as SA? As Jamo said: In SQL Server Configuration Manager: Have you enabled Names Pipes and TCP/IP?

Not afar as i'm aware...but during the service break i'm on a 16core 64gb xeon server by myself

we skip simsload.exe and go straight for pulsar.exe...

We've had SQL2008 R2 on for over a year now and we have tried a reindex... oh well if nobody else has seen slowness then I can't blame Capita straight away this time! Thanks Matt!

Our slowness is only around SIMS... Discover,FMS,etc all running normally. I was also expecting the spring upgrade to break discover, but other than it changing one of the .configs in the hosted version back to default it went pretty smoothly on both standalone and hosted. There are two flavours of the config tool, "Discover SIMS Hosted Transfer Configuration" and "Discover SIMS Configuration" (standalone)... The standalone is used to setup custom graphs - as it's still running you could export any you've setup, install a fresh Discover SQL DB and re-import them. If your not comfortable with SQL then Capita would be your best bet as they've better know which SQL table needs looking at... FYI: Our Discover transfers normally only take roughly one min

Not seen that one... my only suggestions: 1. Not all Discover Errors actually say what they mean! So double check your "Discover.Designer.Desktop.exe.config" pre and post Spring 2012. (Spring upgrade defaulted back one setting that we needed!) 2. If you've got a copy of the Discover SQL DB before the upgrade restore / attach and re-run the upgrade on just the DB. Also just before upgrading DB try Config Tool (doesn't seem to be version error pre/post upgrade) as I don't think it changed much and will see if error is present. 3. If not and users havn't put too much customisation in, backup / detach the Discover DB then install a clean Spring 2012 Discover Database (in advanced options)... 4. Worse case... call Capita and wait for the callback!

Dedicated M$ SQL Clusters on multiple SANS running fast disks (loads of space)... Admittedly we have a few schools with 2gb+ logs, but for the most (200+) they tickover around 500Mb(logs). Yes, we have the works SIMS, FMS, SLG, InTOUCH, DISCOVER, the usual 3rd Parties (and shortly EMERGE) but we keep everything on seperate SQL clusters. I noticed the slow down during the service break (no other users on the system) Autumn 2011 running ok, upgrade Spring 2012 huge slowdown!!!! Anyone else????