Error 1097 running a DLL
Hello Friends
I am using CLFn to Implement FMI functionality in Labview.
For starters the program is pretty simple.
It has a for loop under which the step integration of the states takes place.
Outside the loop are the CLFN blocks that Instantiate, Initialise and set time of simulation for the model.
Using Highlight execution I found out that there were errors from the CLFn that was responsible for the SET TIME function.
I am attaching the complete List of required files for you to get some idea.
regards
raghu
Attachments:
Untitled 4.vi 12 KB
Well, since those functions have no parameters there is really very little you can do wrong as far as the LabVIEW CLN is concerned. One is the calling convention. You don't specify that in the C code explicitedly so it will depend what you have set in your project file. Visual C uses by default cdecl. Make sure you set the same calling convention in the CLN as you have selected in your C compiler project settings (thus C by default).
If you still get an error, then you have a bug in your C code. It is anyhow a good idea to test a DLL first with some C routines before starting to integrate it in LabVIEW through CLNs. As a good C programmer you know, that a bad pointer derereferencing, improper memory allocation or what else is made very easily and needs to be debugged first.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions
Similar Messages
-
I encounter 2 errors in the controller when running FSCT.
- "There were errors during running WordFileClose.dll scenario"
- "There were errors during running WordFileClose.dll scenario"
Does anyone has any ideas for this errors?
I am using the following server to run the FSCT:
- AD Server: Windows 2008 R2 SP1 x64
- FSCT Controller: Windows 2008 R2 SP1 x64
- Client: Windows 7 x64
- File Server: Non-Windows Server (EMC Isilon)
And the commands are as follows:
> fsct prepare dc /users 10 /clients testing /password password
> fsct prepare controller
> fsct prepare client /server ofscluster /password password /users 10 /domain abc.local /server_ip 192.168.2.16
> fsct prepare server /clients testing /password password /users 10 /domain abc.local /volumes \\ofscluster\fsroot1 /workload HomeFolders /create_only_fileset
> fsct run client /controller fsctcon /server ofscluster /password password /domain abc.local
fsct run controller /server ofscluster /password password /volumes \\ofscluster\fsroot1 /clients testing /min_users 2 /max_users 10 /step 2 /duration 360 /workload HomeFoldersDear all,
The errors were:
<Error>1264 DeviceIoControl 1{WINERR}</Error>
<Error>Error executing scenario: WordFileOpen.dll</Error>
<Error>943 DeviceIoControl 50{WINERR}</Error>
<Error>Error executing scenario: WordFileClose.dll</Error>
Do you have any idea about what the errors mean?
Thanks,
Rayson -
I'm using more than 20 functions from a .dll code to Labview and have in some of then the 1097 error.
Error 1097 occurred at Call Library Function Node
Possible reason(s):
LabVIEW: An exception occurred within the external code called by a Call Library Function Node. The exception might have corrupted the LabVIEW memory. Save any work to a new location and restart LabVIEW.
I have read a lot about this error and I still didn't find a solution.
Thinking that could be a problem on the configuration of the VI, I imported it again and this solved the problem in the first VI. I did the same with the second one with an error but this time didn't solve.
The weird is that this VI with the error (intRun):
_API void intRun_ ( int* run_ , int* devList_ ,int* numDev_, char* retval )
it is exactly the same as another (anaRun) and this I don't have the error:
_API void anaRun_ ( int* run_ , int* devList_ ,int* numDev_, char* retval )
Inside the C code they look like the same (but each function will run a different device) and the configuration in Labview is also the same.
Is that possible that I have any problem with my device? Or could be really a problem with the .dll or with the VI?
I read something about wrappers but really I don't understand why I have the error with one VI and don't have with the other (running together) and how (or if) the wrapper could solve my problem.
Please give me any idea what I could try.
For example, I tried to disconect the input numDev (that is a constant, always 1) and then I don't have the error. Why?
Best Regards,
ThaisThank you for reply.
I'm using LV09.
Actually I figured out that before this VI that I have the error the device is not working as should be .
When running the program step by step I realized that what I was expecting to happen (locking ports before initialization) didn't happen.
So it is probably a bad configuration of the other VIs that I have (there is no Error but returns me an Bad Argument in the return_output);
I will try to solve it and then I tell here if it was really that.
Thak you all.
Thais -
Error 1097 after calling dll function which allocates memory inside
Hello!
When a call one my functions in my dll from LabView, i get an error 1097. My function takes a few arguments and then allocates some memory for measurement.
It's not returning any pointers to that memory area, it is just allocates that memory for itself. I don't know what could be the problem, probably i am missing something.
Could you help please?
Best regards,
Tamas
Solved!
Go to Solution.Are you sure that the allocate function is the problem?
Error 1097 simply means something inside the external code wrote into memory locations that it was not meant to write. That is usually because of output buffer parameters that are not allocated (large enough) in LabVIEW when passed to the external code fucntion, so the function assuming it received a buffer of a certain size happily writes into that buffer but overwriting other information it should not have.
But that is by far not the only possibility to cause this error. A simple bug in the external code can cause the same problem when a pointer goes astray or such. The fact that you used that library elsewhere already without seeing any problem is unfortunately no guarantee that the function is not buggy. The LabVIEW exeception handling around the Call Library Node has gotten rather picky and can detect violations that do not have to cause visible problems at all. But the violations it detects are real violations so just silencing them is not a good idea, as they could cause all kinds of problems including overwriting vital data structures in your program that either cause a crash later on or simply wrong results in other parts of your program. Especially the last one is a total bummer to debug.
Without seeing much more of your code it is basically impossible to point out where the problem could lie. The particular Allocate function doesn't look like there is much that could be done wrong, but I would assume that you call several other functions too somewhere, which could cause the problem. If you can absolutely positively say that you never ever call any library function with a to short (or unallocated) buffer parameter, then you will have to take it up with the manufacturer of your lib, as it would seem very likely that there is some problem in there.
Also you pass a handle to the library function but your Allocate function does not have this as a parameter! Where does this handle come from? Are you sure you have allocated and prepared it properly before calling this function? A handle is quite often a pointer, although usually a so called opaque pointer meaning the user of the library does not and should not know anything about the structure this pointer points to. It is only known internal to the library.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
Hi,
I am trying to read Data from a frame grabber card in my PCIe slot. When I call the "Initialize" function from the .dll I got with the card I always get the error 1097. 1097 means that the function called threw an error. When I run the program that came with the frame grabber, the frame grabber still works.
If I simply omit the "initialize" function call and continue with the function, that would be called after the "Initialize" function, LabVIEW crashes(Program shuts down without any warning).
I also got a LabVIEW program that uses the dll which was supposed to work. But here I get the same error.
Do you have any idea what normally causes this behaviour and how I can solve this Problem?
Solved!
Go to Solution.jak888 wrote:
The thing is:
I don't have many options left to configure e.g.: there's one function called void initialize (uint_16t nDevNo) so I call it configuring it accordingly. The only thing I could change is the calling convention. When I set it to C I got the 1097 error. When I set it to stdcall I think it destroyed the dll. I had to replace it to make the VI start again.
When I looked at the dll before I baught the grabber card, I paid attention if there were any "funny" variables, like unions, structs or Arrays of pointer to union of struct, because I had Problems with stuff like that before. The dll is really simple basically, so I don't quite get why it shouldn't work. As you said: the reason it sometimes works and sometimes not is because it never really works...
Today I am going to send back the frame grabber and order another one that's supposed to work with DirectShow... Hopefully that turns out better.
Well a frame grabber surely has more complex functions than "void initialize(unsigned short)". How would you get otherwise the grabbed image in LabVIEW. If this function alone already bombs (sorry for the old Mac reference), well then this DLL surely is worthless. It could be that you need to pass a valid device number of course, but such a simple function that attempts to corrupt memory when passed an invalid parameter is simply rubbish.
Usually the problem starts with other functions. And it's not only the problem with the complicated data types. A simple byte array can cause that error too. Lets assume you have instructed the frame grabber to return an image of 1024 * 800 pixels in RGB 8 bit format. When you call the grab function, it will want to write the image data into a memory buffer. And someone needs to provide that buffer. And LabVIEW not having mind reading capailities can not do that for you. So you need to know how the function will try to store the image data in the buffer. Each pixel would require at least 3 bytes. Maybe 4 if they store it in RGBx format, since that is easier to align in memory. Then the grabber may also add a border around the image. This could be anything from 0 to several pixels on each side. And last but not least it may add a header with image information before the image pixels.
So you get x + (1024 + y) * (800 + y) * 3 or 4 bytes. This buffer needs to be allocated by you on the diagram and passed to the DLL function.If you happen to not allocate that buffer or make it a few bytes to small the DLL function will attempt to write into memory that has not been allocated for that purpose. It could not be allocated at all for the current process in which case the CPU will raise an exception, and LabVIEW will report the 1097 errror or it could be allocated for something else in LabVIEW and sooner or later LabVIEW trips over that corrupted memory and does something weird or crashes, causing itself an exception that could cause the 1097 error. Sometimes the error only makes itself apparent when you close LabVIEW and it tries to properly deallocate all its memory blocks, stumbling eventually over some corrupted memory pointer your DLL has caused.
A frame grabber may support different image formats so your grab function would also need to be flexible enough to account for that too.This all is why writing a frame grabber interface for LabVIEW (or any other programming language) is usually a much sought something but seldom gets done by anyone in a way that really works.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
I wish to convert my Matlab files into .dll's so that I can use them in LabVIEW. I am using 'mcc' and 'mbuild' of Matlab to convert my .m files into .c and .dll.
When I try to run the .dll's in LabVIEW, I get an error message in a modal window stating some required .dll or procedure is not found.
How should I resolve this issue. Should I add any other Matlab .dll's in course of making my .dll?
Please help in solving this issue... Thankyou very much.KJV wrote in message news:<[email protected]>...
> When I run the matlab generated dll, it is stating 'matllb.dll not
> found'. Is it that I should set the path for matlab\bin to include
> all the dll's before I compile? When I make dll from C, it works fine
> in LabVIEW. The problem is from .m to .dll. The problem also arises
> when I convert my .m to .exe. The same error of 'matllb.dll not
> found' comes over. Should I change my matlab compiler options or
> something else? Please help me?
I have the same question,I don't know how to use the matlab DLL file in labview,
I hope someone can descripe the procedure in detail. -
I am running Windows 7 64Bit system and everything was working normal. However, I am now getting an error message stating objc.dll is missing. I've re-installed Itunes but to no avail. How can I get this error message corrected?
See this User Tip by turingtest2
https://discussions.apple.com/docs/DOC-6562 -
Error Code 1097 Coming in DLL Calling
Hi,
I am getting error code 1097 in DLL calling function. Please find the DLL calling function details for more information.
Function : GetControllerListTest(controller *ptrControllertest,char *max_controller);
Controllertest parameter details:
define NO_OF_CONTROLLER 100
#ifndef CONTROLLER_STRUCT
typedef struct
CString name;
char status;
CString blocked_by;
char group;
}controller;
Controllertest parameter data type is structure. In LabVIEW, I have configured parameter as a cluster.
name : String control
status : U8 Integer control
blocked_by : String control
group : U8 Integer control
Could you please confirm it, did I configured the datatype in correct way?
I am getting empty array output and Error Code from the DLL 1097. Can you please tell me where I am missing?
Thanks
Sivaramkumar.V
Solved!
Go to Solution.Call Library Node problems without the VI in question attached AND the complete C prototype of the function provided, AND preferably some documentation about the C function in question can be not diagnosed. These informations are paramount to get the Call Library Node configured properly since there is no way a calling application can retrieve the necessary information from the DLL itself. The DLL interface was never intended to be a self configuring interface and it was designed with the understanding, that the user of such an interface is a fully knowledgeable C programmer knowing both, how to read a header file definition as well as various details about memory buffer handling.
So show us your VI and the C header file, and we can start to help you. Otherwise all we can do is guessing in the way you have done with changing the calling convention randomly. You can of course try to shoot in the shooting range with a blindfold on, but the chances that you not only do not hit the target, but injure some other person instead is very high.
The only reason that the suggestion from Fragger Fox has any merits is the fact that LabVIEW used to have some heuristics that changed the Call Library Node automatically from C calling convention (the LabVIEW default) to Windows calling convention, if it recognized a certain pattern in the exported function name. This heuristic was removed in LabVIEW 2009 because it did prevent the Call Library Node to be able to call functions that were using C calling convention but happened to match the heuristic pattern. So changing a Windows calling convention to C calling convention when the code has "seemed" to work before is NEVER a solution.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
Am getting error message missing MSVCR80.dll and itunes will not run
am getting error message missing MSVCR80.dll itunes will not run
Solving the iTunes Installation Problems in Windows
1. Apple has posted their solution here: iTunes 11.1.4 for Windows- Unable to install or open - MSVCR80 issue.
2. If the Apple article does not fully resolve the problem for you, then try Troubleshooting issues with iTunes for Windows updates - MSVCR80. -
Error 1097 - function works in C++ application, but not in LabView
Good afternoon,
I have a C++ OpenCV application that I am trying to port to LabView for a co-worker. The application is fully functional when it's compiled standalone as an .exe. When called from LabView it reports error 1097.
However, this error is not being caused by not allocating momeory space or the way I am calling the DLL, because I can successfully run the DLL from LabView if I omit one function "findContours(..)" from being called inside my rotuine. Meaning that without this function I can send and receive an Image to my DLL and display it in LabView without a problem. This function is not being called directly from LabView either, it's called inside the main function that is being called by LabView.
That being said, the function allocates memory on its own for it's internal calculation purposes, I do not know what they are, but I know it works perfectly well in a standalone C++ application.
My DLL application consistenly uses 180Mb of memory without any leaks
My Question is:
Is it possible that LabView or windows may be preventing the DLL from allocating enough memory (I have 12Gb total)?
Is it possible to run the DLL as a separate application or in a different configuration that would prevent error 1097 from occuring?
How could LabView possibly be restricting the DLL?
Thanks,error 1097 means that the function somewhere and somehow overwrote memory areas that LabVIEW monitors as its own during the call. This could be memory buffer function parameters that are unallocated or to small or stack variables or some other memory areas LabVIEW puts in place around the DLL call when the highest debugging level is selected for the Call Library Node. But lowering the debugging level is not the solution as the function certainly does something that it should not do.
What that could be is impossible to say without analyzing the actual C source code of the function and possibly all the other functions involved in this as well as all the Call Library Nodes. It could even be that its something that is not even directly evident from the C source code but an effect of some (falsely invoked) optimization from the used C compiler.
I assume that you have actually a self written wrapper DLL here and that is where I would focus on in my search. It is quite unlikely that the OpenCV source code itself would still contain such errors after that much of time.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
Hi,
I am having a problem when deploying a model from Veristand (Windows) to a PXI equipment.
Let's start from the beggining: I have written a simulink model and compiled it for Veristand 2014 target. This generates a DLL, that I load it in Veristand at my Windows PC. From Veristand (Windows) I am able to run the model and the results are the same as Simulink. Now I want to run the model in the PXI (PXI-8176 with Phar Lap ETS 13.1). When I try to deploy the model to the PXI target, I've got the following error:
Start Date: 05/05/2015 11:16
Loading System Definition file: C:\Users\Public\Documents\National Instruments\NI VeriStand 2014\Projects\DC_Motor\DC_Motor_Ecosim\DC_Motor_Ecosim.nivssdf
Initializing TCP subsystem...
Starting TCP Loops...
Connection established with target Controller.
Preparing to synchronize with targets...
Querying the active System Definition file from the targets...
Stopping TCP loops.
Waiting for TCP loops to shut down...
TCP loops shut down successfully.
Unloading System Definition file...
Connection with target Controller has been lost.
Start Date: 05/05/2015 11:16
Loading System Definition file: C:\Users\Public\Documents\National Instruments\NI VeriStand 2014\Projects\DC_Motor\DC_Motor_Ecosim\DC_Motor_Ecosim.nivssdf
Preparing to deploy the System Definition to the targets...
Compiling the System Definition file...
Initializing TCP subsystem...
Starting TCP Loops...
Connection established with target Controller.
Sending reset command to all targets...
Preparing to deploy files to the targets...
Starting download for target Controller...
Opening FTP session to IP 169.254.104.111...
Processing Action on Deploy VIs...
Gathering target dependency files...
Downloading DC_Motor_Ecosim.nivssdf [71 kB] (file 1 of 4)
Downloading DC_Motor_Ecosim_Controller.nivsdat [6 kB] (file 2 of 4)
Downloading CalibrationData.nivscal [0 kB] (file 3 of 4)
Downloading DC_Motor_Ecosim_Controller.nivsparam [0 kB] (file 4 of 4)
Closing FTP session...
Files successfully deployed to the targets.
Starting deployment group 1...
The VeriStand Gateway encountered an error while deploying the System Definition file.
Details:
Error 1097 occurred at Project Window.lvlibroject Window.vi >> Project Window.lvlib:Command Loop.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi
Possible reason(s):
LabVIEW: An exception occurred within the external code called by a Call Library Function Node. The exception might have corrupted the LabVIEW memory. Save any work to a new location and restart LabVIEW.
=========================
NI VeriStand: Call Library Function Node in SIT Model API.lvlib:Load Model DLL.vi->SIT Model API.lvlib:Initialize Model.vi->Model Execution.lvlib:Initialize Model Loop Data.vi->NI VeriStand Engine.lvlib:VeriStand Engine State Machine.vi->NI VeriStand Engine.lvlib:VeriStand Engine.vi->NI VeriStand Engine.lvlib:VeriStand Engine Wrapper (RT).vi
Sending reset command to all targets...
After this, I cannot connect to the PXI and I have to reset it.
Any idea?
Thank you,
Jesús M. ZamarreñoNothing to see in this VI and DLL. For one a DLL is just a compiled code so there is very little to see from the DLL alone. Also a DLL does not contain any other information as to how it is supposed to be called. The implementation of the driver is terrible with all the calls in one single VI and half a dozen booleans to select which one of them to call. It deserves maybe a 6 out of 10 for functionality, a 1 for style and a 2 for cleanliness.
Without the API documentation of that driver DLL, there is absolutely nothing possible to say about the correctness of the CLN configurations. As simple as the functions look, there is still a chance that this configuration got wrong somewhere. Another a least as likely cause is that the DLL itself is poorly written too. If the LabVIEW implementation is any hint for the quality of the DLL driver implementation, then I guess it would be simpler to throw it all away and reimplement the driver purely in LabVIEW.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions -
How to rectify Error 1097 in labview?
I am using call library function for calling a dll.when it is running it is showing an error 1097. "An exception occurred within the external code called by a Call Library Function Node. The exception may have corrupted LabVIEW's memory".How this error can be solved?
Please Mark the solution as accepted if your problem is solved and donate kudoes
Solved!
Go to Solution.check the following link, may give you some pointers:
http://forums.ni.com/t5/LabVIEW/Error-Code-1097-Coming-in-DLL-Calling/m-p/1847055
i used the search box at the top right of the ni website and entered 1097
hope it helps
Please remember to accept any solutions and give kudos, Thanks
LV 8.6.1, LV2010,LV2011SP1, FPGA, Win7 -
Hello!
I'm trying to run lv_WriteRealtimeDacData.vi the program is quite easy
Spoiler (Highlight to read)
But when I'm running it there's an error 1097 message, I'm triying to configure call library fuctions and looks like the problem is in .dll file (The function name specified for this node cannot be found in the library. Right-click the Call Library Function node and select Configure, then choose the correct function name.) The right file is in the system folder, and I choose the right path for it, any ideas what's the key for this problem? I'm actually quite new to labview, please be patient)There are lot of discussions regarding this error code and most of the problems are solved. Search here and post if you still find problems.
Mathan -
"Couldn't load library 'C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll'"
Hi!
As you can see from here :
http://www.fabiocavallo.it/sap/maxdb.jpg
MaxDB seems to work fine, but after starting application server i have got an error :
SAPGUI Logon Error Message:
http://www.fabiocavallo.it/sap/sapguilog.jpg
...here comes dev_w0 :
trc file: "dev_w0", trc level: 1, release: "700"
ACTIVE TRACE LEVEL 1
ACTIVE TRACE COMPONENTS all, MJ
B
B Thu May 22 19:58:50 2008
B create_con (con_name=R/3)
B Loading DB library 'C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll' ...
M *** ERROR => DlLoadLib: LoadLibrary(C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll) Error 126 http://dlnt.c 237
M Error 126 = "Impossibile trovare il modulo specificato."
B *** ERROR => Couldn't load library 'C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll'
http://dbcon.c 4726
M sysno 00
M sid NSP
M systemid 560 (PC with Windows NT)
M relno 7000
M patchlevel 0
M patchno 95
M intno 20050900
M make: multithreaded, ASCII, optimized
M pid 3376
M
M kernel runs with dp version 224(ext=109) (@(#) DPLIB-INT-VERSION-224)
M length of sys_adm_ext is 360 bytes
M ***LOG Q0Q=> tskh_init, WPStart (Workproc 0 3376) http://dpxxdisp.c 1301
I MtxInit: 30000 0 0
M DpSysAdmExtCreate: ABAP is active
M DpSysAdmExtCreate: VMC (JAVA VM in WP) is not active
M
M Thu May 22 19:58:51 2008
M DpShMCreate: sizeof(wp_adm) 6328 (904)
M DpShMCreate: sizeof(tm_adm) 3605136 (17936)
M DpShMCreate: sizeof(wp_ca_adm) 1200 (60)
M DpShMCreate: sizeof(appc_ca_adm) 1200 (60)
M DpCommTableSize: max/headSize/ftSize/tableSize=500/8/528040/528048
M DpShMCreate: sizeof(comm_adm) 528048 (1048)
M DpSlockTableSize: max/headSize/ftSize/fiSize/tableSize=0/0/0/0/0
M DpShMCreate: sizeof(slock_adm) 0 (96)
M DpFileTableSize: max/headSize/ftSize/tableSize=0/0/0/0
M DpShMCreate: sizeof(file_adm) 0 (72)
M DpShMCreate: sizeof(vmc_adm) 0 (1280)
M DpShMCreate: sizeof(wall_adm) (22440/34344/56/100)
M DpShMCreate: sizeof(gw_adm) 48
M DpShMCreate: SHM_DP_ADM_KEY (addr: 06420040, size: 4205552)
M DpShMCreate: allocated sys_adm at 06420040
M DpShMCreate: allocated wp_adm at 06421A28
M DpShMCreate: allocated tm_adm_list at 064232E0
M DpShMCreate: allocated tm_adm at 06423310
M DpShMCreate: allocated wp_ca_adm at 067935A0
M DpShMCreate: allocated appc_ca_adm at 06793A50
M DpShMCreate: allocated comm_adm at 06793F00
M DpShMCreate: system runs without slock table
M DpShMCreate: system runs without file table
M DpShMCreate: allocated vmc_adm_list at 06814DB0
M DpShMCreate: allocated gw_adm at 06814DF0
M DpShMCreate: system runs without vmc_adm
M DpShMCreate: allocated ca_info at 06814E20
M DpShMCreate: allocated wall_adm at 06814E28
X EmInit: MmSetImplementation( 2 ).
X MM global diagnostic options set: 0
X <ES> client 0 initializing ....
X Using implementation view
M <EsNT> Memory Reset disabled as NT default
X ES initialized.
M ThInit: running on host PCFABIO
M
M Thu May 22 19:58:52 2008
M calling db_connect ...
B create_con (con_name=R/3)
B Loading DB library 'C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll' ...
M *** ERROR => DlLoadLib: LoadLibrary(C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll) Error 126 http://dlnt.c 237
M Error 126 = "Impossibile trovare il modulo specificato."
B *** ERROR => Couldn't load library 'C:\SAP\NSP\SYS\exe\run\dbsdbslib.dll'
http://dbcon.c 4726
M ***LOG R19=> ThInit, db_connect ( DB-Connect 008192) http://thxxhead.c 1426
M in_ThErrHandle: 1
M *** ERROR => ThInit: db_connect (step 1, th_errno 13, action 3, level 1) http://thxxhead.c 10240
M
M Info for wp 0
M
M stat = WP_RUN
M waiting_for = NO_WAITING
M reqtype = DP_RQ_DIAWP
M act_reqtype = NO_REQTYPE
M rq_info = 0
M tid = -1
M mode = 255
M len = -1
M rq_id = 65535
M rq_source =
M last_tid = 0
M last_mode = 0
M semaphore = 0
M act_cs_count = 0
M csTrack = 0
M csTrackRwExcl = 0
M csTrackRwShrd = 0
M control_flag = 0
M int_checked_resource(RFC) = 0
M ext_checked_resource(RFC) = 0
M int_checked_resource(HTTP) = 0
M ext_checked_resource(HTTP) = 0
M report = > <
M action = 0
M tab_name = > <
M vm = no VM
M
M *****************************************************************************
M *
M * LOCATION SAP-Server PCFABIO_NSP_00 on host PCFABIO (wp 0)
M * ERROR ThInit: db_connect
M *
M * TIME Thu May 22 19:58:52 2008
M * RELEASE 700
M * COMPONENT Taskhandler
M * VERSION 1
M * RC 13
M * MODULE thxxhead.c
M * LINE 10439
M * COUNTER 1
M *
M *****************************************************************************
M
M PfStatDisconnect: disconnect statistics
M Entering TH_CALLHOOKS
M ThCallHooks: call hook >ThrSaveSPAFields< for event BEFORE_DUMP
M *** ERROR => ThrSaveSPAFields: no valid thr_wpadm http://thxxrun1.c 720
M *** ERROR => ThCallHooks: event handler ThrSaveSPAFields for event BEFORE_DUMP failed http://thxxtool3.c 260
M Entering ThSetStatError
M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)
M Entering ThReadDetachMode
M call ThrShutDown (1)...
M ***LOG Q02=> wp_halt, WPStop (Workproc 0 3376) http://dpnttool.c 327
File dbsdbslib.dll' is 'there' (in 'C:\SAP\NSP\SYS\exe\run\), maybe i have to set environment variable in windows for SAP.
Could you help me, please ?
I don't know how to set these variables.......
Many thanks.
Regards.
FabioHello Fabio,
-> You wrote:
"File dbsdbslib.dll' is 'there' (in 'C:\SAP\NSP\SYS\exe\run\)"
=> Please check the version of this file.
< Go to file properties ->Version && update with 'file version', Platform,
Product Name, Product Version information >
-> What version of the SAP system did you install?
"I suppose that i can download this patch from Sap MaketPlace, but i can't register there, because i have no
Customer or Installation Number! (i can't Logon in SAP....) "
From were did you get the SAP software installation or CD?
-> Could you upgrade the database client software on the application server to the version 7.7.04.08 or higher.
You pointed "As you can see from here : http://www.fabiocavallo.it/sap/maxdb.jpg u2026 "
=> If the database and application were running on the same server, you installed the database
Software version 7.6.02.17. Please run 'sdbregview -l' to review the list of all installed packages
on the server.
-> "MaxDB seems to work fine, but after starting application server i have got an error"
Was the system working fine before? What was changed?
Or you was not able to start the application server after installation. ?
Thank you and best regards, Natalia Khlopina -
Error on running JVM from a C program
Hello there!!
I'm using Open Watcom as a C compiler on Windows XP. I'm trying to run a JVM from a C program.
I have specified the following as a library file :
C:\Java\jdk1.5.0_04\lib\jvm.lib
The code compiles very well, but I'm getting an error when running it.
Windows tells me the following :
"The entry point of the function ??_7VM_GetCurrentLocation@@6B@ can't be found in jvm.dll dynamic linking library"
The code I've been trying to run is the following one :
#include <jni.h>
#include <stdio.h>
#include <stdlib.h>
void main()
JavaVMOption options[3];
JavaVMInitArgs vm_args;
JavaVM *jvm;
JNIEnv *jenv;
long result;
jmethodID mid;
jfieldID fid;
jobject jobj;
jclass cls;
int asize;
printf("coucou\n");
getchar();
options[0].optionString = ".";
options[1].optionString = "-Djava.compiler=NONE";
options[2].optionString = "-verbose:jni";
vm_args.version = JNI_VERSION_1_2;
vm_args.options = options;
vm_args.nOptions = 3;
vm_args.ignoreUnrecognized = JNI_FALSE;
JNI_GetDefaultJavaVMInitArgs(&vm_args);
result = JNI_CreateJavaVM(&jvm,(void **)&jenv, &vm_args);
/* if(result == JNI_ERR )
printf("Error invoking the JVM");
exit (-1);
cls = (*jenv)->FindClass(jenv,"C:\Formation\Joly\FromCtoJava\WATCOM\samples\ide\win32\FromCtoJava");
/* if( cls == NULL )
printf("can't find class FromCtoJava\n");
exit (-1);
(*jenv)->ExceptionClear(jenv);
mid=(*jenv)->GetMethodID(jenv, cls, "<init>", "()V");
jobj=(*jenv)->NewObject(jenv, cls, mid);
fid=(*jenv)->GetFieldID(jenv, cls, "arraySize", "I");
asize=(*jenv)->GetIntField(jenv, jobj, fid);
printf("size of array is %d",asize);
(*jvm)->DestroyJavaVM(jvm);*/
Cheers
JolyI already did PATH.
Open a console window.
Explicitly set PATH to point ONLY to the appropriate java directory (where the dll is and executable) using something like the following
set PATH=C:\xxx\yyy
Then run your app again in the console window - no where else.
Maybe you are looking for
-
Acrobat plug-ins PPKLite.api, HTML2PDF.api fail to initialize & file reducing plug-in not available
Trying to figure out why in last 2 wks I've been getting error messages when I open a PDF doc with Acrobat 7.0.9 professional. Initially 2 pop-ups saying error loading plug-ins PPKLite.api and HTML2PDF.api & they "failed to initialize. I can click OK
-
Hello Dev's, I am having a problem in only one project and I have even tried to recreate the project with no success but previous projects created years prier (made with previous versions of FB) are not experiencing this. I am trying to place breakpo
-
What is the Best Power MAC G5 for Graphic Design and Video Edit
I need the Best Power MAC G5 Processor CPU and Ram HDD Graphic card for Graphic Design and Video Edit and the name of the Processor how much the price
-
Swf files that scale with the browser
I uploaded a swf file with dreamweaver as a stand alone window and it works fine. How do I get the swf file to scale larger or smaller as the user adjusts their browser window larger and smaller? I would like to get the swf file to scale along with
-
What filename is Bootcamp looking for when it searches for Windows installer?
I purchased a download file of Windows 7 Home Premium x64 which when downloaded has the filename X15-65733.iso. When opened it provides a diskimage called GRMCHPXFRER_EN_DVD on which are the files and folders for the Windows 7 installation: autorun