Needed to change a few things in sage corrections and so went into company and corrections, afterwhich I was booted out. Ive been trying to log back in but it says cannot login as (ME) is making error corrections. How do I bypass this??? I think I may have clicked on sort in te corrections field before it kicked me out.
- If you need clarification, ask it in the comment box above.
- Better answers use proper spelling and grammar.
- Provide details, support with references or personal experience.
Tell us some more! Your answer needs to include more details to help people.You can't post answers that contain an email address.Please enter a valid email address.The email address entered is already associated to an account.Login to postPlease use English characters only.
Tip: The max point reward for answering a question is 15.
I installed Sage Payment Gateway over a Magento website last year and got to come the same kind of problem for shipping in UK. I think you need to upgrade your Sage software to PRO if its free one as their free versions are not sufficient enough to get the work done.
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.
Sage 50 has a file called company. that holds the path to the sage Data. From version 2007 onwards this is held in c:\documents and settings\all users\application data\sage\accounts\2010(or whatever version you have)
Sage Line 50 Addpurch Utility
In Sage Line 50 V5, you could only produce remittances for the supplier accounts you had set up in your Sage Line 50 program. The information that appeared on your remittances was taken from the supplier ledger.
In newer versions of Sage Line 50 you can produce remittances for suppliers who do not have a corresponding supplier record. This allows you to produce free-format cheques for one-off payments. To enable you to produce free-format cheques, Sage Line 50 no longer takes the information for remittances from the supplier ledger. This means that you can produce remittances whether there is a corresponding supplier record or not.
If you want to include additional information from your supplier records on your remittances, for example bank sort codes and account numbers, you should convert the layouts you require using this utility.
Note: This utility is installed automatically into your Sage Line 50 program directory when you install Sage Line 50.
>> To use the Addpurch utility
1. Open a Command Prompt by clicking on to your Windows Start Button selecting Run, then type the word COMMAND and click on to OK.
From the command prompt (for example, c:\windows\desktop>) type cd\ and then press ENTER.
2. At the c:\> prompt type cd "Program Files\Sage Accounts\layouts" and then press ENTER.
The prompt should now read c:\Program Files\Sage\Accounts\layouts
Note: If your Sage Line 50 program is installed in a different directory replace the above instruction with your own directory name. The directory path can be found within your program by clicking on to Help and then About and choosing the System Information Tab. Your layouts will be held on the same path as your data directory.
3. Before you can convert your remittance layout you will need to save this with a new filename. (maximum of 8 characters).
For example, to rename one of your existing layouts from the c:\Program Files\Sage\Accounts\layouts prompt type:
copy remita4.sly newrema4.sly
and then press ENTER.
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.
User Name is Already in Use / Cannot Access YYY because XXX is logged in
Typically, when you get this message you will be asked if you want to remove the user from the request list. If you are asked this question, simply answer Yes and you'll be able to continue.
An alternative solution is to go in the data folder for your sage data (the default folder for versions prior to 14 is c:\program files\sage\accounts\accdata for v14, the folder is c:\documents and settings\all users\application data\sage\accounts\2008\company.000\accdata on XP and c:\programdata\sage\accounts\2008\company.000\accdata. In the data folder, you will find a file called QUEUE.DTA - delete the file and you should be able to get back into Line 50. If you have a multi user version of Line 50, you should only delete this file if you are sure that no-one else is using Line 50.
All the back files that was created is on that other machine even while you may think its on that disk in theory YES but physically NO.
Thats why you got this:
Error message keeps coming up which is:
Just one more try the disk you used look on it if it has the 288.pdf file you may be able to read it from the PDF software and then recreate it in the sage financial creater?