back_in_the_1980s
New Member
- Joined
- Jul 28, 2016
- Messages
- 5
Hello:
My apologies, for cross-posting. I had posted this in the "Excel Questions" Forum. I'm new and did not see this "Power BI" Forum.
Upon clicking the "Finish" button in the Excel 2010 (32-Bit) PowerPivot Table Import Wizard, I get the "XML parsing failed at line 7, column 397. Illegal name character." error, unless I'm logged in as a Windows Authenticated user with db_owner rights to the SQL database that I'm trying to pull data from.
If I'm logged in as a SQL Authenticated user with db_reader rights, I get this error.
In fact, even logged in as SQL's "sa" login, I get this error.
I read that this error does not happen in version 2 of the Excel 2010 PowerPivot. But, version 2 is for SQL Server 2012. We're on SQL Server 2008 R2.
It sounds like Windows Authentication is going to need to be used, in order to not get this error. But, our database administrator is not going to want to give users db_owner rights.
Is there some sort of other "fix" for this, other than being logged in as a Windows Authenticated user with db_owner rights?
Thank you!
John
My apologies, for cross-posting. I had posted this in the "Excel Questions" Forum. I'm new and did not see this "Power BI" Forum.
Upon clicking the "Finish" button in the Excel 2010 (32-Bit) PowerPivot Table Import Wizard, I get the "XML parsing failed at line 7, column 397. Illegal name character." error, unless I'm logged in as a Windows Authenticated user with db_owner rights to the SQL database that I'm trying to pull data from.
If I'm logged in as a SQL Authenticated user with db_reader rights, I get this error.
In fact, even logged in as SQL's "sa" login, I get this error.
I read that this error does not happen in version 2 of the Excel 2010 PowerPivot. But, version 2 is for SQL Server 2012. We're on SQL Server 2008 R2.
It sounds like Windows Authentication is going to need to be used, in order to not get this error. But, our database administrator is not going to want to give users db_owner rights.
Is there some sort of other "fix" for this, other than being logged in as a Windows Authenticated user with db_owner rights?
Thank you!
John