logo

Warning: The forum is now for consultation only. Please use GitHub Discussions to post any questions or comments.


Welcome Guest ! To enable all features please Login or Register.

Notification

Icon
Error

Options
Go to last post Go to first unread
AlbertZ  
#1 Posted : Tuesday, February 23, 2016 7:30:22 PM(UTC)
AlbertZ

Rank: Newbie

Groups: Registered
Joined: 2/23/2016(UTC)
Posts: 4
United States

I have created a report, two data sources, twenty models so far. In the report designer everything is OK. The connections work, I see my reports when executed.

Then I used the Server Manager as Administrator, and published the website to my localhost. The samples work, both Dashboard - Sales and Search - Orders. But not the report I created myself. The error seams to indicate that the problem is in the connection.

First it shows Processing..., when I press CTRL+F5 it shows the actual error message.

Code:

1:11:57 PM Error in model 'P_Last100TransactionResults': Unexpected error when executing the following SQL statement:
SELECT
 TransactionHundredResults.LoadTestRunId AS C0,
 TransactionHundredResults.TransactionName AS C1,
 Sum(TransactionHundredResults.Average) AS C2
FROM TransactionHundredResults
GROUP BY TransactionHundredResults.LoadTestRunId,TransactionHundredResults.TransactionName
ORDER BY TransactionHundredResults.LoadTestRunId ASC,TransactionHundredResults.TransactionName ASC,Sum(TransactionHundredResults.Average) ASC


Error detail:
Login failed for user '<Domain>\<MachineName>$'.
1:11:57 PM Error in model 'P_Last100PageResults': Unexpected error when executing the following SQL statement:
SELECT
 PageHundredResults.LoadTestRunId AS C0,
 PageHundredResults.RequestUri AS C1,
 Sum(PageHundredResults.Average) AS C2
FROM PageHundredResults
GROUP BY PageHundredResults.LoadTestRunId,PageHundredResults.RequestUri
ORDER BY PageHundredResults.LoadTestRunId ASC,PageHundredResults.RequestUri ASC,Sum(PageHundredResults.Average) ASC


Note the line with <Domain>\<MachineName>. There is no user MachineName in the domain, it should not be used. As a result, I can not give this user access to the MSSQL database. I tried a lot to make the ApplicationPool use another user, but that only results in different errors. For what I can find out, the user that should be used would be NT_AUTHORITY\SYSTEM or NETWORK. At least those I can give access to the database.

The connection string is:
Provider=SQLNCLI11.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=PerformanceAnalysis;Data Source=(local);Initial File Name="";Server SPN=""

I have tried to use ODBC, but that had the same result.

Best Regards,
Albert

P.S. Also, the report website does not work properly in Chrome and this form does not work properly in IE.

Edited by user Tuesday, February 23, 2016 7:32:12 PM(UTC)  | Reason: Not specified

epf  
#2 Posted : Thursday, February 25, 2016 8:08:02 AM(UTC)
epf

Rank: Administration

Groups: Administrators
Joined: 12/20/2013(UTC)
Posts: 1,209
Switzerland

Thanks: 14 times
Was thanked: 206 time(s) in 199 post(s)
Yes this is definetely a problem with the identity used by IIS to connect to the database as you have chosen the mssql integrated security...
But I am surprised you get the error using the user system...
Depending on your authentication mode, application pool identity and several options either in the pool or the web site, you have to understand which Windows user you should use...
Other option is to create a pure Mssql user dedicated for seal report and you set the user name password in your datasource connection.
You can also create a dedicated Windows user for the same goal.
Good luck...
AlbertZ  
#3 Posted : Thursday, February 25, 2016 1:51:19 PM(UTC)
AlbertZ

Rank: Newbie

Groups: Registered
Joined: 2/23/2016(UTC)
Posts: 4
United States

Thank you for your reply.
You are right, it is purely authorization in SQL server.
What complicates things is that I use views that in their turn pull their data from another server. So, once I have the login to the local database solved, then login to the linked server object is not solved. Using SQL Server authentication helps indeed. But, that brings its own problems. So, I will continue experimenting on this.

Albert
AlbertZ  
#4 Posted : Thursday, February 25, 2016 2:07:21 PM(UTC)
AlbertZ

Rank: Newbie

Groups: Registered
Joined: 2/23/2016(UTC)
Posts: 4
United States

I have it working now. I use a SQL server authenticated user on the local database and a SQL server authenticated user on the linked server.

One minor point. Given I am in the Data Link Properties dialog, when I select Allow saving password then the password is not saved and I have to reenter it in the Datasource configuration window.
Users browsing this topic
Guest (2)
Forum Jump  
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.