03-02-2012 05:03 AM
I am running Windows 7, 64-bit and Sage ACT Premium 2011.
The software freezes within 2 minutes, right on time, each time I load it.
Typically I will run a report and it freezes right awar the report is completed. However, it doesnt really matter what I'm running. It will freeze even if I am not using it.
03-05-2012 07:50 AM
Can you provide some additional information about the situation:
- Is this a shared database?
- If yes, are other users experiencing the same thing?
- Is this database saved locally on your computer? Or is it on a server?
- If on a server, are you able to open it (without it locking up) on the server or another workstation?
- Open the demo database to test. Does the demo also hang?
03-13-2012 05:27 AM
Thanks for the reply.
I believe this is a shared database on our server. About 10 other people are using this I believe and I'm the only one with a problem.
I've run the demo database and it seems to run perfectly fine.
When I go to close the application Windows ask if I want to close the program or check online for a solution. Clicking either one just close the program.
The details of this problem are:
A problem caused this program to stop interacting with Windows.
Problem Event Name: AppHangB1
Application Name: ActSage.exe
Application Version: 13.0.401.0
Application Timestamp: 4c6cde36
Hang Signature: 8908
Hang Type: 256
If I let the program sit for a while, whilst frozen, this is the report I get:
Problem Event Name: CLR20r#
Problem Signature 01: actsage.exe
Problem Signature 02: 13.0.401.0
We uninstalled and reinstalled the software but did not fix the problem. I'm thinking the next thing to do will be to "sweep" the computer and reinstall everything and start from scratch as I am the only one with a problem.
I thought I had heard that it may have a problem with 64bit but again, I'm not the only one with 64bit.
What are your recommendations?
03-13-2012 07:33 AM
03-13-2012 12:03 PM
On the other computer my logon freezes.
So... we removed my account from the server and then added it again.
It seems to have fixed the problem. However were unsure of what caused the problem.
Thanks for your help. It worked out really well.
03-13-2012 12:09 PM