A clients 'software' support have loaded a new sage (v22) on the same PC as the old sage (v11), without saving it to a different directory!!!! Its all messed up (polite term) and the only sage that will now open is the v22 as the system thinks an upgrade has been done. So we have been advised to remove both sets of sage and re-install the old one.
Tried to remove, had some problems with that, BUT it looks like its all gone, however I know from something Ive read somewhere that parts of it can, shall we say - linger!
As far as I know there are some of the document folders remaining on the PC - not sure if these need deleting too, and would appreciate a steer as to anything else I need to look for (and how to find it!)
When they tried to load the v1 back on again the following error message occurs...
Hi Joanne. I'm going to suggest doing a system restore to before the new sage was put on. That will get rid of the new version and correct any changes you've tried to do to sort it out.
If you are going to uninstall both ensure that everything has been removed. From memory there are some files left behind, and will affect the re-install oh, just seen you already know about it lol. Look in c drive for anything sage and look in the c/program files as well. Remove the sage directory completely. Daft to say this to you, knowing how meticulous you are, but ensure the backup directory is saved somewhere else before uninstalling/removing folders. As an extra suggestion I would download agent ransack (file manager) and do a search for "sage". It's far more powerful than the windows file manager.
Is this the one you were asking about the other day? I nearly said something but I wasn't sure if I was right. Do you still get an option to set a different install path? I'm a bit trigger happy when I install software because I'm that used to it but I don't remember that you can, possibly since Windows Vista or 7 came on the scene. Vince would probably know more on that score.
__________________
John
Any advice given is for general guidance and professional advice should be sought applicable to your circumstances.
I've never seen that error, so I can only guess. That guess would be that when uninstalling Sage, the uninstall wasn't 'clean', so the subsequent installation is getting in a pickle. And I can imagine an uninstallation of two different versions of the same software that had been mistakenly put in the same location might cause such a pickle.
If it's possible, a better solution than attempting to reinstall Sage might be to use the computer's system restore to restore back to a point just before the support people installed the new Sage. This should only affect programs, not files. (I've never been in a situation where I'd want to use it to reinstate something that has been removed - but if there's a suitable restore point, I'd expect it to work.)
If that *doesn't* work, or isn't possible, if it was me I'd clean all traces of Sage from the Registry before trying again - but I don't recommend anyone does anything like that unless they know what they're doing. You can properly mess things up when playing in the Registry.
TBH, it sounds like these support people made a proper mess of it - so they ought to put it right, IMO. (Did they not think to test what they've done? At that point they would/should have spotted their error and should have put it right there and then.)
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
I can't remember if Sage gives you an option of where to install. I'm sure it used to in the old DOS version days, because I used to install multiple copies to keep previous years' data accessible - but I don't know with modern-ish Windows versions. I've never thought to try it because I've always assumed it would use registry entries to hold key info such as data locations, and that those entries might clash.
__________________
Vince M Hudd - Soft Rock Software
(I only came here looking for fellow apiarists...)
I think PC problems are catching, after this one yesterday and sister in laws last night, Ive had my own PC issues this morning, so apologies for the delay in responding.
Yes this is sort of related to my previous question, although that was me wanting to load the software on to my own PC. Im like you - just press install and dont really look at which directory its going to so decided to wait and see what the so called experts did at my clients before trying it on my PC. So glad I did know as now I know better than ever the problems that can be created! Plus I mightve lost access to my sage!
At the clients - its brand new PCs that the clients IT support peeps have put in, with some configuration done before yesterday and some on site, so fortunately the old software is on the old PC, plus I do have a backup on a USB Stick. But OMG they could have really messed this one up! Especially given its all networked. Im dreading going in on Monday now as they will be back, although apparently its a different tech bod and Ive told all the staff not to let him near ANYTHING until I can go in and get at least another two up to date backups (they work Saturdays and issue loads of invoices on the software every day!) before they even touch it.
A system restore sounds like a plan, thank you, thats my failsafe option but one I didnt consider this time (isnt that always the way??!!) - although there were that many things moved to that new PC from the server before he tackled sage that Im now thinking oh boy I will be sitting there whilst all that lot is done again. BUT, if it needs doing and that sounds like a good way to help then I will just have to sit it out - as long as I dont get the whines that were going on on Friday (was ready to commit hari kari when I came out of there!)
I dont think I would be messing about with the Registry, no way would I trust myself to do that. After seeing the carnage on Friday Im not sure I trust the support peeps neither. I told the owner right form the start that I wasnt getting involved in putting software on his servers etc and that he would need to involve his support and this was all discussed in a meeting with them, so yes they will be made to sort it out. But I sure as hell am going to be there when they do it to make sure I and all the staff on the networked version of sage can do what we need to do. Of course with the PCs being brand new I suppose there could also be the option of restoring factory settings, which I might suggest #.
Ive read about several horror stories about clashing and data corruption from loading more than one sage software but I also know that it is absolutely possible. You do still have the option of a custom install to park it wherever you want. Thanks for the agent ransack tip - I will be taking that one with me.
# reckon I will ring sage support (as client has it, its just that I was going to go in this morning and try to sort it!) and put them on speaker phone whilst they tell the IT 'support' how to sort this!
Dreading Monday. I will be taking earplugs and will be forced to do my filing in any downtime I have, bummer!!!!! Hate filing.
Thanks guys for your input, wish me luck!
-- Edited by Cheshire on Saturday 7th of May 2016 12:20:37 PM
__________________
Joanne
Winner of Bookkeeper of the Year 2015, 2016 & 2017
Thoughts are my own/not to be regarded as official advice,which should be sought from a suitably qualified Accountant.
You should check out answers with reference to the legal position
