Sage Drive Issue

-
A customer recently called with an issue they were having with Sage 50 Accounts.

When they would fire up the application it would give the following error: "An error has been encountered with your Sage ID", as shown below:


Unfortunately, hitting "Retry" did not allow the correct Sage Drive credentials to be entered.
A phone call to a nice fella in Sage support yielded the following:

https://ask.sage.co.uk/scripts/ask.cfg/php.exe/enduser/std_adp.php?p_faqid=33481

The gist of it is:
  • Stop 2 x Sage Accounts services
  • Delete a folder called "Collaborate" which is buried down in subfolders of Windows
  • Start the 2 x services, and then 
  • Launch Sage
You will then be able to enter the correct Sage Drive credentials and all should be well with the world.


Comments

Post a Comment

Popular posts from this blog

Evolution MK-249C MIDI Keyboard Mac OS X Problem

-
Mac OS X generally seems capable of dealing with just about anything you can throw at it. However upon connecting my trusty Evolution MK-249C MIDI keyboard up to my 2nd generation MacBook it steadfastly refused to play ball. This keyboard has always been instantly recognised by Windows XP and so it was surprising to encounter this. The M-Audio website (M-Audio took over Evolution it appears) offered no real assistance. There was no driver available for Mac OS X 10.4.9 as the keyboard is supposed to be "Class Compliant" which apparently means it doesn't need one... strange. Eventually after consulting some forums I found the fix. The problem seems to be related to Mac OS on the Intel MacBooks. There is a patch on the M-Audio site but only for MacOS 10.1.5. This must be downloaded and installed. Here is the link: http://www.m-audio.com/index.php?do=support.drivers&f=596 Upon restarting the OS the keyboard was recognised by Mac OS and GarageBand had no trouble tal
Read more

Where are SCANPST.EXE and/or SCANOST.EXE?

-
Image
I sometimes have to deal with customer computers whose Outlook PST or OST files have become corrupted.  Very often the fix is to run SCANPST.EXE on the offending PST/OST file.   However, every time I go to do this I forget where the two executable files are.  Here is where they are on a Vista machine running Office 2007: C:\Program Files\Microsoft Office\Office12 I hope this helps.
Read more