Jump to content

Recommended Posts

Posted (edited)

Not sure if anyone else has this issue. "Upgraded" to Spring 2021 and discovered today that all of our scheduled reports which automate all sorts of stuff fail with the following error:

 

Unhandled Exception: System.TypeInitializationException: The type initializer for 'SIMS.UserInterfaces.CommandReporter' threw an exception. ---> System.IO.FileLoadException: Could not load file or assembly 'AbstractProcesses, Version=7.198.31.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)

at SIMS.UserInterfaces.CommandReporter..cctor()

--- End of inner exception stack trace ---

at SIMS.UserInterfaces.CommandReporter.processCommandLine(String[] commandLine)

at SIMS.UserInterfaces.CommandReporter.Main(String[] args)

 

Its with Capita tier 2 support - might just be us - but might not be. Anyone got any ideas what might be broken?

 

Thanks,

 

Roger

Edited by rogerdnixon
Posted
Ah crud. We’ve only recently started using this, our SIMS is being updated on Friday. Will pre warn the member of staff that uses the reports. Thank you for the heads up.
Posted

We are getting an incorrect syntax error when staff try and enter data into their marksheets, (aspects?) clicking the tab to the right of the register to access them crashes SIMS with an unclosed quotation mark error.

 

It's almost like a programming bug made its way into production but there's no way of that happening with the software being fully tested before release, right?

Posted

Have you tried deleting the SIMS client installation and re-installing? I've seen a similar error with commandreporter when the SIMS client upgrade couldn't upgrade commandreporter.exe as it was in use at the time.

 

Meldrew.

Posted
Have you tried deleting the SIMS client installation and re-installing? I've seen a similar error with commandreporter when the SIMS client upgrade couldn't upgrade commandreporter.exe as it was in use at the time.

 

Meldrew.

 

Spot on - thats what Capita did to fix the issue today. Some files locked by a third party tool they said.

Posted
It's almost like a programming bug made its way into production but there's no way of that happening with the software being fully tested before release, right?

 

At least we have you brave souls to test it for us!

 

Imma grab my popcorn and sit on this thread watching for a few weeks (or months).

 

Carry on...

  • Thanks 4
Posted
We had been running with those apostrophe's just fine until this update, but yes removing them fixed the crash. Unsanitized SQL inputs must have been the cause, a sign of very shoddy programming
Posted
We had been running with those apostrophe's just fine until this update, but yes removing them fixed the crash. Unsanitized SQL inputs must have been the cause, a sign of very shoddy programming

 

yes, something in the Spring update broke it, there is now a patch out to fix it....

  • 1 month later...
  • 8 months later...
Posted
Have you got UDF's in the template with apostrophe's? That appears to be the issue....

 

Came here after googling why a CommandReporter batch file of ours is sporadically failing and I found the irony in this post amazing :D

Posted (edited)

They're just reminding everyone why they need to keep paying for support [emoji57]

 

Keep creating bugs that they then need to fix.

Edited by jmak

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...