StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO"Object reference not set to an instance of an object" caused by height of Tablix
primarykey
Id
9165724
data
AcceptedAnswerId
9365391
AnswerCount
2
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2012-02-06T19:06:07.833
FavoriteCount
0
LastActivityDate
2014-06-16T11:54:25.487
LastEditDate
2012-02-06T19:12:08.110
LastEditorUserId
250385
OwnerUserId
250385
ParentId
0
PostTypeId
1
Score
0
ViewCount
9363
LastEditorDisplayName
text
Body
I have an issue with a report causing an "Object reference not set to an instance of an object" exception when run through my web application. This is, so far, only happening on one QA machine. I can: <ul> <li>Run the report locally on my development machine (latest code, same database)</li> <li>Run the report through the Reporting Services Web Interface on the QA machine</li> <li>Run the report on the QA machine through my web app if I select a format other than PDF/TIFF (e.g. Excel, CSV, HTML, XML all report successfully)</li> </ul> The Reporting Services log on the QA machine looks <a href="http://www.o1solution.com/rsLog.txt" rel="nofollow">like this</a> when I get the exception. I did not find the log helpful so I started whittling the report down to a minimum to find the issue. What I found confuses me. Given <a href="http://www.o1solution.com/myReport.txt" rel="nofollow">the following RDL</a>; I can change the height of Tablix list1 from 3.09444in to 1in, deploy the report to the QA server and the report will run successfully. How in the world could shortening the height of Tablix list1 prevent the exception? <hr> UPDATE It's not moving height of the tablix to 1in. It's getting rid of the long decimal on the height. I changed (3.09444in to 3.1in) and the report ran successfully. FTR, I did not choose the height 3.09444in...rs chose that for me while I designed the report.
Tags
<reporting-services>
Title
"Object reference not set to an instance of an object" caused by height of Tablix
singulars
PostAcceptedAnswerId
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
PostParentId
1. This table or related slice is empty.
PostTypePostTypeId
1. PTQuestion
UserLastEditorUserId
1. USray
UserOwnerUserId
1. USray
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. PL
 singulars
 LinkTypeLinkTypeId
 LTLinked
2. PL
 singulars
 LinkTypeLinkTypeId
 LTDuplicate
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. PO
 singulars
 PostTypePostTypeId
 PTAnswer
2. PO
 singulars
 PostTypePostTypeId
 PTAnswer
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.