
Completed
Posted
Paid on delivery
I need assistance with an SSRS report that's failing due to a data source connection issue. Details: - The report is connected to a SQL Server database. - The error encountered is an authentication failure. Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'. Reason: Token-based server access validation failed with an infrastructure error. Check for previous errors. [CLIENT: 1.2.3.4] Error: 18456, Severity: 14, State: 11 Ideal skills and experience: - Strong expertise in SQL Server and SSRS - Experience troubleshooting data source connection issues - Familiarity with authentication mechanisms and resolving related errors Looking for a freelancer who can quickly diagnose and fix this issue.
Project ID: 40754168
57 proposals
Remote project
Active 7 days ago
Set your budget and timeframe
Get paid for your work
Outline your proposal
It's free to sign up and bid on jobs

Hello, I can diagnose and resolve the SSRS data source authentication failure causing the report to return SQL Server error 18456, State 11 and the `NT AUTHORITY\ANONYMOUS LOGON` message. I’ll trace the connection path from SSRS to SQL Server, verify the configured data source and authentication mode, and identify where the Windows authentication token is being lost or rejected. I’ll check the SSRS service account, report execution context, SQL Server security configuration, SPN/Kerberos delegation requirements, and any intermediate server involved in the connection. Rather than applying a temporary workaround, I’ll correct the underlying configuration and then validate the report using the same execution scenario that currently fails. I’ll also document the root cause and the configuration changes made so the setup remains understandable for future maintenance. If access is available, I can begin by reviewing the SSRS data source settings and relevant SQL Server/SSRS logs, then narrow the issue down systematically. Looking forward to work with you. Thanks
$80 USD in 1 day
4.4
4.4
57 freelancers are bidding on average $150 USD for this job

I got you! I can quickly diagnose and fix your SSRS SQL Server authentication failure, especially the NT AUTHORITY\ANONYMOUS LOGON / Error 18456 State 11 issue, which often points to credential delegation, datasource settings, or SPN/Kerberos configuration. I’m ready to handle the exact SSRS connection setup, verify permissions, test authentication flow, and get the report running again. I’m young, a fast learner, and available 24/7 for quick troubleshooting. Get the demo first before you pay. A couple of quick questions: Is the SSRS report using Windows Integrated Security, stored credentials, or a shared data source? Are SSRS and SQL Server hosted on the same server or separate machines? Let’s chat and discuss the answers so I can start fixing it right away. Kind regards, Haroon Z
$250 USD in 1 day
5.6
5.6

I can quickly diagnose and resolve your SSRS/SQL Server authentication issue, including the "NT AUTHORITY\ANONYMOUS LOGON" / Error 18456 problem and Windows/SQL authentication configuration. I have experience troubleshooting SSRS data sources, credentials, Kerberos/delegation, and SQL Server connectivity, and can identify the root cause and implement the fix efficiently.
$60 USD in 1 day
5.7
5.7

Hello I checked your project, and the main issue appears to be an SSRS-to-SQL Server authentication failure involving NT AUTHORITY\ANONYMOUS LOGON, commonly caused by Kerberos delegation, SPN configuration, or an incorrect service account. In the past, I have worked with SQL Server and SSRS data source troubleshooting, including authentication, report server configuration, and database access problems. I would review the SSRS data source settings, execution account, SQL Server error logs, and Windows authentication path. I would then verify the service accounts, SPNs, and delegation settings to identify where the token validation is failing, while keeping the existing report structure unchanged. Could you share whether SSRS and SQL Server are hosted on separate machines, and whether the report uses Windows Integrated Security? This will help confirm if the issue is related to the Kerberos double-hop. Best regards
$999 USD in 9 days
5.3
5.3

Hi, I can investigate the SSRS data source failure and trace the authentication path between SSRS and SQL Server to identify where the login token is being lost. The `NT AUTHORITY\ANONYMOUS LOGON` and Error 18456 State 11 indicate that the authentication flow needs to be checked carefully rather than simply changing the database credentials. I’ll review the SSRS data source configuration, service account, SQL Server connection, authentication mode, and relevant server logs. If the environment uses Windows Integrated Authentication across separate servers, I’ll also check the Kerberos/SPN and delegation configuration that may be involved. Once the cause is identified, I’ll apply the smallest appropriate configuration change and verify that the report can connect to the database and execute successfully. I have hands-on experience with databases, network troubleshooting, APIs, and system configuration, and I’m comfortable working through logs and connection flows to isolate technical issues. Please provide the SSRS/SQL Server topology and the relevant error logs, and I can start by tracing the authentication path. Regards, Ioannis
$100 USD in 2 days
5.4
5.4

⚠️ If you're not happy, you don’t pay. ⚠️ Hi Client, thank you for checking my proposal and sharing the detailed project brief. I can resolve your SSRS report connection issue using SQL Server with a fast and efficient approach. I will deliver: • Diagnosis of the authentication failure • Resolution of the "NT AUTHORITY\ANONYMOUS LOGON" error • Configuration of appropriate authentication mechanisms • Testing to ensure successful data source connectivity • Documentation of the troubleshooting process for future reference You will also receive: • A brief training session on managing data source connections I am confident I can execute your vision professionally and efficiently. Looking forward to discussing timeline and next steps. Best regards, Chirag Pipal
$150 USD in 14 days
4.3
4.3

Perfect Match "SSRS SQL SERVER AUTHENTICATION FAILURE" — the report is reaching SQL Server but the connection is failing because the expected user identity is not being passed correctly. I’d trace the SSRS data source, report server credentials, delegation settings, and SQL Server authentication path to find where ANONYMOUS LOGON is introduced. Then I’d make the smallest configuration change needed and verify the report runs successfully. Can you provide access to the SSRS configuration and confirm whether Windows Authentication is being used? Looking forward to work with you
$140 USD in 7 days
3.4
3.4

Hi, Dejan here, from Croatia. I can resolve your SSRS data source authentication failure quickly. The error `Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'` means SQL Server is receiving an anonymous token instead of a valid Windows or SQL login, which is a common SSRS double-hop or misconfiguration issue. My plan: - Review your SSRS data source settings (authentication type and stored credentials). - Check whether SSRS and SQL Server are on the same machine or different machines. - Fix the issue by either: - Configuring the data source to use stored SQL/domain credentials, or - Adjusting Kerberos delegation / service account permissions if Windows integrated security is required across servers. - Test the data source connection and confirm the report executes successfully. - Provide a short note on what was changed so your team can avoid the same issue in future reports. I’ve handled similar SSRS + SQL Server authentication problems before and can start right away. Happy to jump on a quick call or chat to confirm your current setup. Looking forward to hearing from you, Dejan
$140 USD in 7 days
3.4
3.4

Hi, this is the classic Kerberos double-hop failure: SSRS's service account passes your Windows identity to SQL Server, but the token arrives as ANONYMOUS LOGON because the SPN or delegation isn't configured. I'll check the SSRS service account SPN, the SQL Server SPN, and Kerberos delegation, then apply the right fix, constrained delegation or switching the data source to stored credentials. Beyond the fix, I'll leave a short runbook on the root cause and how to prevent it, and I can add a simple alert that catches this connection failure before it breaks reports again. Does the report data source use Windows authentication or stored credentials?
$50 USD in 1 day
3.1
3.1

Hello. The authentication failure in your SSRS report indicates a potential misconfiguration in the data source settings or a permissions issue. I've addressed similar SQL Server connection issues, where the root cause often stemmed from incorrect user permissions or settings in the report server. In those cases, ensuring that the service account has the necessary privileges resolved the problem efficiently. My approach would involve reviewing the SSRS configuration, verifying the data source credentials, and ensuring the SQL Server allows the necessary access rights. This will enhance the reliability of your reporting system and minimize future access issues. I emphasize thorough testing and validation after implementing the fix to confirm that the report functions correctly under various scenarios. Additionally, I recommend documenting the changes made for future reference and monitoring the system post-launch to ensure stability. I invite you to discuss further details to align on the best way forward. Thanks, Artiom.
$30 USD in 2 days
2.3
2.3

Hey, Just fixed a similar SSRS data source that was stuck on “Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'” – resolved the token‑based validation error, re‑authorized the service account, and restored seamless report delivery. I’m the perfect fit: I specialize in SSRS and SQL Server, diagnosing and correcting connection and authentication glitches. I work with structured data sources, secure service accounts, and advanced connection strings to eliminate errors like 18456. Multiple 5‑star reviews on complex SSRS reporting and database connection solutions back my track record. Let’s hop on a quick call or I can start with a free consultation to get your report running again. Chris | Lead Developer | Novatech
$250 USD in 7 days
3.0
3.0

Hi there, I can diagnose and resolve the SSRS authentication failure causing `NT AUTHORITY\ANONYMOUS LOGON` and SQL Server Error 18456. This issue commonly points to Windows authentication delegation, Kerberos/SPN configuration, double-hop behavior, or an SSRS data-source credential mismatch. My approach would include: • Review SSRS data-source authentication settings • Verify SQL Server and Report Server service accounts • Check SPN registration and Kerberos delegation • Confirm whether the connection is using Windows Integrated Security, stored credentials, or impersonation • Review SQL Server logs and SSRS logs for the exact failure path • Test connectivity from the report server to SQL Server • Correct the configuration and validate the report end-to-end • Document the root cause and final fix I’m comfortable troubleshooting SSRS/SQL Server authentication issues and can work directly through the infrastructure checks needed to isolate this quickly. Best Regards
$140 USD in 1 day
2.1
2.1

Hi, i am Albert from Philipin!!! I will troubleshoot the SSRS data source authentication failure and identify why SQL Server is receiving `NT AUTHORITY\ANONYMOUS LOGON`. I will review the SSRS data source configuration, authentication mode, Windows/SQL credentials, delegation or Kerberos-related settings, and SQL Server connectivity to locate the root cause. I will apply the required fix without disrupting the existing report, then test the connection and confirm the SSRS report runs successfully. I will also provide a brief explanation of the issue and the changes made. Best regards, Albert
$120 USD in 2 days
1.7
1.7

Hi, Good day! I came across your project "[[Project Title]]" and I'm excited to discuss how I can help. I'm confident that my experience and dedication make me an ideal candidate for Fix SSRS Data Source Issue. My work portfolio includes several high-quality Data Processing, SQL, Troubleshooting, Database Administration, Microsoft SQL Server, Database Development, Report Development, Data Analysis, Data Integration, Database Management projects. I can show you examples that prove I'm the right fit for Fix SSRS Data Source Issue. Lets connect in chat so that We discuss further. Regards, Manisha
$140 USD in 4 days
1.4
1.4

⭐⭐⭐Hi, I can handle this. An SSRS report failing with error 18456, State 11, and the NT AUTHORITY\ANONYMOUS LOGON message, which is almost always a double-hop authentication problem rather than a wrong password. The report server authenticates the user, then tries to reach SQL Server as that user, and without Kerberos delegation the credentials cannot pass through, so the connection arrives anonymously and SQL rejects it. State 11 points at token-based validation failing rather than a bad login. The usual causes are missing SPNs for the SQL and report server service accounts, delegation not enabled on the report server account, or Windows Integrated Security being used where stored credentials would be simpler. I would check which applies rather than assume, since the fix differs between SPN registration, enabling constrained delegation, or switching the data source to stored credentials if delegation is impractical. I have resolved this exact error before, including missing SPNs causing anonymous logon failures and constrained delegation resolving it without changing the data source. Is the data source using Windows Integrated Security, and are the report server and SQL Server on the same machine or separate? I'm ready to start work immediately. Best Regards
$150 USD in 2 days
0.4
0.4

That ANONYMOUS LOGON error 18456 State 11 is almost always a Kerberos double-hop failure, where SSRS can't pass the user's Windows login on to SQL Server. I can confirm and fix it fast. - I'd check the SPN registration for the SQL and SSRS service accounts, since missing or duplicate SPNs cause this exact error. - Then I'd review the data source: either switch to stored credentials, or set up constrained delegation if you need per-user access. - I'd also read the SQL Server error log and SSRS log for the earlier error that this message points to. - On Day 1 I can diagnose the cause and get the report running, so you can see it working. You pay only once it works. Can you share the data source settings (credentials type, no passwords) and whether SSRS and SQL Server run on different machines?
$30 USD in 7 days
2.2
2.2

Error 18456 with state 11 and anonymous logon usually means a Kerberos double-hop problem. I'd fix the data source or the SPN delegation and document the change. I can deliver it in 2 days, and it includes up to 2 rounds of adjustments. Does the report use Windows authentication, and can I get remote access to the server? You can see my work here: https://www.freelancer.com/u/Deived3339
$50 USD in 2 days
0.0
0.0

Hi, resolving your SSRS "NT AUTHORITY\ANONYMOUS LOGON" error (Error 18456, State 11) comes down to curing the classic Kerberos double-hop authentication drop between the report server and SQL Server. I isolate the root cause by checking the data source credentials in Report Manager and verifying your Active Directory SPNs (Service Principal Names) for both the SSRS service account and the SQL Server engine. We will either configure Kerberos constrained delegation cleanly or standardise the data source to use securely stored Windows credentials, avoiding unintended unauthenticated hops entirely. I can test and resolve this within 24 to 48 hours. Stage 1 delivers root-cause verification and connection validation in your staging environment first, keeping your live production configuration completely safe. Is the SSRS instance running on the same physical server as the target SQL database, or are they on separate hosts? Best regards, Tumisang
$78 USD in 2 days
0.0
0.0

Hi there, The hard part is not just identifying the data source connection issue, but understanding the underlying authentication failure. This specific error often indicates a problem with the security context or permissions of the user account being used. I can analyze the SQL Server configuration and SSRS setup to identify the root cause and implement a fix, ensuring proper authentication mechanisms are in place. Could you clarify if there have been any recent changes to the server or user permissions that might have contributed to this issue? Thank you.
$140 USD in 7 days
0.0
0.0

Hi, I have a deep understanding with SSRS. In my opinion, this is very likely a Windows Authentication / Kerberos delegation problem, commonly called the Kerberos double-hop problem. Let's get in touch. Thanks.
$100 USD in 1 day
0.0
0.0

Hi You're facing an SSRS report error due to a "Login failed for user 'NT AUTHORITY\ANONYMOUS LOGON'" issue, which relates to authentication failing between your SSRS and the SQL Server. This typically happens when Windows Authentication doesn't pass the correct credentials through to the SQL Server due to improper configuration or permissions. My approach would involve verifying the authentication settings in your data source connection and ensuring the necessary permissions on the SQL Server for the SSRS service account. I've handled similar SQL Server authentication issues before, particularly fixing token-based validation problems for reports in enterprise environments. One example was resolving state 11 errors by correctly configuring Kerberos delegation for services spread over multiple servers. The specifics of using NT AUTHORITY make me think you've got a slightly unusual configuration or an oversight in your setup. Let's get this sorted; I'm ready to walk you through the process and dive into your configuration for an effective fix. Thanks, Jonathan
$140 USD in 7 days
0.0
0.0

Austin, United States
Payment method verified
Member since Jan 30, 2024
$750-1500 USD
₹37500-75000 INR
£750-1500 GBP
₹100-400 INR / hour
₹12500-37500 INR
$30-250 USD
₹37500-75000 INR
€12-18 EUR / hour
₹750-1250 INR / hour
₹750-1250 INR / hour
£10-20 GBP
₹1500-12500 INR
₹600-1500 INR
₹1500-12500 INR
₹1500-12500 INR
$30-250 USD
₹400-750 INR / hour
$25-50 USD / hour
$10-30 USD
₹12500-37500 INR
€30-250 EUR