Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
jr3151006
Helper IV
Helper IV

Power BI Desktop - First DataSource SQL SERVER - Error to add using specific login

Hi team,

 

I'm new with Power BI, just to clarify this case I installed 'PBI Desktop' and also using MS SQL Management Console, create a new LOGIN as 'public' at server role and assigned it to a specific database as 'public' and 'datareader' permissions. Using MS SQL Management Console the connection works fine but when tryng to add a DataSource as 'SQL SERVER' using this new user, shows a msg as invalid credentials os something like that. But when I try using 'same credentials' which means that administrator user has 'SA' equivalent permissions, connect fine and show on the next step an another alert regarding encription not available and ask to confirm...

 

The user used to this first connection (IMPORT mode) should have some specific permission??

2 REPLIES 2
jr3151006
Helper IV
Helper IV

Looking at Windows EventViewer\Security we realize this:

 

---

Log Name: Security
Source: Microsoft-Windows-Security-Auditing
Date: 7/25/2017 8:16:26 PM
Event ID: 4625
Task Category: Logon
Level: Information
Keywords: Audit Failure
User: N/A
Computer: u6329vm1
Description:
An account failed to log on.

Subject:
Security ID: U6329VM1\Administrator
Account Name: Administrator
Account Domain: U6329VM1
Logon ID: 0x6b29508

Logon Type: 8

Account For Which Logon Failed:
Security ID: NULL SID
Account Name: anjorenato
Account Domain: U6329VM1

Failure Information:
Failure Reason: Unknown user name or bad password.
Status: 0xc000006d
Sub Status: 0xc0000064

Process Information:
Caller Process ID: 0x249c
Caller Process Name: C:\Program Files\Microsoft Power BI Desktop\bin\Microsoft.Mashup.Container.NetFX40.exe

Network Information:
Workstation Name: U6329VM1
Source Network Address: -
Source Port: -

Detailed Authentication Information:
Logon Process: Advapi
Authentication Package: Negotiate
Transited Services: -
Package Name (NTLM only): -
Key Length: 0

This event is generated when a logon request fails. It is generated on the computer where access was attempted.

The Subject fields indicate the account on the local system which requested the logon. This is most commonly a service such as the Server service, or a local process such as Winlogon.exe or Services.exe.

The Logon Type field indicates the kind of logon that was requested. The most common types are 2 (interactive) and 3 (network).

The Process Information fields indicate which account and process on the system requested the logon.

The Network Information fields indicate where a remote logon request originated. Workstation name is not always available and may be left blank in some cases.

The authentication information fields provide detailed information about this specific logon request.
- Transited services indicate which intermediate services have participated in this logon request.
- Package name indicates which sub-protocol was used among the NTLM protocols.
- Key length indicates the length of the generated session key. This will be 0 if no session key was requested.
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Microsoft-Windows-Security-Auditing" Guid="{54849625-5478-4994-A5BA-3E3B0328C30D}" />
<EventID>4625</EventID>
<Version>0</Version>
<Level>0</Level>
<Task>12544</Task>
<Opcode>0</Opcode>
<Keywords>0x8010000000000000</Keywords>
<TimeCreated SystemTime="2017-07-25T23:16:26.701239400Z" />
<EventRecordID>8496997</EventRecordID>
<Correlation />
<Execution ProcessID="512" ThreadID="11048" />
<Channel>Security</Channel>
<Computer>u6329vm1</Computer>
<Security />
</System>
<EventData>
<Data Name="SubjectUserSid">S-1-5-21-2290545486-2615049865-41561844-500</Data>
<Data Name="SubjectUserName">Administrator</Data>
<Data Name="SubjectDomainName">U6329VM1</Data>
<Data Name="SubjectLogonId">0x6b29508</Data>
<Data Name="TargetUserSid">S-1-0-0</Data>
<Data Name="TargetUserName">anjorenato</Data>
<Data Name="TargetDomainName">U6329VM1</Data>
<Data Name="Status">0xc000006d</Data>
<Data Name="FailureReason">%%2313</Data>
<Data Name="SubStatus">0xc0000064</Data>
<Data Name="LogonType">8</Data>
<Data Name="LogonProcessName">Advapi </Data>
<Data Name="AuthenticationPackageName">Negotiate</Data>
<Data Name="WorkstationName">U6329VM1</Data>
<Data Name="TransmittedServices">-</Data>
<Data Name="LmPackageName">-</Data>
<Data Name="KeyLength">0</Data>
<Data Name="ProcessId">0x249c</Data>
<Data Name="ProcessName">C:\Program Files\Microsoft Power BI Desktop\binMicrosoft.Mashup.Container.NetFX40.exe</Data>
<Data Name="IpAddress">-</Data>
<Data Name="IpPort">-</Data>
</EventData>
</Event>

There is a way to specify and use SQL LOGIN instead Windows Login to connect to the db??

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

Find out what's new and trending in the Fabric Community.