Offline Sync Error

Hey all, I am receiving a "login error for user sa" everytime i z out and the offline db tries to sync with the main db. The main db is located on another server, while the offline db is located on the register machine itself. Both dbs connect successfully from within the Administrator application. The register works successfully with the main db, and when disabling the connection to the main db, it successfully uses the offline db. Also, I created a different user to connect to the offline db (not sa), so it seems that it is getting this login error trying to connect to the main db. The main server is xp prof, while the register is xp home running msde. Any ideas? Thanks.

Reply to
Angelo
Loading thread data ...

btw, the actual error is: Login failed for user 'sa' Reason: Not associated with a trusted SQL Server Connection.

Not sure why it works fine when using the POS system, but not on syncing...

Reply to
Angelo

Reply to
Angelo

Angelo,

Change the server machine to a static IP address and then change the server name in SO Admin of each register machine to the IP address of the server.

Reply to
Jeff

Reply to
Angelo

Angelo,

Any firewalls running on either machine? If running XP SP2, open the Windows firewall using these instructions;

formatting link

Reply to
Jeff

Reply to
Angelo

That error seems to be indicating that SQL Server or MSDE was installed with the "Windows Authentication" option rather than "Mixed Mode", which is what KB872360 is trying to address. Did you run the statement from the KB on ALL systems, including the server?

There is a registry entry that you can check to see the current authentication mode, but the SQL from the KB should have updated this...

HKLM\SOFTWARE\Microsoft\MSSQLServer\MSSQLServer\LoginMode

In Mixed Mode (What you want it to be) this registry entry will have a value of 2. If you see any other value in that key, try the instructions from the KB again - make sure you stop and restart SQL Server...

Reply to
Glenn Adams [MVP - Retail Mgmt]

Reply to
Angelo

Angelo,

Re-reading your original message again, while it shouldn't make a difference, delete and re-create the offline database again. This time use the "sa" user name. There is no need to use anything different. Make sure you follow the instructions in this KB article;

formatting link

Reply to
Jeff

Actually, I did create the db using the sa user (many times,actually). What I meant to say in the original post is that I used different sql server account logins(created new ones and gave permissions to dbs) on the configuration tabs for the offline and main db, so that I would know where the logon failure was occuring (locally or remotely). One thing i did do though, is created an offline db on the main server (I know, not supposed to do that) and it syncs fine to the same server...which leads me to believe somehow this Windows authentication issue still exists(from kb article

872360). But I know those reg values are correct...

"Jeff" wrote:

Reply to
Angelo

Angelo,

I don't use XP Home, but I remember something about Simple File Sharing in Pro having some issues with Home. Try adding the user name of the Home machine into the user group on the Pro machine and turn off Simple File Sharing. Restart both and log into the Pro machine from the Home machine manually.

Reply to
Jeff

Reply to
Angelo

If I understand this correctly, you are not using sa to connect to the server. If that is correct, first just switch to the sa account to see if it fixes the problem (This is on the Database tab - connection to the Server).

The offline database syncs by creating a linked server object. You need a fairly high level of access (way beyond DBO on the database) to create a linked server - switch to sa and see if that helps, then you can check out SQL Server Books Online to find exactly what server role you need to be in...

Reply to
Glenn Adams [MVP - Retail Mgmt]

Angelo,

That could be an issue! ;-)

Glad you worked it out.

Reply to
Jeff

BeanSmart website is not affiliated with any of the manufacturers or service providers discussed here. All logos and trade names are the property of their respective owners.