Start a conversation

Aurea CRM Interface 15.25.2: Windows Domain (SingleLogin) Authentication Fails with 10043 / Err: -13

Contents

Overview

After upgrading Aurea CRM Interface to 15.25.2 (example build: 15.25.2.3174), authentication using Windows domain / Windows username can fail for all users through the CRM Interface SingleLogin path.

This issue was confirmed as a version-specific regression introduced in 15.25.2 (not seen in 15.25.1 or earlier). Engineering has implemented a fix that will be included in the next official release after 15.25.2 (exact version not specified).

Solution

1) Confirm the error signature

You are likely encountering this regression if, immediately after upgrading to Aurea CRM Interface 15.25.2, domain/Windows authentication fails and you see one or more of the following.

XML response error:

return type="error" func="C_Portal::XmlDoLogin" code="10043" text="Login error"

CRM Interface log error (in u8_interface.log):

SingleLogin failed! Err: -13

In some contexts, the XML error may appear as -10043.

2) Check affected versions

  • Affected: Aurea CRM Interface 15.25.2 (observed build: 15.25.2.3174)
  • Not affected (workaround baseline): 15.25.1 or earlier
  • Fix status: Engineering confirmed the regression and implemented a fix to be delivered in the next official release after 15.25.2 (exact version not provided).

3) Validation checks (to narrow down and rule out common confounders)

Use the checks below to confirm you’re seeing the same regression and to rule out common environment-related causes.

  1. Prove it’s version-specific (optional but strong evidence)
    • If possible, run 14.4 and 15.25.2 against the same server environment (same host, similar configuration, comparable database connectivity) and repeat the same login test.
    • If 14.4 succeeds and 15.25.2 fails with 10043/-10043 and Err: -13, that strongly indicates a regression rather than an environment issue.
  2. Validate the identity mapping CRM.interface is attempting
    • Confirm the affected user’s CRM login and the configured Windows username + domain values in the user (US) record.
    • Re-test using the CRM Interface Test Application with the same values used in production:
      • user=<windows_username>
      • domain=<domain>
    • Capture the full XML request and full XML response.
  3. Confirm you are testing the correct endpoint everywhere
    • Ensure the exact same CRM.interface URL is used in the test tool and in any connector/configurator.
    • Example format: http(s)://your_instance.domain.com/CRMInterface/xml
  4. If using HTTPS, validate the SSL/TLS trust path
    • Open the CRM.interface URL in a browser on the same machine that is making the request and confirm there are no certificate warnings.
    • If using an internal CA, ensure root/intermediate CA certificates are installed on the calling host.
  5. Collect logs from the same reproduction attempt
    • u8_interface.log
    • u8_iis_interface.log
    • Look specifically for SingleLogin failed! Err: -13 and the related XML login error 10043/-10043.
  6. Time sync evidence (to conclusively rule out -10043 time drift scenarios)
    • Provide current date/time + timezone (or NTP status output) for:
      • (a) calling machine
      • (b) CRM.interface server
      • (c) domain controller

4) Resolution / Mitigation options

This behavior is a confirmed 15.25.2 regression affecting Windows domain authentication (SingleLogin). The options below are the practical mitigation and the long-term fix path.

Option A (recommended workaround): Use CRM.interface 15.25.1 or earlier

  1. Install/deploy Aurea CRM Interface 15.25.1 or earlier (in place of 15.25.2).
  2. Point it to the same backend configuration as before (same mm.ini/settings.xml patterns used in your environment).
  3. Re-test domain login using the CRM Interface Test Application against: http(s)://your_instance.domain.com/CRMInterface/xml
  4. Verify the response is no longer an error and that u8_interface.log does not show: SingleLogin failed! Err: -13

Option B: Upgrade to the next official release that includes the fix

Engineering indicated the regression is fixed and will be included in the next official release after 15.25.2 (exact version not specified). When that release becomes available:

  1. Upgrade CRM.interface to the fixed release.
  2. Re-test the same domain login scenario and confirm the XML response is successful (no 10043/-10043).
  3. Confirm logs no longer show SingleLogin failed! Err: -13.

5) Verification checklist (post-change)

  • CRM Interface Test Application login using <windows_username> + <domain> succeeds.
  • No XML response containing: func="C_Portal::XmlDoLogin" code="10043" text="Login error"
  • u8_interface.log does not record: SingleLogin failed! Err: -13
  • If applicable, connector/configurator authentication also succeeds using the same endpoint URL.

Additional context

It was observed that Aurea CRM Interface 15.25.2 introduced significant SSO-related changes; this issue is consistent with those changes and was confirmed as a regression in the Windows domain authentication (SingleLogin) path.

Frequently Asked Questions

1. How can this be identified quickly?
Look for the exact XML error return type="error" func="C_Portal::XmlDoLogin" code="10043" text="Login error" (sometimes -10043) and the interface log line SingleLogin failed! Err: -13 immediately after attempting domain/Windows authentication in CRM Interface 15.25.2.
2. Which versions are affected, and what’s the fastest workaround?
The regression was confirmed in 15.25.2. The fastest workaround is to run CRM.interface on 15.25.1 or earlier until the next official release containing the fix is available.
3. We already checked time sync, rights, and configuration—what should be provided if escalation is needed?
Provide (1) full XML request/response from the CRM Interface Test Application using the production user/domain values, (2) the exact CRM.interface endpoint URL being tested, (3) both u8_interface.log and u8_iis_interface.log from the same failed attempt, and (4) date/time/timezone (or NTP status) for the calling machine, CRM.interface server, and domain controller.
4. Does HTTPS/certificate trust matter for this symptom?
If you are calling CRM.interface over HTTPS, certificate trust problems can surface as authentication-like failures. Verify the CRM.interface URL opens without certificate warnings on the same machine making the request, and ensure internal CA chains are installed if applicable.
5. How do we verify the fix after upgrading to the next release?
Repeat the same domain login test. Success means no code="10043" text="Login error" in the XML response and no SingleLogin failed! Err: -13 in u8_interface.log.
Choose files or drag and drop files
Was this article helpful?
Yes
No
  1. Priyanka Bhotika

  2. Posted

Comments