Offline synchronization error

K

Kris 19 years ago

We just upgraded to 2.0. We upgraded our OFFLINE database to 2.0 also. After I run a Z report on the networked computers, the following happens:

The synchronoization window is open and shows folders floating from the left to the right and the window says: "Synchronizing table: Alias", it stays on this for a couple of minutes and the following error message pops up:

Run-time error '-2147217900 (80040e14)': OLE DB provider "SQLNCLI" for linked server "(null)" returned message "Login timeout expired

I've seen others have had this problem, and Akber and Glenn have made suggestions for fixing the problem, but nothing worked for the other folks. I have tried turning off firewalls, I've configured the SQL Server Surface Area tool as suggested and Configuration for Features as suggested. But still getting the problem.

I thought deleting the offline database through Administrator and making a new one might help, but rather than create a new one, it automatically "recovered" the old one. I tried offline sync with that, it still didn't work. Should I delete the OFFLINE database and then go into the MSSQL folder and delete it also - how can I truly delete it so when I create a new one it doesn't try recover the old one? Would that even matter?

Any other suggestions?

Vote

A

Akber Alwani 19 years ago

HI Kris, if you have already upgraded to POS2.0 my suggestion to use blank database for the offline as there is no need really to upgrade the offline

2.0 database as it is just a snapshot of your reall data with some informations. So create first the blank new offline database and save the information of new db to configuration. Then run the Z I believe this will solve the issue the next important thing which I like to say is that check your database collation for both offline and your actual real data.

In SO Admin once connected to db then go to Database > then Click Change Collation Check what the server and datbase collation are ?? then click the cancel button as you not changing the collation here. Do the same thing with offline db. If different than your actual db collation change it as it is with your live data.

Then try the Z out. Hope this will work.

"Kris" wrote:

Vote

G

Glenn Adams [MVP - Retail Mgmt 19 years ago

Make sure you installed the local DB using MIXED MODE Authentication - SQL Express defaults to Windows only authentication which will not work with RMS.

Recheck your firewalls on both sides. If you have third party firewalls (Symantec or McAfee for example) make sure that the firewall built into Windows is ALSO turned off - the 3rd party tools try to turn it off, but they are not always successful.

Glenn Adams Tiber Creek C> We just upgraded to 2.0. We upgraded our OFFLINE database to 2.0 also.

Vote

K

Kris 19 years ago

Final note: Raymund at Microsoft solved my problem. For the computers to work offline we had to use the IP address of the database server as the Offline Server Name, rather than (local). If someone has the same problem, note the IP address of the server (Start:Run:type in cmd:type in ipconfig) then use that IP address rather than (local) in the Store Ops Config Manager. Hope this helps someone.

Vote

Y

Yuri Bey 18 years ago

I got the same problem right after updating Windows Xp Pro Sp1 to Sp2 and RMS1.2 to 1.3 on both Main server and on backup server. Using IP address instead of the server name did not help. So, I am open for more suggestions.

Yuri

"Kris" wrote:

Vote

K

Kris 18 years ago

We had the error again and Ken from Computer Associates helped me out. We did the following:

Windows Firewall: Exceptions: Add Port: Name: SQL 1433, Port#:1433, select TCP, Add Port: Name: SQL 1434, Port#: 1434, select UDP

This immediately fixed my problems. We don't even need to use the IP addresses anymore, we switched back to the computer names.

Vote

Y

Yuri Bey 18 years ago

Thanks, It works now.

Yuri

"Kris" wrote:

Vote

Offline synchronization error

Join the Discussion

Didn't find your answer?