Liveware Publishing Support Forum

We have been doing a bit of rearranging of our domains. Temporarily our database server is not in the same domain as our users so we abandoned integrated security and went for SQL login.____This works fine for most users but for a limited number the runtime reports launched from our app insist on trying to logon using integrated security instead of popping up the SQL login with the user name in it.____I cant see what is different about these machines. The odbc setup looks the same.____I realise that this isnt really an RR issue but wondered if anyone could point me in the right direction.____Many thanks

Is it dependent upon as the logged in user as well as the actual machine? Maybe that would be a clue.____Kathleen__R&R Support

Hi Kathleen hope you are well.__I never really figured this out. Yesterday I installed R&R on a new machine. Until the install the regular application based runtime reports had been working fine but now it gives an authentication error along the "not a trusted user" line.__Does this give any clu as to where I might look. I^m thinking maybe its down to a DLL version ?__

It would in theory be based on how the ODBC data source is set up.__If it is the Microsoft SQL Server driver, one of the configuration screens aks whether NT or SQL Server authentication should be used.____Kathleen__R&R Support