Hi everyone,
I have a client who has been having issues with opening Alpha Five Runtime version 11 Build 3381, Addin build 4096. The error is "Alpha Five has stopped working" and can be seen in the screenshot attached.
First, has anyone ever run across this problem where it consistently reoccurs...I have seen this message but a few times over the years and closing and reopening Alpha has always resolved it...not this time!
The error code 41244 was obtained by running the debug from the error dialog box...whether this error is the error regarding Alpha or the debugger I do not know. Anyone know the meaning of this code?...it is not listed in the error codes I can get.
Alpha is connected to by 5 users via remote desktop to a Terminal Server.
I and one other can use Alpha with NO issues. Others can only start Alpha say 1 out of 4 times without error. Once started, if they close Alpha and then reopen, the error occurs. The best results in opening Alpha is when they log off the server and log back in and try it....but does not always work.
It seems like having QuickBooks open influences whether Alpha can open...could be coincidence. The only possible here, IMO, is that having QuickBooks open would cause less computer memory...which, at times, is fairly low (as low as 1000mb Available, 0 free--16 gb total ram). But I can open Alpha without issue when memory is this low.
Some troubleshooting aspects that have been checked out or tried:
All users have exactly the same Windows permissions.
Alpha was installed by choosing "Run as Administrator".
All shortcuts have been changed to "Run as Administrator"...which worked for quite a few times, but failed (error message) the next day.
Verified that prior to trying to connect that there is only one instance of Alpha running via task manager (imagine a different error would occur from RMUF).
Users have rebooted computers.
Terminal Server had been restarted.
'--------------------------------------
The line in red above seems to be the biggest lead as it worked for a short time after doing it.
Could it be a bad install of Alpha on the computers affected?
Could it be that the Terminal Server somehow resets the permissions or ignores them?
I will add more if I try anything else.
Thanks for looking,
Mike
I have a client who has been having issues with opening Alpha Five Runtime version 11 Build 3381, Addin build 4096. The error is "Alpha Five has stopped working" and can be seen in the screenshot attached.
First, has anyone ever run across this problem where it consistently reoccurs...I have seen this message but a few times over the years and closing and reopening Alpha has always resolved it...not this time!
The error code 41244 was obtained by running the debug from the error dialog box...whether this error is the error regarding Alpha or the debugger I do not know. Anyone know the meaning of this code?...it is not listed in the error codes I can get.
Alpha is connected to by 5 users via remote desktop to a Terminal Server.
I and one other can use Alpha with NO issues. Others can only start Alpha say 1 out of 4 times without error. Once started, if they close Alpha and then reopen, the error occurs. The best results in opening Alpha is when they log off the server and log back in and try it....but does not always work.
It seems like having QuickBooks open influences whether Alpha can open...could be coincidence. The only possible here, IMO, is that having QuickBooks open would cause less computer memory...which, at times, is fairly low (as low as 1000mb Available, 0 free--16 gb total ram). But I can open Alpha without issue when memory is this low.
Some troubleshooting aspects that have been checked out or tried:
All users have exactly the same Windows permissions.
Alpha was installed by choosing "Run as Administrator".
All shortcuts have been changed to "Run as Administrator"...which worked for quite a few times, but failed (error message) the next day.
Verified that prior to trying to connect that there is only one instance of Alpha running via task manager (imagine a different error would occur from RMUF).
Users have rebooted computers.
Terminal Server had been restarted.
'--------------------------------------
The line in red above seems to be the biggest lead as it worked for a short time after doing it.
Could it be a bad install of Alpha on the computers affected?
Could it be that the Terminal Server somehow resets the permissions or ignores them?
I will add more if I try anything else.
Thanks for looking,
Mike
Comment