Sage V21 on NAS

[freedomit]

Just so others know, Sage Accounts v21 now requires the Sage Data Service on the machine/device hosting the data file. I did an upgrade on a client who stored the data file on a NAS and it would no longer open the data file.

My workaround was to create an iSCSI LUN on the NAS connected to one of the PC's and move data file onto that. Sage then thinks the data is local but the benefit of being backed up on NAS. Only downside is that if that PC is turned off then other users lose Sage.

 

[PCSupportGlasgow]

yeah have same problem with a client who had data files stored on a shared folder in sbs2003 (yes i know it EOL but client has a bespoke software app running that would be very costly to move). so anyone with clients running an old server will need to move the data files.

 

[MobileTechie]

This data service thing is a pain.

I've a 2012 Essentials customer and despite installing the service and running it, the client PC won't detect the data service running. We've been through Sage's troubleshooting steps, firewall settings etc etc and neither I nor Sage can get it working.

 

[JustInspired]

This data service thing is a pain.

I've a 2012 Essentials customer and despite installing the service and running it, the client PC won't detect the data service running. We've been through Sage's troubleshooting steps, firewall settings etc etc and neither I nor Sage can get it working.

Does your 'company' file on the workstations contain the server's hostname or IP address? I just had to change a bunch of them to the IP for a client.

 

[MobileTechie]

Does your 'company' file on the workstations contain the server's hostname or IP address? I just had to change a bunch of them to the IP for a client.

Hi

We've tried both and it makes no difference unfortunately, but thanks for the idea.

Sage can't fix it. They're saying it's "the server" but can't be more specific than that other than trying to say it's probably the firewall. But we've tried the firewall ports open, both the PC and the server's firewall off etc and no dice.

 

[JustInspired]

Hi

We've tried both and it makes no difference unfortunately, but thanks for the idea.

Sage can't fix it. They're saying it's "the server" but can't be more specific than that other than trying to say it's probably the firewall. But we've tried the firewall ports open, both the PC and the server's firewall off etc and no dice.

That sucks.
I read (think it was on Spiceworks forum) that one person had to completely reinstall Server 2012 Essentials to get the stupid thing working. Hope that doesn't turn out to be the case for you.