[Bug] Default timeout value of Wait for Occurrence

This one kind of cheesed me off this morning.
When I create a constant/control from a terminal on a primitive I have come to expect the value to be the default value. Those tricky folks found a way to get me again.
Drop a Wait on Occurrence onto the BD
Right-Click on 'Create Control' or 'Create Constant' from the suggestively named 'ms timeout (-1)' terminal
The value/default is not -1, but rather 0.
Slightly different behavior between -1 and 0.
LV8.2-LV12 (at least)

nathand wrote:
Hooovahh wrote:
Similarly I have an issue with how the Delete From Array function. If I wire a 1D array of string to the input, and nothing else my output has the 1D array (with that index deleted), and then the Deleted Portion as a scalar string.
If I create a constant from the Length terminal, the value is 0 and the functionality of the primative changes so that now Deleted Portion output is an Array of String.
Personally, I greatly appreciate this usability enhancement. It would annoy me if I had to put an index array after every delete from array when I delete only a single element.
I like the feature, I don't like the implementation. Why can't a value of -1 be the default and that corresponds to a single scalar item being removed? Instead of 0 be the default corresponding to delete nothing.
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Similar Messages

Bug in timeout behavior of wait for queue element

The first time a wait for queue element is executed with an infinite timeout (-1 ms) after previously having waited with a finite timeout, it actually times out after the previously used finite interval, a subsequent wait with an infinite timeout then works correctly. Attached is a test program demonstrating the problem. I have tried this demo on both Mac and Sun (LV 6.1 on Mac, LV 6.1f1 on Sun) and it behaves the same on both.
Attachments:
QueueTest.vi.sit ‏22 KB

I do not have an answer at the moment but I have unsuffited the file so that others can look at the program.
Jeremy Braden
Attachments:
Queue.vi ‏77 KB

What is the default timeout value for the SPQuery object?

What is the default timeout value for the SharePoint SPQuery object? I've tried searching online but can't find anything with the actual timeout value.
Someone suggested it might use the timeout property in the database? Anyone know if that's how it works?

Hi,
Do you want to avoid timeout when you query list items?
If so, we can use the following C# code to set timeout.
HttpContext.Current.Server.ScriptTimeout = 600; // 10 minutes
More information is here:
http://200oksolutions.blogspot.com/2013/03/sharepoint-2010-set-timeout-only-to.html
The SPQuery object doesn’t provide any property to set timeout. We can also set timeout in web.config, or SQL Connections or IIS.
Thanks,
Dennis Guo
TechNet Community Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]
Dennis Guo
TechNet Community Support

OWB9.0.4-- ORA-02049: timeout: distributed transaction waiting for lock

I'm running a simple mapping that copies all columns of data (using a filter on date for just current records) from one table in SQL Server into a staging table on my Oracle DW schema. It's using a dblink with transparent gateway for SQL Server, which works fine from SQL*plus.
The map is in default mode (bulk-failoverto-row) with bulk size and commit frequency = 1000.
The audit details show the first 1000 rows selected on the source, with an error on both the source and target tables:
Target--
ORA-02049: timeout: distributed transaction waiting for lock
Source--
ORA-01002: fetch out of sequence ORA-02063: preceding line from INTERGRATION@JXNSQL01
(INTERGRATION@JXNSQL01 is the dblink name)
Any ideas on how I can clear this up?
Thanks,
Paul

Hi,
After having upgraded to 9.0.4 (from 9.0.3) I'm running into exactly the same problems with some of my mappings. Actually I don't get any rows transferred from the mappings that fail.
Out of 7 mappings, 3 worked just liked before while the 4 others just keep on running until I cancel them and I then see the BUSY/ORA-02049 in the Audit Browser.
When comparing the mappings I see that the 3 that works all use some custom Procedures I have made.
The 4 that doesn't work are all very simple - one of them just loads all the content from a table with two columns in my source to another table with two columns in my target! Two of the other mappings that doesn't work includes some simple CASE-expressions.
Both my source and my target resides in a Oracle 9.2.0.3 database (not the same).
Regards,
Bent Madsen

ORA-02049: timeout: distributed transaction waiting for lock

Hi,
My name is Guneet and I'm working on an application running on BEA Weblogic Server 9.2 running on a Red Hat Linux box using Oracle 10g as the database. My problem is that recently our code started getting the following exception while updating a database table.
java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock
Application Details
* Using Stateless Session EJB
* Only one Business method in this EJB with transaction attribute set to "required"
* This method executes two select queries & one update query
* We are using JDBC to access the database.
* We have configured a Data Source & are using it to get a database connection.
* Weblogic's Oracle Driver is being used.
More details
* The application has been running well since a month.
* Two days ago,the update query failed with the above error.
* At that time, a single client was accessing the system.
* Once this problem occurs, it starts appearing frequently.
* Eventually a request to get a connection from the Data Source times out & the exception copied at the end is thrown
* At this stage the application gets stuck and all requests trying to get a connection end up with this exception.
* Fortunately, Restarting the Weblogic Server gets us out of this problem and transactions resume normally.
Now my questions are
# Why is this error happening & what does it mean?
# It looks like the second exception (unable to get a connection from ds) is an after effect of the first problem (ORA-02049) once it appears for a couple of times. Can somebody validate this?
# Though I don't understand JTA well but I don't think this application needs distributed transactions so, I'm thinking of modifying the driver type to non-XA oracle driver. Any advise/pointers/comments on this front is welcome !!!!!!!!
Thanks
Guneet Sahai
Exception Trace
Dec 27, 2006 4:47:50 PM | com.gisil.themis.db | SEVERE | Unable to load merchant DEL = 911168900164. Reason - java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMERR start() failed on resource 'themis-ds': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException: Unexpected error during start for XAResource 'themis-ds': Transaction timed out after 29 seconds
BEA1-252DE51AC930078CA638
at weblogic.jdbc.wrapper.XA.createException(XA.java:103)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:753)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1182)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1115)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:497)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:429)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1408)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1332)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:440)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.gisil.themis.db.impl1.DbManagerImpl.isPinValid(DbManagerImpl.java:872)
at com.gisil.themis.ejb.ThemisBean.isPinValid(ThemisBean.java:185)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl.isPinValid(Themis_aqqc4k_EOImpl.java:207)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1413)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1332)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:440)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.gisil.themis.db.impl1.DbManagerImpl.isPinValid(DbManagerImpl.java:872)
at com.gisil.themis.ejb.ThemisBean.isPinValid(ThemisBean.java:185)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl.isPinValid(Themis_aqqc4k_EOImpl.java:207)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

guneet sahai wrote:
Hi,
My name is Guneet and I'm working on an application running on BEA Weblogic Server 9.2 running on a Red Hat Linux box using Oracle 10g as the database. My problem is that recently our code started getting the following exception while updating a database table.
java.sql.SQLException: [BEA][Oracle JDBC Driver][Oracle]ORA-02049: timeout: distributed transaction waiting for lock
Application Details
* Using Stateless Session EJB
* Only one Business method in this EJB with transaction attribute set to "required"
* This method executes two select queries & one update query
* We are using JDBC to access the database.
* We have configured a Data Source & are using it to get a database connection.
* Weblogic's Oracle Driver is being used.
More details
* The application has been running well since a month.
* Two days ago,the update query failed with the above error.
* At that time, a single client was accessing the system.
* Once this problem occurs, it starts appearing frequently.
* Eventually a request to get a connection from the Data Source times out & the exception copied at the end is thrown
* At this stage the application gets stuck and all requests trying to get a connection end up with this exception.
* Fortunately, Restarting the Weblogic Server gets us out of this problem and transactions resume normally.
Now my questions are
# Why is this error happening & what does it mean?
# It looks like the second exception (unable to get a connection from ds) is an after effect of the first problem (ORA-02049) once it appears for a couple of times. Can somebody validate this?
# Though I don't understand JTA well but I don't think this application needs distributed transactions so, I'm thinking of modifying the driver type to non-XA oracle driver. Any advise/pointers/comments on this front is welcome !!!!!!!!
Thanks
Guneet SahaiHi Guneet. If you want to debug the JTA issue, I suggest opening an official
support case. They will lead you through producing the JTA debug information.
However, I believe you are correct that the transaction you describe is
completely doable with a simple local transaction, so if you were to alter
your pool to use the non-XA driver, it would probably be faster, simpler,
and just work.
Let me know...
Joe
>
Exception Trace
Dec 27, 2006 4:47:50 PM | com.gisil.themis.db | SEVERE | Unable to load merchant DEL = 911168900164. Reason - java.sql.SQLException: Unexpected exception while enlisting XAConnection java.sql.SQLException: XA error: XAResource.XAER_RMERR start() failed on resource 'themis-ds': XAER_RMERR : A resource manager error has occured in the transaction branch
javax.transaction.xa.XAException: Unexpected error during start for XAResource 'themis-ds': Transaction timed out after 29 seconds
BEA1-252DE51AC930078CA638
at weblogic.jdbc.wrapper.XA.createException(XA.java:103)
at weblogic.jdbc.jta.DataSource.start(DataSource.java:753)
at weblogic.transaction.internal.XAServerResourceInfo.start(XAServerResourceInfo.java:1182)
at weblogic.transaction.internal.XAServerResourceInfo.xaStart(XAServerResourceInfo.java:1115)
at weblogic.transaction.internal.XAServerResourceInfo.enlist(XAServerResourceInfo.java:274)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:497)
at weblogic.transaction.internal.ServerTransactionImpl.enlistResource(ServerTransactionImpl.java:429)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1408)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1332)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:440)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.gisil.themis.db.impl1.DbManagerImpl.isPinValid(DbManagerImpl.java:872)
at com.gisil.themis.ejb.ThemisBean.isPinValid(ThemisBean.java:185)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl.isPinValid(Themis_aqqc4k_EOImpl.java:207)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)
at weblogic.jdbc.jta.DataSource.enlist(DataSource.java:1413)
at weblogic.jdbc.jta.DataSource.refreshXAConnAndEnlist(DataSource.java:1332)
at weblogic.jdbc.jta.DataSource.getConnection(DataSource.java:440)
at weblogic.jdbc.jta.DataSource.connect(DataSource.java:396)
at weblogic.jdbc.common.internal.RmiDataSource.getConnection(RmiDataSource.java:359)
at com.gisil.themis.db.impl1.DbManagerImpl.isPinValid(DbManagerImpl.java:872)
at com.gisil.themis.ejb.ThemisBean.isPinValid(ThemisBean.java:185)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl.isPinValid(Themis_aqqc4k_EOImpl.java:207)
at com.gisil.themis.ejb.Themis_aqqc4k_EOImpl_WLSkel.invoke(Unknown Source)
at weblogic.rmi.internal.BasicServerRef.invoke(BasicServerRef.java:517)
at weblogic.rmi.cluster.ClusterableServerRef.invoke(ClusterableServerRef.java:224)
at weblogic.rmi.internal.BasicServerRef$1.run(BasicServerRef.java:407)
at weblogic.security.acl.internal.AuthenticatedSubject.doAs(AuthenticatedSubject.java:363)
at weblogic.security.service.SecurityManager.runAs(SecurityManager.java:147)
at weblogic.rmi.internal.BasicServerRef.handleRequest(BasicServerRef.java:403)
at weblogic.rmi.internal.BasicServerRef.access$300(BasicServerRef.java:56)
at weblogic.rmi.internal.BasicServerRef$BasicExecuteRequest.run(BasicServerRef.java:934)
at weblogic.work.ExecuteThread.execute(ExecuteThread.java:209)
at weblogic.work.ExecuteThread.run(ExecuteThread.java:181)

DatabaseError: ORA-02049: timeout: distributed transaction waiting for lock

Hi all
There is script running in my database 'A' that will select some data from tables in other database through DBLINK and update some tables too. The script which 6 I am running for the past 6 monts succesfully. Yesterday I got error saying that,
DatabaseError: ORA-02049: timeout: distributed transaction waiting for lock
ORA-02063: preceding line from test
I have tested the Link and its active no issues in DBLINk
I understand the objects which I am accessing the table in locked mode,
SQL> select OBJECT_ID,SESSION_ID,PROCESS,LOCKED_MODE from v$locked_object where
SESSION_ID=121;
OBJECT_ID SESSION_ID PROCESS LOCKED_MODE
77391 121 21394 3
i
I killed the session 121 and in v$session status is Killed, but I am getting the same error repeating while running the script. And the session_id is still in locked_mode.
Could please add some light on this?
-Thanks
Antony

Hi,
I have killed the session which caused blocking and the status is KILLED for the past two days. But still the object is in locked mode
SQL> select OBJECT_ID,SESSION_ID,PROCESS,LOCKED_MODE from v$locked_object where
SESSION_ID=121;
OBJECT_ID SESSION_ID PROCESS LOCKED_MODE
77391 121 21394 3
How would I resolve this any idea
-Thanks & Cheers
Antony

SOAP receiver Default timeout value

Hi Everybody,
I have a Proxy to SOAP scenario.
Can somebody tell me the default timeout for SOAP receiver adapter.
Note : Is it the same as SOAP sender which is 5 mins?
Thanks,
Zabiulla

Yes , it is same like sender soap adapter i.e. 5 mints. You can increase this in module tab of receiver soap CC. check sap note no 856597 for more detail.
Thanks!

Timeout error in Wait for Operation Complete VI for TEKDPO4054 scope driver

Hi,
I keep getting a timeout error (-1073807339) when I run the "wait for operation complete" sub-VI that comes with the tektronix DPO4000 series oscilloscope driver. I'm using a DPO4054 scope. The error out source is the VISA Read STB command, but I can't figure out what's wrong. Has anyone else encountered this error? Please help!
Thanks for your time!
I've attached the sub-VI where I'm having this problem.
Attachments:
tkdpo4k Wait for Operation Complete.vi ‏27 KB

duplicate post
Please try to keep your questions to a single board.

Asynchronous Call - collect values without waiting for sub VI to finish executing

Hi All, I'm relatively new to LabVIEW and for the first time I'm attempting to make use of Asynchronous calls in a program.
What I would like to accomplish, generally, is this: At the beginning of the main vi, begin running a sub-vi in the background. This sub-vi is collecting streaming data from an instrument with a refresh rate of 50Hz. At various points in the main vi I would like to call the instantaneous value of that streaming data from the sub vi, passing it back into the main vi, while allowing the sub-vi (the streaming data collection) to continue running. The reason for this, is that I need to collect the data from this instrument many times wihtin a loop, and the connection initialization to the streamin data instrument is both slow and faulty, and takes too long if I have to initialize the connection, collect the data, close the connection, each time I wish to collect the data. I would prefer to initialize the connection once at the beginning, have a stream of continuous data being collected in the background, and then at certain points within the main vi loop, query that streaming data for its instantaneous value, but allow the streaming data sub vi to continue running.
I recognize that a method to allow the streaming data collection sub vi to run in the background is to use the Asynchronous call method - however, to collect the data I need to use an asynchronous wait, which will only collect the data if the streaming data sub vi finishes executing. How can I collect the data at a particular instant while still allowing the subvi to keep running (thereby minimizing the number of times the connection to the instrument needs to initialized)?
Any suggestions or alternative methods would be great!
Thanks
Jason

This is typically solved in a different way than what you envision. Have your parallel deamon post its current values to a buffer. This could be a global variable (gasp!!) or an intelligent global variable (a VI with loop that executes always once and has an unitialized shift register that can either be initized or read based on a control input). You can add extra code to the read and write selection such as scaling etc to turn the intelligent global into an action engine that does extra things on its different methods.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions
Attachments:
Intelligent Global.vi ‏19 KB

Change connection timeout, not found waiting for dialup connection

Using Firefox 6.02 on Vista 32.
The dial-up connection is slow connecting which cause Firefox to time out with a page not found while waiting. Is there a setting to extend the time out?

Mark,
This has been implemented in Headstart PATCH6530_for_6i and PATCH6530_for_9i.
Regards,
Marcel

Using DAQ occurrence to wait for start trigger

Hi,
I'm trying to use digital triggers to start and stop datalogging. Every time start trigger appears, new file is created and data is acquired to file until stop trigger occurs. Now I'm using set DAQ occurrence and wait for occurrence functions to wait for start trigger before creating a new file. The problem is that after first stop trigger this occurrence method doesn't work. I believe it's because AI is not cleared and configured before calling DAQ occurrence again. Number of scans acquired is not zero, if I don't clear and configure AI again? Am I right?
Do I have to clear and init AI everytime before occurrence config or is there a better way to make program wait for start trigger?
Thanks in advance,
Jakke

Hi Matt99eo,
Have you configured your device for triggering? Although you have not mentioned your device specifically, the M series user manual provides a great explanation of digital triggering. Using the DAQ Assistant, this can be configured from the triggering tab. Hopefully this helps!
Regards,
h_baker
National Instruments
Applications Engineer
Digital Multimeter Resources

How to check the default checked value for radio button on jsp for struts

Hello , I just want to check the default checked value in JSP for a radio button, how can i do that?
<html:radio property="sale" value="permanent" style="vertical-align: middle;">Permanent</html:radio>
<html:radio property="sale" value="temporary" style="vertical-align: middle;">Temporary</html:radio>

you can set the default value for property ( which you want to default selected when the form is first loaded) in reset method of the form.
<html:radio property="sale" value="permanent" style="vertical-align: middle;">Permanent</html:radio>
<html:radio property="sale" value="temporary" style="vertical-align: middle;">Temporary</html:radio>
In the above case you can write the code as follows in the perticular form of this jsp.
public void reset(ActionMapping mapping, HttpServletRequest request) {
super.reset(mapping, request);
sale = "permanent";
This will show the first check box default selected when the first time the page is loaded.

How to decrease timeout value when there is no response from BOE server?

We are using BOE XI R2 .NET SDK to logon BOE XI R2 Server as below as well as using Infoview/CMC logon BOE:
set boSessionManager = Server.CreateObject("CrystalEnterprise.SessionMgr")
set boEnterpriseSession = boSessionManager.Logon(boUserID, boPassword, boCMS, boAuthType)
There is no response for long time from BOE server after I excuting log on BOE using .NET SDK or Infoview/CMC App for more than one minute.
So I want to timeout the logon atction after a certain time such as one minute if there is no response from BOE server.
My question comes:
1. What is the default timeout value for this operation?
    Where can I find it and how to modify it?
2. I found ther are some registry keys on .NET APP Server:
    HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Report Application Server\InprocServer\EnterpriseRequestTimeout
    HKEY_LOCAL_MACHINE\SOFTWARE\Business Objects\Suite 12.0\Report Application Server\Client SDK\CorbaAdapter\WaitReplyTimeout
Are they for the action timeout I mentioned above? If not, what do they work for?
It seems that WaitReplyTimeout is for report data retrieval timeout according to Kbase article 1199286 and which registry setting to change for long running reports, is it correct?
Thanks for any response.
Thanks,
Sunny

I don't think there is a setting available for this. The timeouts you are looking at are essentially how long to wait for a report to process.
My concern about trying to find a setting like this is that if you do get the client (aka SDK) to timeout after one minute, the CMS may still recieve this request shortly after and logon, creating a session that no longer has a handle to it and will then have to wait for it to timeout because of inactivity which would tie up a license.

Unhandled Exception: System.TimeoutException: The request channel timed out while waiting for a reply after 00:01:59.9139778.Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding.

Hi,
I created a simple plugin and since i wanted to use Early Binding i added Xrm.cs file to my solution.After i tried registering the plugin (using the Plugin Registration Tool) the plugin does not gets registered and i get the below mentioned Exception.
Unhandled Exception: System.TimeoutException: The request channel timed out while waiting for a reply after 00:01:59.9139778. Increase the timeout value passed to the call to Request or increase the SendTimeout value on the Binding. The time allotted to this
operation may have been a portion of a longer timeout.
Server stack trace:
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.SecurityChannelFactory`1.SecurityRequestChannel.Request(Message message, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannel.Call(String action, Boolean oneway, ProxyOperationRuntime operation, Object[] ins, Object[] outs, TimeSpan timeout)
at System.ServiceModel.Channels.ServiceChannelProxy.InvokeService(IMethodCallMessage methodCall, ProxyOperationRuntime operation)
at System.ServiceModel.Channels.ServiceChannelProxy.Invoke(IMessage message)
Exception rethrown at [0]:
at System.Runtime.Remoting.Proxies.RealProxy.HandleReturnMessage(IMessage reqMsg, IMessage retMsg)
at System.Runtime.Remoting.Proxies.RealProxy.PrivateInvoke(MessageData& msgData, Int32 type)
at Microsoft.Xrm.Sdk.IOrganizationService.Update(Entity entity)
at Microsoft.Xrm.Sdk.Client.OrganizationServiceProxy.UpdateCore(Entity entity)
at Microsoft.Crm.Tools.PluginRegistration.RegistrationHelper.UpdateAssembly(CrmOrganization org, String pathToAssembly, CrmPluginAssembly assembly, PluginType[] type)
at Microsoft.Crm.Tools.PluginRegistration.PluginRegistrationForm.btnRegister_Click(Object sender, EventArgs e)
Inner Exception: System.TimeoutException: The HTTP request to 'https://demoorg172.api.crm.dynamics.com/XRMServices/2011/Organization.svc' has exceeded the allotted timeout of 00:01:59.9430000. The time allotted to this operation may have been a portion of a
longer timeout.
at System.ServiceModel.Channels.HttpChannelUtilities.ProcessGetResponseWebException(WebException webException, HttpWebRequest request, HttpAbortReason abortReason)
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
at System.ServiceModel.Channels.RequestChannel.Request(Message message, TimeSpan timeout)
Inner Exception: System.Net.WebException: The operation has timed out
at System.Net.HttpWebRequest.GetResponse()
at System.ServiceModel.Channels.HttpChannelFactory`1.HttpRequestChannel.HttpChannelRequest.WaitForReply(TimeSpan timeout)
And to my Surprise after i remove the Xrm.cs file from my solution the Plugin got registered!
Not understanding what exactly is the issue.
Any Suggestions are highly appreciated.
Thanks,
Shradha


Hello Shardha,
I really appreciate that you have faced this issue.This is really very strange issue and basically it occurs because of big size of your early bound class and slow internet
connection.
I would strictly recommend you to reduce the file size of your early bound class and then register.By default early bound class is created for all the entities which are
present in CRM(System entities as well custom entities).Such kind of early bound classes takes lots of time to register on server and hence timeout exception comes.
There is some standard define to reduce the size of early bound class.Please follow the link to get rid from big size of early bound class.
Create a new C# class library project in Visual Studio called SvcUtilFilter.
In the project, add references to the following:
CrmSvcUtil.exe(from sdk) This exe has the interface we will implement.
Microsoft.Xrm.Sdk.dll (found in the CRM SDK).
System.Runtime.Serialization.
Add the following class to the project:
using System;
using System.Collections.Generic;
using System.Xml.Linq;
using Microsoft.Crm.Services.Utility;
using Microsoft.Xrm.Sdk.Metadata;
namespace SvcUtilFilter
    /// <summary>
    /// CodeWriterFilter for CrmSvcUtil that reads list of entities from an xml file to
    /// determine whether or not the entity class should be generated.
    /// </summary>
    public class CodeWriterFilter : ICodeWriterFilterService
        //list of entity names to generate classes for.
        private HashSet<string> _validEntities = new HashSet<string>();
        //reference to the default service.
        private ICodeWriterFilterService _defaultService = null;
        /// <summary>
        /// constructor
        /// </summary>
        /// <param name="defaultService">default
implementation</param>
        public CodeWriterFilter( ICodeWriterFilterService defaultService )
            this._defaultService = defaultService;
            LoadFilterData();
        /// <summary>
        /// loads the entity filter data from the filter.xml file
        /// </summary>
        private void LoadFilterData()
            XElement xml = XElement.Load("filter.xml");
            XElement entitiesElement = xml.Element("entities");
            foreach (XElement entityElement in entitiesElement.Elements("entity"))
                _validEntities.Add(entityElement.Value.ToLowerInvariant());
        /// <summary>
        /// /Use filter entity list to determine if the entity class should be generated.
        /// </summary>
        public bool GenerateEntity(EntityMetadata entityMetadata, IServiceProvider services)
            return (_validEntities.Contains(entityMetadata.LogicalName.ToLowerInvariant()));
        //All other methods just use default implementation:
       public bool GenerateAttribute(AttributeMetadata attributeMetadata, IServiceProvider services)
            return _defaultService.GenerateAttribute(attributeMetadata, services);
        public bool GenerateOption(OptionMetadata optionMetadata, IServiceProvider services)
            return _defaultService.GenerateOption(optionMetadata, services);
        public bool GenerateOptionSet(OptionSetMetadataBase optionSetMetadata, IServiceProvider services)
            return _defaultService.GenerateOptionSet(optionSetMetadata, services);
        public bool GenerateRelationship(RelationshipMetadataBase relationshipMetadata, EntityMetadata otherEntityMetadata, IServiceProviderservices)
            return _defaultService.GenerateRelationship(relationshipMetadata, otherEntityMetadata, services);
        public bool GenerateServiceContext(IServiceProvider services)
            return _defaultService.GenerateServiceContext(services);
This class implements the ICodeWriterFilterService interface. This interface is used by the class generation
utility to determine which entities, attrributes, etc. should actually be generated. The interface is very simple and just has seven methods that are passed metadata info and return a boolean indicating whether or not the metadata should be included
in the generated code file.
For now I just want to be able to determine which entities are generated, so in the constructor I read from an XML
file (filter.xml) that holds the list of entities to generate and put the list in a Hashset. The format of the xml is this:
<filter>
<entities>
    <entity>systemuser</entity>
    <entity>team</entity>
    <entity>role</entity>
    <entity>businessunit</entity>
</entities>
</filter>
Take a look at the methods in the class. In the GenerateEntity method, we can simply check the EntityMetadata parameter
against our list of valid entities and return true if it's an entity that we want to generate.
For all of the other methods we want to just do whatever the default implementation of the utility is. Notice
how the constructor of the class accepts a defaultService parameter. We can just save a reference to this default service and use it whenever we want to stick with the default behavior. All of the other methods in the class just call the default
service.
To use our extension when running the utility, we just have to make sure the compiled DLL and the filter.xml file
are in the same folder as CrmSvcUtil.exe, and set the /codewriterfilter command-line argument when running the utility (as described in the SDK):
crmsvcutil.exe /url:http://<server>/<org>/XrmServices/2011/Organization.svc /out:sdk.cs /namespace:<namespace> /codewriterfilter:SvcUtilFilter.CodeWriterFilter,SvcUtilFilter
/username:[email protected] /password:xxxx
That's it! You now have a generated sdk.cs file that is only a few hundred kilobytes instead of 5MB.
One final note: There is actually a lot more you can do with extensions to the code generation utility.
For example: if you return true in the GenerateOptionSet method, it will actually generated Enums for each CRM picklist (which it doesn't normally do by default).
Also, the source code for this SvcUtilFilter example can be found here.
Use at your own risk, no warranties, etc. etc.
Please mark as a answer if this post is useful to you.

How to up the timeout setting to solve password reset portal error "Authentication gate timed out waiting for a challenge response"?

Hi Everyone,
We have the password portal up and running on one box and another server with FIM R2 and SharePoint 2010. All is good with the exception that our end users typically get distracted during the password registration and/or reset process and receive:
"An error has occurred. Please try again, and if the problem persists, contact your help desk or system administrator. (Error 3000) ". The timeout kicks in after 5 minutes of inactivity in the browser.
The FIM Service log shows the following:
"Authentication gate timed out waiting for a challenge response".
I have confirmed that the default password portal web.config setting is <add key="SessionTimeoutInMinutes" value="20" />.
We have also updated Microsoft.ResourceManagement.Service.exe.config per this
article to the following but with no luck:
<resourceManagementClient resourceManagementServiceBaseAddress="myAddress" timeoutInMilliseconds="600000" />
<resourceManagementService externalHostName="myHost" dataReadTimeoutInSeconds="600" dataWriteTimeoutInSeconds="600"/>
We did not update the Windows SharePoint Servicesweb.config setting per the article about since we are on SharePoint 2010.
There is no NLB or firewall in front on this server.
If anyone has any solution to how to solve this on FIM R2/SharePoint 2010 please let me know.
Cheers!

FIM_Admin,
You could try changing the receiveTimeoutInSeconds parameter of the resourceManagementService node in your Microsoft.ResourceManagement.Service.exe.config file. However, you are warned not to do this unless instructed to by MS customer support.
http://msdn.microsoft.com/en-us/library/windows/desktop/ee652424(v=vs.100).aspx
http://technet.microsoft.com/en-us/library/ff800821(v=ws.10).aspx

[Bug] Default timeout value of Wait for Occurrence

Similar Messages

Maybe you are looking for