Jump to content

Recommended Posts

Posted

Hi All,

 

hopefully some of you will have seen this. We have upgraded to the summer release and in most cases all is well. There is one server (our cashless catering system) that requires the SIMS client on to link to SIMS.

When we try and launch SIMS the update starts gets to the yes/no prompt and then stops. the two event below are generated.

 

The server is fully patched and in all other aspects happy. Any ideas greatly appreciated

 

Event ID 1026, .Net Runtime error

Application: Pulsar.exe

Framework Version: v4.0.30319

Description: The process was terminated due to an unhandled exception.

Exception Info: System.IO.FileLoadException

Stack:

at SIMS.UserInterfaces.DefaultEntryPoint.Main(System.String[])

 

 

Event 1000, Application error

Faulting application name: Pulsar.exe, version: 7.159.4.0, time stamp: 0x53bd5995

Faulting module name: KERNELBASE.dll, version: 6.1.7601.18409, time stamp: 0x53159a86

Exception code: 0xe0434352

Fault offset: 0x0000c42d

Faulting process id: 0x350

Faulting application start time: 0x01cfc8e0946e7a79

Faulting application path: C:\Program Files (x86)\SIMS\SIMS .net\Pulsar.exe

Faulting module path: C:\Windows\syswow64\KERNELBASE.dll

Report Id: d361246b-34d3-11e4-aa65-3440b5884c03

  • 2 years later...
Posted
You need a later .Net installed. I put 4.6.2 on to fix the same error today

 

 

thanks problem is when i try install that version i get this

 

.NET Framework 4.6.2 or a later update is already installed on this computer

Posted
what version of .net is it reporting it already has?

 

uninstall .net and put it back on?

 

It seems be a feature in 2016 so I'm not sure that will work but will try it.. this is beyond annoying

Posted
It seems be a feature in 2016 so I'm not sure that will work but will try it.. this is beyond annoying

I think this is one to refer to your SIMS support people.

 

It also sounds like you aren't using SOLUS 3 to do the updates?

Posted
i am using solus 3 thats the strange thing....

its very weird.. it works when i put the user into install mode but once i switch to execute it crashes.

I'm a little confused then. You said in your first post "When we try and launch SIMS the update starts gets to the yes/no prompt". There isn't any install prompt with the SIMS client when using SOLUS 3. It updates in the background, and opening the SIMS client should present you with the normal login box.

Posted
I'm a little confused then. You said in your first post "When we try and launch SIMS the update starts gets to the yes/no prompt". There isn't any install prompt with the SIMS client when using SOLUS 3. It updates in the background, and opening the SIMS client should present you with the normal login box.

 

sorry mate i didnt start the post? just having a similar issue.

Posted

I was about to post and say that "aulting application name: Pulsar.exe, version: 7.159.4.0, time stamp: 0x53bd5995" is a really old version - and suggest that the catering system service likely has capita's Business objects open in the background so it's not updated due to them being in use (i.e. server would need a reboot), but that's likely not to be the case as I looked at the original post. However, posting this anyway, as i've seen this happen in the past.

@victory2015 maybe start a new thread with the actual error you are hitting? I'd also look in the sims folder and check .dll files look to all be updated (for the reason I say above)

Posted
Hi all, i worked it out.. for some reason sims does not work on a 2016 server when the session broker is installed.. nothing seems get round this so i have had to build another server to act solely as a session host and this server will now only handle the remote desktop gateway.
Posted
Hi all, i worked it out.. for some reason sims does not work on a 2016 server when the session broker is installed.. nothing seems get round this so i have had to build another server to act solely as a session host and this server will now only handle the remote desktop gateway.

 

Well that's a bit strange, considering it worked in 2012 R2, I wonder what has changed that stops it from working.

  • 5 months later...
Posted
Just as a note I was coming up against this problem. The server was installed and running in UEFI boot mode. I changed it to legacy and reinstalled everything and it started working fine again.

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