Hello Charleygirl77,

Thanks for reaching out! I've forwarded this request to the Sage 50 US Support Team to try and setup a callback. I assume this is for the account UPM #400xxxx618. We'll update you as soon as possible.

Warm Regards,
Erzsi

When we finally talked to a tech about the same issue here is what they said:

• Fatal File Error #43 is unavoidable with Sage Drive. If you want to use Sage Drive, be prepared to have this continue to happen.  There’s nothing to fix it.  It’s because it’s going over the internet.  Doesn’t matter if you’re hard wired, or on a fast pipe; doesn’t matter if it’s a tower or a laptop.  It’s just Sage Drive is completely unstable. Tech guy: “The only option is to never use Sage Drive, install it on a local server, and map to the local server.” “We bought it because it’s supposed to be a cloud solution.” “It is, ma’am, it’s just that you’re always at risk if you use Sage Drive.
• This time Amanda’s Fatal File Error #43 had a different file associated with it – it wasn’t the audit trail, it was some journal one. “It’s because you’re using Sage Drive.  Ma’am, if you use Sage Drive, you’re at risk for this happening.  The only guarantee that it won’t happen is to not use Sage Drive.”
• Sage Drive plus a Server isn’t a thing.  The tech guy had no idea why we would have a computer set up as a server while also using Sage Drive.  “You either use a server, or you use Sage Drive. You don’t have them both. I don’t know why someone told you to do that.”
• We don’t have a support plan that can get us guaranteed call backs.  If we want to pay extra, we can get better tech support.  What we paid for doesn’t guarantee it.

I tried everything including making one of the computers a server based on the suggestion of a previous tech. We have done everything just to keep two computers talking to each other and this has cost us a lot of time and a lot of money. This keeps us from providing healthcare to more people across Chicago which is not great. Our solution is to see if there is a higher level of Sage that would work, while trialing all the potential accounting software at on the market and reading A LOT of reviews. I would suggest the same.  

We do use Sage Drive. We have discovered that you must have good internet service at both locations and good computers on both sides to have a successful outcome. 

We have one client that we just could not connect to on a regular basis, yet we have no trouble with others.  

If you want to keep it in house, my suggestions would be to set up a terminal server or remote desktop.   

If you want to access your software from anywhere, we do offer Sage 50 hosting services.  If you are interested, please give me a call.  Shirley Byard, Owner Best Business Strategies. 304-233-2612.

I ran into the same problem a long time ago in testing it out and after getting the Error 43 three out of four times I decided it's far less trouble just running a backup and sending it by way of a secure portal and then just restoring.  I do this with all my clients who are running Sage.  Nobody has time to screw with these kinds of failures.  I agree the root case has to do with internet transmissions.  On rare occasions get the fatal I/O errors and these I am convinced also have to do with internet transmissions because the only companies I have seen these on that I can recall were on companies where we send backups back and forth over the internet.  

I really don't understand why there isn't a way to do this without the corruptions or perhaps I should say why Sage has not figured out a way to do this without so many corruptions.  They charge extra for a process that does not work well and as far as I am concerned that is a bad business practice.