One of our clients is having trouble getting into Sage, she is getting "error code AUSE099 Unrecognised response" when she tried to do an automatic update. I have tried to remove Microsoft .NET Framework 3.5 SP1 (ask suggested on fixya.com) however this has had no effect. The user clicked "no" to ignore the message however it just closes and doesn't let her in. She is currently running version 18.1.0.12 and the update is 18.1.0.16.
I would say go in the time menu - go time back 1 day before she had that problem. hopefully it helped greetings
I have found good technical information on How to Fix Sage 50 Error Ause099
If you want to troubleshoot you problems with experts then visit here - https://www.accountsportal.co/sage-support-phone-support/
SOURCE: Hello Please can you help. We
This is usually caused by the user not having full rights to the Data directory. right click on the data director select security and you can a click on users network logon and tick on full control
SOURCE: Invalid Path error
I get this error when trying to run Financial reports in Sage line 50 financial controller verson 10: C:\PROGRAM FILES\SAGE\ACCOUNTS\REPORTS\\*TB.SRT contains an invalid path No matter what financial report I try to access I get the same error including audit trail. My computer is window Vista. Please help me and also let me know how much is it cost for on line chat?
Thank you
from selvi
SOURCE: Hi. I am having problems
It sounds like the SBD installer isn't working you need to ensure you have full administrator rights and you can run setupsbd.exe from the program directory
SOURCE: i was working in sage
If you are unable to logon to Sage you can try deleting the Queue.dta
file. All users MUST be logged out of Sage and Sage should not be
running. Sage will recreate the queue.dta file when it is restarted. The
Queue.dta file can be found in the ACCDATA folder for the Sage Company
Data that is experiencing the problem.
Note that the "Username already in use" message from Sage can occur if
Sage wasn't shut down tidily for that users session. If you are sure
that the user is not actually logged in it's OK to allow Sage to clear
the session and log in.
SOURCE: WE have upgraded a sage
hi dmatharu667
this happens when you take a backup of a company that has a accdata folder in the accdata folder and it reports version as v9. To correct this go to data directory go into accdata directory and in that director move or delete the second accdata directory, repeat your backup and it should then restore perfectly
Nigel
4,181 views
Usually answered in minutes!
×