Application locking up at Call by Reference

We are seeing our application lock up occasionally at a VI Server Call By Reference node. The VI acts like it is waiting for subVI called to execute, but the subVI acts like it never got the message to execute. We've seen this at a number of VIs that call subVIs by reference. In some cases we are using strickly typed VI references, and in other cases we are not. We've seen the code lock up in both. Has anyone else seen this type of behavior?
We are running LabVIEW 7.0, Windows XP, and TestStand 3.0.
Also, I noticed that in a couple of places, the reference isn't explicitly closed. Since these VIs are only a small part of the application, not called very often, would that cause much of a problem (memory or otherwise)?

It sounds like your reference is pointing to something else than you
think it is pointing to. Generally speaking, not closing
references is not good. Whether it will lead to problems is most
likely a matter of probability. Could it be that the reference is
actually being closed before you issue the correct command?
Fix the code first (make sure that references are closed when they're
no longer used and make sure references aren't closed when they are
still in use).
References are great for uncovering tiny errors in code. Hunt
them down and show no mercy! Or just debug, that'll work too.
Seriously, I recommend you trace where the references are coming from and make sure they're being closed at the right time.
Important is also the difference between (what I understand as)
"static" references (right-clicking a control and selecting -create
reference) and those created dynamically (such as in lauching a VI via
VI server). All Dynamic references should be closed when finished.
If you could post a picture of the block diagram (Jpg is good, BMP is bad) maybe someone can offer some more precise help.
Hope this helps
Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)

Similar Messages

Application locking up at Call by Reference

We are seeing our application lock up occasionally at a VI Server Call By Reference node. The VI acts like it is waiting for subVI called to execute, but the subVI acts like it never got the message to execute. We've seen this at a number of VIs that call subVIs by reference. In some cases we are using strickly typed VI references, and in other cases we are not. We've seen the code lock up in both. Has anyone else seen this type of behavior?
We are running LabVIEW 7.0, Windows XP, and TestStand 3.0.
Also, I noticed that in a couple of places, the reference isn't explicitly closed. Since these VIs are only a small part of the application, not called very often, would that cause much of a problem (memory or otherwise)?

SAS,
The problems described by TPoint in the thread "TestStand hang, Execution with Event-Callback-VI " sound familiar. Our code locks up at the "Run VI" Method (I've enclosed a screen capture of the VI where it locks up), and once it does, you can't open any VIs from Explorer. You can still open VIs from within LabVIEW. My main problem, though, is trying to get it to happen in a small application, and getting it to repeat more frequently. Right now, we can go through 200 test runs before it happens. Not enough to stop production, but enough to cut into our yields. Unfortunately, it also makes it very hard to diagnose. On our development system, it takes about 4 days to get through 200 runs. So what I'm getting at is, if you can post an example of where you saw the problem, may that would help me put together an example of my problem.
We don't use Events, we use polling. We are also using LabVIEW 7.0, and I see that TPoint was using LV 7.1, so I couldn't open that example. If there are other screen shots that you think would be helpful, let me know. The Operator Interface is huge (its inherited code, I wish I had the time to rewrite it), so I can't post the whole thing, but if there are specific routines (such as the polling routine) that you'd like to see, I could post that.
Thanks,
Tom
Attachments:
Call_Driver_Mode_Block_Diagram.jpg ‏72 KB

Check VI type for call by reference node

Hi Ppl,
I'm calling a set of VI's dynamically using call by reference node. And I have a type specifier linked to a particular type connector pane. But at times when the VI prototypes do not math I get error from the open VI reference node. Is there any way to check if the VI connector panes matches before opening the refrence with the VI type specifier ?, or using the error code is the only way to check if there were miss match in VI connector pane.
Thanks
Solved!
Go to Solution.

But what is wrong with Error checking?
For example, I using code like this in my application for detect which type of dynamic VI should be used (decision based on Error output):
Andrey.

Is there any way to show vi's called by reference in the hierarchy window

I've inherited some code and in order to save memory and system resources at run time it calls several vi's by reference rather than including them as sub vi's.
Howver I would like to use the hierarchy window to get a more general overview of how the system works but the vi's called by reference don't show up here. Is there any easy way of finding out how all the parts interconnect?

VIs called by reference should appear in the hierarchy window but not under the caller icon. They appear at the top line of VIs.
If you are sure that a VI is in memory and it does not appear in the Hierarchy window, this VI has been marked as "System VI". Such a VI won't appear on the Hierarchy window or on the application property "VIs in memory".
LabVIEW, C'est LabVIEW

LabVIEW RT, Timed loop, finished late, Call by reference

I have a timed loop triggered by the sample clock of a DAQ-Card. The sample Clock is 8 kHz and the loop will run with dt = 4. Normally the loop is running without finished late[i-1]. But from time to time it happens that the loop is running extremly longer which means instead of 0.5 millisec it needs 4 - 5 millisec. It seems this doesn't never occur while accessing DAQmx.
The application uses plugin technologies and some of the VIs in the timed loop are preloaded and called by Call by Reference.
Does those VIs inherit the priority, execution system and CPU of the timed loop?
The application is running on LV RT 2009 on a Dual core PXI-Controller. The timed loop is bound to CPU 1. There is no difference runinng the application from the development environment or as a startup application.
For the measuring test I modified the application in a way that I don't have:
disk access for storing the result file
TCP/IP communication
Controls on the front panel of the top level VI
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

To keep you informed:
I stripped the application and have left only the measurement storing module and the timed loop. The loop was using the microsecond timer running each 500 µsec. Additional all Non-Real-Time modules were loaded and only one module creates a XML string and sends it to the communication layer which will drop it because no TCP/IP port is open. The creation of the XML string is done each 300 ms.
In this case I don't have any finished late iterations
Next I added the DAQ Module. Now I get finished late again but with a lesser frequency as original.
I removed all unnesseccary tasks from the DAQ moulde leaving one task for a PXI-4204 for using as the clock source for the timed loop. No I get finished late seldom.
I removed the module which will send the XML string and I don't get finished late.
Next I was adding code to see memory allocation. I can when memory allocation is changing but it is not related to the finished late iterations.
Next time I have the chance to do more tests I will see which DAQ task triggers the finished late iterations. I have one AI task on a PXI-4204, 4 Counter tasks on a PXI-6602, 1 DI task on a PXI-6514, 1 DO task on a PXI-6514, 1 DI task on a PXI-6259, 1 DO task on a PXI-6259, 1 AO task on a PXI-6259 and 1 AO task on a PXI-6711.
The AI task on the PXI-4204 is running in Continous Sampling (Single Point HW Timed is not supported), all other tasks exept the DI and DO are Single Point HW Timed.
Waldemar
Using 7.1.1, 8.5.1, 8.6.1, 2009 on XP and RT
Don't forget to give Kudos to good answers and/or questions

How to get caller object reference from a method

Hi,
I am working a already existing Java Swing project, now I got a problem, in a method I need to get the caller object reference otherwise, I can't succeed this operation. So please tell me a way how to get the caller object reference from a method. that method would be static or regular method anything will do for me.
Edited by: navaneeth.j on Jan 29, 2010 11:20 PM

navaneeth.j wrote:
Actually my doubt is, I have a method "addition" method, which is using by many classes so my requirement is in the addition method I want to write a code snippet which will identify and get the the caller object. Actually I tried Reflection.getcallerclass but there I am getting "CLASS" object not the actual object reference, but I want object reference.
Actually we have a huge project which is writen plain JAVA, so in this project the authors written the Database connection package for single database transaction. so now we are using this project source code for JSF application in this web application the DB package has serve based on the dynamic db connection parameters, so if we want to change this package fully means need to solve the dependency problem in hundreds of classes, so my point is if I can access the caller object in the DB package when ever it gets called by any class from any where of the project. So actually I liked Reflection.getcallerclass, the way of implementation perfectly works for me but it is not giving caller object reference, if something gives the caller object then I can get the DB connection parameters then there is no need to pass the parameters in the hierarchy.You can add a parameter (of type Object) to your addition() method
and everywhere you call the addition() method also pass this (which from the POW of the addition() method will be a reference to the calling class instance).
There may be alternative solutions
but none that require less effort.

Call by reference in weblogic

hi all,
i am using statful session ful bean ,where are i am using Vector ,when i retrieve
the vector in to another Vector and do some manipulation on the new Vector ,but
the Vector that is declared in the Stateful session bean remains unchanged , i
had using the same thing with the main site , and my local site ,it is working
on the localsite but not on the main site.
e.g Vector test = m_sessionfulBean.getAllValue();
when i do the changes it won't get reflected to the vector that it return.
Can somebody help?

The problem with the Vector (and almost all collections) is that while
they clone the main object, the elements are not cloned so any
modification to the elements will affect your original. That is why I
said that you should clone the collection only if the caller would not
modify the elements.
Or the EJB method can also clone the elements and return a new Vector.
The gain is performance since cloning is usually faster than serializing
for local clients but the down side of this is that remote clients will
have an overhead as for them the result will be serialized anyway so
there was a cloning done with no need for it.
Cheers,
Dejan
Byron Xiao wrote:
See, I am not sure what he really means in his message. By the way, Vector also
implements the Clonable interface. But the elements of the Vector may not implement
the Clonable interface. If you clone the Vector and return the cloned Vector
to the caller. There is no guarantee that the changes he made in the Vector elements
will get clone properly. So in that case, you aren't really seeing the true "call
by reference" behavior.
Basically, I don't understand what his question was. Sorry for the confusion.
"Deyan D. Bektchiev" <[email protected]> wrote:
Not really true, if the Vector is serialized then it would have to
serialize all of its elements and you'd get an exception that some
elements were not serializable.
The optimization that Sanjeev is seeing is a BEA optimization to allow
calls by reference within the same enterprise application (parameter
<enable-call-by-reference> in weblogic-ejb-jar.xml).
By default the value is true so calls within the same EAR are just
normal Java calls.
If you set it to false then the parameters and return value of the EJB
call will be serialized and the object that the EJB has will not be
affected by any change that the caller does to it.
Another way to get out of this situation is to clone the Vector (if that
is acceptable since it would not clone the elements the Vector contains).
--dejan
Byron Xiao wrote:
I don't know if I understand your problem 100%, but it seems like you
manipulated
the elements in your vector, which is a class member variable in your
stateful
session bean, and passing the vector back as the return parameter to
the caller
via the remote interface. And you don't see the changes in the "elements"
of
the vector, is that correct?
Well, remember all parameters and the return value of the remote calls
are Serializable.
In this case, Vector indeed is serializable. But the ELEMENTS inside
the vector
may not be serializable objects. In this case, the container will use
the default
serialization mechanism to serialize / deserialize the elements into
the persistent
store or through the RMI I/O stream, which is just using a bit-wise
dump of your
Vector and all its elements object references to the persistent store
or RMI I/O
stream.
So the solution is to declare all the objects in your Vector elements
to implement
the java.io.Serializable interface. If all the Objects in your vector
elements
only contain primitive data types, you don't need to do anything extra.
If some
objects in your vector elements contain other object types that don't
implement
the java.io.Serialiazable interface, then you will need to write your
own writeObject
and readObject method to serialize /de-serialize those objects. You
can look
up many tutorial on Sun's website on how to do this. Hope it helps.
"sanjeev" <[email protected]> wrote:
hi all,
i am using statful session ful bean ,where are i am using Vector ,when
i retrieve
the vector in to another Vector and do some manipulation on the new
Vector
,but
the Vector that is declared in the Stateful session bean remains unchanged
, i
had using the same thing with the main site , and my local site ,it
is
working
on the localsite but not on the main site.
e.g Vector test = m_sessionfulBean.getAllValue();
when i do the changes it won't get reflected to the vector that it
return.
Can somebody help?

Labview 7.1 call by reference node that won't compile on OSX

Hi,
Here is the issue. I have an app that has been running in dev mode for a few years. Someone just noticed and wants it compiled. Everything seems to compile properly and loads fine. It is only when I get to a part in the code that has a call by reference node does it crash. It is a bad crash. The app quits all the way to the finder. I have no idea even where to begin to debug these. I am pretty sure that call by reference is the think that is causing. I remove it, doesn't crash. Only problem is that if I need to remove it, the whole app needs to be redesigned..... Soooo anyone has an ideas?
Spec:
OS X 10.4.8
Labview 7.1.1
PPC
I have tried to goto Labview 8 but that was another headache. Alot of the code changes and acts differently then it did in 7. So for now I am going to stay with 7. Anyone had this problem or can think of a way to figure out fix it or even find out for sure what the problem is?
Any help is much appreciated........
Message Edited by Tarek316 on 06-04-2007 09:11 PM

Hello,
You may be calling dynamically loaded VIs and not including them in your build. If so, please include the VIs that you are calling. You can add them by going to the Source Files Tab and clicking on Add Dynamic VI. Then please rebuild your executable.
ERROR 7 When Running LabVIEW Executable That Uses Dynamically Loaded VIs (VI Server)
http://digital.ni.com/public.nsf/websearch/FEE9D75A70FB8EBA86256A9D00498B8A?OpenDocument
Please let me know if this does not fix the problem.
Regards,
Elizabeth S.
Applications Engineer
National Instruments

Need help with Call By Reference on cRIO-9012

I have a RT application running on a cRIO-9012 in which I am attempting to establish references to a variable number of clones of the PID Autotuning (Temperature).vi, and then passing these references to a FOR loop in which I am opening each clone with a Call By Reference node to perform the PID. Essentially, I am trying to make the PID Autotuning (Temperature).vi accept an array of process variables, similar to the behaviour that some of the simpler PID VIs provide out-of-the-box.
The code I am using to obtain the references is here:
...and the code within the control loop where I am trying to do the processing is here:
The problem I am encountering, according to the Highlight Execution tool, is that all inputs to the Call By Reference node are present and reach the node, but all processing stops at this point on the first iteration and the cRIO hangs. I cannot stop the SubVI or the RT parent VI without performing a software restart on the target.
I don't know if I am using the Call By Reference node or Open VI Reference functions incorrectly, or if there is a problem with the VI being part of a library, or if something else is wrong. Any help would be appreciated.
Sean

I'm not sure this is your issue, but I think there's a conflict between opening a bunch of rereferences, and then setting the asynchronous call pool size for one of them.You don't need asynchronous execution here, you just need reentrant parallel execution (you may not even need the parallel part; your current code, if it worked, would execute sequentially, and the PID calculation is just math so should be quick and may not benefit from parallel execution). You do need reentrant execution to maintain separate data spaces.
Try opening the references with the 0x08 (Prepare for Reentrant Run) flag instead. Remove the Populate Asynchronous Call Pool. If this works, you can run in parallel by enabling For loop parallelism - but you might find that's actually slower, especially on a cRIO.

Cluster & Call by reference ( Sorry for the re-posting)

If this is set to 'true', then what happens when the bean is in a diffent
          machine(Cluster)( Does it automatically passes object by 'value' or still
          tries to pass the object by reference, in which it is going to be a empty
          object )
          Looking at the document provided by weblogic , it looks like it
          automatically passes the object by 'value' even if it is set 'true'(Only
          incase of bean is running in a different container/server)
          Thanks
          
          <!ELEMENT enable-call-by-reference (#PCDATA)>


You cannot pass-by-reference a non-RMI Object across 2 VMs, no matter what the flag is, no matter
          what application server you are running under. An object reference in one VM is meaningless in
          another VM, for they do not share the same memory-address-space.
          Even though EJBs are RMI Objects, their method arguments are not unless you explicitly pass the RMI
          interface.
          Gene Chuang
          Join Kiko.com!
          "lal" <[email protected]> wrote in message news:[email protected]...
          > Is this true for WEBLOGIC server (5.1) ?
          > Does the container automatically switches to 'call by value' mode even
          > though the flag is set 'true' for call_by_reference in XML deployment
          > descriptor.(I know this only arise in the fail over process in a cluster
          > environment)
          >
          >
          > "Rob Woollen" <[email protected]> wrote in message
          > news:[email protected]...
          > > Anytime a call goes over the network, it will be call by value.
          > >
          > > Call by reference is only possible within the same server vm.
          > >
          > > -- Rob
          > >
          > > lal wrote:
          > > >
          > > > If this is set to 'true', then what happens when the bean is in a
          > diffent
          > > > machine(Cluster)( Does it automatically passes object by 'value' or
          > still
          > > > tries to pass the object by reference, in which it is going to be a
          > empty
          > > > object )
          > > >
          > > > Looking at the document provided by weblogic , it looks like it
          > > > automatically passes the object by 'value' even if it is set 'true'(Only
          > > > incase of bean is running in a different container/server)
          > > >
          > > > Thanks
          > > >
          > > > 
          > > > <!ELEMENT enable-call-by-reference (#PCDATA)>
          >
          >

Locking in EntityFramework - calling empty stored procedure releases lock acquired using sp_getapplock

I have a patient table in the SQL Server database. Clients connect to the database and checkout one of the patients and do some operations on it and save it afterwards.
Since multiple clients might access the patient at the same time. I wanted to implement pessimistic locking mechanism, So that if one client can acquire a lock to a particular patient at a time.
Also if one of the clients locks a particular patient and either crashes or closes the client application the lock should be released. In case of crash the lock should be released when we detect that the connection of client with the database is closed.
I found out that I could use sp_getapplock and sp_releaseapplock to
do achieve this and specify @LockOwner
= 'Session' when calling sp_getapplock,
this ensures that the lock is released once the database session with the client closes.
From the code, I call a stored procedure in database to acquire the lock. This acquires the lock correctly and if i close off the client app or the client app crashes the lock is released. This is behaving as I wanted it to.
The problem happens when I call another stored procedure which is supposed to release the lock. As soon as the stored procedure is entered the lock is released, before we even execute sp_releaseapplock
@patientId, @LockOwner = 'Session' the line which is actually supposed to release the lock.
I tried creating an empty stored procedure (just commented out
DECLARE @result int
EXEC @result = sp_releaseapplock @patientId, @LockOwner = 'Session'
This stored procedure still releases the lock I acquired using sp_getapplock.
I can't seem to understand why this is happening. It should only release when I explicitly call `sp_releaseapplock @patientId, @LockOwner = 'Session'``
CREATE PROCEDURE [dbo].[uspReleaseAppLock]
@patientId nvarchar(max), -- Patient ID
@ReturnValue int Output
AS
BEGIN
DECLARE @result int
EXEC @result = sp_releaseapplock @patientId, @LockOwner = 'Session'
SET @ReturnValue = @@SPID
END
Could someone tell me why this is happening. What am I missing here ? I checked that the session ids of both the stored procedures (for acquiring and releasing the lock) are same, so it dose not seem that a new session is being created by entity frame work
for each call to the stored procedure. Something else is going on which I am not able to comprehend. Any ideas ?

Hi oalvi,
The Stored Procedure(SP) sp_getApplock initialed with "@LockOwner='Session'" is
session scoped. Your procedure
[dbo].[uspReleaseAppLock]
did the same work as you explicitly call "sp_releaseapplock @Resource = @patientId, @LockOwner='Session'", after the SP
uspReleaseAppLock
called or the current session ends, the lock released.
It doesn't make sense to call the uspReleaseAppLock to release the lock initialized in another session. If you try, you get the error like below, as I mentioned, the lock is session scoped.
"Cannot release the application lock (Database Principal: 'public', Resource: 'patient1') because it is not currently
held"
Regarding the same session ID you get from calling 2 SPs separately in Entity Framework(EF). As per my limitation knowledge on EF, If the maxsize of the project connection
pool equals 1, you may get the same session always.
Some cautions for sp_getApplock
Locks can be explicitly released with sp_releaseapplock. When an application calls sp_getapplock multiple times for the same lock resource, sp_releaseapplock must be called the same number of times to release the lock.
Due to the connection pool, the sessions may last long, that's what you need to take into account.
By the way, is there any reason that you have to use the sp_getApplock? What is the procedure doing that you cannot rely on SQL Servers build-in concurrency control mechanisms?
If you have any question, feel free to let me know.
Eric Zhang
TechNet Community Support

All EJBs with enable-call-by-reference=true

How can I set 'enable-call-by-reference' to 'true' to all my my EJBs?
I don't want to set this option for each one EJB.
Thanks. Mauro.

The Java EE specification requires that EJB components invoked through their remote
interfaces must use pass-by-value semantics, meaning that method parameters are
copied during the invocation. Changes made to a parameter in the bean method are
not reflected in the caller's version of the object. Copying method parameters is required
in the case of a true remote invocation, of course, because the parameters are serialized
by the underlying RMI infrastructure before being provided to the bean method. Pass-by-value
semantics are also required between components located in different enterprise applications in the
same Java virtual machine due to classloader constraints.
EJB components located in the same enterprise application archive (.ear) file are loaded by
the same classloader and have the option of using pass-by-reference semantics for all invocations,
eliminating the unnecessary copying of parameters passed during the invocation and improving
performance. Set the <enable-call-by-reference>parameter to true in the weblogic-ejb-jar.xml
descriptor file to enable this feature for each bean in your application. Local references always
use pass-by-reference semantics and are unaffected by the <enable-call-by-reference> setting.
The default value of <enable-call-by-reference> was true in WebLogic Server 7.0
but is false in WebLogic Server 8.1 and later to comply with Sun's Java EE
licensing policy changes that require all Java EE compatible servers to support the
specification with their out-of-the-box configuration.

When my iPhone 4S (with ios7) experiences a failed call while connected to my Bluetooth hands free in my car(screen locked) the failed call appears on the locked screen, as it should, then when I unlock the phone it automatically redials the failed call,

When my iPhone 4S (with ios7) experiences a failed call while connected to my Bluetooth hands free in my car(screen locked) the failed call appears on the locked screen, as it should, the problem arises whenever I unlock the phone, it automatically redials the last failed call, it doesn't do this with missed calls that are on the locked screen, if any. It is really annoying as sometimes the phone doesn't respond to attempts to end the call before it connects to the number. I then have to explain that it was my phone and not me, I look like an idiot, which I don't really need any extra help with!! Does anyone have any ideas? I don't want to stop missed call from showing in the locked screen but it might be associated with the failed calls and therefore be the only resolution

I have had the same issue which was driving me mad but think I have just found a way around it. In iOS 7 if you swipe up on the lock screen to access quick settings and go into timer then click the home button you get into the phone without calling the person back. Not a great 'fix' but hope it works for you. Come on Apple this isn't good enough, fix this bug otherwise you will lose your customers.

HFM EPMA application deployment aborted with error Object reference not set

HFM EPMA application deployment aborted with error Object reference not set to an instance of an object when trying to validate/deploy any HFM application in EPMA. This has started happending after we have deleted a Dimension in one of HFM applications. The deleted dimension is a shared dimension.
We are facing this issue in a distributed environment with version 11.1.2.1. This applications are built here newly.
Following is the error log entry
16] ERROR Object reference not set to an instance of an object.
at Hyperion.DimensionServer.CompareCriteria.<>c__DisplayClass5.<GetMemberClassProperties>b__4(Dimension dim)
at Hyperion.DimensionServer.Library.IterateDimensions(Action`1 action)
at Hyperion.DimensionServer.CompareCriteria.GetMemberClassProperties(ApplicationClass appClass, DimensionClass dimClass, MemberClass mbrClass)
at Hyperion.DimensionServer.CompareCriteria.GetCommonMemberClassProperties(RelationshipMember fromMember, RelationshipMember toMember, ApplicationClass fromAppClass, ApplicationClass toAppClass)
at Hyperion.DimensionServer.CompareMemberEvaluator.CompareProperties(RelationshipMember fromMember, RelationshipMember toMember, ApplicationClass fromAppClass, ApplicationClass toAppClass, List`1 propertyDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Compare(RelationshipMember sourceMember, Application sourceApp, Application targetApp, Boolean firstPass, Int32 level, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Compare(List`1 sourceTopMembers, List`1 targetTopMembers, Application sourceApp, Application targetApp, Boolean firstPass, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Execute(List`1 fromTopMembers, List`1 toTopMembers, Dimension fromDimension, Dimension toDimension, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareDimensionEvaluator.Execute(Dimension fromDimension, Dimension toDimension, ApplicationClass fromAppClass, ApplicationClass toAppClass)
at Hyperion.DimensionServer.CompareEngine.CompareDimensions(Dimension fromDimension, Dimension toDimension)
at Hyperion.DimensionServer.CompareEngine.StartCompare()
at Hyperion.DimensionServer.Validations.HFMApplicationValidation.CheckStaticDimension(Library snapShot, Dimension dim, Application oldApp, String[] skipProperties)
at Hyperion.DimensionServer.Validations.HFMApplicationValidation.CheckStaticDimensions(Application baselineApp)
at Hyperion.DimensionServer.Validations.ApplicationValidation.ValidateAgainstBaseline()
at Hyperion.DimensionServer.Validations.HFMApplicationValidation.InternalValidate()
at Hyperion.DimensionServer.Validations.ApplicationValidation.Validate()
at Hyperion.DimensionServer.Validations.ApplicationValidation.<ValidateAsync>b__0()System.NullReferenceException: Object reference not set to an instance of an object.
at Hyperion.DimensionServer.CompareCriteria.<>c__DisplayClass5.<GetMemberClassProperties>b__4(Dimension dim)
at Hyperion.DimensionServer.Library.IterateDimensions(Action`1 action)
at Hyperion.DimensionServer.CompareCriteria.GetMemberClassProperties(ApplicationClass appClass, DimensionClass dimClass, MemberClass mbrClass)
at Hyperion.DimensionServer.CompareCriteria.GetCommonMemberClassProperties(RelationshipMember fromMember, RelationshipMember toMember, ApplicationClass fromAppClass, ApplicationClass toAppClass)
at Hyperion.DimensionServer.CompareMemberEvaluator.CompareProperties(RelationshipMember fromMember, RelationshipMember toMember, ApplicationClass fromAppClass, ApplicationClass toAppClass, List`1 propertyDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Compare(RelationshipMember sourceMember, Application sourceApp, Application targetApp, Boolean firstPass, Int32 level, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Compare(List`1 sourceTopMembers, List`1 targetTopMembers, Application sourceApp, Application targetApp, Boolean firstPass, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareMemberEvaluator.Execute(List`1 fromTopMembers, List`1 toTopMembers, Dimension fromDimension, Dimension toDimension, Boolean continueCheckingAfterDifferences)
at Hyperion.DimensionServer.CompareDimensionEvalua
There was a bug in earlier releases for deleting dimensions with children, making the children orphans.
Heard from release notes that it has been fixed, but we are seeing this issue in 11.1.2.1 again.
Please help us out in resolving this error.

Hi,
I always ask this first, have you installed all the planning and epma patches as there have been many issues addressed in 9.3.1
Cheers
John
http://john-goodwin.blogspot.com/

Java programming language uses call by reference for objects?

Is Java programming language uses call by reference for objects?

Yes. You make calls to an object via itsreference.
No.Yes, you're referring to passing a reference into a
method in which case the value of the
reference is passed.I believe the OP is using the term "call by reference" to mean "pass by reference." The two are interchangable, AFAIK. So, while "making calls to an object via its reference" is correct, I don't believe it's germane to the question.

Application locking up at Call by Reference

Similar Messages

Maybe you are looking for