Jump to content

Recommended Posts

Posted

Hi all,

 

i have noticed this morning on our SIMS server that when i try to load SIMS software on it, I get the following message:

 

Fault Code: 1384-4508-8400

 

Could not load file or assembly 'AlternativeDatabaseProcesses. Version=7.168.50.0 Culture=neutral.

PublicKeyToken=21f532fe36bf9cd6' or one of its dependencies. The located assembly's manifest definition does not match the assembly

reference. (Exception from HRESULT: 0x80131040) : System.IO.FileLoadException

 

im not sure whether if it has any relevance to the other message on a machine thats used by our attendance officer:

 

Fault Code: 1183-3672-8000

 

Cannot insert the value NULL into column 'forename'. table '@attendees'. column does not allow nulls. INSERT fails.

The statement has been terminated. : System.Data.SqlClient.SqlException

 

I have tried googling to no avail and there is nothing on captia support either. just wondered if anyone has experienced the same or similar issues.

 

Thanks,

 

Simon

Posted

First try running simsapplicationsetup.exe in sims drive

 

Fail that try reinstalling sims client through solus 3 or using simsinst installer in setups.

 

Not to be confused with sims server and its database. You would be in a whole heap of sh!t if you remove that

  • Thanks 1
Posted (edited)

Your first error is where not all of the SIMS client files could be upgraded (usually because SIMS is left running on the server, or there is a third party plugin service like MIS Sync accessing some of the SIMS .net client DLL files). You might spot a lot of "tmp" files in the SIMS .net client directory which indicates the client update has a pending reboot to update the files that were inaccessible. A reboot will finish the client upgrade.

 

Failing that if you don't want to/can't reboot, then rename/delete the SIMS .net folder and cleanly reinstall it. If you do opt for the reinstall method and you do have third party plugins running and accessing your SIMS files, be sure to stop the relevant services first so you don't have the same issue again.

 

The second error is a known issue. Somehow, a pupil does not have a legal forename in SIMS. Run a report showing all pupil's legal forename and surnames to find the affected pupil and correct the record.

Edited by Bubbles

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...