Offline Dbase Synch gives SQL server not found error

Hey Pete, I am having the same problem. My vendor said that the reason was that i had

1.3 installed in the back office and 2.0 on the pos. I wasnt there friday so i will see today what the deal is i will let you know.

"Pete A." wrote:

If you have MSDE and or SQL Server 2000 on both ends, the issue is almost certainly a firewall problem on the register. Try turning off any firewalls including the Windows XP SP2 firewall and see if the connection starts working. If it does, you just need to enter an exception for SQL Server - see the help files for your Firewall software for specifics.

It looks like from your followup post that you have upgraded the register to 2.0. If that is the case, you may have been upgraded to SQL

2005 Express at the same time. I just posted in another thread with some additional settings to check when using SQL Express - it has a couple of other ways to block incoming connections in addition to the firewall...

Glenn Adams Tiber Creek C> Hi,

Thanks but I already checked the versions and they are identical. I agree that may be a problem though. Glenn Adams suggested switching off the any firewalls on the client, which is a good idea too. I'd already done that but it's worth you checking as I suspect this can be caused by multiple things. If you didn't spot my note earlier another trick (which didn't work for me but may for you) is to hard code main server IP on the client and then stop and start the offline server so it resets the network addresses. I'll let you know if I ever get to the root of this.

Pete

"Doug Pic-N-Pac" wrote:

Just lost a lengthy reply in the ether so apologies if this duplicates. In summary turning off the firewall was a good idea didn't make a difference. We are still on 1.3 refresh and MSDE on all systems. Am going to see if the 1.3 Refresh hotfix makes any difference and try to install the offline dbase on a second POS PC to see if it's a systemwide problem or PC specific. Will let you know how it goes but let me know if you have any more ideas.

Pete

"Glenn Adams [MVP - Retail Mgmt]" wrote:

Try deleting the local offline database and creating a new one from the blank backup. Sometimes it works...

Glenn Adams Tiber Creek C> Just lost a lengthy reply in the ether so apologies if this duplicates. In

Hi Glenn,

Your earlier reply about the firewall ended up solving the problem. Although the message was on the client and the client firewall was disabled I suddenly realized that I should disable the server firewall too and that resolved the problem. Now I just need to figure out how to turn it back on without problems but at least I know what's going on now.

Thanks,

Pete

"Glenn Adams [MVP - Retail Mgmt]" wrote:

I'm going from memory, but try opening port 1433 in the firewall exceptions and see if that does it.

Marc