>>>Hi all,
>>>
>>>out application runs fine on server 2012 in a customer site. 4-5 users log in via RDP and use the application and another 2-3 on the network. The program will runs for days or weeks but then suddenly we'll get an appcrash error when users try to use it on the server. Those on the network are unaffected and can login and use the program with no issue while those on RDP cannot use it. The only solution I've found is a reboot but anyone any ideas on what could be causing this?
>>>
>>>

>>>Problem signature:
>>>  Problem Event Name:	APPCRASH
>>>  Application Name:	lpj.exe
>>>  Application Version:	12.8.876.0
>>>  Application Timestamp:	3f73b447
>>>  Fault Module Name:	ntdll.dll
>>>  Fault Module Version:	6.2.9200.16420
>>>  Fault Module Timestamp:	505aaa82
>>>  Exception Code:	c0000006
>>>  Exception Offset:	00052850
>>>  OS Version:	6.2.9200.2.0.0.16.7
>>>  Locale ID:	6153
>>>  Additional Information 1:	3874
>>>  Additional Information 2:	387413904d106150599113a8be265de1
>>>  Additional Information 3:	7771
>>>  Additional Information 4:	777104861a64a35a285b1ec9993c9be8
>>>

>>
>>Are any errors or warnings being recorded in the System or Application event logs around the time of known crashes?
>
>None that I can find. A server reboot was supposed to be done last ngiht but they forgot, strage thing is that the program is running as normal again. No settings changed and nothing modified, just started working again. Bizarre stuff.

On a server, RDP sessions are usually configured to time out and disconnect and/or log off after a certain period of inactivity. Maybe there were one or more "orphaned" sessions and one of them was in a state such that it prevented the app from running in any other sessions on the server. Maybe they timed out and automatically closed last night so the app can now run in new RDP sessions.

That's enough "maybes" that it qualifies as a SWAG. Still, the next time it happens, rather than just rebooting the server, you could go into Remote Desktop Services Manager, check the active sessions, and manually log off any that appear to be orphans.