November 6, 2008 at 10:21 am
Hi guys,
I have found a bug in BIDS which I have not found documented anywhere and which caused me a whole afternoon's pain with no sensible error message.
If you have a table with the same name as one of your data sources, going into the preview pane crashes BIDS and attempting to Build the solution gives the dreaded, infamous:
Error 1, An internal error occurred on the report server. See the error log for more details.
Imagine my frustration when I found the fix was so easy.
How can I report this bug to Microsoft and avoid the same pain in my fellow BIDS sufferers/users.
November 6, 2008 at 11:45 am
Post it on Connect. Make sure you've applied the latest service pack and CU before you do so, so that you know that it hasn't already been fixed.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 7, 2008 at 6:53 am
Thanks for your response Gail. Looks like a sensible thing to do.
Can anybody advise me on where to look to find out what the latest version of the BIDS Reporting Services module is?
Thanks,
Rob
p.s. My current version is 9.00.1399.00
November 8, 2008 at 3:20 am
Build 1399 is RTM, meaning it's never been patched at all. The latest will be SP2 CU 10. Get SP2 and apply it to the machine where the client tools are, then get cumulative update 10 and apply that.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
November 19, 2008 at 1:43 pm
mikebally888 (11/19/2008)
Hi,Maybe you can try removed here too 😉 ,it is better than Crystal Report in many aspects
Where does anyone mention crystal reports, or any reporting tool for that matter
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply