Commerce Server Setup - SQL is seperated from CS02

This is Interesting: Free IT Magazines  
Home > Archive > Commerce Server Setup > February 2004 > SQL is seperated from CS02





You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

Author SQL is seperated from CS02
newsgroup user

2004-02-07, 9:37 am

Keep getting following error message when we seperate SQL from Commerce (Web) servers
Anybody knows why? ...

Error in Commerce Administration Object : Description -
'SiteConfigReadOnly:Initialize : Login failed for user '(null)'. Reason: Not
associated with a trusted SQL Server connection.'
Ryan Ross

2004-02-07, 9:37 am

You need to setup Active Directory. Create global ASP.NET, IWAM, and IUSR
accounts. Assign them the proper permissions in SQL, and then tell Commerce
Server to use those accounts instead of the defaults (or installed ones). I
think the ASP.NET account trying to access SQL causes that particular error.
Good luck with that one ;).

Ryan


<Po-Shan Chang> wrote in message
news:6956EFFA-4296-4F61-936B-D0159008861C@microsoft.com...
> Keep getting following error message when we seperate SQL from Commerce

(Web) servers
> Anybody knows why? ...
>
> Error in Commerce Administration Object : Description -
> 'SiteConfigReadOnly:Initialize : Login failed for user '(null)'. Reason:

Not
> associated with a trusted SQL Server connection.'



Eric Tremblay

2004-02-07, 9:37 am

Also, if you are trying to acces the site using your own credentials
(Windows Authentication) make sure that Kerberos is working properly.
Otherwise, you can only access the site using Basic Authentication.

Eric




"Ryan Ross" <ryanr@nni.com> wrote in message
news:100jr2d7d8l8a67@corp.supernews.com...
> You need to setup Active Directory. Create global ASP.NET, IWAM, and IUSR
> accounts. Assign them the proper permissions in SQL, and then tell

Commerce
> Server to use those accounts instead of the defaults (or installed ones).

I
> think the ASP.NET account trying to access SQL causes that particular

error.
> Good luck with that one ;).
>
> Ryan
>
>
> <Po-Shan Chang> wrote in message
> news:6956EFFA-4296-4F61-936B-D0159008861C@microsoft.com...
> (Web) servers
> Not
>
>



Sponsored Links






Free braindumps | Software forum | Database administration forum

Copyright 2003 - 2008 webservertalk.com