Home Dashboard Directory Help
Search

Unsupported RPL stream version detected: 10.0.0. Expected version: 10.3. by wewec


Status: 

Closed
 as Not Reproducible Help for as Not Reproducible


1
0
Sign in
to vote
Type: Bug
ID: 355502
Opened: 7/9/2008 2:31:32 AM
Access Restriction: Public
0
Workaround(s)
view
0
User(s) can reproduce this bug

Description

There seems to be a version problem between the reporting servivices addin for sharepoint and sql server in the 32 bit versjon

From the config file:

<SafeControl Assembly="Microsoft.ReportingServices.SharePoint.UI.WebParts, Version=10.0.0.0, Culture=neutral, PublicKeyToken=89845dcd8080cc91" Namespace="Microsoft.ReportingServices.SharePoint.UI.WebParts" TypeName="*" Safe="True" />
    
Details
Sign in to post a comment.
Posted by SACSgtMike on 4/3/2014 at 7:48 AM
Checking further into this, the reason we're doing this is a cheap way to get a .csv export. It's working for other reports we have and we're saving time by just training the end users to export stripped down versions of the full report as Excel or CSV files.

For these files, however, the volume is GIHUGEUOUS. What we can get away with in other reports isn't working here so it may be we're tasking report builder with something Atlas in scope.

Nonetheless, we'd love this idea to work since it's one less layer of application an end user has to think with, If they can do it all from the report and not have to open up another app to export once they have the report -- great.

Thanks for any input.
Posted by SACSgtMike on 4/3/2014 at 7:06 AM
I'm not sure if this is being viewed. I can run this query in Report Builder and check it in the query window. It runs in about 10-15 seconds. The short version is first (truncated the SELECT for readability). In the Report Builder Query Window I can insert a year into the dialog that pops up when the Execute (!) icon is clicked. As mentioned, takes 15 seconds or less to run.

From Run Mode, however, which I'm thinking is equivalent to running it from where it lives on Sharepoint, then I get this same error.

We have Aqua Data Studio for our "SSMS" and it dies out after 322,000 records and change with an Out Of Memory error -- so I guess it can be a flaky query but if that's the case ... why does it execute so cleanly in the Query Window in Report Builder?

Short Version:

SELECT
    CU.DOCUMENT_NBR,
    CU.ODPS_UNIT_NBR,
    ....
    CU.ODOT_UNBELTED_OCCUPANTS,
    CU.ODOT_UNIT_POS_NBR,
    CU.ODOT_OBJECT_STRUCK

FROM CR_UNITS CU
    JOIN CR_CRASH CR ON CR.DOCUMENT_NBR = CU.DOCUMENT_NBR

WHERE EXTRACT(YEAR FROM CR.CRASH_DATE) = :YEAR

This query shows a count of 512,802

SELECT COUNT(*)

FROM CR_UNITS CU
    JOIN CR_CRASH CR ON CR.DOCUMENT_NBR = CU.DOCUMENT_NBR

WHERE EXTRACT(YEAR FROM CR.CRASH_DATE) = :YEAR


Full Query:

SELECT
    CU.DOCUMENT_NBR,
    CU.ODPS_UNIT_NBR,
    CU.UNIT_HIT_SKIP,
    CU.NUMBER_OF_OCCUPANTS_NBR,
    CU.VEHICLE_YEAR,
    CU.TOWING_SERVICE_FLAG,
    CU.ODPS_DIRECTION_FROM_CD,
    CU.ODPS_DIRECTION_TO_CD,
    CU.MOST_DAMAGED_AREA,
    CU.DAMAGE_SCALE,
    CU.TYPE_OF_UNIT_CD,
    CU.TRAFFIC_WAY_DESC_CD,
    CU.SPECIAL_FUNCTION_CD,
    CU.SPEED_DETECTED,
    CU.UNIT_SPEED_NBR,
    CU.POSTED_SPEED_NBR,
    CU.PRECRASH_ACTION_CD,
    CU.TRAFFIC_CONTROL_CD,
    CU.CONT_CIR_PRIMARY_CD,
    CU.CONT_CIR_SECONDARY_CD,
    CU.VEHICLE_DEFECTS,
    CU.SEQ_OF_EVENTS_1_CD,
    CU.SEQ_OF_EVENTS_2_CD,
    CU.SEQ_OF_EVENTS_3_CD,
    CU.SEQ_OF_EVENTS_4_CD,
    CU.SEQ_OF_EVENTS_5_CD,
    CU.SEQ_OF_EVENTS_6_CD,
    CU.FIRST_HARMFUL_SEQ_NBR,
    CU.FIRST_HARMFUL_CD,
    CU.MOST_HARMFUL_SEQ_NBR,
    CU.MOST_HARMFUL_CD,
    CU.COLLISION_ACTION_CD,
    CU.IN_EMERGENCY_RESPONSE,
    CU.IMPACT_AREA,
    CU.NON_MOTORIST_LOC_CD,
    CU.CARGO_BODY_TYPE_CD,
    CU.WEIGHT_CLASS_GVWR,
    CU.HAZ_MAT_PLACARD_IND,
    CU.PLACARD_NBR,
    CU.HM_CLASS_NBR,
    CU.HAZ_MAT_RELEASED_IND,
    CU.VEHICLE_MAKE,
    CU.VEHICLE_MODEL,
    CU.VEHICLE_COLOR_CD,
    CU.DAMAGE_AREA_02,
    CU.DAMAGE_AREA_03,
    CU.DAMAGE_AREA_04,
    CU.DAMAGE_AREA_05,
    CU.DAMAGE_AREA_06,
    CU.DAMAGE_AREA_07,
    CU.DAMAGE_AREA_08,
    CU.DAMAGE_AREA_09,
    CU.DAMAGE_AREA_10,
    CU.TYPE_OF_USE_CD,
    CU.ODOT_AT_FAULT_IND,
    CU.ODOT_UNIT_FATALITIES,
    CU.ODOT_UNIT_INCAPAC_INJ,
    CU.ODOT_UNIT_NONINCAP_INJ,
    CU.ODOT_UNIT_POSS_INJ,
    CU.ODOT_UNIT_NONINJURY,
    CU.ODOT_UNIT_HAS_INJURY_IND,
    CU.ODOT_UNBELTED_OCCUPANTS,
    CU.ODOT_UNIT_POS_NBR,
    CU.ODOT_OBJECT_STRUCK

FROM CR_UNITS CU
    JOIN CR_CRASH CR ON CR.DOCUMENT_NBR = CU.DOCUMENT_NBR

WHERE EXTRACT(YEAR FROM CR.CRASH_DATE) = :YEAR
Posted by Microsoft on 7/24/2008 at 9:58 AM
Hello,

I'm closing this as Not Reproducible. We cannot reproduce this based on the information provided, and have not received a response.

Thanks,
Chris B.
SQL Server Reporting Services
Posted by Microsoft on 7/9/2008 at 11:52 AM
Hello Charlie,

This error typically occurs when your SharePoint webpart and SSRS server version are out of sync, particularly when either the webpart or the server are SSRS 2008 pre-CTP6. Please verify the following:

1) The precise version of your SharePoint webpart. You can check this by looking at the version number on the assembly itself (in other words, not from the config file).
2) The version of the report server to which your webpart points. You can verify this by browsing to the server in IE at http://yourserver/reportserver and noting the version number at the bottom of the screen.

I look forward to hearing back from you with this info.

Best regards,
Chris B.
SQL Server Reporting Services
Sign in to post a workaround.