Monitoring the manual recovery queue

Recently we have had a large number of transactions going into the manual recovery queue on our produbion BPEL app server. I have tuend the thread performance and this has helped.
However we would like to setup a notification when we get something in the manaul recovery queue. Is there a way to monitor the manual recovery queue for certain processes, and if so, how?

You could write a BPEL process that wraps a databse adapter that monitors rows in the hydration store, or use Java Embedding and the API;s to monitor the messages ending on the queue. The API guide has some details on how to do this.
Pete

Similar Messages

  • Manual Recovery Queue

    When messages end up on the manual recovery queue the operator needs to intervene.
    I thought I read somewhere there was a recovery agent that can be configured to automatically recover the messages.
    Does anyone know if this is true.
    Pete

    For invocation msgs. Similar for other cases. Just an example.
    import com.oracle.bpel.client.IBPELDomainHandle;
    import com.oracle.bpel.client.IBPELProcessHandle;
    import com.oracle.bpel.client.IDeliveryConstants;
    import com.oracle.bpel.client.IInvokeMetaData;
    import com.oracle.bpel.client.Locator;
    import com.oracle.bpel.client.NormalizedMessage;
    import com.oracle.bpel.client.ServerException;
    import com.oracle.bpel.client.delivery.IDeliveryService;
    import com.oracle.bpel.client.util.SQLDefs;
    import com.oracle.bpel.client.util.WhereCondition;
    import java.util.Hashtable;
    import com.evermind.server.rmi.RMIInitialContextFactory;
    public class BpelRecovery
    private Locator locator = null;
    public BpelRecovery() throws Exception
    Hashtable ctx = new Hashtable();
    ctx.put("orabpel.platform", "oc4j_10g");
    ctx.put("java.naming.factory.initial", "com.evermind.server.rmi.RMIInitialContextFactory");
    ctx.put("java.naming.provider.url", "ormi://localhost/orabpel");
    ctx.put("java.naming.security.principal", "admin");
    ctx.put("java.naming.security.credentials", "welcome");
    try
    System.out.println ("Connecting to BPEL...");
    locator = new Locator("default","bpel", ctx);
    IDeliveryService deliveryService = (IDeliveryService)locator.lookupService(IDeliveryService.SERVICE_NAME );
    catch (Exception e)
    e.printStackTrace();
    throw new Exception ("Failed to connect to BPEL, caused by " + e.getMessage());
    public void recovery() throws Exception
    IBPELProcessHandle[] pcs = locator.listProcesses();
    StringBuffer buf = new StringBuffer();
    WhereCondition where = new WhereCondition( buf.append(SQLDefs.IM_state)
    .append( " = " )
    .append( IDeliveryConstants.STATE_UNRESOLVED )
    .toString() );
    IInvokeMetaData[]imd = locator.listInvokeMessages(where);
    String[] ids = new String[imd.length];
    for (int i = 0; i < imd.length; i++)
    System.out.println("ConversationId=" + imd.getConversationId());
    System.out.println("ProcessId=" + imd[i].getProcessId());
    System.out.println("State=" + imd[i].getState());
    ids[1] = imd[i].getConversationId();
    locator.lookupDomain().recoverInvokeMessages(ids);
    public static void main(String[] args) throws Exception
    BpelRecovery recovery = new BpelRecovery();
    recovery.recovery();
    System.out.println("done");

  • Python script to automate the manual recovery of BPEL instances in SOA 11g

    I have a requirement for automating the manual recovery of BPEL instances pending for recovery at a particular time. It will be called inside a cron job.
    Any help will be much appreciated.
    Thanks in advance,
    Ravi Prakash

    Hi,
    When I try to recover the instance that is waiting for manual recovery, I didn't see anything happening.
    Also the the fault policy is active and working fine during the retry intervals. That means If I disable one of the webservices and enable them during the retry it is success after some failure retries.
    Any ides why the recovery not working in SOA 10.1.3.3
    --Khaleel                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • How do I send instance for manual recovery at run time.

    Hi
    I have a BPEL process within which I am trying to handle a business error. I understand using the default-policies on the application server I can send a message for manual recovery. But is it possible to force an instance into the manual recovery queue in the event of a handled error?
    I have previosuly used the default policies to route remote/binding faults to the activities tab (manual recovery) tab and the users find this useful to adjust XM land retry, re-throw etc. But can we do the same for errors handled within the BPEL. So if I have a catch all within my process how would I send the instance to this manual recovery queue.
    Thanks
    Rich

    I hate it when after an hour's searching I post a question
    and then find the answer ten minutes later...
    "Current VI's Path" on the file IO palette...
    Bob

  • Manual Recovery

    Could somebody please tell me why a process could go into manual recovery list. One of my processes is getting into the manual recovery list and am not able to see its activity flow. The console keeps saying "Try again".
    Thanks,
    Valli.

    Could somebody help me with the below.
    Thanks,
    Valli.

  • Do instance id #s change on manual recovery?

    We are having instance which go to the manual recovery list, and so we recover them.
    Then on the log we see these types of messages:
    <INFO> <default.collaxa.cube.engine> <CubeEngine::expireActivity> Instance/activity not found, next expiration attempt (?/5) for activity "130130-BpInv1-BpTry2.10-1" scheduled for "November 14, 2007 8:32:43 AM GMT"
    These messages are referencing instances that don't exist on the server, maybe an instance number less(in this example 130129) or instance number more(in this example 130131) do exist, but this one doesn't.
    So we are thinking if this instance gets a new number id once it is recovered. Does anyone know about if this is true or false?

    may i know the release number of bpel engine? obversion.sh or obversion.bat should give this info.
    are there any other errors (rollback exceptions) in the log file? looks like the invoke failed due to some system exception, the transaction rolled back but the retry gets scheduled...we fixed similar issue in 10.1.3.3.

  • Manual Recovery of BPEL Instances -- Failed

    Hi
    I am facing some issue related to Manual Recovery Process. All my BPEL instances are sitting in the Manual Recovery Mode, when I try to Recover / Call the instances, the console if failing to deliver the Conversation ID.
    Can any one help me out..
    Regards
    Kirthi

    Hi,
    When I try to recover the instance that is waiting for manual recovery, I didn't see anything happening.
    Also the the fault policy is active and working fine during the retry intervals. That means If I disable one of the webservices and enable them during the retry it is success after some failure retries.
    Any ides why the recovery not working in SOA 10.1.3.3
    --Khaleel                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Callback Manual Recovery record created and never cleared

    Hi Guy's,
    I just noticed (meaning its been happening all along) in the Manual Recovery function of BPEL console, that under the 'callback' option, there seems to be an entry in there for most if not all BPEL processes that have ever been invoked. They don't seem to ever clear, and if I perform a manual recovery, this is the output traced to domain.log:
    <2007-09-14 11:43:52,510> <DEBUG> <gmc.collaxa.cube.engine.delivery> <SOAPProtocolHandler::resolveSubscriber> trying to find callbacks of convId=MD5{6e3d428f177762ae547ed02a43caca5a}
    <2007-09-14 11:43:52,513> <DEBUG> <gmc.collaxa.cube.engine.delivery> <SOAPProtocolHandler::resolveSubscriber> No callbacks are found of convId=MD5{6e3d428f177762ae547ed02a43caca5a}
    <2007-09-14 11:43:52,513> <DEBUG> <gmc.collaxa.cube.engine.delivery> <DeliveryService::resolveSubscriber> No messages found for subscriber bpel://localhost/gmc/SFI_CreateExceptionTask~1.0/2500004-BpRcv1-BpSeq2.9-4 for conversation MD5{6e3d428f177762ae547ed02a43caca5a}
    <2007-09-14 11:55:44,760> <DEBUG> <gmc.collaxa.cube.engine.delivery> <DeliveryService::resolveCallback> Resolving subscribers for convId bpel://localhost/gmc/SFI_CreateChartOfAccount~1.0/2500016-BpInv2-BpSeq5.15-1, msgGuid=51b8f0982742e789:-74af1a88:1150396d9bc:-7a53
    <2007-09-14 11:55:44,775> <DEBUG> <gmc.collaxa.cube.engine.delivery> <SOAPProtocolHandler::resolveCallback> trying to find subscribers for convId=bpel://localhost/gmc/SFI_CreateChartOfAccount~1.0/2500016-BpInv2-BpSeq5.15-1, operation onResult, process bpel://localhost/gmc/SFI_CreateChartOfAccount~1.0/
    <2007-09-14 11:55:44,777> <DEBUG> <gmc.collaxa.cube.engine.delivery> <SOAPProtocolHandler::resolveCallback> No subscribers found for convId: bpel://localhost/gmc/SFI_CreateChartOfAccount~1.0/2500016-BpInv2-BpSeq5.15-1
    <2007-09-14 11:55:44,777> <DEBUG> <gmc.collaxa.cube.engine.delivery> <DeliveryService::resolveCallback> No subscribers found for message 51b8f0982742e789:-74af1a88:1150396d9bc:-7a53 for conversation bpel://localhost/gmc/SFI_CreateChartOfAccount~1.0/2500016-BpInv2-BpSeq5.15-1
    <2007-09-14 11:56:11,540> <DEBUG> <gmc.collaxa.cube.engine.delivery> <DeliveryService::resolveCallback> Resolving subscribers for convId bpel://localhost/gmc/SFI_CreateChartOfAccount~1.0/2500016-BpInv2-BpSeq5.15-1, msgGuid=51b8f0982742e789:-74af1a88:1150396d9bc:-7a53
    <2007-09-14 11:56:11,547> <DEBUG> <gmc.collaxa.cube.engine.delivery> <SOAPProtocolHandler::resolveCallback> trying to find subscribers for convId=bpel://localhost/gmc/SFI_CreateChartOfAccount~1.0/2500016-BpInv2-BpSeq5.15-1, operation onResult, process bpel://localhost/gmc/SFI_CreateChartOfAccount~1.0/
    <2007-09-14 11:56:11,548> <DEBUG> <gmc.collaxa.cube.engine.delivery> <SOAPProtocolHandler::resolveCallback> No subscribers found for convId: bpel://localhost/gmc/SFI_CreateChartOfAccount~1.0/2500016-BpInv2-BpSeq5.15-1
    <2007-09-14 11:56:11,548> <DEBUG> <gmc.collaxa.cube.engine.delivery> <DeliveryService::resolveCallback> No subscribers found for message 51b8f0982742e789:-74af1a88:1150396d9bc:-7a53 for conversation bpel://localhost/gmc/SFI_CreateChartOfAccount~1.0/2500016-BpInv2-BpSeq5.15-1
    Any ideas what I might have configured incorrectly?
    Thanks.

    Hi Subhra,
    you could configure the FileAdapter debatching to say only raise 100 records at a time as part of one xml payload/BPEL instance. That way on failure less records will need to be retried. Performance may be a little more stable as a result too.
    As for on retry getting unique constraint exceptions, I would try using 'merge' instead of 'insert'. Merge does an existence check first and if your payload sizes are 100+ the performance hit is very minimal, as it does a single existence query for all rows at once.
    Thanks
    Steve

  • BPEL manual recovery - 10.1.3.3

    Hi,
    We have some stuck processes in our BPEL manual recovery console.
    We have tried recovering messages from the console itself. However they still dont to disappear and create an instance.
    I dont see anything in the logs as well.
    Can you please help in getting the messages? ALso, is the payload stored anywhere?
    Version is 10.1.3.3
    Thanks,
    Rosh

    On BPEL Console, select your domain. Go To Configuration --> Logging and increase the logging level, preferably to All or DEBUG. Now try to recover and check if you find anything in logs.
    On the Manual Recovery (invoke/recv/activity), when you click on conversation Id, are you able to see the right payload ?

  • Auto retry for the instances under manual recovery

    Hi
    I have a situation where i need to refire all the instances which are in activities tab [because of manual intervention in the fault policy] at regular intervals.
    Checked the documentation where it says in 10.1.3.4 we can configure a time frame where it will refire all the instances which are in recover tab under administration.
    Tried out that option but it is not taking the instacnes which are in activities tab
    Can some one suggest a workaround for this
    Thanks
    Vamsi

    Hi,
    When I try to recover the instance that is waiting for manual recovery, I didn't see anything happening.
    Also the the fault policy is active and working fine during the retry intervals. That means If I disable one of the webservices and enable them during the retry it is success after some failure retries.
    Any ides why the recovery not working in SOA 10.1.3.3
    --Khaleel                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                       

  • Issues monitoring the 2602i Cisco AP with Zabbix.

    Hi!
    My workplace just bought a lot of Cisco AP (2602i) and a WLC 2500 and I'm in deep trouble trying to monitor them with Zabbix, wich is the SW we use for our whole Network.
    After a lot of time I got to monitor the CPU use (in %), traffic of each interface, the AP serial number and the AP software version.
    I really need to monitor how many clients are connected (associated) to each radio and if the AP mode Flex Connect it is activated or not.
    I would really appreciate some help with this, I'm out of ideas!
    Thanks you soooo very much!
    Some extra info regarding my APs:
    AP6c41.6aa3.4b6e#show version 
    Cisco IOS Software, C2600 Software (AP3G2-K9W8-M), Version 15.2(4)JB3, RELEASE SOFTWARE (fc1)
    Technical Support: http://www.cisco.com/techsupport
    Copyright (c) 1986-2013 by Cisco Systems, Inc.
    Compiled Wed 18-Dec-13 22:30 by prod_rel_team
    ROM: Bootstrap program is C2600 boot loader
    BOOTLDR: C2600 Boot Loader (AP3G2-BOOT-M) LoaderVersion 12.4(25e)JA1, RELEASE SOFTWARE (fc1)
    AP6c41.6aa3.4b6e uptime is 1 week, 4 days, 3 hours, 16 minutes
    System returned to ROM by power-on
    System image file is "flash:/ap3g2-k9w8-mx.152-4.JB3/ap3g2-k9w8-xx.152-4.JB3"
    Last reload reason: 
    This product contains cryptographic features and is subject to United
    States and local country laws governing import, export, transfer and
    use. Delivery of Cisco cryptographic products does not imply
    third-party authority to import, export, distribute or use encryption.
    Importers, exporters, distributors and users are responsible for
    compliance with U.S. and local country laws. By using this product you
    agree to comply with applicable laws and regulations. If you are unable
    to comply with U.S. and local laws, return this product immediately.
    A summary of U.S. laws governing Cisco cryptographic products may be found at:
    http://www.cisco.com/wwl/export/crypto/tool/stqrg.html
    If you require further assistance please contact us by sending email to
    [email protected].
    cisco AIR-CAP2602I-A-K9 (PowerPC) processor (revision A0) with 204790K/57344K bytes of memory.
    Processor board ID FTX1723J66B
    PowerPC CPU at 800Mhz, revision number 0x2151
    Last reset from power-on
    LWAPP image version 7.6.100.0
    1 Gigabit Ethernet interface
    2 802.11 Radios
    32K bytes of flash-simulated non-volatile configuration memory.
    Base ethernet MAC Address: 6C:41:6A:A3:4B:6E
    Part Number                          : 73-14588-02
    PCA Assembly Number                  : 800-37899-01
    PCA Revision Number                  : A0
    PCB Serial Number                    : FOC17191EJT
    Top Assembly Part Number             : 800-38356-01
    Top Assembly Serial Number           : FTX1723J66B
    Top Revision Number                  : A0
    Product/Model Number                 : AIR-CAP2602I-A-K9   
    Configuration register is 0xF
    AP6c41.6aa3.4b6e# Connection to 172.19.0.110 closed by remote host.
    Connection to 172.19.0.110 closed.

    Hey Saul,
    I didn't really solve my problem.
    I managed to monitor some items (connected clients, rogue aps, eth rx total, eth tx total, last reboot reason, lwapp image version, lwapp os version, mac address eth, ap name, power status, ssh enable, shown in the attachment) but those are just regular items and, to be able to monitor them, after each OID I had to write the AP's mac address in decimal format  (which I did using Macro's to make it automatic, taking it from another OID). 
    Now at this point I have two issues:
    First - using this template, which I applied one per AP host referring to the WLC IP address, makes my Zabbix Queue and Zabbix busy unreachable poller processes go up to the sky, which is no good at all and that's why I'm still working on how to fix this (maybe changing the way I monitor de APs at all).
    Second - I still couldn't monitor important stuff regarding reach radio (for example), since all my APs have two radios and I find it interesting to monitor which channel are they at. The issue with this is (after a little internet research) that Zabbix allows me to use a Discovery Rule with only one variable field, in this case, the AP's mac address. It wouldn't allow me to double the Discovery Rule.
    Let me be more explicit regarding this second issue with an example.
    1.3.6.1.4.1.9.9.513.1.2.1.1.21 is the OID where I can find info regarding the radio channel.
    208.199.137.14.211.112 is my AP's mac
    0 or 1 indicates which radio I'm talking about (also dynamic as you see).
    So to get that info it would be something like (and its response):
    1.3.6.1.4.1.9.9.513.1.2.1.1.21.208.199.137.14.211.112.0 =  STRING: "This is a 802.11b/g interface, slot ID is 0"
    1.3.6.1.4.1.9.9.513.1.2.1.1.21.208.199.137.14.211.112.1 =  STRING: "This is a 802.11a interface, slot ID is 1"
    So as you see, I have to variable fields, the AP's mac and the radio index (0 or 1).
    I would really love to monitor it with the help of a discovery rule, a double one which doesn't exist.
    Of course you can do it manually, for each of your AP's radios and for each of your APs but, in my network scenario, we have more than two or three APs so it makes this impossible and poorly efficient. 
    I'm sorry for not having the answers and I really hope this helps you.
    Cheers!
    Yael

  • Error while monitoring the Info Package

    Hi,
    While monitoring the info package, I'm having the following errors:(The data source is of type standard R3 Datasource).
    " Error when updating Idocs in Source System
    Diagnosis
    Errors have been reported in Source System during IDoc update:
    System Response
    Some IDocs have error status.
    Procedure
    Check the IDocs in Source System . You do this using the extraction monitor.
    Error handling:
    How you resolve the errors depends on the error message you get.       "
          pls help me in this...
    With regards,
    Yokesh.

    Hi Yokesh,
    Try these to solve your issue,
    tRFC Error - status running Yellow for long time (Transact RFC will be enabled in Status tab in RSMO).
    Step 1: Goto Details, Status get the IDoc number,and go to BD87 in R/3,place the cursor in the RED IDoc entroes in tRFC
    queue thats under outbound processing and click on display the IDOC which is on the menu bar.
    Step 2: In the next screen click on Display tRFC calls (will take you to SM58 particular TRFC call)
    place the cursor on the particular Transaction ID and go to EDIT in the menu bar --> press 'Execute LUW'
    (Display tRFC calls (will take you to SM58 particular TRFC call) ---> select the TrasnID ---> EDIT ---> Execute LUW)
    Rather than going to SM58 and executing LUW directly it is safer to go through BD87 giving the IDOC name as it will take you
    to the particular TRFC request for that Idoc.
    OR
    Go into the JOB Overview of the Load there you should be able to find the Data Package ID.
    (For this in RSMO Screen> Environment> there is a option for Job overview.)
    This Data Package TID is Transaction ID in SM58.
    OR
    SM58 > Give * / user name or background (Aleremote) user name and execute.It will show you all the pending TRFC with
    Transaction ID.
    In the Status Text column you can see two status
    Transation Recorded and Transaction Executing
    Don't disturb, if the status is second one Transaction Executing. If the status is first one (Transation Recorded) manually
    execute the "Execute LUWs"
    OR
    Directly go to SM58 > Give * / user name or background (Aleremote) user name and execute. It will show TRFCs to be executed
    for that user. Find the particular TRFC (SM37 > Req name > TID from data packet with sysfail).select the TrasnID (SM58) --->
    EDIT ---> Execute LUW
    OR
    In RSMO, select the particular load you want to monitor.
    In the menu bar, Environment >>> Transact. RFC >>> Select whichever is required, BW or Source System.
    In the next screen you can select the Execute button and the IDOCS will be displayed.
    Hope it helps
    Regards,
    Arun.M.D

  • How do I install just the Lion installer via the lion recovery partition.

    I am trying to bootcamp windows 7 on my new macbook pro (early 2011), the installation was successfull but i am missing drivers on the windows side and cannot access the internet until i install them.  I installed all the bootcamp updates and put them on a usb to transfer to windows partition but windows kept telling me i need an earlier version of bootcamp which is not available from the update support downloads section of the apple website.
    After some research i realized i needed the mac boot disc for lion, which doesnt exist so i need to create my own.  I was told i could install lion from the lion recovery partition.
    here is my question....If i install lion onto my mac partition that currently has lion, can i stop the download after the initial 4 gb installer and not go through with the full re-installation of lion?  so that i can then take the installesd.dmg (i think thats right) file and put it on a dvd to install from the windows partition and finally get the drivers i need to get it running.
    Comment: based on what i have read on how you used to bootcamp a mac, apple has made it very difficult, unneccesarily difficult it seems.

    Before you do anything else, I suggest a thorough read of this:
    http://manuals.info.apple.com/en_US/boot_camp_install-setup_10.7.pdf

  • What is required in the HOST and QUEUE field when ...

    Hi
    When setting up my printer, i fill the options identical to what follows:
    PRINTER:  SAMSUNG HOME
    DRIVER:    GENERAL
    BEARER:  LPR <-----------------------------( NOT SURE IF IT IS THE CORRECT OPTION TO SELECT )
    The following fields appear once LPR is selected:
    ACCES POINT : HOME
    HOST:              WHAT COMES HERE?
    USER:              SKY00BER
    QUEUE:            WHAT COMES HERE?
    ORIENTATION: PORTRAIT
    PAPER SIZE: A4
     if it helps, my printer is SAMSUNG CLX-3175FW. It is Wifi Enable and is connected to my HOME acces point.
    please do correct me if there has to be changes to the BEARER or anything else.
    i could really use some help.
    thanks in advanced.

    sky00ber wrote:
     Hi,
    What is required in the HOST and QUEUE field when setting a WIFI printer?
    When setting up my printer, i fill the options identical to what follows:
    PRINTER:  SAMSUNG HOME
    DRIVER:    GENERAL
    BEARER:  LPR <-----------------------------( NOT SURE IF IT IS THE CORRECT OPTION TO SELECT )
    The following fields appear once LPR is selected:
    ACCES POINT : HOME
    HOST:              WHAT COMES HERE?
    USER:              SKY00BER
    QUEUE:            WHAT COMES HERE?
    ORIENTATION: PORTRAIT
    PAPER SIZE: A4
     if it helps, my printer is SAMSUNG CLX-3175FW. It is Wifi Enable and is connected to my HOME acces point.
    please do correct me if there has to be changes to the BEARER or anything else.
    HELP URGENTLY NEEDED!
    I'm not sure but I give it a try.Turn your security(WPA/WEP) and Firewall temporarely off. HOST is the IP address of the printer. QUEUE can be YES or a specific amount of prints, like 1,2,3......
    If I look at the manual of your printer I see that you can find the IP and MAC addresses in the Network Configuration Report.I don't know what the USER is doing there because if there is a user then there must be a password.
    ‡Thank you for hitting the Blue/Green Star button‡
    N8-00 RM 596 V:111.030.0609; E71-1(05) RM 346 V: 500.21.009

  • Spool requests are being sent the the B9 printer queue(RSNAST00).

    Hi gurus,
    has anyone found a fix for this issue? i'm currently experiencing the same issue and would like to know how i can fix this..
    Spool requests are being sent the the B9 printer queue. Most spool requests are for one page, when there are spool requests for multiple pages these spool requests take longer to create, in the meantime, other spool requests that are single pages are going to the printer queue. This creates and "out-of-vendor-order" issue during printing.
    The out of vendor order sequencing creates a significant level of work effort for the business users to resort the printed copies in order to prepare the documents for mailing. A change is required to eliminate this manual effort.
    Development has indicated an enhancement could be made to the RSNAST00 program where only those print jobs for application "MR" with transmission "1" (for print) would be gathered in groups of "X" number of documents to create one spool, prior to creating the spool, a check would be made to see if the next document was for the same vendor, if so the next document/s would be included in the same spool, when a new vendor was found, a new spool would be created.
    To temporarily fix the issue the jobs have been placed on "no execute" and the support team is identifing the chargebacks and RTV created during the week, manually running the RSNAST00 program in groups of 500 - 800 documents, ensuring all doucments for a vendor a sent in the same spool request.

    Post Author: Stephen@Azzu
    CA Forum: General
    Nobody know the answer to this one? Stephen@Azzu:Here's a good one...I'm using Crysal Reports XI (fully service packed) and the reports I have created are being used in a VB.Net application. I have no problems whatsoever in printing the reports, everything is fine. However, when the report is sent to the printer, the printer queue displays 'document' as the, err, document name. I'd like it to say something more relevant, such as the document number the user selected.So I've tried setting the ReportDocument.Name but wait, it's read only!? How about the summary info? No change. Filename? No change either. I've browsed the internet, searched the knowledge base and found nothing. So my question is this...How do I get the printer queue to display an appropriate name for my document?Stephen

Maybe you are looking for