LabVIEW error -200324 handling
I am using a USB-6259 with LV2010, and have written an application to control a test stand. There are times when power to the stand is removed, and therefore also power to the DAQ board, causing error -200324. With LV running on a laptop with a battery, I keep the LV program running. When power is restored, the continue button in the error display window can be pressed, and the LV code begins executing again. My issue is that the stand is in the state at which power is lost, which places the test stand in an unsafe condition upon resuming. I need to have LV recognize the error code and place the test stand in a safe condition prior to power restoration/continuing code execution. Can the error be trapped (error cluster read) and acted upon, or is there another way to check the state of the DAQ device to perform the necessary actions? Thanks in advance!
I'm pretty sure on a USB-6259 you can set power-up states for the digital ports. Easiest way is using MAX and going to the attributes tab.
I would probably go for trapping this error and then polling the device by attempting to restart the task until it wakes back up and doesn't transmit the error.
Probably not possible in your case, but for test rigs that need to run unattended we use external watchdog circuits to make sure everything is safe. The watchdog circuit receives a low frequency digital pulse generated by the VI using a digital out on the DAQ. If the VI stops working or the power to the DAQ fails the watchdog drops all the power lines. In that way you can make sure the DAQ is in a safe state before restarting the watchdog signal and bringing the power back on in a situation like the one you describe. An external physical E-Stop button is always connected into the same circuit so an operator can also disable the rig in an emergency.
Not sure if this helps, but you never know.
Paul
Regards
Paul
CLD running LabVIEW 2012 32 & 64 bit on Windows 7 64 bit OS.
Similar Messages
-
General Labview Error Handler question discussion
Recently two functions were brought to my attention, the General Error Handler and the Simple Error handler.
And I cannot wrap my hand around these two features. While I have been using Labview I have always used the Labview error cluster. When would you use these two features? As I feel the cluster error is much help.
Maybe it is my defnition that I have confused:
The general error handler will display a dialogue box describing the error that will be passed and shuts down the code?
The simple error handler notifys the operator that an error has occured but it can be customized for adding functionality, it takes the error cluster input and determines if an error was generated. "If an error has been generated, the VI displays a dialog box with the error code, a brief description of the error, and the location of the error." How is this not the same as an error cluster?
If anyone has any simple code examples for this or knowledge I greatly appriciate it.
CalebJacobson wrote:
Psireaper9 wrote:
The simple error handler notifys the operator that an error has occured but it can be customized for adding functionality, it takes the error cluster input and determines if an error was generated. "If an error has been generated, the VI displays a dialog box with the error code, a brief description of the error, and the location of the error." How is this not the same as an error cluster?
You are correct that they give the same information. The difference is that if you want to use an error cluster you will need an indicator on your front panel. If you use the simple error handler you won't have to have an error cluster on your front panel but the user will be notified if an error does occur.
Think about all the programs you normally use (excel, chrome, etc.). As a user you expect that errors aren't happening, and if errors do occur then the application will usually just close out and you get an error dialog about the error.
I use the simple error handler with no user interaction to extract the error text. Is there an easier way of doing that? -
Watch the NI-Week 2009 Presentation: Updating the LabVIEW Error Handling Core
The resources for the "Updating the LabVIEW Error Handling Core" NI-Week 2009 Presentation are now online.
See them here: http://lavag.org/topic/10741-updating-the-labview-error-handling-core/
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.I have always gone the latter route when I needed it. I usually use an action engine to keep track of the error messages. Said action engine can be used to combine and suppress errors, as well. I have posted an example below (LabVIEw 7.1). In this case, the error propagation is occurring in a task handler which is processing multiple command/data pairs. The command is set at the beginning of the task and the error handler is sprinkled liberally throughout the task code. In this particular case, the desired behavior is to continue execution on error, but log the errors.
I prefer this type of method because it gives me complete control over the error propagation. It has the down side of requiring more code and effort, but I think it is worth it. I like functionality to be explicit on my block diagrams. It makes long-term maintenance much easier.
This account is no longer active. Contact ShadesOfGray for current posts and information.
Attachments:
ErrorPropagation.llb 65 KB -
Crystal Report error - The Handle is invalid;
I get the error 'The handle is Invalid' when I try to print a crystal report that is opened in the Report viewer.
I was wondering if anyone has encountered this is has a solution.
The report was created using Crystal Report 2008 for SAP B1.
Regards
AlbertAlbert,
You may check those old threads first:
Embarrasing issue
Re: 5 : - The handle is invalid
Landscape test connection failure: The handle is invalid.
Thanks,
Gordon -
Crystal Report: irregular error not handled by the application component
Hi all,
The error message u201Cirregular error not handled by the application componentu201D comes up when I run any of the Crystal Report in the SAP Business One.
But this error happens only in the client Machines, from the Server I can run the report normally.
Thanks and Regards,
Alberto FrançHi,
It seems installation and registration problem, have you tried to other client computers? Try to reinstall the Crystal Report in client.
Regards,
Clint -
Error message handling in BAPI...
Hi Guys,
I am working on documentation of a BAPI used SAP insurance module. Now I want to see all the error messages associated/ handled in that BAPI. How can I do that ? Is there a table in data dictionary where I can see error messages handled by a given Function module/ BAPI?
Any inputs will be highly appreciated.
Thanks.
Regards,
Tushar.Hi,
here´s one possible solution:
CALL FUNCTION 'MESSAGES_INITIALIZE'.
LOOP AT it_return_bapi.
CALL FUNCTION 'MESSAGE_STORE'
EXPORTING
arbgb = it_return_bapi-id
exception_if_not_active = ' '
msgty = it_return_bapi-type
msgv1 = it_return_bapi-message_v1
msgv2 = it_return_bapi-message_v2
msgv3 = it_return_bapi-message_v3
msgv4 = it_return_bapi-message_v4
txtnr = it_return_bapi-number
zeile = ' '
EXCEPTIONS
message_type_not_valid = 1
not_active = 2
OTHERS = 3.
ENDLOOP.
CALL FUNCTION 'MESSAGES_STOP'
EXCEPTIONS
a_message = 04
e_message = 03
i_message = 02
w_message = 01.
IF NOT sy-subrc IS INITIAL.
CALL FUNCTION 'MESSAGES_SHOW'
EXPORTING
i_use_grid = 'X'
i_amodal_window = i_amodal_window
EXCEPTIONS
inconsistent_range = 1
no_messages = 2
OTHERS = 3.
ENDIF.
ENDFUNCTION.
Best regards -
UCCX 8.0.2 - error while handling the request
Hi Guys,
My Customer have UCCX 8.0.2. He needed did change prompt and when He try to do upload the new script, appear the message: "error while handling the request". Any have idea who solve this problem?
Thanks,
WilsonI saw this before on 8.0.2, I had to delete the prompt/script/document and the upload it again (instead of overwriting it). I believe this was fixed in SU4.
Edit: this is the bug id - CSCtq23837 (unable to overwrite scripts) - resolved in 8.0(2) SU4
Brian
Please rate helpful posts -
Error: 'Database handles still open at environment close'
Hello,
I have read information about this error, but I cannot solve it.
I think I have closed all objects that I use, but the error appears.
When I remove next code, the error doesn't appear:
while (xmlValue != null) {
XmlDocument theDoc = xmlValue.asDocument();
String docName = theDoc.getName();
String docString = xmlValue.asString();
String message = "Document ";
message += theDoc.getName() + ":\n";
message += xmlValue.asString();
message += "===============================\n";
System.out.println(message);
xmlValue = results.next();
theDoc.delete();
The error:
Database handles still open at environment close
Open database handle: myContainer.dbxml/secondary_document_statistics_string
Open database handle: myContainer.dbxml/secondary_document_index_string
Open database handle: myContainer.dbxml/node_nodestorage
Open database handle: myContainer.dbxml/secondary_document
Open database handle: myContainer.dbxml/secondary_dictionary
Open database handle: myContainer.dbxml/primary_dictionary
Open database handle: myContainer.dbxml/secondary_sequence
Open database handle: myContainer.dbxml/secondary_configuration
Exception in thread "main" java.lang.IllegalArgumentException: Invalid argument
at com.sleepycat.db.internal.db_javaJNI.DbEnv_close0(Native Method)
at com.sleepycat.db.internal.DbEnv.close0(DbEnv.java:217)
at com.sleepycat.db.internal.DbEnv.close(DbEnv.java:77)
at com.sleepycat.db.Environment.close(Environment.java:39)
at berkeleydbxml.Test1.main(Test1.java:137)
Java Result: 1
The code:
public static void main(String[] args) {
Environment myEnv = null;
File envHome = new File("C:/extranet/tecnologias/BerkeleyDBXML/Java/BerkeleyDBXML/dbxml");
XmlManager myManager = null;
XmlContainer myContainer = null;
XmlQueryContext context = null;
try {
EnvironmentConfig envConf = new EnvironmentConfig();
envConf.setAllowCreate(true); // If the environment does not
// exits, create it.
envConf.setInitializeCache(true); // Turn on the shared memory
// region.
envConf.setInitializeLocking(true); // Turn on the locking subsystem.
envConf.setInitializeLogging(true); // Turn on the logging subsystem.
envConf.setTransactional(true); // Turn on the transactional
// subsystem.
myEnv = new Environment(envHome, envConf);
XmlManagerConfig managerConfig = new XmlManagerConfig();
myManager = new XmlManager(myEnv, managerConfig);
XmlContainerConfig containerConf = new XmlContainerConfig();
containerConf.setTransactional(true);
containerConf.setAllowCreate(true);
String containerName = "myContainer.dbxml";
myContainer = myManager.openContainer(containerName, containerConf);
// Get a query context
context = myManager.createQueryContext();
// Declares namespaces
// Default namespace
context.setNamespace("", "urn:oasis:names:specification:ubl:schema:xsd:Invoice-2");
context.setNamespace("cac", "urn:oasis:names:specification:ubl:schema:xsd:CommonAggregateComponents-2");
context.setNamespace("cbc", "urn:oasis:names:specification:ubl:schema:xsd:CommonBasicComponents-2");
context.setNamespace("ccts", "urn:un:unece:uncefact:documentation:2");
context.setNamespace("ext", "urn:oasis:names:specification:ubl:schema:xsd:CommonExtensionComponents-2");
context.setNamespace("qdt", "urn:oasis:names:specification:ubl:schema:xsd:QualifiedDatatypes-2");
context.setNamespace("udt", "urn:un:unece:uncefact:data:specification:UnqualifiedDataTypesSchemaModule:2");
// Declare the query string
String myQuery =
"collection('myContainer.dbxml')/Invoice";
// Prepare (compile) the query
XmlQueryExpression qe = myManager.prepare(myQuery, context);
// Run the query. Note that you can perform this query many times
// without suffering the overhead of re-creating the query expression.
// Notice that the only thing we are changing is the variable value,
// which allows us to control exactly what gets returned for the
// query.
XmlResults results = qe.execute(context);
// Display the result set
XmlValue xmlValue = results.next();
while (xmlValue != null) {
XmlDocument theDoc = xmlValue.asDocument();
String docName = theDoc.getName();
String docString = xmlValue.asString();
String message = "Document ";
message += theDoc.getName() + ":\n";
message += xmlValue.asString();
message += "===============================\n";
System.out.println(message);
xmlValue = results.next();
theDoc.delete();
xmlValue.delete(); <-- the error happens here
qe.delete();
results.delete();
} catch (DatabaseException de) {
// Exception handling goes here
int i = 1;
} catch (FileNotFoundException fnfe) {
// Exception handling goes here
int i=1;
} catch (Exception e) {
// Exception handling goes here
int i = 2;
} finally {
try {
if (myContainer != null) {
myContainer.close();
if (myManager != null) {
myManager.close();
if (myEnv != null) {
myEnv.close();
} catch (DatabaseException de) {
// Exception handling goes here
If I remove the xmlValue.delete() sentence, the error appears in myEnv.close().
I use berkeley 2.3.10 version, Windows XP.
Thanks.I am having a similar problem. My method:
protected void searchQuestions(String keyword) throws LibraryException {
XmlQueryContext xqc = null;
XmlResults xr = null;
XmlQueryExpression xqe = null;
String[] qids = null;
String query = "collection()/*[contains(question, '" + keyword + "')]";
try {
conQuestions = man.openContainer(QUESTION_CONTAINER);
xqc = man.createQueryContext();
xqc.setDefaultCollection(QUESTION_CONTAINER);
xqe = man.prepare(query, xqc);
xr = xqe.execute(xqc);
conQuestions.delete();
xqc.delete();
xqe.delete();
XmlValue val = xr.next();
while (val != null) {
String name = val.asDocument().getName();
System.out.println(name);
val = xr.next();
val.delete(); <-- PROBLEM HERE
xr.delete();
} catch (XmlException xe) {
throw new LibraryException("Unable to search for questions. " + xe.getMessage());
If I leave the val.delete() line then I get a java.lang.NullPointerException but if I remove it then I get an error stating 'Database handles still open at environment close'. I run a clean up method after the previous method as follows:
protected void close() {
if(conQuizes != null)
conQuizes.delete();
if(conQuestions != null)
conQuestions.delete();
if(conUsers != null)
conUsers.delete();
if(man != null)
man.delete();
I have many other methods that interact with containers perfectly but this is the only one where I use the XmlValue class. I tried the solution that worked for brais.mendez with no luck. Any advise or ideas would be much appreciated.
Thanks,
Matt -
[BUG] Problem with Error message handling in JDeveloper 11.2.1.0
Hello!
I'm Daniel from Brazil.
I have been facing a problem recently to which I see no solution. I need to use a specific component called 'Panel Label and Message' in order to nest three other components which need to be grouped together to work properly (an input text box, a LOV calling 'search button', which searchs and populates the input box, and an output text box which displays text depending on the input field). This works fine!!
The problem comes when I try to place an Access Key that should focus on the input text box part of the group component. In order to do that, I put it on the 'Panel Label and Message' component, and set the 'for' property to the input text box. This too works fine, as when I access it the component redirect the focus to the right place.
Problem is, when the user decides to this specific field (which is required) blank, JDev has problems handling the actual name of the component, and just calls it 'Component', as the screenshots below show. Apparently, for the other error messages that are handled by myself or generated by other means, it deals with the component's actual name just fine. Is there any way around this? Thanks!
'Panel Label and Message' component properties. it9 is the id of the 'Input Text' field component. Access Key set to F.
http://img.photobucket.com/albums/v82/myfireburnsblack/PropertiesErrorBug.png
Error message I get (it's in portuguese). Field has been left blank, and JDev says I have to put something in, but refers to the field as 'Component'. Any other error is handled correctly, as far as I've tested.
http://img.photobucket.com/albums/v82/myfireburnsblack/jdevError.pngHi Daniel,
You're not the only one who has seen this: {message:id=9938606}
As mentioned in that other thread - I had tested similar use cases and it works for me.
Do you have access to https://support.oracle.com to file an SR?
John -
Amfphp - flex remote object error event handler
I'm using amfphp and I want it to return an error that the flex remote object error event handler will pick up. At the moment I can get only the result handler to do anything in flex.
Hi,
Try throwing an exception in the remote method. For example,
function inverse($x) {
if (!$x) {
throw new Exception('Division by zero.');
else return 1/$x; -
Labview error GPIB controller not adressed correctly
I get this Labview error: GPIB controller not adressed correctly (LV5.1, win NT4) when i try to send data to a HP4275A LCR meter. How ever it works on an older system running with LabView 5.0 (also NT)!!!
How can I get rid of this problem????Hi Diego, thanks for the hints!
I tried to configure (GPIB) everything standard.
when I try a 488 command initialze, I get the controller conflict, when i don't do this I get atime out problem either by 488 write-command or by 488.2 send-command.
the differences between the systems where it works and where not are:
working: Win 95, LV 5.0, GPIB-card/TNT (plug & play)
not-working: WinNT, LV 5.1, GPIB-card/PCI
i tried to set baord config to the same parameters...
on the faulti system however I see the instrument with the MAX and I can send commands, without problems !!!!
Also the driver you posted does not work (but the NI-communicate program ;-)
i have no clue what else to do!
btw. how do I copy the spy output when running the program? I may provide
this to find errors.
Since MAX indicates the board is all right I guess it is not necessary to reinstall the boarddrivers?! -
LabVIEW error code3: Could not load front panel.
Hi
I am getting second time the "LabVIEW error code3: Could not load front panel." when working with the development environment of LabVIEW 2009 SP1.
It is really annoying as I loose time as I have to revert to saved previously code.
Does anybody know where it may be coming from and how to avoid it?
Thanks
Pawel
Solved!
Go to Solution.Pawel,
the panel has an origin which you can see in your VI:
Every element will be placed in a position in regard to this origin:
The position has a limit in regard to the bound. I am not sure about the value, but it should be around -35k...35k (or the double of it)....
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it. -
16 bit MS-DOS Subsystem
C:\WINDOWS\system32\msiexec.ex NTVDM has encountered a System Error The handle is invalid.
Choose 'Close' to terminate tha application.
Close IgnoreOkay. It seems unlikely to be the class of similar problems caused by various Symantec programs blocking installs.
It's a bit of a mystery in the first place why the 16 bit DOS subsystem is running in this context. (The iTunes installer is 32-bit on XP machines.)
Just in case it's a damaged NTVDM, perhaps try an sfc /scannow:
http://www.updatexp.com/scannow-sfc.html
Does that clear up the error? -
Labview slider event handling problems - revisited
This topic asked a question that was very close to a problem I am having:
Labview slider event handling problems
That is, how do I, using an event structure and/or other means, only read out the value of a slider control after the value change is finalized?
The extra constraint I'd like to place on this, which I believe will invalidate the answer given in the thread above, is that my slider control also has a digital display which can also be used to change the value without ever using the mouse. I cannot look for a value change followed by a mouse-up event if the mouse was not used to change the value.
Any ideas how this might be accomplished? FWIW, I am using LabVIEW 7.0Each and every incremental value-change event generated by the movement of the slider is still detected and queued up for use by the event structure and the event structure loop wades through them all before it's done.
I have come up the attached "fix" (LV v7.0) for this problem. While it is not as clean a solution as I had hoped it would be, it's the best I can manage given what LabVIEW offers me to work with and it does work in the situation where I need to use it.
Now, within the Finalize Slider Events subVI, I'm keeping track of the most-recent values seen by the subVI, checking to see if they have changed, and reporting out that fact. That gives me a Changed/Not-Changed bit within the event case that I can use to control what code then gets executed. If the event case is just playing catch-up to the real value of the control, I can now see that fact and ignore it.
In this version I've also dumped the variant output and limited the VI to using DBL values. I decided it added complication to something that was too complicated already and I wanted the output terminals for other purposes anyway (reporting of the correct "OldVal" of the control).Message Edited by Warren Massey on 04-28-2005 03:56 AM
Attachments:
slider_events[5].llb 77 KB -
All of the system data collection sets have been running for 6+ months without any issues, couple of weeks ago the 'Server Activity' collection set failed to restart after a planned maintenance server reboot.
When attempting to manually start the collection set it indicates "success", but after refreshing the collection set it showing as stopped. Viewing the logs for the Data Collection (Server Activity) I am getting the message:
Waiting on a kernel object(s) failed. Inner Error ------------------>
The handle is invalid.
After some research into this really unhelpful message I came across one posting where this error has been found to occur in SP1. We are running SP2 which include the fix so this shouldn't be the problem (ref http://connect.microsoft.com/SQLServer/feedback/details/585210/sql-server-2008-data-collection-execmasterpackage-timeout).
To see more detail on the root cause of the error I enabled the additional tracing for data collection (http://blogs.msdn.com/b/sqlagent/archive/2011/07/13/enabling-additional-tracing-for-data-collector.aspx). This provided an exception stack which indicated
that the issue was thrown to what looks like an existing file, referring to a location (e:\) which doesn't exist in our system.
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: wmain _IN
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Command line: dcexec -c -s 2 -i "S160OLTP\OLTP" -m 0 -e 0x09C1635DD4C4C6478A145D679AFE718F_1_STOP
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Application::Init _IN
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Console code page (m_codePage): 437
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Application::ParseCommandLine _IN
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Application::ParseCommandLine _OUT:00000000
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Application::Init _OUT:00000000
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Application::Main _IN
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Started continuous mode collection on thread 12036
DCEXEC!26d0!2f04!2012/11/28!11:17:25:: StartCachedCollectionWrapper _IN
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Waiting for collection to exit or stop event to be signaled
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: StartCollection _IN
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: StartCollection(iSetId = 2, iCollectionMode = 0, pwszInstanceName = S160OLTP\OLTP)
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CDataCollectorController::ExecuteCollectionSet _IN
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: SQL Instance Name: OLTP
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CDataCollectorController::TryExecuteCollectionSetOnce _IN
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CDataCollectorController::Initialize _IN
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CDataCollectorController::Initialize _OUT:00000000
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CDataCollectorController::PopulateCollectorPackageParameters _IN
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CacheWindow=1, CacheDirectory='I:\MSSQL10.OLTP\MSSQL\dccache'
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CDataCollectorController::PopulateCollectorPackageParameters _OUT:00000000
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CDataCollectorController::PopulateSetPackageParameters _IN
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CollectionSetUID='{49268954-4FD4-4EB6-AA04-CD59D9BB5714}', ExecutionMode=0, IsSystem=-1, LoggingLevel=0, DaysUntilExpiration=14, ExitEventName=''
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CDataCollectorController::PopulateSetPackageParameters _OUT:00000000
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CreateControlEvents _IN
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: e ERROR: Win32 Error: GetLastError=183, retCode=0x4, function CDataCollectorController::CreateControlEvents, line 470, file e:\sql10_katmai_t\sql\mpu\shared\dc\runtime\controller\src\datacollectorcontroller.cpp
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: e ERROR: Failed to create kernel event for collection set: {49268954-4FD4-4EB6-AA04-CD59D9BB5714}. Inner Error ------------------>
Cannot create a file when that file already exists.
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CreateControlEvents _OUT:00000000
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: e ERROR: DC_FAILED: function CDataCollectorController::TryExecuteCollectionSetOnce, line 350, file e:\sql10_katmai_t\sql\mpu\shared\dc\runtime\controller\src\datacollectorcontroller.cpp
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CDataCollectorController::TryExecuteCollectionSetOnce _OUT:0x000004
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: Collection set execution failed, retrying in 5 seconds...
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: Waiting for exit event or retry timer failed.
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: e ERROR: Win32 Error: GetLastError=6, retCode=0x4, function CDataCollectorController::ExecuteCollectionSet, line 278, file e:\sql10_katmai_t\sql\mpu\shared\dc\runtime\controller\src\datacollectorcontroller.cpp
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: e ERROR: Waiting on a kernel object(s) failed. Inner Error ------------------>
The handle is invalid.
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: CDataCollectorController::ExecuteCollectionSet _OUT:0x000004
DataCollectorController!26d0!2f04!2012/11/28!11:17:25:: StartCollection _OUT:00000000
DCEXEC!26d0!2f04!2012/11/28!11:17:25:: StartCachedCollectionWrapper _OUT:0x000004
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Collection thread returned (00000001)
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Waiting for collection thread to exit
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Collection thread signaled
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: Application::Main _OUT
DCEXEC!26d0!1b88!2012/11/28!11:17:25:: wmain _OUT:0x000004
I am now stumped as I haven't found anyone else experiencing this issue.
Any ideas, please help??Thanks for the pointer Eileen, problem solved.
Can't believe I missed it, but after reading the last section on system hangs it occurred to me that I hadn't checked that all dcexec.exe processes were killed when I disable the data collection service.
For anyone else experiencing this issue I identified the dcexec.exe processes using the following in cmd line:
TASKLIST /SVC /FI "IMAGENAME EQ DCEXEC.EXE"
On the default setup of the data collection there should be two dcexec.exe processes constantly running, one for "Server Activity" and another for "Query Statistics". On our server there were five running with the data collection disabled.
After killing all of the processes and restarting the data collection problem solved!!
Still need to understand why the processes didn't shut down cleanly when the server was restarted, but at least I know where to look now.
Maybe you are looking for
-
Don't they give you any manuals for your laptop anymore. I just bought a Satellite M305-S4910 and there was no manual with it and searched the web site thinking I could download one with no luck. Can someone help me. Solved! Go to Solution.
-
Procedure for delta intialization of datasource 2LIS_11_VAHDR
Hello experts, I need some help with the delta intialization for the datasrouces 2LIS_11_VAHDR and 2LIS_11_VAITM. I'm working on SAP R/3 4.7C and extracting data to BI 3.5. I'll be grateful if someone could send some links where I can find the step b
-
Hi all - I have a 30 fps clip that I have sent to motion and I want to start the speed off at 50% and then ease it up very quickly to 100%. I know how to key frame this in FCP, but I've always found it sort of rudimentary. Is there a behavior in Moti
-
REFRESH STATISTICS ON THE INFOCUBE
Hi , Under the manage tab of the infocube i have clicked the tab refresh statistics.I clicked on the log and it showed that the statistics were successfully compiled on the infocube. Is this the only way of confirming that the refresh statistics we
-
Sometimes FF has crashed and lost its "memory" of the tabs I had opened. I want to have a backup in case that happens, so I know what tabs I had up and can restore them.