|
Posted by Angelo on December 16, 2005, 8:47 pm
Please log in for more thread options hey glenn, thanks for the reply. I actually came across that KB article
right after I posted here. It was the exact problem I was having, but,
unfortunately it didn't solve my issue. I did check the reg values (after I
ran those scripts) on both machines and they were both set to 2. I not only
started/stopped sql server but rebooted both machines. I am pretty confident
that the issue lies in the server. As I stated above, I set up my laptop as
a test POS register and it has the same problem when pointing to my live
server. The same exact laptop (same settings) pointed to my test server
works perfectly fine. I am pretty much at a loss right now; any ideas,
suggestions, or anything would be great. thanks!
"Glenn Adams [MVP - Retail Mgmt]" wrote:
> 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...
>
> HKLMSOFTWAREMicrosoftMSSQLServerMSSQLServerLoginMode
>
> 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...
>
>
>
> --
> --
> Glenn Adams
> Tiber Creek Consulting
> http://www.tibercreek.com
> glenn@tibercreek.com
> ----------------------------------------------
> Please DO NOT respond to me directly but post all responses here in the
> newsgroup so that all can share the information
>
> >I found KB article 872360 and thought that was the answer. So far didn't
> > seem to work. Will try tonight after closing.
> >
> > "Angelo" wrote:
> >
> >> 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...
>
>
>
|