Changing server computer help

[ethanaonyx]

Hi,

the company I have recently joined use sage 50 Accounts professional with the sage data service on a computer acting as a server on a network and then client computers with the application running on their pc's and the data is stored on the server.

We have recently bought a new more powerful computer to run as the server to store the sage data on, I am tasked with getting this pc set up on the network to be the new storage server for sage.

I have installed the Sage Accounts Data service to the new machine.

The thing I am stuggling with, is getting the sage client pc's to read the new destination with the whole company and files still the same so not loosing anything.

Any help with this would be great.

I am fairly new with networking.

Thanks,

Ethan

[brucedenney]

First uninstall the data service, it is not a good way to work.

Make a full backup from your old system.

Install the Full Sage 50 Accounts product on the server, this includes the data service and has the advantage of a UI that will do updates so is a lot easier to maintain going forwards.

Open Sage 50 and create a company by restoring your full backup.

During this process Sage should make a file share for your data on the server

On each of the existing workstations go to c:\programdata\sage\accounts\2xxx where 2xxx is the version you have

You can now do 1 of 2 methods

Method 1
=========
Rename the files company and company.unc (company.unc might not exist)
When you open sage on this workstation it will now ask for a data location
browse to the new server share and connect to the data.

Method 2
=========
Open company with notepad
Change the path to the new server
repeat with company.unc

Test it has worked.

Now you have a company and company.unc file, you can copy these to other workstations rather than editing them on each.

[ethanaonyx]

Hi brucedenney,

Thank you very much for your help.

However we already have the system working with a machine running the sage data service and this is the way i am told we would like to continue working

As by installing the full sage 50 accounts product on the computer would require an added license no?

I have set the new server up sharing the folder with the sage data and mapped this network drive and have checked the permsission and it should be set so everyone has access without a password needed.

When i got to sage and remove the old company and add new and then add from existing on network and choose the new pathway to new mapped network drive when i go to the accdata folder and click ok sage freezes and cant do anything. I have left it a while thinking it is maybe connecting for the first time so might take a while but no it isnt doing anything i then force close it and go back in and add a new company connecting it back to the old server and this works instantly first time.

This leads me to believe it is either an error with the data service on the new machine but it works on the older one, or a problem with permissions on the new network drive.

Any help with this would be great.

Thanks,

Ethan

[brucedenney]

If your way doesn't work I respectfully suggest you try my way, it is much easier to set up and maintain

[ethanaonyx]

Thanks Bruce,

I respect that and may be forced to use your way, the only thing is that it would require paying for a new license. We have it working in this way already just baffled as to why the new machine will not work in this way.

This is why my superiors are reluctant to gain another license as they know it works without it so should work again and in theory it should.

However if I cant get it working in this way again then the only way will have to be the way you suggest.

Thanks,

Ethan

[brucedenney]

Why would you need to buy a new licence?

My method does not require any change to your licensing.

I think you may not understand how the licensing works.

Sage 50 Licensing is per concurrent user. You can install even a single user copy on as many desktops as you on a network like and create as many user names as you wish, the limitation is simply how many users can log in at one time.

The server install would only have a user logged in on it when you were updating, or if you wanted to run something that was very slow on a workstation and wanted to take advantage of the improved performance of running on the server.