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

Similar Messages

[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.

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)

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

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

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.

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

MMP 5.2p2 'waiting for connection; X on queue' errors, X increasing

Shortly after manually upgrading our standalone POP/IMAP multiplexors to 5.2 Patch 2, we started experiencing problems where the CPU utilization of the AService process would drop to almost nothing, and this message would begin to appear in the logs:
20060328 161950 PopProxyAService.cfg (ldap 0x4bb0d8) (uid=redacted) waiting for connection; 10 on queue
20060328 161952 PopProxyAService.cfg (ldap 0x819c50) (uid=another.redacted) waiting for connection; 11 on queue
20060328 161952 PopProxyAService.cfg (ldap 0x817918) (uid=redacted3) waiting for connection; 12 on queueThis message continues with the value increasing:
20060328 163719 PopProxyAService.cfg (ldap 0xcae928) (uid=redacted4) waiting for connection; 235 on queue
20060328 163733 PopProxyAService.cfg (ldap 0xcb13c8) (uid=redacted5) waiting for connection; 236 on queue
20060328 163809 PopProxyAService.cfg (ldap 0xcb5250) (uid=redacted6) waiting for connection; 237 on queue... until AService is restarted.
At first blush, it looks like something is making the LDAP connection wedge, and it's not timing out for some reason, but that's a guess.
I see that someone on the Info-iMS list had the same problem shortly after installing 6.1 back in September 2004:
http://lists.balius.com/pipermail/info-ims-archive/2004-September/019517.html
Has anyone else seen this or know if this has been identified as a specific bug ... or is a symptom of something else?
Royce

That's the problem. THere IS no timeout for the
situation you've gotten into, where MMP (or messaging
server itself) believes a connection exists, and is
active, but gets no response.That's unfortunate. It sounds like a useful timeout for a number of circumstances.
The solution is to refresh all connections so you
don't get into this situation.Unfortunately, the LdapRefreshInterval doesn't appear to be a documented option for 5.2p2, but only for 6. Can you confirm this?
The overhead of binding and unbinding once every 10
minutes or so is very, very minimal.Fair enough.
The latter, if it exists, would be a much more
precise way of handling our symptom. Well, actually, the real problem is that the
connection between MMP and LDAP is getting silently
severed by the load balancer. That's something
that's BAD for both LDAP and for MMP.
Causes fd leaks in ldap, as it never knows when to
close what it beleives is an active connection. It
will attempt to close, but, since it can never get an
ack back after the load balancer severs the
connection, it can't fully close it.
This is truly a bad situation, and it's easy to fix.
recycle the connections before the LB cuts you off.It looks like our LB has an idle timeout of 1 hour, with any traffic at all resetting the timer. In other words, it doesn't look like the LB that's causing the wedge. There is also no internal LB probing going on.
From ulimit/plimit/pfiles output, I've also learned that the slapd user currently has a 65536 FD cap. I've been monitoring the FD usage of the slapd process for the past couple of days, and our LDAP servers have not been getting above 1000. We've also had multiple lockups in that period of time. So running out of FDs may not be causing our problem.
You're very clear about what you want.
Unfortunately, you are not correct about what is
s possible.Perhaps our definitions of 'possible' need some negotiation. :) You're saying that the MMP can't do this today, which I accept as fact. But the pieces are all there, as far as I can see.
The MMP keep close track of how many queries have been served by a particular LDAP connection, how many are on queue without being serviced, and the age of the existing connection. In other words, the app has all the information necessary to do what I'm describing: notice that a connection hasn't actually gotten a response back in X seconds, and terminate it.
Since the app doesn't support what I'm yearning for, this is academic at this point, so I agree that it's time to take a different tack. I don't want to appear ungrateful for your responses. I appreciate the time you've spent on this issue with me. I'm just trying to understand the underlying issues.
So I find myself in these unfortunate circumstances:
1. 5.2 doesn't lock up.
2. No other applications using our LDAP are experiencing any hung LDAP connections (neither at the TCP level nor at the LDAP application level), even though they're using the same LB front-end.
3. From the output of plimit/pfiles, our LDAP servers are configured to handle far more file descriptors than they're consuming. The FD theory appears to not apply.
4. Our LB is configured to time out after 1 hour of inactivity.
5. It seems unlikely that any of the LDAP connections coming from the MMPs are reaching the 1-hour threshold, considering how high-volume they are for POP, unless they are distributing queries across connections very asymmetrically. Even at 3am, there are enough people who leave their computers on all night who check every 1 minutes that the connections are almost never idle for more than a few tens of seconds.
Based on the above, it's hard for me to not conclude that 5.2.p2 appears to either have a regression bug that's causing the wedge itself, or has changed the way that it handles some types of timeouts.
We cannot use 5.2 because we need a bugfix that is in 5.2p2. We appear to not be able to use 5.2p2 because it has this lockup problem that 5.2 does not.
My 'strings' search for LdapRefreshInterval on the AService binary and Pop/IMAP libraries turns up nothing. Can you confirm that 5.2p2 does or does not support this feature?
If not, and the only solution is to use LdapRefreshInterval, do you know if II can run 6.x MMP on our multiplexor boxes and leave 5.2 running on our back-end systems?

BackupExec: A timeout occurred waiting for NDMPD.NLM to init

"Error: 1004 A timeout occurred waiting for NDMPD.NLM to initialize."
A very common and well documented issue but every fix I have found has not worked. The list is extensive so I will start by describing the issue, then the environment and finally what I have tried so far.
The issue
I can not load BackupExec 9.1 or 9.2 on NetWare 6.5 SP8. The loader starts and when it gets to loading NDMPD.NLM the CPU hits 99% (reported by monitor.nlm) and BackupExec stops loading for about 80-120 seconds. The loader eventually gives up after a non-critical abend. From this point on I can not unload becdm.cdm and I generally reboot the server to clear the abend.
BackupExec has been working on the server for about 2 years, I can not link any changes to the time it stopped working.
It used to load reliably every time for about 1.5 years and then it started to exhibit this issue when loading 1 in 10 times. It has gradually gotten worse and now will not load at all.
Before you say it, yes I know Symantec dropped BackupExec for NetWare years ago.
It seems to me this can only be a hardware issue now but I'm keen to hear any other ideas?
The environment
* The physical server is a HP DL385 G5 (SKU 411360-371), the tape drive is an external half height HP Ultrium 448 LTO 2 (SKU DW086A) using SAS to connect to a HP SC44Ge SAS HBA (SKU 416096-B21). It has 18GB of RAM, Two quad-core AMD Opteron 2352 2.1 GHz CPU's and 5 x direct attached SAS hard drives running on the internal P400 RAID controller configured with RAID 5.
* I can provide firmware versions if needed, the BIOS is HP A09 2009-07-11. Don't have the tape drive or HBA versions to hand.
* The server is running VMware ESXi 4.1.0 build 260247, using a free license i.e. stand alone.
* The VMware server uses about 50% of RAM, 70% of storage and 12% of CPU.
* The guest is NetWare 6.5 SP8 (overlay) running as a guest with 4GB of vRAM and a single CPU. The tape drive is presented as a generic SCSI device.
* I'm running BackupExec for NetWare 9.2.1401.5 build 287839 with the NetWare Open File Option and a Windows Remote Agent.
* I'm running the storage driver LSIMPTNW.HAM version 5.02, 5 Dec 2007, which is default with SP8. BackupExec 9.2 device driver becdm.cdm version 7.50, 7 Feb 2006.
* The NetWare server sees the tape drive as an "Unbound Device Object" until becdm.cdm is loaded at which point its recognsied as "HP Ultrium 2-SCSI T65D"
* The tape drive is listed on the BackupExec HCL - "StorageWorks Ultrium 448 LTO2" except mine is SAS not SCSI. Enterprise Support - Symantec Corp. - Symantec Backup Exec for NetWare Servers (tm) 9.x (9.0, 9.1, 9.2) Hardware Compatibility List. Includes HCL information for supported drives, libraries, virtual tape devices, fibre-channel HBAs, switches, and rou
What have I tried so far?
* We have a rental tape drive identical to our own as the original one was over-heating, so I have tried two physical tape drives. Both using the same server, HBA and SAS tape drive cable.
* I have used tcpcon.nlm to check that port 10,000 is unused.
* I have tried the parameter -!X on the line of bestart.ncf that loads BackupExec to stop it checking if port 10,000 is free.
* I have added a set statement to c:\nwserver\startup.ncf "set auto load of cdm modules = off" so it will not try to load unwanted CDM's.
* I have renamed all copies of nwtape.cdm to nwtape.cdx on the C: so they can not be auto loaded.
* There are no load statements in the startup.ncf for other tape drive device drivers. Just scsihd.cdm and idecd.cdm.
* There are no tape libraries or robots involved. Its just a basic tape drive.
* The physical and virtual server have been rebooted numerous times to ensure its not a memory issue etc...
* I've loaded the server with no other significant modules loaded. Just the basics like eDirectory etc... and the same issue still occurs.
* In addition to the NW65 SP8 default version of lsimptnw.ham I have tried version 5.03.01, 23 Jan 2008, from the LSI website.
* I have deleted the original BackupExec folder from the server (sys:\bkupexec) and re-installed BackupExec numerous times.
* I have powered off the tape drive a number of times
* I have changed the tape drives virtual SCSI ID, presented by VMware to the NetWare guest, to be a higher number on the same virtual HBA as the virtual disk. I have also tried allocating the tape drive a virtual SCSI ID on a dedicated virtual HBA, SCSI 1:0.
* I have deleted the SMDR config file (sys:\etc\sms\smdr.cfg) and re-created it using the command "load smdr.nlm new"
* I have deleted the NetWare servers backup queue and the SMS SMDR Group from eDirectory and re-created the queue using the command "load qman.nlm new". Note: as its NW65SP8 the SMS RPC object does not exist and the SMS SMDR group is not re-created.
* I have deleted the two BackupExec objects from eDirectory and re-created them by loading BackupExec using "bestart.ncf".
* I have checked the health of eDirectory.
* I have tried the LSI SAS and LSI Parallel virtual HBA's in the VMware guest machine.
* I have tried adding the parameter qtags=off to the load command for lsimptnw.ham in startup.ncf.
* I have tried the parameter -b on the line of bestart.ncf that loads BackupExec
* I have tried loading ipxspx.nlm to stop any public symbol error messages when loading BackupExec
* I have also tried BackupExec version 9.1 build 0306.12 and 9.1.1158.10 build 289707
* I have built a second NetWare 6.5 SP8 server (SP8 overlay DVD, MD5 verified ISO media) using the Backup server profile during the GUI install stage. I have loaded afreecon.nlm, installed VMware tools (vmwtool.nlm) and BackupExec for NetWare 9.2.1401.5 build 287839. The same issue occurs
System output
1) Excerpt from "list storage adapters"
0x04 [V358-A3] SAS1068:00008 [slot 8]
0x06 [V358-A3-D0:0] HP Ultrium 2-SCSI T65D
2) Backup Exec SureStart Console
Module NETDB.NLM is already loaded
Module SMDR.NLM is already loaded
Module TSAFS.NLM is already loaded
Loading module TSANDS.NLM
Module BECDM.CDM is already loaded
Loading module B2D.NLM
Module NWIDK.NLM is already loaded
Module NSS.NLM is already loaded
Loading module OFM.NLM
Loading module NRLTLI.NLM
Loading module AD_ASPI.NLM
Loading module NDMPD.NLM
Error: 1004
A timeout occurred waiting for NDMPD.NLM to initialize.
Press <Alt+Esc> to return to the Server Console. After you resolve
the error condition(s), re-execute the BESTART command.
3) Abend log
Novell Open Enterprise Server, NetWare 6.5
PVER: 6.50.08
Server halted Sunday, 6 May 2012 5:38:23.196
Abend 1 on P00: Server-5.70.08: Page Fault Processor Exception (Error code 00000002)
Registers:
CS = 0008 DS = 0010 ES = 0010 FS = 0023 GS = 0023 SS = 0010
EAX = 00000000 EBX = 00204B58 ECX = 896B77E0 EDX = 8A26157C
ESI = 00204B58 EDI = 00000F9B EBP = 8A261DD4 ESP = 8A261DA8
EIP = 8A1E03FD FLAGS = 00010082
8A1E03FD C680B00E000000 MOV [EAX+00000EB0]=?, 00
EIP in LSIMPTNW.HAM at code start +000013FDh
Access Location: 0x00000EB0
The violation occurred while processing the following instruction:
8A1E03FD C680B00E000000 MOV [EAX+00000EB0], 00
8A1E0404 8A45FC MOV AL, [EBP-04]
8A1E0407 8845F8 MOV [EBP-08], AL
8A1E040A 8A45F8 MOV AL, [EBP-08]
8A1E040D 89EC MOV ESP, EBP
8A1E040F 5D POP EBP
8A1E0410 5F POP EDI
8A1E0411 5E POP ESI
8A1E0412 5B POP EBX
8A1E0413 C3 RET
Running process: Server 10 Process
Thread Owned by NLM: SERVER.NLM
Stack pointer: 8A261F5C
OS Stack limit: 8A25A020
Scheduling priority: 67371008
Wait state: 50500F0 Waiting for work
Stack: --8A261E01 ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00951740 ?
8A1E0414 (LSIMPTNW.HAM|(Code Start)+1414)
--0097BAA0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--01900190 ?
--157C157C ?
--0D000001 ?
--0097BACC ?
--8A261D01 ?
--8A261E18 ?
--00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
--00204B58 ?
--00204B58 ?
8A1DFD6B (LSIMPTNW.HAM|(Code Start)+D6B)
--0097BAA0 ?
--0097BAC0 ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--0097BA50 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00F20000 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00200000 ?
--0097BAA0 ?
--0097BAC0 ?
--8A261EB0 ?
--8A261E44 ?
--00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
--00204B58 ?
--00204B58 ?
8A1FAA64 ?
--0097BA50 ?
--00000F03 (LOADER.NLM|KernelAddressSpace+F03)
--00000286 (LOADER.NLM|KernelAddressSpace+286)
--00951740 ?
8972FA00 (NWPA.NLM|HAI_Enable_Real_Mode_Access+34)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--8A261E70 ?
--00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
--00204B58 ?
--00204B58 ?
8A1FAC47 ?
--0097BA50 ?
--00204B58 ?
--0097BA50 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--01080000 ?
--01080000 ?
--8A261E90 ?
--00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
--00204B58 ?
--00204B58 ?
8A1FAC95 ?
--00952180 ?
--010824A0 ?
--02058001 ?
--8A261EB8 ?
--00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
--00204B58 ?
--00204B58 ?
8A207658 ?
--010824A0 ?
--01091240 ?
--00951740 ?
--00008100 (LOADER.NLM|KernelAddressSpace+8100)
--00008134 (LOADER.NLM|KernelAddressSpace+8134)
--8A261EEC ?
--00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
--00204B58 ?
--00204B58 ?
8A208ED6 ?
--010824A0 ?
--00000003 (LOADER.NLM|KernelAddressSpace+3)
--00000046 (LOADER.NLM|KernelAddressSpace+46)
--02010002 ?
--010824A0 ?
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--00951740 ?
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00204B60 ?
--00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
--00204B58 ?
--00204B58 ?
89729AE5 (NWPA.NLM|NPAThreadRoutine+3D)
--00010002 ?
-896E5110 (MM.NLM|PostponeEvent+0)
8973173F (NWPA.NLM|CDM_MountActivate_Message+EB)
--00000001 (LOADER.NLM|KernelAddressSpace+1)
--00000000 (LOADER.NLM|KernelAddressSpace+0)
--802171E4 ?
--802171E4 ?
80327F6B (MM.NLM|RetryPostponedMessages+237)
--01081A00 ?
--00204B60 ?
--00000F9B (LOADER.NLM|KernelAddressSpace+F9B)
--00204B58 ?
--00204B58 ?
003682B2 (SERVER.NLM|CallAESRoutineWithEsiSet+A)
Additional Information:
The CPU encountered a problem executing code in LSIMPTNW.HAM. The problem may be in that module or in data passed to that module by a process owned by SERVER.NLM.
Thanks,
MC

Well the problem is now resolved. It was either faulty tapes (about 12 of) or two tape drives with faulty heads. We had the heads replaced in one of the drives and tested it with a new tape, it works perfectly again.
MC

Timeout waiting for Oracle WebLogic Server v10.3 at localhost to start

I am trying to run .portal file using "Run on server" option in Workshop for weblogic.
After doing this, its trying to start the server Oracle weblogic server v10.3 at localhost and then publish my module.
Server view status shows as "State" as "Starting" and "Status" as "Synchronizing". When status reaches 82% it gets stopped there for a long time, and when 83% comes up, I can see the "State" as "Stopped" and "Status" as "Republish". And then an error window with title as "Problem Occured" and contents saying, Starting server- Oracle weblogic server v10.3 at localhost (Time of error: ...) Details >> Timeout waiting for Oracle WebLogic Server v10.3 at localhost to start. Server did not start after 480s.
But the console tab (when I give the startup & Deployment option as "Launch Weblogic server in eclipse console) shows,
<Sep 8, 2011 6:15:03 PM IST> <Notice> <WebLogicServer> <BEA-000365> <Server sta
e changed to STARTING> (final step alone I pasted)
Before this I can see, WLS Start mode = Development, setting Classpath ,
<Sep 8, 2011 5:56:36 PM IST> <Notice> <Log Management> <BEA-170019> <The server
log file C:\bea\user_projects\domains\myPortalDomain\servers\AdminServer\logs\Ad
minServer.log is opened. All server side log events will be written to this file
.>
When I checked Adminserver file its having,
<AdminServer> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1315487671986> <BEA-160151> <Registered library Extension-Name: wlp-groupspace-app-lib, Specification-Version: 10.3, Implementation-Version: 10.3.0.1 (EAR).>
And many more similar entries...
Also there is Adminserver.logxxx file which is having,
####<Sep 8, 2011 5:33:58 PM IST> <Warning> <JDBC> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1315483438048> <BEA-001129> <Received exception while creating connection for pool "portalDataSourceNeverXA": SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.>
####<Sep 8, 2011 5:33:58 PM IST> <Info> <JDBC> <CINTNCHEOLY0GX7> <AdminServer> <[ACTIVE] ExecuteThread: '2' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1315483438267> <BEA-001156> <Stack trace associated with message 001129 follows:
java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093.
     at com.pointbase.dbexcp.dbexcpException.getSQLException(Unknown Source)
     at com.pointbase.net.netJDBCConnection.a(Unknown Source)
     at com.pointbase.net.netJDBCConnection.<init>(Unknown Source)
     at com.pointbase.net.netJDBCDriver.getConnection(DashoA10*..:170)
     at com.pointbase.net.netJDBCDriver.connect(DashoA10*..:94)
     at com.pointbase.jdbc.jdbcUniversalDriver.getConnection(Unknown Source)
     at com.pointbase.jdbc.jdbcUniversalDriver.connect(Unknown Source)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.makeConnection(ConnectionEnvFactory.java:316)
     at weblogic.jdbc.common.internal.ConnectionEnvFactory.createResource(ConnectionEnvFactory.java:217)
     at weblogic.common.resourcepool.ResourcePoolImpl.makeResources(ResourcePoolImpl.java:1109)
     at weblogic.common.resourcepool.ResourcePoolImpl$ResourcePoolMaintanenceTask.timerExpired(ResourcePoolImpl.java:2282)
     at weblogic.timers.internal.TimerImpl.run(TimerImpl.java:273)
     at weblogic.work.SelfTuningWorkManagerImpl$WorkAdapterImpl.run(SelfTuningWorkManagerImpl.java:516)
     at weblogic.work.ExecuteThread.execute(ExecuteThread.java:201)
     at weblogic.work.ExecuteThread.run(ExecuteThread.java:173)
And many more entries like the above...
I even tried startup & Deployment option as "Start weblogic server in Expressmode" and still same error I am getting and this time instead of in eclipse console, I can see command prompt and here also showing "Server state changed to STARTING"
FYI, I created domain with runtime JRocket 1.6.0_05.
I even tried to clean build the portal project and publish using clean option. Still same problem coming :(
FYI, my system is having 1 GB RAM only and bit slow. Could this be a problem or something else? Please suggest.
Thanks in advance.
Edited by: gopikrish on Sep 8, 2011 6:20 AM

Hi Gopikrish
The root cause for your error is, it is not able to start the Pointbase database. Looks like you configured a domain with default pointbase database. In the domain\bin\ one of the starup scripts like startWeblogic.cmd, you should see some lines that start the pointbase database.
java.sql.SQLException: SQL-server rejected establishment of SQL-connection. Pointbase Server may not be running on localhost at port 9093
Instead of starting from Workshop, go to the domain root folder and start the weblogic using the command like startWeblogic.cmd (or .sh on unix). This should start the pointbase and then start the portal domain. Portal domain does need this backend pointbase database to store all the portal meta data and has datasources configured for this.
Do you have a Clustered Portal domain, with one of the managed servers located in the remote machine. If yes, and if you use default Pointbase database, you need to change something like pointbase db should not be localhost but the name of the machine where you have the admin server running.
Either way, the issue is not able to stat the pointbase db and thus serve not starting.
Thanks
Ravi Jegga

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.

Waiting for upload queue ?

I ,i have a little problem to charge on the store my app(iOS).I have two element that have the state of "waiting for upload"... when i try to charge from xcode the last that i have created , the software recognize this like the first ( i show the name of the first app ) despite the bundle id is correct. Is a bug ? or if i have two or more app in "waiting for upload " i need to charge the first in the queue ? thanks

Follow this guide, start on page 59 it will walk you through the rest of the process. Good luck!
http://help.adobe.com/en_US/ppcompdoc/Step_by_step_guide_to_dps_se.pdf

Flicker footage in Premiere Pro CC 2014.2. Tested on different computers. When waiting for fixes this bug?

Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different. Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
It can occur even in the parts without filters !!! But no all time.
ver 2014.2 - win 7 - intel i7-4770 - gtx 770 - flicker!
ver 2014.2 - win 7 - intel i7-4770 - Intel HD Graphics 4600 - flicker!
ver 2014.2 - win 7 - intel i7-2700K - quadro 2000 - flicker!
MERCURY PLAYBACK ENGINE work fine! But still flickering in preview and render.
When waiting for fixes this bug?

Hi Aleksey,
Flicker appears solely the fault of Premiere Pro CC 2014.2. Tested on different computers. Used as nVidia Quadro and GeForce GTX770. Drivers were different.
Have you tried with the Mercury Playback Engine set to "Software Only?" More info please: FAQ: What information should I provide when asking a question on this forum?
Everywhere equally evident flicker. Incidentally, it defies logic and may occur at different film pieces. If re-render that flicker may occur on another spot in the video.
Is this a brand new project or one you updated from an earlier version? What kind of footage are you exporting? Which preset are you using?
When waiting for fixes this bug?
If I can repeat the case here with the same hardware, GPU, and drivers, that would be easier to fix the bug. Currently, I cannot recreate the bug. If you or anyone else can provide me with steps to recreate the bug, that would help immensely. It sounds like this will be the difficult thing.
Thanks,
Kevin

Why am I now waiting in queue over an hour...no...two hours for support chat?

Since this last CC desktop client update, CC decided it needed to sync all 7k+ of my files in my CC folder, crashing once in process, and creating a multitude of Acrobat Distiller errors, much as it has been doing for more than the past year. I figured I'd try to ask support chat about this. I'd also like to inquire as to whether I can expect my CC folder location to be moved from my data drive back to my system SSD on my desktop, as happened with the last CC desktop update, and if there is any way to avoid this from happening.
That was about an hour and 30 minutes ago. As I was waiting I rediscovered this thread: Adobe Support Availability Questions and Feedback . Funny, as it outlines issues with chat support and offers suggestions that could greatly lower queue times during off hours, as I'm currently experiencing, but it received zero replies. I also received zero replies in these forums to a thread I bumped asking why the Adobe Shape app is sometimes not uploading to CC and what to do when that happens. It seems at least two other people have run into the same issue. That thread was started two months ago and has so far received zero response: Adobe shape only partially uploading to the cloud I didn't start this thread, just had the same issue as the originator.
Coming up on an hour and 40 minutes now, and if I get through, I'll probably be told they cannot offer any support for troubleshooting the CC desktop app. Ironic that, seeing as I first reported very similar issues back in December of 2013, dealt with it for months, even installing logging versions of the CC software, and some issues still remain unresolved.
Yes, I'm whining. I am paying $50/month for CC, and I'm reaching the point where I'm believing support is largely non-functional. I dread contacting support at this point, whether phone or chat. It is a large time and attention sink, that much more often than not, does not seem to solve the issue(s), many times for days, weeks, months, sometimes even years. I used to have much more hope for these forums, but as of late, my last two questions, as detailed above, received no responses in over a month.
Beginning to approach 2 hours in the chat queue. Need to get to bed. It is really frustrating that Adobe seems to be developing the support strategy of a monopoly, "Why bother, who else are they going to move to?". This seems to me to be the case, growing the number of clients, and not bothering to grow support at the same rate. How else does one explain a chat queue that used used to take 30 minutes, a month ago it took an hour, and tonight is taking two hours with no response, or that my questions on these forums used to receive an almost immediate response here, and now they languish with no replies, even when they are not whining, but legitimate technical questions, and yes, the legitimate technical questions came before the whining. Time to de-queue, after waiting for two hours, and go to bed.

Once you do get things working... Hardware crashes or virus infections happen, so you should buy software to make a full backup of your hard drive to an external USB hard drive... plus, making step-by-step backups during a new install or major program addition makes it easy to go back a step if something doesn't work
This backup and then restore is, of course, only to the same computer with a new drive (or the same drive as long as you don't mind writing over everything) since doing a restore to a new computer won't work due to Windows and many programs having activation information that is keyed to your hardware (which is why Windows will force you to RE-Activate if you change very much hardware)
The product I use is at http://www.terabyteunlimited.com/image-for-linux.htm
Image runs off of a bootable CD via Linux (the Zip you download includes a program to make the bootable CD) and it reads EVERYTHING on the drive, even the hidden registration information, so everything is restored when needed... and you may restore the image to a brand new drive in case of a crash, and not have to re-install anything
Please note that I own no part of Image, and I don't get a referral fee (that is just a plain web link) but I use the program and it has saved me a LOT of trouble when I had a hard drive die... and I was able to restore everything and not have to re-install or re-activate a single program, from Windows on up

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 in timeout behavior of wait for queue element

Similar Messages

Maybe you are looking for