Error Rfc 00202
Contents |
+ Analytics Conference: Oct 18, Mastering SAP BI, Melbourne: Oct 23. DESKI report showing "Error RFC 00202.(Error:Inf)" Search this topic...|Search Semantic Layer / Universe Designer...|Search Box Select a search Explain These Choices... --------------------Recent Topics (All sap error messages list Forums) Unanswered Posts Register or Login to Post Forum Index -> Semantic Layer
Sap Error Messages Explained
/ Universe Designer Author Message CA_BOPrincipal MemberJoined: 10 Jun 2008Posts: 164Location: California,US Posted: Tue Feb 24, 2009 2:58 pmPost subject: DESKI
Sap Error Messages Table
report showing "Error RFC 00202.(Error:Inf)" I am having issue with my report when running from Infoview.In Deski it runs and fetches data without any error, unless I edit LOV list in prompts and refresh LOV,then it
Sap Error Messages Tcode
hangs for long time, otherwise when I do not edit the LOVs and run with default value "ALL" for the prompts, it runs and fetching data.In universe level when I select LOVs and refresh it hangs for long time. When running from Infoview, it runs for quite a while and then throws error "An error occured while retriving a list of values .The XML response from the server can not be parsed.(Error RFC sap errors and solutions 00202.(Error:Inf). From database side, the view, on which report is based takes long time to fetch data, even a distinct(same in LOV of prompt) takes long. Any suggestion or solution? Back to top peacockForum AssociateJoined: 07 Nov 2002Posts: 690 Posted: Tue Feb 24, 2009 3:47 pmPost subject: Re: DESKI report showing "Error RFC 00202.(Error:Inf)&q rerun the view. Back to top CA_BOPrincipal MemberJoined: 10 Jun 2008Posts: 164Location: California,US Posted: Tue Feb 24, 2009 4:08 pmPost subject: Re: DESKI report showing "Error RFC 00202.(Error:Inf)&a Can you detail me the issue and why the view rerun required? Back to top sukravPrincipal MemberJoined: 29 Jan 2008Posts: 114 Posted: Wed Feb 25, 2009 1:46 amPost subject: Re: DESKI report showing "Error RFC 00202.(Error:Inf)&q Hi, When the LOVs from database is taking lot of time, then for sure Universe LOV refresh would make the universe hang. The first step should be to improve the performance of the database so that the retrieval of the LOVs in database should be very fast. If this is resolved at DB then refresh LOVs from universe or deski or webi won't be a problem. Hope useful Regards, Sukesh Back to top CA_BOPrincipal MemberJoined: 10 Jun 2008Posts: 164Location: California,US Posted: Wed Feb 25, 2009 1:45 pmPost subject: Re: DESKI report showing "Error RFC 00202.(Error:Inf)&a Thanks, we are current
and SafetyAsset NetworkAsset Operations and sap bo errors MaintenanceCommerceOverviewSubscription Billing and Revenue ManagementMaster Data Management for CommerceOmnichannel business objects #error CommerceFinanceOverviewAccounting and Financial CloseCollaborative Finance OperationsEnterprise Risk and ComplianceFinancial Planning and AnalysisTreasury and Financial http://www.forumtopics.com/busobj/viewtopic.php?p=592012&sid=7c5a6375abac63f5f8b6c20543a43d6d Risk ManagementHuman ResourcesOverviewCore Human Resources and PayrollHuman Capital AnalyticsTalent ManagementTime and Attendance ManagementManufacturingOverviewManufacturing NetworkManufacturing OperationsResponsive ManufacturingMarketingOverviewMarket with Speed and AgilityUnique Customer ExperiencesReal-Time Customer InsightsR&D/EngineeringOverviewDesign NetworkDesign OrchestrationProject and Portfolio ManagementSalesOverviewCollaborative Quote https://scn.sap.com/thread/1205691 to CashSales Force AutomationSales Performance ManagementSelling Through Contact CentersServiceOverviewEfficient Field Service ManagementOmnichannel Customer ServiceTransparent Service Process and OperationsSourcing and ProcurementOverviewContingent Workforce ManagementDirect ProcurementSelf-Service ProcurementServices ProcurementStrategic Sourcing and Supplier ManagementSupply ChainOverviewDemand ManagementDemand NetworkLogistics NetworkManufacturing Planning and SchedulingResponse NetworkResponse and Supply ManagementSales, Inventory, and Operations PlanningTransportation ManagementWarehouse ManagementSustainabilityOverviewEnvironment, Health, and SafetyProduct Safety and Stewardship NetworkBrowse by IndustryAerospace and DefenseAutomotiveBankingChemicalsConsumer ProductsDefense and SecurityEngineering, Construction, and OperationsHealthcareHigh TechHigher Education and ResearchIndustrial Machinery and ComponentsInsuranceLife SciencesMediaMill ProductsMiningOil and GasProfessional ServicesPublic SectorRetailSports and EntertainmentTelecommunicationsTravel and TransportationUtilitiesWholesale DistributionBrowse Platform and TechnologyAnalyticsOverviewBusiness IntelligencePredictive Analytic
references to the message class/stream mappings > in draft 12. > > 1. The "Invalid Stream Identifier" error is sent if a message is received > on an unexpected SCTP stream (e.g., a Management message http://osdir.com/ml/ietf.sigtran/2002-04/msg00202.html was received > on a stream other than "0"). > > 2. DATA messages MUST be sent on an SCTP stream > other than stream '0'. > > 3. ASPTM messages MAY be sent on one of the streams used to carry the data > traffic related to the Routing Context(s), to minimize possible message > loss. BEAT and BEAT Ack messages MAY be sent using out-of-order > delivery, and MAY be sent on any stream. > sap error > >From these three references, one can draw following conclusions : > 1. DATA is never sent on stream 0. > 2. Management messages (Class 0 messages only as specified in > section 3.1.2) can be sent on stream 0 only. > 3. All other messages (ASPSM, RKM, ASPTM, SSNM) can be sent on any > stream. > > If this is not the intended stream mapping, then some more > text is needed in the draft sap error messages to clarify this. > > Umesh > -- Brian F. G. Bidulock bidulock@xxxxxxxxxxx http://www.openss7.org/ Thread at a glance: Previous Message by Date: RE: M3UA : Messages and Streams Hi Brian I see following references to the message class/stream mappings in draft 12. 1. The "Invalid Stream Identifier" error is sent if a message is received on an unexpected SCTP stream (e.g., a Management message was received on a stream other than "0"). 2. DATA messages MUST be sent on an SCTP stream other than stream '0'. 3. ASPTM messages MAY be sent on one of the streams used to carry the data traffic related to the Routing Context(s), to minimize possible message loss. BEAT and BEAT Ack messages MAY be sent using out-of-order delivery, and MAY be sent on any stream. >From these three references, one can draw following conclusions : 1. DATA is never sent on stream 0. 2. Management messages (Class 0 messages only as specified in section 3.1.2) can be sent on stream 0 only. 3. All other messages (ASPSM, RKM, ASPTM, SSNM) can be sent on any stream. If this is not the intended stream mapping, then some more text is needed in the draft to clarify this. Umesh -----Original Message----- From: Brian F. G. Bidulock [mailto:bidulock@xxxxxxxxxxx] Sent: Wednesday, April 17, 2002 12:45 PM To: Javier Pastor-Balbas (ECE) Cc: 'sigtran@xxxxxxxx'; Vats, Umesh Subject: Re: [Sigtran] M3