Originally Posted by SoCalFP
.... I rebooted SQL server by Restarting the Main computer, which was also unsuccessful, although introduced an unrelated frustrating loss of network connectivity among computers which was eventually solved by turning every computer and network hardware device off, then brought power up on each one in this order: CableEthernetModem, Router, WAP, Switch, Main, Clients.

I will monitor this forum topic periodically for any further helpful insights.

A couple of things to note here:

>Restart SQL Server from the services interface. You can run services.msc as a short-cut, or go through the Control Panel to the Administrative tools and get to services that way.

>With the recent versions, we are finding that what works reliably for connecting to the AC main machine has changed. The most reliable way to point to the AC database is now via a static IP path. i.e. When AC asks to browse to the main computer, use the static network path ==> \\[192.168.1.100]\Amazing Charts\ insert your machine's IP into the path.

If your AC 'server' isn't on a static IP, it is past time to change it to one.

This also means that mapping AC as a network drive is now out-of-favor as the prefered method.


Indy
"Boss"

Indy's Blog

www.BestForYourPractice.com
Our Name is Our Creed