Xl Reporter Timeout Setting

Hi All
We have the following message when trying to generate a large report in XL Reporter. 
An error occurred while Executing report!
Decription: Rows 2358, Column 244
Timeout expired
This is a very large report and it times out before it completes.  This message comes up after approximately 20 minutes of running.
Please can anyone advise asap if they are aware of a timeout setting that can be extended in XL Reporter. 
Alternatively is there a fixed limitation in the number of rows or the time a report is allowed to run?
Kind regards
Sam Burchell

Hi Sam Burchell,
When XLR builts report, it need both disk space and memories. For such large report, I doubt you have anyway to run. You need to redesign the report or add parameter to restrict the data range.
For a report with over 200 columns, how would user read it?
You can calculate by yourself: 2358 X 244 (cells) is probably the limit for this specific environment
Thanks,
Gordon

Similar Messages

  • Business Objects XI report timeout

    Hi All,
    I'm running a quite simple environment:
    Windows 2003 R2 SP2
    IIS 6
    Oracle Database (remote on Linux but same subnet)
    Business Objects Server XI R1 SP3.
    I'm having an issue with reports getting time out errors after 2 minutes before they have had a chance to complete.
    What I want to do is increase the setting that lets the report run before it errors. I can monitor my database and still see SQL being passed when the 2 minute limit is reached.
    I have changed the 'Default Website Properties' Connection Timeout setting in IIS to 500 seconds and restarted, this has not helped the problem. I have looked through all the settings under Servers in the CMC, I can't see the right one. I'm not asking for the connecting setting before I need to log back in, I need the setting that will let a report run for 10 minutes before it errors.
    If I run a problem report via Schedule, it completes but is very close to 2 minutes. If I run it On Demand, it times out after 2 minutes, but I can still see the query selecting data then gets terminated.
    Thanks in advance, Jason.
    Edited by: Glenn Rieger on Oct 20, 2008 2:52 AM
    Edited by: Glenn Rieger on Oct 20, 2008 2:55 AM

    I had the same problem on a 12 mo cost report that produced 95,000 records and read close to 400,000.  Could only run 4 months. 
    Changed the "Database Records Read When Previewing or Refreshing" parameter to 0 (unlimited) in CrystalReportsProcessingServer
    and changed the "Maximum Cache Size (KB)" parameter in CrystalReportsCacheServer from 250,000 to 500,000 - then it would run.
    Sorry, wrong thread I think - I was getting "max processing time or max records limit reached" error message but I think my problem was max records rather than timeouts.
    Edited by: Richard Carlson on Dec 22, 2008 9:03 AM

  • How can I adjust the Timeout setting?

    I'm running some OBIEE reports in Firefox that by nature do take a long time to run. One of my local Tech Support folks suggested increasing the Firefox Timeout setting (he showed me how to do this once, but I didn't write it down). Can you provide written instructions (or annotated screen pictures), please?

    Alright. There are two ways to do this. You can extend your timeout, or you can totally disable timeout. Depending on the way you use firefox, either may be helpful. If you want to extend your timeout, type about:config in your search bar on the top. From there it will take you to a list of preferences. There is a search bar. Type "Timeout" into it. The top two are disable timeout and the "count timeout". If you want to disable timeout, simply double click the "enabletimeout" on the top. This will change the value to false. If you would like to change the value of how long it takes to timeout, double click the "CountTimeout" and enter in your new value. If this doesn't make sense, see the screenshots.
    Have a great day!!
    -Jon

  • Multiple data sets: a common global dataset and per/report data sets

    Is there a way to have a common dataset included in an actual report data set?
    Case:
    For one project I have about 70 different letters, each letter being a report in Bi Publisher, each one of them having its own dataset(s).
    However all of these letters share a common standardized reference block (e.g. the user, his email address, his phone number, etc), this common reference block comes from a common dataset.
    The layout of the reference block is done by including a sub-llayout (rtf-file).
    The SQL query for getting the dataset of the reference block is always the same, and, for now, is included in each of the 70 reports.
    Ths makes maintenance of this reference block very hard, because each of the 70 reports must be adapted when changes to the reference block/dataset are made.
    Is there a better way to handle this? Can I include a shared dataset that I would define and maintain only once, in each single report definition?

    Hi,
    The use of the subtemplate for the centrally managed layout, is ok.
    However I would like to be able to do the same thing for the datasets in the reports:
    one centrally managed data set (definition) for the common dataset, which is dynamic!, and in our case, a rather complex query
    and
    datasets defined on a per report basis
    It would be nice if we could do a kind of 'include dataset from another report' when defining the datasets for a report.
    Of course, this included dataset is executed within each individual report.
    This possibility would make the maintenance of this one central query easier than when we have to maintain this query in each of the 70 reports over and over again.

  • Reporting Services Report Timeout

    hi Getting Time Out error on Production server..... same report working fine on UAT.
    I Individually executed query on both UAT and production taking same time. 
    I have checked all the option in the given link...please tell me any another solution if you have
      https://stackoverflow.com/questions/840629/reporting-services-report-timeout/3505765#3505765?newreg=f7ac9bb2b2ff4924a0fc2ffc6b52ff17 

    Hi VMuradiya,
    Thank you for your question.
    I am trying to involve someone more familiar with this topic for a further look at this issue. Sometime delay might be expected from the job transferring. Your patience is greatly appreciated.
    Thank you for your understanding and support.
    Best regards,
    Qiuyun Yu
    Qiuyun Yu
    TechNet Community Support

  • Samplerate problem using Analog In and Counter In from a NI 6259 USB. "Counter timeout" setting in DAQmx?!

    Hello,
    I got a fundamental problem with the correlation of the timer settings of the DAQmx driver in DIAdem DAQ. I dont know where the problem is located exactly but maybe someone can help me if I explain what happens:
    In my configuration I use some analog inputs from a USB 6259 with 20kHz samplerate and two counter inputs for frequency measuring via DAQmx in DIAdem DAQ.
    There has to be an extra DAQin block for the analog inputs and the counter inputs with also an extra "Clock"-block for each of them. The clock of the analog inputs runs with 20kHz hardware clock and the other one with 10Hz software clock because the hardware clock mode is not allowed or supported.
    My problem is the display refresh rate in VIEW. If the counter signal has no input (because the measured system is not active) the display seems to wait for any input and doesnt refresh the analog values on screen. If the system is active and a rectangle signal is seen by the counter in, the display refresh rate raises and the frequency value is displayed more or less accurate. Has that something to do with the counter timeout setting in the DAQin driver options block (marked in the attached image)? If i decrease the timeout, the display refresh rate gets better but not as good as without using the counter inputs in my DAQ diagram. I think the counter input is not as easy to handle as the usual analog inputs... I only want to see the measured frequency on the display during the measurement without getting any influence on the analog input channels and their displaying.
    The other problem is the display and the measurement of the frequency itself. If i check the function of the counter input in the Meas. & Automation Explorer the frequency is display correct without any dropouts or something like that. The signal I measure in DIAdem on the other side looks quite bad because there are spikes of some MHz and even more although the measured range is between 20 and 80Hz!
    Has anybody made similar experiences?
    Regards
    S. Zimmer
    Attachments:
    probs.png ‏112 KB

    Hi there,
    it seems that german is your mothertongue, so I'll reply on german.
    Digitale Eingänge müssen Software getaktet werden, da nur analoge Eingänge Hardware-Takt Unterstützung haben!
    Sie können den Hardware-Takt nur mit analogen Eingängen einsetzen, die, von einem Timer gesteuert, gepuffert Werte einlesen können. Digitale Größen verarbeitet der Hardware-Takt nicht.
    Mit dem Hardware-Takt erreichen Sie sehr hohe Abtastraten. DIAdem überträgt die gewünschte Rate und die Kanalliste auf die Karte und startet die Messung. Die Hardware erfasst die Daten selbstständig und sammelt die Daten. Der PC ist nur für den Abtransport und die Weiterverarbeitung verantwortlich.[...]
    Da digitale Signale nicht im Hardware-Takt erfasst werden können, müssen diese Signale parallel in Software-Takten ermittelt werden. Dies kann zu zeitlichen Verschiebungen führen, weil sowohl beim Start der Messung als auch während der Messung keine Synchronisierung der Timer im PC und im Messgerät erfolgen kann. Da zwei Timer nie ganz genau gleichzeitig gestartet werden und auch nie ganz genau gleich schnell laufen, stimmen die Zeiten in den Zeitkanälen nach der Messung nicht genau überein. Üblicherweise betragen die Abweichungen einige Millisekunden.[...]
    Weiters hab ich mal n Versuchsaufbau für die Frequenzmessung gemacht. Ich konnte problemlos Frequenzen messen...
    Am besten du schilderst kurz den Aufbau deiner Messung, was du messen möchtest und wie du den Max konfiguriert hast.
    Mfg Markus

  • New-WebServiceProxy timeout setting?

    Hi,
    Is there a way to increase the timeout setting for new-webserviceproxy? I am calling a webservice that takes a some time and my powershell script times out "New-WebServiceproxy : The operation has timed out"
    Thanks

    Hi,
    Change the intellisense timeout value from the default 3 seconds to a greater value.
    To do this, click Tools, and then click Options. On the General Settings tab, in the Intellisense section of the form, click the drop-down list to
    change the Intellisense timeout in seconds value. 
    This works for Windows PowerShell 3.0 ISE. Please try it also with your own powershell.
    In addition, hope the below link be helpful:
    BUG: You receive a "The operation has timed-out" error message when you access a Web service or when you use the IPAddress class
    http://support.microsoft.com/kb/815209
    Regards,
    Yan Li
    Yan Li
    TechNet Community Support

  • Scheduled a webi report and set it send to EMAIL.

    Our customer found when they scheduled a webi report and set it send to EMAIL, it will cost much more time than usual after they have their SIA restarts.
    The first time it takes 4-5 times longer to receive a report in mailbox than next time onwards.
    Please help.
    Thanks Much,
    Abhishek

    Hi Abishek,
    If the schedule is taking 4-5 times longer to schedule following the SIA restart I suppose it is possible that the Webi Job Server and Webi Processing Servers are not fully registered with the CMS - can you check that.
    Also can you test by ensuring that if there are any Webi Job Servers\Webi Processing Servers in the environment which are stopped\disabled, can you retest after deleting those servers. There is a bug with XI3.1:
    ADAPT01371367
    Description:
    Scheduled jobs often have a delay when the system is upgraded to BusinessObjects Enterprise XI 3.1 SP2 FP 2.2 or FP 2.3.This problem also happens when some of the servers required for scheduling are stopped and disabled. In this case, the Adaptive Job Server (AJS) tries to confirm if all available Webi Report Servers are running, and this causes the delay in running the scheduled jobs.
    New Behavior:
    This problem has been resolved.
    Do you have a test system where you could install FP3.1 and check the fix?
    The only "workaround" I could suggest would be to ensure that all services needed for the schedule are running\enabled (Adaptive Job Servers and Webi Processing Servers). This will stop the Adaptive Job Server from its continual querying for those servers. The adverse effect of this is that the more unnecessary services which are running will necessitate increased network communication.
    To check if this is the actual issue you are hitting, you would need to trace the schedule and check for messages like this in the logs:
    [2010-08-27 12:02:08,769] [TID:24] [ERROR] [webi.PublishingHelper.<init>():89]: unable to retrieve all mandatories servers to proceed this job
    Alternatively, log a message with SAP Support for further investigation.
    <<Text removed>>
    Kind regards,
    John
    Edited by: Matt on Oct 10, 2011 10:14 AM

  • Not able to see negative exception in reporting agent setting.

    Hello Gurus,
    I created a query with exceptions on top of a multi-provider. This multi-provider is built on top of a DSO and a remote cube.
    Exceptions is the query
    1. range from -1,00,00,000 to -0.1
    2. range from 1 to 1,00,00,000.
    When I created a reporting agent setting for this query, i was able to see the positive exception but not negative. Please help me regarding this.
    thanks,
    Aarthi.

    Hello Aarthi,
    Have you checked the dataprovider contains the negative values.
    Do a list Cube on the multiprovider and confirm it.
    Have you defined single exception for both or seperate exception. If 2 then check whether exception is active?
    Thanks
    Chandran

  • Portal Session Timeout Setting

    There is a JServ session and a portal session. I know how to control session timeout and session clean up frequency in JServ - that's in zone.properties. But, I dont know how to set timeout for portal session, i.e., I'd like to have the user be forced to login again when he has been idle for 15 mins - and only if he has been idle. Jserv session settings are not sufficient for this because Portal has it's own session that must time out.
    How to set this timeout value (I'm using my own provider which has a timeout setting in zone.properties and includes a bunch of JSP portlets)? Also, is there a clean up thread for which the frequency has to be set?

    I've contacted metalink weeks ago, and this is NOW, a know bug...
    Incredible... Oracle just DO NOT TEST their products... Even a simple SESSION timeout do not work. Also, if I click back after "I log In and Log out" ... Session still up without have to login again!
    BUG 2442268

  • IIOP timeout setting??

    I have a client that calls an EJB using IIOP through a servlet. It connects fine
    and I can see the bean "working" on the server side. After 60 seconds, the client
    receives the following error:
    java.rmi.MarshalException: CORBA COMM_FAILURE 1 Maybe; nested exception is:
         org.omg.CORBA.COMM_FAILURE: minor code: 1 completed: Maybe
    org.omg.CORBA.COMM_FAILURE: minor code: 1 completed: Maybe
         at com.sun.corba.se.internal.iiop.IIOPConnection.purge_calls(IIOPConnection.java:785)
         at com.sun.corba.se.internal.iiop.ReaderThread.run(IIOPConnection.java:118)
    However the bean is unaffected and completes its processing later. It does get
    an exception when trying to send the result back to the client. It seems that
    there is an IIOP timeout setting that needs to set higher in this case and the
    default is approximately 60 seconds. Any suggestions?
    Thanks in advance.
    -geoff.

    andy,
    you mean as another attribute somewhere in config.xml? please specify how to
    go about configuring this.
    -geoff.
    Andy Piper <[email protected]> wrote:
    "Geoff" <[email protected]> writes:
    I have a client that calls an EJB using IIOP through a servlet. Itconnects fine
    and I can see the bean "working" on the server side. After 60 seconds,the client
    receives the following error:
    java.rmi.MarshalException: CORBA COMM_FAILURE 1 Maybe; nested exceptionis:
         org.omg.CORBA.COMM_FAILURE: minor code: 1 completed: Maybe
    org.omg.CORBA.COMM_FAILURE: minor code: 1 completed: Maybe
         at com.sun.corba.se.internal.iiop.IIOPConnection.purge_calls(IIOPConnection.java:785)
         at com.sun.corba.se.internal.iiop.ReaderThread.run(IIOPConnection.java:118)
    However the bean is unaffected and completes its processing later.It does get
    an exception when trying to send the result back to the client. Itseems that
    there is an IIOP timeout setting that needs to set higher in this caseand the
    default is approximately 60 seconds. Any suggestions?There is an undocumented property on the Server MBean:
    IdleIIOPConnectionTimeout
    which you can configure in seconds to fix this. Unfortunately the JDK
    Orb is particularly bad at connection management which is why we had
    to do this. With 1.4 we can do somewhat better since we can use
    CloseConnection to tell the client to gracefully shutdown. We have
    revamped some of this also in WLS 7.0 so that the default timeout is
    longer for pending requests (as opposed to idle connections).
    andy

  • HTTP Connection timeout setting

    Hi,
    I'm using ebXML protocol for B2B 10.1.2.3+MLR 5.
    I talk to multiple trading partners and when one of the TP is down, we see that there is a pileup of messages in the backend queues.
    This is because, there is constant message inflow into the JMS queues by the back-end application and each message is taking a long time to timeout (nearly 20 seconds). So what effectively happens is that a message was supposed to reach the TP in 1 sec will take 20 sec before it labels as a HTTP connection timeout error .
    Can we set the HTTP Connection timeout setting in B2B? (I saw a setting in B2BGurus for EDI though)
    If not, please can you suggest if it can be set in the Application Server level?
    Please help!
    Thanks in advance,
    Warm Regards,
    Suhas.

    All,
    At the application server level, there is a timeout setting in httpd.conf. The default value has been set to 300 seconds.
    Regards,
    Suhas.

  • Reporting agent setting to drill down

    My requirement is that I want to create a reporting agent setting.
    When executed the report it should drill down a particular characteristic to the lowest level.
    Is there any setting I can do?

    you need not need reporting agent to do this
    lets say you have characteristic Country and hierarchy for it with sub levels 4
    you want the country hierarchy to display to its level 4 by default
    set this property in query designing , open to node 4
    this way it will always drilldown to sub level 4

  • Timeout setting in setup package server

    Hi All,
    We wanted to change the time out setting in our Middleware server(Windows platform wintel) from present 120 mins to 180 mins which is used for creation of setup package.Where we can change the timeout setting in server.Please give me the path or location ..
    Thanks in advance
    Devendra

    Hi,
    I am not sure about the native Jboss JTA, but in general the following is true:
    -the transaction timeout determines when 'pending' transactions are cleaned up by the JTA
    -the larger the value, the longer the time that such transactions can be around
    The performance impact depends on the particularities of your application and server environment; to name a few:
    -For hot-spot data in your database, transactions will normally have to wait longer to get locks held by other transactions. If the timeout is too short then the clients will see many requests fail because the underlying transaction will timeout before the locks are gotten, and the JTA will rollback.
    -On the other hand, if (for some reason) you have failing requests that leave active transactions floating in the server, then a larger timeout will mean that such floating transactions will not release their locks yet (happens at rollback/commit only). So here a larger timeout means that lost transactions (that will rollback anyway) will prevent other transactions from doing business.
    -The same argument holds for deadlocks. If a transaction is involved in a deadlock situation then the deadlock will not be resolved until the transaction rolls back after timeout. In this case too, the other transactions are hindered by the locks of a 'lost' transaction.
    As a rule of thumb, I would say: keep transaction timeout as high as necessary to allow most transactions to get 'useful' locks (but not much higher than that). For instance, you could measure the statistics on response times under realistic loads and base your timeout value on that (if you're not measuring the deadlocks of course).
    Best,
    Guy
    http://www.atomikos-support.com:8080/forums -- Java/J2EE/JTA Transactions Forum

  • Timeout setting for Realtime-Sequence execution

    Hello,
    I'm referring to the "Timeout" setting in the stimulus profile editor or the "Timeout" parameter of the SequenceCallInfo Constructor. The description of this parameter is as follows:
    The timeout in milliseconds within which the sequence must complete each time step.
    What exactly is this parameter good for? I understand that each task in a realtime sequence is executed once per PCL iteration and that the "time step" of a task is completed when the control flow reaches a "Yield" statement (or the end of a loop with autoyield enabled).
    When I'm running a sequence where a timestep takes longer than the PCL period, the VeriStand engine will abort and undeploy the system definition. In my case the PCL rate is 2KHz so isn't the timeout implicitly given as 500us?
    I thought that maybe I can use the timeout parameter to set an additional timeconstraint from "greater 0 to less than PCL period". So for example if I set it to 0,1ms, the realtime sequence would have to hit a Yield statement within 100us. But this doesn't seem to be the case either because the realtime sequence is not aborted and it still stops the VeriStand engine.
    Thanks
    Krid

    Hi Jarrod,
    thanks for your answer but your second use case is exactly what I tried to do. The VeriStand engine is still aborted even when I run the sequence with timeout set to 0,01:
    Error -307743 occurred at NI VeriStand Engine.lvlib:VeriStand Engine Wrapper (RT).vi >> NI VeriStand Engine.lvlib:VeriStand Engine.vi >> NI VeriStand Engine.lvlib:VeriStand Engine State Machine.vi >> HP Loop.lvlib:HP Loop Main.vi
    I just tested it again and the first time I started the stimulus profile, the realtime sequence actually was aborted and the VeriStand engine continued to run. Then I started the stimulus profile a second time (without changing anything) and this time the profile was not aborted and hence  the VeriStand engine was stopped. It's also not possible to stop the profile in stimulus profile editor. It just hangs and I have to kill it.
    After this happened it's also not possible to run any other realtime sequences (they will simply not start but no error message is returned).  One has to completely close down VeriStand (just re-deploying doesn't work) and restart it before it works again.
    Why isn't the timeout parameter working as it's supposed to?
    Regards
    Krid

Maybe you are looking for