Raise exception from standard FM

I have a standard FM as below:
    CALL FUNCTION 'OIGI_LOADING_CREATE'
      EXPORTING
        i_subrc                   = 19
        i_shnumber                = load_inbound_hdr-shnumber
        i_vehicle                 = load_inbound_hdr-vehicle
        i_ldplt                   = lv_plant
      I_LDDATE                  = 00000000
      I_LDTIME                  = 000000
      I_LDCDAT                  = 00000000
      I_LOAD_AS_SCHEDULED       = ' '
      I_VEH_NR                  = 000
      I_ROLLBACK                = ' '
      I_RECURSIVE               = ' '
      I_CORRECT                 = ' '
      I_MBLNR                   = ' '
      I_MJAHR                   = ' '
      I_PSTDAT                  = 00000000
      I_PSTTIM                  = 000000
      I_DCMDAT                  = 00000000
     IMPORTING
       O_SUBRC                   = wf_subrc
As this FM returns error messages on some wrong input data it stops the execution and I cannot capture the exception and raise messages, also this FM does not contain any exception messages and directly raises Error messages.
How can I go about it.

Hi Karan,
I don't have FM OIGI_LOADING_CREATE existing in my system. I'm using ECC 5.0. I came across a thread explaning about handling error messages in this FM.
You can have a look.
[Is there a way to handle system exception ERROR_MESSAGE?|Is there a way to handle system exception ERROR_MESSAGE?;

Similar Messages

  • How to view list of all system exceptions from standard package?

    Hello,
    How to view list of all system exceptions from standard package?
    Regards
    Krishna

    Just for fun:
    SQL> conn sys/****** as sysdba
    Verbonden.
    SQL> select cast(trim(substr(text,instr(text,'(')+1,instr(text,',')-instr(text,'(')-1)) as varchar2(30)) exception_name
      2       , to_number(replace(substr(text,instr(text,',')+1,instr(text,')')-instr(text,',')-1),'''')) error_number
      3    from user_source
      4   where text like '%pragma EXCEPTION_INIT%'
      5     and type = 'PACKAGE'
      6     and name = 'STANDARD'
      7   order by exception_name
      8  /
    EXCEPTION_NAME                 ERROR_NUMBER
    ACCESS_INTO_NULL                      -6530
    CASE_NOT_FOUND                        -6592
    COLLECTION_IS_NULL                    -6531
    CURSOR_ALREADY_OPEN                   -6511
    DUP_VAL_ON_INDEX                         -1
    INVALID_CURSOR                        -1001
    INVALID_NUMBER                        -1722
    INVALID_OBJECT_NAME                  -44002
    INVALID_QUALIFIED_SQL_NAME           -44004
    INVALID_SCHEMA_NAME                  -44001
    INVALID_SQL_NAME                     -44003
    LOGIN_DENIED                          -1017
    NO_DATA_FOUND                           100
    NO_DATA_NEEDED                        -6548
    NOT_LOGGED_ON                         -1012
    PROGRAM_ERROR                         -6501
    ROWTYPE_MISMATCH                      -6504
    SELF_IS_NULL                         -30625
    STORAGE_ERROR                         -6500
    SUBSCRIPT_BEYOND_COUNT                -6533
    SUBSCRIPT_OUTSIDE_LIMIT               -6532
    TIMEOUT_ON_RESOURCE                     -51
    TOO_MANY_ROWS                         -1422
    USERENV_COMMITSCN_ERROR               -1725
    VALUE_ERROR                           -6502
    ZERO_DIVIDE                           -1476
    26 rijen zijn geselecteerd.Regards,
    Rob.

  • Catching errors in Web Dynpro for Java when thrown from RFC Raise Exception

    Hello Developers,
    I'm looking for information that explains how a Web Dynpro for Java application responds and processes errors that are thrown from a Raise Exception event within an RFC.
    The Exceptions do not appear to be part of the Model and I can't identify how they get processed.
    When rfc HRXSS_CAT_WD_RECORD raises exception PERNR_NOT_LOCKED this exception is passed back to the calling webdynpro CAT DC that displays the exception on the web page along with the log. 
    I would like to display a friendlier message and without the log.  Any information on how to customize the handling of this error would be greatly appreciated.
    Thank you,
    Terry

    [see here|https://www.sdn.sap.com/irj/servlet/prt/portal/prtroot/com.sap.km.cm.highlightedcontent?documenturi=%2flibrary%2fuser-interface-technology%2fwdJava%2FHowtoHandleExceptionsEffectivelyWhileWorkingwithWebDynproJava%28WDJ%29.pdf]

  • Raise customized JBO exception from AM to Client

    All
    I want to raise exception in am, vo or eo to client side when some kind of business rules hit. How can i raise the JBO exception with info to identify the failed root reason?
    If execute the binding operation I can call the getErrors() to check if the last execute succeed or not. How can i get this error message when call the operation via web service which exported from am,
    follow are the code part in DemoAMServiceImpl for example, the DemoAMServiceImpl is generated by default when export DemoAM to support web service:
    public EventsVOSDO updateEventsVO1(EventsVOSDO eventsVO1) throws ServiceException {
    return (EventsVOSDO)update(eventsVO1, "EventsVO1");
    when call this method to update event via web service to update event in AM, logic in eventEO checks the event property and raise custom event to client to indicate failure.
    any one have good ideals on this requirement?

    Try something like this in your method:
    throw new JboException("Don't do that.", "101", null );

  • Raise exception in function module call from SAP owned program

    I need to raise an exception in a function module to terminate a transaction, display a error message and return to to previous selection screen so the user can fix the error before moving forward.......  
    How do you do this when the program using the function module is SAP owned?
    Thank You!
    Jeff

    Hi,
    After calling the function module, you can do something like this.
    IF SY-SUBRC <> 0.
      RAISE EXCEPTION.
    ENDIF.
    Regards,
    Ferry Lianto

  • Raise exception in Start Routine

    Hi,
    In my start routine of the update rules, I would like to raise an exception when an entry is not found in the master data...
    like this,
    SELECT Y FROM TABLEX
    where X = A.
    IF SY-SUBRC NOT 0.
    Raise Exception "Value X not maintained in TABLEX.
    If you can provide me an example on how to do it, that would be great...
    Thanks
    Gova

    Hi Gova,
    you might even be able to use one of 2 standard features to solve your problem:
    1.) use referential integrity check in the transfer rules
    2.) use the check of existing master data (in the InfoPackage)
    You find detailed description of both features in the standard documentation of the BW system.
        Cheers
          Andreas

  • Raise exception while running ad hoc query

    Hi,
    I receive a "raise exception" when I try to run an existing ad hoc query in the work area: "standard area (client specific)". This does not happen when I when I create a new query or run a existing query in the work area:"Global(cross client)".
    How can this be? Very thankful for answers:-)
    -hilde

    rohit,
    just now my client informed that, he is getting same user group, not which he changed from AQB.
    Please let me know if there is any other setting....
    early reply appreciated..
    thanks,
    kumar

  • Re: Raising Exceptions Vs returning erro[Ref:C809787]

    Hi Steve !
    Probably the following explanation might help in resolving the issue raised by
    you:
    At a more abstract level, there is only one thing, i.e. the EVENT. According to
    it's definition, an event is a relatively infrequent occurrence in one portion (lets
    call it event raiser) of the application, which some other portion (or portions,
    lets call them event handlers) (of the same application) are interested to respond
    to it. Now there are two scenarios:
    (A) Event raiser and Event handler(s) are being executed under different threads
    of control (Asynchronous) and
    (B) Event raiser and Event Handler(s) are being executed under same thread of
    control (Synchronous).
    So, Exception Handling belongs to scenario B where the method raising the
    exception (Event Raiser or exception raiser) and the method handling it (Event
    Handler or exception block) are under the same thread of control. More ever it has
    to be insured that at a time only one handler (first the inner most one) receives
    the message.
    Fort&eacute; provides a generic Event handling mechanism (Post Event and Event Loop) to
    handle the scenario A (which is the more generic one). But it also provides a
    specialized Event Handling mechanism (Raise Exception and Exception block) to
    efficiently handle the relatively simple scenario B. Why I am saying that the later
    is efficient because it won't be needing to register the event queue address of the
    interested task (after all there is only one task involved) and put the event
    message in queue.
    Finally let me mentioned that it is just my view based on the understanding I
    have and it may not be true. Only a person from fort&eacute; can confirm it. I will really
    appreciate if somebody correct and or refine it.
    Wish a Very Very Happy New Year to all Fort&eacute; Users
    Regard,
    Kailash.
    [email protected] wrote:
    I would agree with Eric entirely. Exceptions seem to me to be a much more
    complete solution to the problem of error handling. A little bit of effort up
    front in making clear the strategy for exception handling and specifying the
    exceptions that can be raised by a class\method will provide an excellent method
    for error handling.
    In the case of ensuring exceptions are always handled, a top level handler for
    GenericException will usually do the job, allowing you to write error
    information out to logs, screen, etc, and then shut down gracefully.
    The only issue I would raise with exceptions is that they are not propagated
    outside an asynchronous task. If an exception is not handled within an
    asynchronous, it will not propagate to the task that started that asynchronous
    task. Forte provides return and exception events when starting asynchronous
    tasks to cope with this, but it seems a shame to have one method of dealing with
    errors (exceptions) for synchronous behaviour, and another (events) for
    asynchronous behaviour.
    Steve Elvin
    Systems Developer
    Frontline Ltd.
    UK
    Mark,
    The problem with return codes is that there is an underlying assumption
    that the receiver will always catch and interpret that error code. This
    may or may not be good thing, depending on how you architect your
    application. If, on the other hand, you want to ensure that an error is
    always handled, if not by the receiver then by the Forte, Exceptions are
    the way to go. To extend this mechanism further, I would subclass
    GenericException and created my own error code attribute on that
    subclass. That way the receiver has the choice of interpreting the
    exception based on that error code, and wrapping it in a
    MessageDialog/window or do the usual 'errormgr.showerrors()'.
    Exceptions seem a more flexible approach to me. That is, if you can live
    with the fact that by using it, you're violating the 'exceptions for
    behavioral anomalies' software engineering principle !
    Best wishes.
    Eric Pereira
    Forte Consultant
    ----Original Message Follows----
    From: "Kallambella, Ajith" <[email protected]>
    To: "'Mark Sundsten'" <[email protected]>, [email protected]
    Cc: [email protected]
    Subject: RE: Raising Exceptions Vs returning error codes
    Date: Wed, 30 Dec 1998 08:52:39 -0500
    Reply-To: "Kallambella, Ajith" <[email protected]>
    Mark,
    Identifying conditions where you would rather use an exception
    to an error_code ( and vice-versa ) normally depends on
    your application design. Usually exceptions
    are used to handle behavioral anomalies which are
    not expected during the normal course of execution of
    the program, and which would affect the continuity of
    your algorithm if ignored. Examples would be a fatal
    error, a semantically invalid( but syntactically-valid
    token ) etc.
    Error_codes and return status's can be used to handle
    anticipated and recoverable errors. Example would
    be presentation layer validations. In any normal
    UI system, the user is expected to make errors and it
    would be annoying to throw an exception( and to handle
    it ), every time user enters wrong data. A well
    modeled client layer should not only handle
    data-validation errors , but should be smart enough
    to encourage users to input correct or
    "near-correct" data. Examples could be
    making use of look-up windows etc. Interestingly,
    Express uses exceptions to handle data-validations.
    As you see, exceptions fit well into your processing
    logic where severity of damage caused by an error
    is more. Where as error_codes fit well into presentation
    logic( and some not-so-critical processing logic ) where
    errors are usually recoverable and normal path of
    execution can be easily restored.
    Hope this helps. I would be very interested to hear
    what others have to say.
    Ajith Kallambella. M
    Forte Systems Engineer,
    International Business Corporation.
    -----Original Message-----
    From: Mark Sundsten [mailto:[email protected]]
    Sent: Tuesday, December 29, 1998 2:10 PM
    To: [email protected]
    Cc: [email protected]
    Subject: Raising Exceptions vs returning error codes
    When dealing with error handling, I find myself struggling with the
    choice
    of
    raising exceptions (and handling them) from the caller
    vs returning an error code of somekind.
    When would you want to use one over the other?
    Should you always use exception handling?
    Any discussion would be appreciated.
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
    Get Your Private, Free Email at http://www.hotmail.com
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>-
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

    Hi Steve !
    Probably the following explanation might help in resolving the issue raised by
    you:
    At a more abstract level, there is only one thing, i.e. the EVENT. According to
    it's definition, an event is a relatively infrequent occurrence in one portion (lets
    call it event raiser) of the application, which some other portion (or portions,
    lets call them event handlers) (of the same application) are interested to respond
    to it. Now there are two scenarios:
    (A) Event raiser and Event handler(s) are being executed under different threads
    of control (Asynchronous) and
    (B) Event raiser and Event Handler(s) are being executed under same thread of
    control (Synchronous).
    So, Exception Handling belongs to scenario B where the method raising the
    exception (Event Raiser or exception raiser) and the method handling it (Event
    Handler or exception block) are under the same thread of control. More ever it has
    to be insured that at a time only one handler (first the inner most one) receives
    the message.
    Fort&eacute; provides a generic Event handling mechanism (Post Event and Event Loop) to
    handle the scenario A (which is the more generic one). But it also provides a
    specialized Event Handling mechanism (Raise Exception and Exception block) to
    efficiently handle the relatively simple scenario B. Why I am saying that the later
    is efficient because it won't be needing to register the event queue address of the
    interested task (after all there is only one task involved) and put the event
    message in queue.
    Finally let me mentioned that it is just my view based on the understanding I
    have and it may not be true. Only a person from fort&eacute; can confirm it. I will really
    appreciate if somebody correct and or refine it.
    Wish a Very Very Happy New Year to all Fort&eacute; Users
    Regard,
    Kailash.
    [email protected] wrote:
    I would agree with Eric entirely. Exceptions seem to me to be a much more
    complete solution to the problem of error handling. A little bit of effort up
    front in making clear the strategy for exception handling and specifying the
    exceptions that can be raised by a class\method will provide an excellent method
    for error handling.
    In the case of ensuring exceptions are always handled, a top level handler for
    GenericException will usually do the job, allowing you to write error
    information out to logs, screen, etc, and then shut down gracefully.
    The only issue I would raise with exceptions is that they are not propagated
    outside an asynchronous task. If an exception is not handled within an
    asynchronous, it will not propagate to the task that started that asynchronous
    task. Forte provides return and exception events when starting asynchronous
    tasks to cope with this, but it seems a shame to have one method of dealing with
    errors (exceptions) for synchronous behaviour, and another (events) for
    asynchronous behaviour.
    Steve Elvin
    Systems Developer
    Frontline Ltd.
    UK
    Mark,
    The problem with return codes is that there is an underlying assumption
    that the receiver will always catch and interpret that error code. This
    may or may not be good thing, depending on how you architect your
    application. If, on the other hand, you want to ensure that an error is
    always handled, if not by the receiver then by the Forte, Exceptions are
    the way to go. To extend this mechanism further, I would subclass
    GenericException and created my own error code attribute on that
    subclass. That way the receiver has the choice of interpreting the
    exception based on that error code, and wrapping it in a
    MessageDialog/window or do the usual 'errormgr.showerrors()'.
    Exceptions seem a more flexible approach to me. That is, if you can live
    with the fact that by using it, you're violating the 'exceptions for
    behavioral anomalies' software engineering principle !
    Best wishes.
    Eric Pereira
    Forte Consultant
    ----Original Message Follows----
    From: "Kallambella, Ajith" <[email protected]>
    To: "'Mark Sundsten'" <[email protected]>, [email protected]
    Cc: [email protected]
    Subject: RE: Raising Exceptions Vs returning error codes
    Date: Wed, 30 Dec 1998 08:52:39 -0500
    Reply-To: "Kallambella, Ajith" <[email protected]>
    Mark,
    Identifying conditions where you would rather use an exception
    to an error_code ( and vice-versa ) normally depends on
    your application design. Usually exceptions
    are used to handle behavioral anomalies which are
    not expected during the normal course of execution of
    the program, and which would affect the continuity of
    your algorithm if ignored. Examples would be a fatal
    error, a semantically invalid( but syntactically-valid
    token ) etc.
    Error_codes and return status's can be used to handle
    anticipated and recoverable errors. Example would
    be presentation layer validations. In any normal
    UI system, the user is expected to make errors and it
    would be annoying to throw an exception( and to handle
    it ), every time user enters wrong data. A well
    modeled client layer should not only handle
    data-validation errors , but should be smart enough
    to encourage users to input correct or
    "near-correct" data. Examples could be
    making use of look-up windows etc. Interestingly,
    Express uses exceptions to handle data-validations.
    As you see, exceptions fit well into your processing
    logic where severity of damage caused by an error
    is more. Where as error_codes fit well into presentation
    logic( and some not-so-critical processing logic ) where
    errors are usually recoverable and normal path of
    execution can be easily restored.
    Hope this helps. I would be very interested to hear
    what others have to say.
    Ajith Kallambella. M
    Forte Systems Engineer,
    International Business Corporation.
    -----Original Message-----
    From: Mark Sundsten [mailto:[email protected]]
    Sent: Tuesday, December 29, 1998 2:10 PM
    To: [email protected]
    Cc: [email protected]
    Subject: Raising Exceptions vs returning error codes
    When dealing with error handling, I find myself struggling with the
    choice
    of
    raising exceptions (and handling them) from the caller
    vs returning an error code of somekind.
    When would you want to use one over the other?
    Should you always use exception handling?
    Any discussion would be appreciated.
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
    Get Your Private, Free Email at http://www.hotmail.com
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>-
    To unsubscribe, email '[email protected]' with
    'unsubscribe forte-users' as the body of the message.
    Searchable thread archive <URL:http://pinehurst.sageit.com/listarchive/>

  • ECL Viewer 5 raise exceptions viewing tif drawings

    Hello all,
    Bit of a strange one here that hopefully someone may be able to help me with...
    We are (still) running 4.6C, on Ora 9.2.0.7 over Windows.
    We are running 640 Gui patched to 24
    We have deployed (in a failed attempt to stop the error I will describe below) ECL viewer 5.1.3.
    Client machines are running XP with SP2
    Error:
    after entering MM03 and choosing Additional Data > Document Data we click on an attchment (doc type DRG) and choose to view via the display (glasses) icon.  The tif file (which is copied into C:\temp) opens.  many of the tif files (scanned drawings) have multiple pages so we move to the next page by clicking 'Navigation' > 'next'. 
    The problem is that after a seemingly random amount of clicks on to next pages a raise exception occurs.  After the short dump it is no longer possible to view the document again as we get the error 'file c:\temp\xxxxx.tif cannot be created' and so the only way to view the drawing is either to access the file from the temp directory or completly log out of SAP and relog back in.
    i have searched for notes and we were advised to deploy the 5.1.3 viewer which only seems to have made it worse because before the 5.1.3 deployment we were getting many short dumps but the user oddly didn't see the short dump on their screens - now 5.1.3 is in place the user now sees the short dump and calls the support desk very often.
    Has anyone been unfortunate enough to have experienced this before or anyone got any brain waves????
    yours thankful in advance and loosing the will to live,
    Andy
    ps here is the short dump extract:
                                                                                    Error analysis                                                                               
    A RAISE statement in the program "CL_GUI_CFW====================CP " raised the
    exception                                                                    
    condition "CNTL_ERROR".                                                       
    Since the exception was not intercepted by a superior program                 
    in the hierarchy, processing was terminated.                                                                               
    Short description of exception condition:                                                                               
    For detailed documentation of the exception condition, use                    
    Transaction SE37 (Function Library). You can take the called                  
    function module from the display of active calls.                             
    How to correct the error                                                                               
    If the error occurred in a non-modified SAP program, you may be               
    able to find a solution in the SAP note system.                               
    If you have access to the note system yourself, use the following             
    search criteria:                                                                               
    "RAISE_EXCEPTION"                                                            
    "CL_GUI_CFW====================CP " or "CL_GUI_CFW====================CM00P "
    "UPDATE_VIEW"                                                                
    or                                                                               
    "CL_GUI_CFW====================CP " "CNTL_ERROR"                                                                               
    or                                                                               
    "SAPMMG01 " "CNTL_ERROR"                                                      
    If you cannot solve the problem yourself, please send the                     
    following documents to SAP:                                                                               
    1. A hard copy print describing the problem.                                  
       To obtain this, select the "Print" function on the current screen.         
    2. A suitable hardcopy prinout of the system log.                             
       To obtain this, call the system log with Transaction SM21                  
       and select the "Print" function to print out the relevant                  
       part.                                                                               
    3. If the programs are your own programs or modified SAP programs,            
       supply the source code.                                                    
       To do this, you can either use the "PRINT" command in the editor or        
       print the programs using the report RSINCL00.

    Hi Andy,
    I would recommend you to upgrade to the latest available ECL Viewer version 6.
    Please see SAP note 1083901.
    Further please upgrade also your SAPGUI to the latest patch level as explained in note 164203. After this upgrade please un-install your ECL Viewer 5.1.3 by using one of the following mehtods:
    Search for WebViewer2d.dll file. If it is present at more than one place then it means ECL Viewer is installed more than once without uninstalling the previous version (You can check the folders and should be able to see all the dll's for ECL Viewer such WebViewer3d.dll/Printing.dll etc to make sure that there is not only single file but the whole installation).
    In this case:
    A) Uninstall the version integrated with SAP GUI by using SAP Installation scripts. You need to uncheck the 'EAI Viewer' component in 'General Add-on' option.
    B) Check add/remove program and if there is an entry like SAP Viewer, uninstall it.
    After this search again, and you should not get WebViewer2d.dll file on machine. Now reinstall the latest Viewer. This should solve most of the issue related to inconsistencies.
    Then install the latest ECL Viewer 6 and the issue should be solved.
    Best regards,
    Christoph

  • Raising exceptions in event handlers?

    Hi
    Is it possible to raise exceptions in event handler? As an example, I added a listener to a UnitOfWork, and implemented the preCommitUnitOfWork() method. In the method, I'm performing some operations, and if something goes wrong, I need to roll back the entire UnitOfWork. Is this possible to raison an exception, or is there some other way to acheive this?
    Thanks
    Regards
    Eric

    Hi
    Is it possible to raise exceptions in event handler? As an example, I added a listener to a UnitOfWork, and implemented the preCommitUnitOfWork() method. In the method, I'm performing some operations, and if something goes wrong, I need to roll back the entire UnitOfWork. Is this possible to raison an exception, or is there some other way to acheive this?Eric,
    I tried this and had some success with a simple test case. I created an exception that extends the oracle.toplink.exceptions.TopLinkException class. Then I added the throws clause to the preCommitUnitOfWork event handler. Throwing my custom exception (that extends TopLinkException) from the event handler works fine and should allow you to retry your update, etc. Note that as long as the exception is thrown at "preCommit" time you should not need to roll anything back as the updates were not applied to the cache or DB. Also, if you applied updates to your registered clones instead of the original objects, the original objects state should be unchanged.
    Hope this helps,
    Pete Farkas

  • An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help The profile for the user is a temporary profile. (Exception from HRESULT: 0x80090024)

    An internal error occurred on the report server. See the error log for more details. (rsInternalError) Get Online Help The profile for the user is a temporary profile. (Exception from HRESULT: 0x80090024) 
     while proview the report i will get this error am using sql server 2008R2,
    can u plesae hlep me out for this
     

    <Header>
      <Product>Microsoft SQL Server Reporting Services Version 2009.0100.1600.01 ((KJ_RTM).100402-1539 )</Product>
      <Locale>English (United States)</Locale>
      <TimeZone>W. Europe Standard Time</TimeZone>
      <Path>C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVEREPORT\Reporting Services\Logfiles\ReportServerService__01_30_2015_03_09_32.log</Path>
      <SystemName>WEGDACM1</SystemName>
      <OSName>Microsoft Windows NT 6.1.7601 Service Pack 1</OSName>
      <OSVersion>6.1.7601</OSVersion>
      <ProcessID>4880</ProcessID>
      <Virtualization>Hypervisor</Virtualization>
    </Header>
    rshost!rshost!5e4!01/30/2015-03:09:32:: i INFO: Currently registered url http://+:80/ReportServer_MSSQLSERVEREPORT/ on endpoint 2
    rshost!rshost!5e4!01/30/2015-03:09:32:: e ERROR: Failed to register url=http://+:80/Reports/ for endpoint 3, error=b7.
    rshost!rshost!5e4!01/30/2015-03:09:32:: w WARN: Endpoint 3 is enabled but no url is registered for vdir=/Reports, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVEREPORT\Reporting Services\ReportManager.
    servicecontroller!DefaultDomain!1e30!01/30/2015-03:09:32:: e ERROR: Error creating HTTP endpoint. System.Runtime.InteropServices.COMException (0x800700B7): Cannot create a file when that file already exists. (Exception from HRESULT: 0x800700B7)
       at Microsoft.ReportingServices.HostingInterfaces.IRsUnmanagedCallback.CreateHttpEndpoint(RsAppDomainType application, String[] urlPrefixes, Int32 cPrefixes, String[] hosts, Int32 cHosts, Boolean wildCardPresent, String virtualDirectory, String
    filePath, Int32 authType, Int32 logonMethod, String authDomain, String authRealm, Boolean authPersist, Int32 extendedProtectionLevel, Int32 extendedProtectionScenario, Boolean enabled)
       at Microsoft.ReportingServices.Library.ServiceAppDomainController.SetWebConfiguration(RunningApplication rsApplication, Boolean enabled, String folder)
    rshost!rshost!65c!01/30/2015-03:09:32:: i INFO: Endpoint 4 is disabled and no url is registered vdir=/ReportServer_MSSQLSERVEREPORT/ReportBuilder, pdir=C:\Program Files\Microsoft SQL Server\MSRS10_50.MSSQLSERVEREPORT\Reporting Services\ReportServer\ReportBuilder.
    rshost!rshost!1e30!01/30/2015-03:09:32:: i INFO: Derived memory configuration based on physical memory as 16776696 KB
    servicecontroller!DefaultDomain!1e30!01/30/2015-03:09:32:: i INFO: Recycling the service from the default domain
    rshost!rshost!1e30!01/30/2015-03:09:46:: i INFO: Application domain type WindowsService statistics: created: 7, unloaded: 7, failed: 0, timed out: 0.
    appdomainmanager!DefaultDomain!1e30!01/30/2015-03:09:46:: i INFO: Appdomain:11 WindowsService_7 started.
    library!WindowsService_7!1e30!01/30/2015-03:09:46:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    servicecontroller!WindowsService_7!1e30!01/30/2015-03:09:46:: e ERROR: Error initializing configuration from the database: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration
    error. 
    resourceutilities!WindowsService_7!1e30!01/30/2015-03:09:47:: i INFO: Reporting Services starting SKU: Enterprise
    servicecontroller!WindowsService_6!1e30!01/30/2015-03:09:47:: i INFO: Service controller exiting.
    appdomainmanager!DefaultDomain!1e30!01/30/2015-03:09:47:: i INFO: Appdomain:10 unregistered.
    appdomainmanager!DefaultDomain!1e30!01/30/2015-03:09:47:: i INFO: Appdomain:10 WindowsService_6 unloading.
    appdomainmanager!DefaultDomain!1f40!01/30/2015-03:09:47:: i INFO: AppDomain:10 0 pending unload(s)
    library!WindowsService_7!2410!01/30/2015-03:09:47:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    library!WindowsService_7!2410!01/30/2015-03:09:47:: e ERROR: ServiceStartThread: Exception caught while starting service. Error: Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: The report server has encountered a configuration
    error. 
    library!WindowsService_7!2410!01/30/2015-03:09:47:: e ERROR: ServiceStartThread: Attempting to start service again...
    library!DefaultDomain!202c!01/30/2015-08:04:43:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    library!DefaultDomain!202c!01/30/2015-08:25:26:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    library!DefaultDomain!202c!01/30/2015-08:26:16:: e ERROR: Throwing Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException: No DSN present in configuration file, Microsoft.ReportingServices.Diagnostics.Utilities.ServerConfigurationErrorException:
    The report server has encountered a configuration error. ;
    The above is my log file pls find it resolve my problem,am trying to add the encryption key to my configuration seetings it will through the error like The profile you were used is temporary profile.

  • Raising Exception-Proxy

    Hi Group,
    Can any body suggest how to raise exception in ABAP proxy with custom message and I want to fail message in SXMB_MONI .
    -Rajiv

    Hi Rajiv
    In addition to the code provided by Jorg's link above, you can also use the RAISE static method in class CL_PROXY_FAULT. This is useful if you already have error messages in the common BAPI return table.
      cl_proxy_fault=>raise( exception_class_name = 'ZCL_YOUR_EXCEPTION_CLASS'
                                              bapireturn_tab                 = t_bapiret2 ).
    Do note that as mentioned by Jorg, you still need to define the fault message, which then causes your error to appear as an "Application Error" in the monitor. ZCL_YOUR_EXCEPTION_CLASS is subclass of CX_AI_APPLICATION_FAULT, and would be automatically generated from the fault message when you generate your proxy.
    Rgds
    Eng Swee

  • UDF to raise exception

    Hi,
    Can anyone help me in providing me the UDF / java code to raise exceptions and fail the mapping.
    I can do it by usinf string out of bound exception to fail the mapping ( which is one of the way).
    But i need to invoke the exception clause to throw the custom message.
    Can anyone please throw some light on this could be helpful..
    Thanks,
    Sneha

    Hi Sneha,
    public String throwexception(String input, Container container) throws StreamTransformationException{
    if(input.equals("ERROR"))
    throw new RuntimeException("Mapping fail");
    else
    return input;
    refer this
    Throwing Custom Exception in SXMB_MONI( Error Node)
    Also see,
    Throwing Smart Exceptions in XI Graphical Mapping
    /people/alessandro.guarneri/blog/2006/01/26/throwing-smart-exceptions-in-xi-graphical-mapping
    XI/PI: Throwing Generic Exceptions from any type of Mapping
    /people/michal.krawczyk2/blog/2007/04/26/xipi-throwing-generic-exceptions-from-any-type-of-mapping

  • Names in Members field under the UNIX Attributes Tab have changed from standard format (i.e. John Doe) to the actual account name (jdoe)

    Hello,
    Names in Members field under the UNIX Attributes Tab have changed from standard format (i.e. John Doe) to the actual account name (jdoe). The only time this happens is if a domain account is deleted and the remnant of the account remains and has to be removed
    manually. However all of the accounts, with the exception of any new ones recently added, now show the account name only. Any ideas on what caused this and how to fix it?
    Thanks :)

    Hi,
    I have not heard from you for some days, currently I am providing the related article for you. Hope this will help you on this matter.
    The UNIX Attributes tab does not appear in the Active Directory Users and Computers MMC snap-in when Server for NIS is installed in the domain
    http://support.microsoft.com/kb/921913/en-us
    Thank you.
    Best regards,
    Steven Song
    Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.

  • Error raising exception in user-exit for idoc_output_delvry.

    Hi All,
       When I try to raise an exception from the user exit (idoc_output_delvry),
    I get an error message 'Assign Measurement unit to ISO code'.
        Can you help me solve this issue.
    Thanks in avance,
    Disney.

    Michael,
           Thanks for the quick response,
    I did check in IMG, an entry is already there, the 'primary field' is checked,
    USD is assigned to the iso code USD.
    Regards,
    Disney.

Maybe you are looking for

  • Dbms_xmlquery.getxml problem

    SQL> select * from emp; EMPNO ENAME JOB MGR HIREDATE SAL COMM --------- ---------- --------- ---------- --------- ---------- ---------- ---------- --------- ------------ 7369 SMITH CLERK 7902 17-DEC-80 800 20 14 rows selected. SQL> select dbms_xmlque

  • Ldap.ora

    Hello, I need to setup an ldap with Oracle v.10g. I read that sqlnet.ora and ldap.ora files are used. Where theses files must be located, on the client or on the server? Has somebody examples of theses two files? Thanks in advance for your help Fabri

  • MacBook Pro Retina Display Quit - A1502

    My MacBook Pro Retina display has quit. It stopped working in the middle of operation and will not come on. The computer boots fine (at least chimes), but nothing in the display. Have tried all possible keyboard resets--no luck. It was not set up for

  • Create multiple Still Proxies

    Having a problem creating multiple still proxies. Basically what I want to do is select all the layers in a PSD imported as a cropped comp and create a half res proxy for each item. the right click "create proxy" option is disabled when I select more

  • One field on update screen refuses to update.

    What the subject line means is this: I have one field (but only one) on my update screen that won't accept a change. When I click Apply Changes it shifts back to the interactive report showing the previous value of that field. I can change anything e