Need more, need help now?
- - - - - - - - - - - - - - - - - - pay-as-you-go support - no contract - tenth of an hour billing - expert help - fast service - no call queues
Need integration?
- - - - - - - - - - - - - - - - - - with your shipping system - website - invoicing system - crm - cms - manufacturing - order import - back to back orders..
Need a report?
- - - - - - - - - - - - - - - - - - Excel reporting that pulls data from Sage - custom layouts - layouts that change adapt to your brands and/or for drop shipping.
Want web hosting?
- - - - - - - - - - - - - - - - - - Your own domain name - email - a shop - wordpress - woo commerce - ticket systems - help desks - forums - portals

Line 50 Pro V9 - Common.js Problem

Sage 50 general help forum - Free help and support for all general issues
Post Reply
nozalls
User
User
Posts: 3
Joined: 18 Apr 2011, 16:28
Sage Version: V08 UK/Europe/Africa

Line 50 Pro V9 - Common.js Problem

Post by nozalls » 18 Apr 2011, 16:48

Previously known as Financial Controller (rather than Pro).

Anyway, we have been running this program for years! Problem free.
We have been running the program on XP since for a hell of a long time and having just bought a new computer to replace the one with Sage on I have re-installed V9 but on restoring the data it gets half way and then common.js throws up the fault and it will not restore past this point.
i.e. I have all Product, Customers, SOP, POP information etc but other information is missing.

With that in mind, yes I know V9 is old but we would need to upgrade to the Line 50 Accounts Professional 2011 version which is rather expensive baring in mind we have just splashed out on several bits of equipment so sticking with V9 is preferred.

Is there a way to produce a successful data restore?
Helpful advice will be greatly appreciated.

Many thanks

leyburnsolutions
User
User
Posts: 132
Joined: 14 Apr 2011, 18:02
Sage Version: v2014 20 UK/Europe/Africa

Re: Line 50 Pro V9 - Common.js Problem

Post by leyburnsolutions » 18 Apr 2011, 17:18

common.js is not a Sage file (I believe that it is a javascript file) so I'm not sure why it would be part of the backup...

Do you still have Sage installed on the other PC? If so, go into Sage and do a 'Data Files only' backup and see if that restores on the other PC.

With regards to v2011, I believe that Sage are currently running a campaign to get users to upgrade at vastly reduced prices.

John

nozalls
User
User
Posts: 3
Joined: 18 Apr 2011, 16:28
Sage Version: V08 UK/Europe/Africa

Re: Line 50 Pro V9 - Common.js Problem

Post by nozalls » 19 Apr 2011, 08:25

Hi John

Thanks for the advice (and info about Sage). Strangely it doesn't seem to like that either. Throws up the same error about being unable to create common.js
I think a downgrade to XP is on the cards. It might be an old system but it worked perfectly.

Cheers

leyburnsolutions
User
User
Posts: 132
Joined: 14 Apr 2011, 18:02
Sage Version: v2014 20 UK/Europe/Africa

Re: Line 50 Pro V9 - Common.js Problem

Post by leyburnsolutions » 19 Apr 2011, 08:57

The error message should include the full path to the common.js file - see if it actually exists in the path and, if it does, delete it and try the restore again.

John

nozalls
User
User
Posts: 3
Joined: 18 Apr 2011, 16:28
Sage Version: V08 UK/Europe/Africa

Re: Line 50 Pro V9 - Common.js Problem

Post by nozalls » 19 Apr 2011, 10:03

Thanks again. Just checked back in here and seen your reply.

I managed to solve it. In Windows 7 there is a feature to make non-compatible software work on what is effectively Window XP but only for that program. I didn't know that until I played around after 10 minutes. Having made that change the restore worked.

Once again, thanks for your help John.

User avatar
brucedenney
Site Admin
Site Admin
Posts: 4664
Joined: 28 Feb 2006, 09:56
Sage Version: v30 UK/Europe/Africa

Re: Line 50 Pro V9 - Common.js Problem

Post by brucedenney » 21 Apr 2011, 11:03

For Vista and Win7 installations, the easy solution is to install into a non standard path.

common.js is part of Sage V9, it is some script that runs in a the browser that sage uses to render some of the application, obviously, this is a security risk, and Win 7 doesn't allow this sort of thing to happen in the Program files directory, by installing outside of the program files directory, you avoid that whole layer of security.

It is worth noting that the security is there for a reason and that is is a potential and very small risk.
For just about anything Sage :- Discount subscriptions, pay-as-you-go support, application integration, reports, layouts, linked excel spreadsheets, analysis or any other help making life with sage easier/less time consuming Contact me.

Post Reply

Who is online

Users browsing this forum: Google [Bot] and 3 guests