Shared Database problems

[tjyak50]

Client Act computer is now having problems accessing database.

I just moved my office and hooked everything up just as it was in the old office.

Now my client computer gets the error "Unable to access DATABASE, check connections, blah blah".

I can see the server perfectly through the network.

Spent several hours on phone with tech support and they changed the PAD file on client to show  IP and SQL number of the host which worked for  a few days.  They also made a bunch of other SQL changes which did nothing except make me nervous. 

Now it stopped accessing the databse again.

In all the years I've never had problems accessing any act DB across a network.

Why now?  Killing me.

[tjyak50 · Accepted solution]

Got it squared away (I did).

But I must say the tech support people were very helpful and tried everything.

By rights it should have worked with the IP address and the SQL number and all the exceptions and permissions triple checked and corrected.

In the end I moved my router to a different computer, moved some network connections around and reestablished connectivity and it all started working like magic.  I did put the Computer Name back int he PAD file in lieu of the IP (and SQL #).

No doubt I contributed to the problem.  I just switched to Qwest from Cox and I think the router and modem were fighting each other.

Tj

[klock]

Did Tech Support change any firewall exclusions?

I usually make sure ActSage.exe, sqlservr.exe and sqlbrowser.exe are excluded (I make it on both server and local machines)

Be sure the user has full control over the database folder.

Also - verify that the database on the server is still shared (there was some instances in previous versions, that after a backup was done, it wouldn't be shared anymore).

Just a few thoughts.

[gmartin]

You'll also want to make sure the host machine's IP address has remained the same.  You can open the PAD file with Notepad and compare it to the IP of the server.  If they are different, update the PAD file.

[tjyak50 · Accepted solution]

Got it squared away (I did).

But I must say the tech support people were very helpful and tried everything.

By rights it should have worked with the IP address and the SQL number and all the exceptions and permissions triple checked and corrected.

In the end I moved my router to a different computer, moved some network connections around and reestablished connectivity and it all started working like magic.  I did put the Computer Name back int he PAD file in lieu of the IP (and SQL #).

No doubt I contributed to the problem.  I just switched to Qwest from Cox and I think the router and modem were fighting each other.

Tj