| Event Id | 36865 |
| Source | Commerce Server 2002 |
| Description | Error in Commerce Administration Object : Description - GlobalConfig:Initialize : Login failed for user (null). Reason: Not associated with a trusted SQL Server connection. |
| Event Information | " This message from newsgroup may help you: -------------------------------------------------------------------------------- Resolution: 1) Ive tried connection strings that use local SQL accounts on Server B with the same db rights and access as [DMZCOMAINNAME]\[CommerceServerServiceAccount] and [SERVERNAME]\[CommerceServerServiceAccount] to no avail (the errors keep occurring). 2) Ive tried this connection string: ""Data Source=[IP Address of DB server];Initial Catalog=msib21_commerce;Integrated Security=SSPI"" which then uses ASPNET to connect to the db (permissions for ASPNET are slightly different than [SERVERNAME]\[CommerceServerServiceAccount] / [DMZCOMAINNAME]\[CommerceServerServiceAccount] however the same errors appear in the logs. 3) I noticed there are Component Services for Commerce Server that run under the account of [DMZDOMAINNAME]\[CommerceServerServiceAccount]. Which is why I pose the question above ""In order to properly use CS Interop API to obtain profile data is it required to run under the Commerce Server Service Account that was used to configure / install CS to begin with?"". 4) A Google search indicated it could be related to the MDAC version. I installed and ran a MDAC checker and v 2.8 is on Server A. So I dont believe this is the issue. --------------------------------------------------------------------------------" |
| Reference Links | Event ID 36865 of Source Commerce Server 2002 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.