Jump to content

kshah58

Members
  • Posts

    24
  • Joined

  • Last visited

Reputation

5 Neutral

About kshah58

Personal Information

  • Occupation
    SIMS Assessment Specialist
  • Location
    Edgware

Employer (optional)

  • Company Represented
    SIMSforSchools
  1. We have a user at a secondary school we support that is getting the following error: "Value was either too large or too small for an Int32. : System.OverflowException" when trying to open a student in Curriculum Assignment by Student. Checked Capita for this issue and they inform that the maximum value for the CommandTimeout is 2147483647, but I believe this is for a 32bit workstations (Refer to KB93300). The CommandTimeout in the school's connect.ini is 10000000 and the workstations in the school are all 64bit. Does anyone know what is the maximum value for the CommandTimeout line for a 64bit workstation?
  2. Hi Rina, For teachers to see their timetable on the timeline, firstly the timetable should have been applied and the teachers need to have their SIMS user account linked to their personnel record. You will not be able to see teachers timetables on your timeline. To see if the teachers have a timetable, go to Reports | Timetable | Staff Timetable(s), set the effective date if required, double click on the teachers you require and click OK. If your new Year 7's are in pre-admissions and the application status is Accepted, you will be able to see the new Year 7s in Focus | School | Pastoral Structure | Current Structure. Expand the Pastoral Structure, right click on Year 7 folder and select Members. Your new Year 7s should be highlighted pink. It is worth while running the Reg Group Dated report in Run Reports. Just change the effective date to the date of admission. The new Year 7 will not show automatically tomorrow. You will need to admit them and you can do this in bulk in Routines | Admission | Admit Applications. Select the Year 7 admission group and all you have to do is add a tick in the Admitted column against the students that turn up on the first day. Hope this helps. Thank you. Kunal
  3. Hi Steve, I used to work at Hillingdon Council for the SIMS Team. Quick question are you based at a school in Hillingdon? If you are I believe the person to speak to is Sally Stone in the Civic Centre to obtain the ATF files. If you can't get in touch with her then contact the Admissions Team on 01895 556 644 or [email protected]. Regards, Kunal
  4. Just checked the system properties on the server and it is a 64bit system. So upgrading to Server 2012 R2 should not cause any problems to SIMS and FMS.
  5. Thanks for your reply. We won't be changing the version of SQL since they are already on SQL 2014. Just need to double check whether the server is 32 bit or 64 bit OS. If the server is a 32 bit OS, then what considerations will we need to be aware of?
  6. One of our schools will be upgrading their current server, which is currently on Windows Server 2008 and holds the SIMS and FMS databases, to Windows Server 2012 R2 this summer. I believe there are no hardware changes to the current server, but I need to clarify with the IT Manager at the School. Will upgrading the server to Windows Server 2012 R2 affect the SIMS and FMS databases?
  7. I'm trying to manually install Borland Database on a Windows 10 workstation, but the application will not run even under the Administrator account. The user cannot log into FMS as she is getting a dbCheckLogin error and has to use the Administrator account to log into FMS. I have also given full control to the FMSSQL folder as it "appears" to be an access rights issue but still the error persists. The Capita solution is to use the ODBCad32 to rectify the issue but there are components missing such as the SQL Native Client. Going through the solution does not resolve the issue as well. I am aware that there are issues installing FMS via SOLUS 3.10 on Windows 10 workstation and a workaround is to extract the BDE.exe from SOLUS 3 and run it manually. I have done this on a different workstation which has worked, the only difference is that the workstation was brand new and had Windows 10 already installed on it. I have a hunch that this workstation has been upgraded from Windows 7 to Windows 10 and wonder if this the cause of all the issues? Has anyone else got issues after upgrading from Windows 7 to Windows 10?
  8. Hi All, Thanks for all your feedback. I will get in contact with the school's IT manager and tell him not to do it.
  9. This may have been asked before...but a school's IT manager would like know if workstations can be reimaged with the SOLUS 3 agent included. I assume this fine to do as long as the IT team do not change the Computer Names.
  10. Quick query, has anyone got any experience with BACs Processing to Lloyd's Corporate rather than Lloyd's Link? We have a school using BACs Processing to Lloyd's Corporate and can't seem to get it working. Something along on the file type or extension used.
  11. Issue has been resolved...Did all the workarounds, plus a reboot and the workstation can log into SIMS.
  12. Hi all, Thanks for your inputs. The Connect.ini is pointing to the correct server name. I've also used the Server IP Address instead plus with a dynamic port. Added a command time out line on the connect.ini file as well. Still no luck!! I have also disabled the firewall and also put an exception for SQL in the firewall. The workstation which contains the SIMS and FMS database works perfectly fine with no errors. Also I just found out that there has been a domain created and the admin users have new profiles for the domain, with the files from their previous profiles been transferred across. Would this have any implications on connecting to the SIMS and FMS database? Thank you. Kunal
  13. Hi, I've been trying to resolve this issue on a workstation for the last 2 hours. Been through the Capita workarounds and still no luck. The school's IT support has been preparing for a server migration and would like to move the SIMS and FMS database from the main office workstation to the new server. The only peculiar thing that comes to my mind is that the IT support changed the IP range so the curriculum network and admin network are on the same range. The admin workstations were on 10.81.90.xx range and were moved to 10.81.92.xx range. The SIMS and FMS database would have been installed on the 10.81.90.xx range. Could the change in IP range cause issues with connections to the SQL Server? Thank you. Kunal.
  14. Had a look at the log file...SOLUS 3 is currently on version 3.9.0.17? Try and change the Authentication type to SQL in the SOLUS 3 settings in your SOLUS 3 Deployment Server UI, save it, restart the deployment service, and redeploy the SOLUS 3.10 upgrade. If this still gives you an error, open SQL Management Studio and give NT AUTHORITY\SYSTEM db_owner permission under User Mapping for the SOLUS 3 database. Restart the deployment service and redeploy the SOLUS 3.10 upgrade. Hopefully this should work. If this still does not work...then have you downloaded the 3.10 installer files from Capita? If you have, then uninstall the SOLUS 3 database from Programs and Features via Control Panel. Run SOLUS3DeploymentServerDatabase.exe adding the server instance, select the SQL Authentication option, add the SQL user (usually "sa") and the password, click test connection in which you will get the message stating that the database already exists and will upgrade to the latest version. Click Next and the database will then upgrade. Check if the SOLUS 3 database is present in the list of Programs and Features and check the version as well. Go back into SOLUS 3 Deployment Server UI and redeploy the 3.10 upgrade. Since the database has been upgraded the deployment should skip to the Deployment Service, GUI and Agent. It looks like a long workaround but in truth it only takes around 10 minutes to do. Good luck and see how you get on! Regards, Kunal
  15. Thanks Atomic_Zombie. I check all the areas you suggested and all was correct. But the issue has been resolved via a Capita remote session. They amended row in SQL Management Studio so the database had a version in the Deployment Server UI.
×
×
  • Create New...