Ni::dsc::osdep::PosixError when starting labview

Hi
When I try and start Labview i get the following error
terminate called after throwing an instance of 'ni::dsc:sdep:osixError'
what(): Invalid argument
Aborted
we have version 9.0 of labview on linux rhel 5.4 and from what i can see from the gui it get's up to running "converting toolkits" before it crashes.
Thanks
Caleb

Hi,
When I try and start Labview i get the same error
"'ni::dsc:sdep:osixError"
I launch labview as root and It works.
Why ?
Presently I wait for the answsers with
grep -r "'ni::dsc:sdep:osixError" *
Cheers,
jo

Similar Messages

Error 2 when starting LabVIEW from ELVIS Instrument Launcher

I have a WinXP Pro SP2 box that's running LabVIEW 7.1 (academic license) and NI ELVIS 2.0.1.
When I perform the following steps,
1) Log on to the WinXP machine as a user who does not have Power User or Administrator privileges.
2) Click on Start > All Programs > National Instruments > NI ELVIS 2.0 > NI ELVIS
3) Wait for the "ELVIS - Instrument Launcher" application to finish initializing.
4) Click on the "Launch LabVIEW" button at the bottom of the ELVIS - Instrument Launcher window.
I immediately get an error dialog that says
_dialog_box_text_
Error 2 occurred at System Exec.vi. Command
was "LabVIEW.exe:\ "C:\Program Files\National
Instruments\NI ELVIS 2.0\ELVIS - LabView
Launcher.lib""
Possible reason(s):
LabVIEW: Memory is full.
NI-488: Write detected no Listeners.
["Continue" button]
_/dialog_box_text_
[n.b. The characters ":\" that immediately follow the LabVIEW.exe program name (see above) are not a typo on my part. Those characters are shown on the Error 2 dialog box.]
It seems unlikely to me that the ELVIS - Instrument Launcher application has run out of memory. The host machine has 512MB of physical memory and the ELVIS - Instrument Launcher application is the only (user-layer) application. The Windows Task Manager (via a "3-finger salute" - Ctrl+Alt+Delete) indicates ample memory resources are still available when the Error 2 dialog pops up.
For what it's worth, if I perform steps 1 thru 4 above while logged on as a WinXP administrator user, I do not get the Error 2 dialog. I get instead the "NI ELVIS - LabVIEW Launcher" dialog which offers the following 3 choices: View NI ELVIS Examples; View NI ELVIS Instrument Source Code; Open LabVIEW.
Is there anything I can do to correct the Error 2 problem for non-administrator users?

Hi,
Well since it works as an admin, I am assuming there is a problem with you being an admin all the time. If there is, then I would suggest giving full sharing privileges to the National Instruments folder, to whichever user you are. See if that works. Let me know.
George

MSVCR90.DLL Error when start LabVIEW 2009

Hi,
   My LabVIEW 2009 failed to start. It pops up a window says fault module MSVCR90.DLL. I have reinstalled LabVIEW but the problem is still there. Anybody has similar problem before?
   Thanks for help!
   Tom

Hi,
unfortunately I can't do anything in c:\windows\... because I'm not an adnministrator. I have to wait at least a week before he comes back and maybe do it for me. There are 2 Versions of Microsoft Visual C+ installed on this comuter: 2008 and 2010. When LabView crashes and I select "Debug" there are 2 possibilities: 2008 and 2010. The msvcr90.dll which is marked as "failure" in an error message referres to Microsoft RunTime Engine 2008 (according to its properties).
I had made another experiment: set "runTime Engine" as VI server by Test Stand. In this case VIs are marked as "erroneus" (with a red button on the module panel). I have to reload every VI (the red button stays, but the picture is loaded), then start execution and ingnore the message, that there are errors. The sequence works OK. When I close TestStand I get an error message "TestStand doesn't work any more-> SeqEdit APPCRASH".
I think it shows, that RunTime Engine (I select the option "Recognize the version automatically") loads VIs in another way than LabView Development Environment does.

Runtime Engine 7.1.1 Disk 2 when starting Labview

I have labview version 8.2.1 installed on my computer.
The other day I installed some application by another company that must have installed Labview Runtime Engine 7.1.1 on my computer. I didn't need that program anymore, so I uninstalled it.
Now anytime I try to run any labview programs on my computer, I get several dialog boxes wanting me to put NI Labview Runtime Disk #2 in my CD drive.
How can I get rid of these dialog boxes?
Please help!!!

Hi bkundework,
This issue seems very strange but I do have a few suggestions. The first idea that comes to mind is to repair LabVIEW 8.2.1 from Add/Remove Programs. If you no longer have the 8.2.1 disks or if a repair does not work, you should install the LabVIEW Run-Time Engine 8.2.1. This download is available on NI’s website.
These two ideas are the easiest ways to possibly fix things. If they don’t, a list of all the NI Software you have installed would be helpful for going forward.
Charlie M. CLD

Labview 8.6 crashes when started

Hi,
I just installed labview 8.6 in an old Linux machine (kernel 2.4.21), and even when labview installed fine (no errors or warnings at all), when I start labview, it crahses with this message:
LabVIEW caught fatal signal
8.6 - Received SIGSEGV
Reason: address not mapped to object
Attempt to reference address: 0x4
Segmentation fault (core dumped)
Now, the core dump trace says this:
#0 0xf6513959 in XSetICFocus () from /usr/X11R6/lib/libX11.so.6
#1 0x08c9664e in WGetStyle ()
#2 0x08c967bb in WGetStyle ()
#3 0x08c96405 in WIsAtRootLevel ()
#4 0x08c96934 in WSendEvent ()
#5 0x08c9705a in WCreateEx ()
#6 0x08bca719 in ChangeVINameWrapper ()
#7 0x08bf875f in CheckShortNameSize ()
#8 0x0857ef65 in DNAllocCookieForObject ()
#9 0x0857f0cd in DNAllocCookieForObject ()
#10 0x0857ef83 in DNAllocCookieForObject ()
#11 0xf629679a in __libc_start_main () from /lib/tls/libc.so.6
#12 0x0807c021 in ?? ()
So it is somehow related to the X server -I think-. Now, the odd part is that if I start labview with a vi, like
labview mydiagram.vi
it starts an opens mydiagram.vi (if mydiagram.vi is set to run when started, it will even run ok). However, if I try to open the diagram, then it will crahs with the same error/core dump.
Has anybody seen this problem?
Thanks.

Bruno,
Thanks. I have verified also that all the requiered libraries are there:
% ldd labview
        libGL.so.1 => /usr/X11R6/lib/libGL.so.1 (0xf65a4000)
        libX11.so.6 => /usr/X11R6/lib/libX11.so.6 (0xf64c5000)
        libXext.so.6 => /usr/X11R6/lib/libXext.so.6 (0xf64b7000)
        libstdc++.so.5 => /usr/lib/libstdc++.so.5 (0xf6404000)
        libm.so.6 => /lib/tls/libm.so.6 (0xf63ce000)
        libdl.so.2 => /lib/libdl.so.2 (0xf63ca000)
        libpthread.so.0 => /lib/tls/libpthread.so.0 (0xf63ba000)
        libc.so.6 => /lib/tls/libc.so.6 (0xf6281000)
        libgcc_s.so.1 => /lib/libgcc_s.so.1 (0xf6278000)
        /lib/ld-linux.so.2 => /lib/ld-linux.so.2 (0xf65e9000)
Regarding how old is the machine, the starnge thing is that I have anoither machine, as old as this -the same kernel-, that is running hapully labview 8.5. So, unless something important changed between 8.5 and 8.6, it is hard to imagine this is due to the age of the kernel or machine. I could try installing labview 8.6 on the other machine, but I'm a bit afraid, since it is a mchine with a running, in-work systenm that I cannot disturb -I know multiple labviews can, in theory, live toguether, but I don't want to find out that "not quite" ...
Thanks a lot anyway
M.B.

Error "An exception occurred within the external code..." when stopping LabView

I am having an error "An exception occurred within the external code called by a Call Library Node...", see the attached image, when I am trying to stop LabView. As a result of the error, the tag engine doesn't close normally.
I am using LabView 7.1 with DSC. I read values from a LNS (LON) OPC-server.
Is this a known issue and is there any way to repair it? I haven't noticed any direct consequences because of the error except that when I re-start LabView and the close it again without having first rebooted the computer, tag engine sometimes starts again when it should stop. This is fixed by always rebooting the computer before restarting LabView. I am getting suspicious that there might be some strange behaviour because the error says "it might have corrupted LabView's memory".
For example, sometimes when I have made a copy of an input number field to another, they follow each other's value changes even though there is no connections between them.
Simo Martikainen
Message Edited by Simo Martikainen on 12-17-2008 03:11 AM
Attachments:
LabView stop error.JPG ‏45 KB
TAGENGINE.JPG ‏16 KB

Especially in earlier versions of LV these sorts of errors were common if the call wasn't made just right or the parameters were set up incorrectly.
Where did you get the DLL from? Was it written internally or did it come from another vendor?
Try building a DLL call into a very small, simple application. Do you see the same issue?
Are there multiple calls to the same DLL in your code? If so, is there problems with all of them?
Can you track it down to a specific function that you are trying to access that is causing the problem?
Is there any indication of a memory leak?
Finally any additional information you can provide would helpful.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Core dump when starting extract, no error messages

Hello,
This is a basic one way replication, Data Pump and Replicat start but Extract stops at once.
In ggserr.log there's only a message: EXTRACT EORATE02 starting, nothing else. In ggsci it can be seen that it's stopped.
CHECKPARAMS didn't give the message "Parameters processed successfully", neither did it give error messages
when starting the extract.
There are no old Oracle processes which could prevent Extract from starting.
There's EORATE02.pce in dirpcs, although EORATE02 is not running. If I delete it and try to start the extract,
the extract will immediately stop.
A core file has been created in GG_HOME when trying to start the extract. I haven't been able to find out how to read it.
Source and target are on Aix 6100-06. The source database is Oracle 10.1.0.5, target database is Oracle 11.2.0.3.
The installation files are V32435-01.zip for db 10.1.0.5 (ggs_AIX_ppc_ora10.1_64bit.tar), V32437-01.zip
for db 11.2.0.3 (ggs_AIX_ppc_ora11g_64bit.tar). This is GoldenGate 11.2.1.0.1.
The db:s are on Asm.
There's only 1 table in source, 1 in target, they are identical and empty.
There's enough space in the OS.
If I run the extract in OS (extract paramfile dirprm/eorate02.prm), it ends like this without more information:
TRANLOGOPTIONS ASMUSER ggs_owner@HOSTNAME:1521/+ASM , ASMPASSWORD *********
Abort(coredump)
This happens in both ways of extract described below.
(1)
EXTRACT EORATE02
USERID ggs_owner, PASSWORD [PASSWORD]
EXTTRAIL ./dirdat/data02/te
TRANLOGOPTIONS ASMUSER ggs_owner@HOSTNAME:1521/+ASM , ASMPASSWORD [PASSWORD]
TABLE USER.myobjects2;
(2)
EXTRACT EORATE02
USERID ggs_owner, PASSWORD [PASSWORD]
EXTTRAIL ./dirdat/data02/te
tranlogoptions COMPLETEARCHIVEDLOGONLY ALTARCHIVELOGDEST /backup/arch_log/abcd/ABCD/archivelog
TRANLOGOPTIONS ASMUSER ggs_owner@HOSTNAME:1521/+ASM , ASMPASSWORD [PASSWORD]
TABLE USER.myobjects2;
Here's more information on this setup and commands which have been used:
add extract EORATE02 tranlog begin now, threads 1
add exttrail ./dirdat/data02/te, extract EORATE02, megabytes 5
EXTRACT EPMPTE02
PASSTHRU
RMTHOST HOSTNAME, MGRPORT 13447
RMTTRAIL /u01/app/oracle/gg11210/for_11g/dirdat/data02/tr
TABLE USER.myobjects2;
ADD EXTRACT EPMPTE02 EXTTRAILSOURCE ./dirdat/data02/te
ADD RMTTRAIL /u01/app/oracle/gg11210/for_db11/dirdat/data02/tr EXTRACT EPMPTE02, MEGABYTES 5
Target
REPLICAT RORATE02
USERID ggs_owner, PASSWORD [PASSWORD]
HANDLECOLLISIONS
ASSUMETARGETDEFS
DISCARDFILE ./dirrpt/RORATE02.DSC, PURGE
MAP USER.MYOBJECTS2, TARGET USER.MYOBJECTS2;
add replicat RORATE02, exttrail /u01/app/oracle/gg11210/for_11g/dirdat/data02/tr
add checkpointtable ggs_owner.ggschkpt
Grants
Source:
grant connect, resource to ggs_owner;
grant select any dictionary, select any table to ggs_owner;
grant create table, alter any table to ggs_owner;
grant flashback any table to ggs_owner;
grant execute on dbms_flashback to ggs_owner;
grant execute on utl_file to ggs_owner;
grant create session, alter session to ggs_owner;
Target:
grant create session, alter session, resource, connect, select any dictionary to ggs_owner;
grant select any table, insert any table, update any table, delete any table to ggs_owner;
grant create table, alter any table, lock any table to ggs_owner;
Source
ALTER DATABASE ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS;
ggsci add trandata USER.myobjects2
mgr.prm
--GoldenGate Manager parameter file
PORT 13346
Target
GLOBALS
CHECKPOINTTABLE ggs_owner.ggschkpt
mgr.prm
--GoldenGate Manager parameter file
PORT 13447
Thanks for reading this far. Possible comments will be much appreciated!
Best regards
Edited by: user11323660 on 14.6.2012 6:39
Edited by: user11323660 on 14.6.2012 6:41

Hello,
Could you wrap your process definitions in proper code brackets so its easier to understand.
Also I'm not sure what your problem is other then you are receiving core dumps. I'm happy to help.
Two small comment though regarding your ASM config
1 . Dont not use ggs_owner as the asm user
TRANLOGOPTIONS ASMUSER ggs_owner@HOSTNAME:1521/+ASM , ASMPASSWORD *********2. Create a TNSNAMES entry for your ASM instance and tehn use the following:
TRANLOGOPTIONS ASMUSER SYS@ASM, ASMPASSWORD *****Also here is an example of an extract process that I've setup on RAC database with ASM
EXTRACT EWFMMTLP
EXTTRAIL ./dirdat/ew
USERID GGATE@MY_DB, PASSWORD ggatehcc
DDLOPTIONS ADDTRANDATA RETRYOP RETRYDELAY 20 MAXRETRIES 5 REPORT
TRANLOGOPTIONS EXCLUDEUSER ggate
TRANLOGOPTIONS ASMUSER SYS@ASM, ASMPASSWORD ****
TRANLOGOPTIONS ALTARCHIVELOGDEST /u02/oracle/fast_recovery_area/MY_DB/archivelog
TRANLOGOPTIONS PURGEORPHANEDTRANSACTIONS
STATOPTIONS RESETREPORTSTATS
REPORT AT 00:01
REPORTROLLOVER AT 00:01
REPORTCOUNT EVERY 60 SECONDS, RATELet me know if that helps
Jan S.

Error updating mutation history every time I start LabVIEW

I have a slightly annoying problem that has been re-occuring the past month or so. Every time I start LabVIEW I get the following error messages:
Error occured updating the mutation history for Progam (2).lvclass. All values of this class in controls and constants will be reset to the default value
The same error appears for Page (2).lvclass, Chart (2).lvclass, Worksheet (2).lvclass and Workbook (2).lvclass.
It slows down my LabVIEW startup time by at least 3-4 minutes every time, which is quite annoying. I imagine the problem is occuring when it populates my existing projects, and in one of these projects contains the problem lvclass files. But I did a search of my ProgramFiles\NationalIntruments folder and my work directory and didn't find any files of those names. Just wondering if any one had any ideas on how to fix it?
Thanks!

Okay, seems like I found the problem. Yes, to answer your question, most of my LabVIEW programming is OO, using GOOP mainly.
I also imported hundreds of LabVIEW libraries where these lvclass files were, they were in ImportedLib\DataLogger\LabVIEW widgets\ActiveX
It's not code I've written, but I don't see why including these files was necessary in the repo, oh well. To get rid of the error I just removed those files and the mutation error stopped appearing. What's still a little confusing is why these files were being accessed on LabVIEW startup. I can imagine it necessary to load these files when the project is opened, but seems weird when it's just populating the existing projects list.
Oh well, thanks for looking into it Andy, files were not in the NI folder which explains why I didn't find them on my first attempt.

Error Code "1097.....this might corrupted LABVIEW's memory.........." appears after exit the labview and re-start labview

        I have a probelm when I use the "tool/import shared library(.dll)" wizard to generate the API from C.
        The API works correctly when I complete the wizard, but after I exit labview and re-start labview to run the API again. The error 1097 code "......this might corrupted LABVIEW's memory.............."appears.
        The only solution now is to re-generate or update the wizard to generate the API.
        I try to find the answer in
        http://digital.ni.com/public.nsf/allkb/58596F5D41CE8EFB862562AF0074E04C?OpenDocument
        The paragraph in above article shows
         "LabVIEW does not crash until it is closed
The most likely problem is that the DLL function being called has corrupted the memory. If you pass arrays or strings to the DLL, the DLL function cannot dynamically resize the array. Writing beyond the last element of the array or string could corrupt the memory and this may not be obvious until LabVIEW is closed."
But it doesn't match my case. Does someone have idea about this? I Attach my .h file for reference
Attachments:
test_api.h ‏1 KB
link_test_api.h ‏1 KB

wewe1215 wrote:
        I have a probelm when I use the "tool/import shared library(.dll)" wizard to generate the API from C.
        The API works correctly when I complete the wizard, but after I exit labview and re-start labview to run the API again. The error 1097 code "......this might corrupted LABVIEW's memory.............."appears.
        The only solution now is to re-generate or update the wizard to generate the API.
        I try to find the answer in
        http://digital.ni.com/public.nsf/allkb/58596F5D41CE8EFB862562AF0074E04C?OpenDocument
        The paragraph in above article shows
         "LabVIEW does not crash until it is closed
The most likely problem is that the DLL function being called has corrupted the memory. If you pass arrays or strings to the DLL, the DLL function cannot dynamically resize the array. Writing beyond the last element of the array or string could corrupt the memory and this may not be obvious until LabVIEW is closed."
But it doesn't match my case. Does someone have idea about this? I Attach my .h file for reference
Which of the 2 functions do you call? How?
The documentation of InitSocketEx() seems to indicate reversed parameter order than what the function prototype looks like!
I indeed do not see much possibilities to pass in to small a buffer that the DLL function might be overwriting past the end. This really only leaves one more possibility:
Your DLL is doing something largely illegal somehow. Maybe something as silly as storing the reference to the ipAdress instead of the address itself. The memory passed as parameters into a C function is generally only valid for the duration of the call. This is especially true if you use LabVIEW since LabVIEW will re- and deallocate memory buffers frequently as soon as they are not used anymore and the parameter to a Call Library node is considered to not be required anymore after the function returns.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

LabVIEW 7.1 reports an application error 'instruction adresses memory at 0x00000000 - ... could not be written' when finishing LabVIEW, even when not running any private code

Hi there,
I have found similar Qs here, but this one is _somehow_ different.
My quite large app (>600 VIs) uses some DLL calls to communicate with medical devices. It runs OK, AFAIK, even when started several times. BUT I get an error message each time I when finishing LabVIEW 7.1 (even when just having loaded the app!!!). The error message states that "The instruction at 0x778cca36 adresses memory at 0x00000000. The process 'written' could not be done on that memory. Click to close the app".
Any clues?
My system: Athlon64 3000+ with 1GB of RAM running W2k German with all availabel SPs, LabVIEW 7.1 English with all support files from the devellopr suite May05 edition. System was set up 2 days ago on a fresh PC. The old system showed the very same behavior.
My opinion is, that simply loading an app and than removing it should not cause such an error??!!
Greetings from Germany!
Uwe
Attachments:
Application_Error_LabVIEW_when_finishing.jpg ‏20 KB

I can't look at your code because I don't have LV 7.1, but I would recommend searching on the side of the DLL.
Do you have the source for the DLL? Can you be sure that the DLL doesn't somehow have a memory addressing bug? The DLL will be loadsd as soon as the program is loaded AFAIK, so maybe when unloading the DLL an error occurs because something isn't initialised properly. I've never programmed a DLL, so I may be way wrong, but my instinct tells me that the problem will most likely be with the DLL.
Hope this helps
Shane.
Using LV 6.1 and 8.2.1 on W2k (SP4) and WXP (SP2)

Error message when starting MaxDB instance

I am getting the following Error message when starting the MaxDB instance after a series of failed attempts at starting the DB Manager Backup for our PI 7.1 server.
"-24994,ERR_RTE: Runtime environment error
1,Cannot create ipc db directories for SID (OS error code 11000)"
Max DB version : 7.7.02
Does anyone have any specific pointers on where the issue could be.
Any help is greatly appreciated.
Regards,
Murali Narayanan

Hi gurus,
I'm a complete newbye searching the forums in order to decrypt what is inconsistent to me (I'm acting as a substitute for a real dba): a sapdb refusing any more connection due to an 'user space exhausted' issue.
I do not even know if/where some admin tool is/isn't installed - eventually, what to look for - onto the running demianapachetomcat framework. Actually, all I have been provided was: 1. call 'Henplus' (done); 2. connect this way (jdbc:sapdb://localhost/database&options) and 3. select, upgrade, delete what needed. Problem arises on point (2): connection resufed 'user space exhausted'.
My question is: this issue seems so similar to mine, how can one eventually check/modify this '/sapdb directory space'?
Thanks in advance for any (much appreciated) hint, and be patient about my English and newbyeness (?).
MaxM

Is there any way to prevent the OS from querying the Superdrive when start

Just a random question. Whenever my MacBook Pro starts up (either from sleep or a complete/fresh start, the OS queries the drive slot to see if there is a disc present. While this may be normal behavior, it seems to slow down the start up process. (I rarely ever have a disc in the drive). Just curious if this, in fact, normal, or if there's something awry.

Is there any way to prevent the OS from querying the Superdrive when start
No
he OS queries the drive slot to see if there is a disc present.
How can you tell? Based on the noise it makes?

Error when starting Weblogic in debug mode

Hi there
Has anyone experienced any difficulties when starting weblogic in debug mode.
More specifically, it cannot start correctly because it thinks that another instance
is using the same port (definately not the case).
Any clues/suggestions are greatly appreciated.
Error log follows:
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <Unable to create
a server socket for port: 8320. java.net.BindException: Address already in use
Perhaps another process is using port 8320.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Notice> <WebLogicServer> <SSLListenThread
listening on port 8321>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <The WebLogic
Server is no longer listening for connections. You should probably restart it.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <Server shutdown
has been requested by system>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <The shutdown sequence
has been initiated.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Info> <WebLogicServer> <Server shutdown is
commencing NOW and is irreversible.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Error> <Performance Pack> <Unable to load
performance pack, using Java I/O.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:581)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:764)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:507)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)

Thanks for the suggestion.
Unfortunatley the port is definately free/available during startup.
Stephane Kergozien <[email protected]> wrote:
Maark,
Before starting your server, please could you check that the port is
not used by one
other process. You can use the netstat command to do this.
Regards
Stephane
Mark wrote:
Hi there
Has anyone experienced any difficulties when starting weblogic in debugmode.
More specifically, it cannot start correctly because it thinks thatanother instance
is using the same port (definately not the case).
Any clues/suggestions are greatly appreciated.
Error log follows:
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <Unableto create
a server socket for port: 8320. java.net.BindException: Address alreadyin use
Perhaps another process is using port 8320.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Notice> <WebLogicServer> <SSLListenThread
listening on port 8321>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Emergency> <WebLogicServer> <TheWebLogic
Server is no longer listening for connections. You should probablyrestart it.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <Servershutdown
has been requested by system>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Alert> <WebLogicServer> <The shutdownsequence
has been initiated.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Info> <WebLogicServer> <Servershutdown is
commencing NOW and is irreversible.>
<Mar 18, 2002 7:42:32 AM GMT+10:00> <Error> <Performance Pack> <Unableto load
performance pack, using Java I/O.
java.lang.ThreadDeath
at java.lang.Thread.stop(Thread.java:581)
at weblogic.t3.srvr.T3Srvr.die(T3Srvr.java:764)
at weblogic.t3.srvr.T3Srvr.waitForDeath(T3Srvr.java:507)
at weblogic.t3.srvr.T3Srvr.run(T3Srvr.java:171)
at weblogic.Server.main(Server.java:35)--
Regards,
Stephane Kergozien
BEA Support

Error when starting work item

Hi
We are having SRM5.0.
Trying to create Contract. Workflow Without approval of contract(WS1400086)is activated and start conditions also no workflow activated.
Contract is created and getting message Contract created.
But when tried to release the contract it shows "Awaiting approval".
In Workflow log (SWI1)it shows error."Error when starting work item xxxx".
What could be the reason. Please let me know the solution if anyone of you come across such error.
Thanks in advance
Jagadish

Masa
It is maintained as General task already.
It seems the workflow task WS14000085 does not have definition.
When checked in SWDD for the above teask there are no steps defined for that workflow.
SAP says that we need to define and action for workflow WS14000085.
But what is the procedure to define the workflow.
I presume this is the standard workflow and it should be defined by default when it comes along with the SRM package.
Anyone of you know how to define the workflow and activate the same?
Regards
Jagadish

Error when starting parser: timeout during allocate / CPIC-CALL:'TfSAPCMRC'

Hello experts.
When I try to preview or refresh a Crystal Report document built on a BEx query I get the following error msg:
Database connector error: BAPI Error #0. Error when starting parser: timeout during allocate / CPIC-CALL: 'TfSAPCMRCV'.
We have done as suggested in "SAP Note 1032461 - MDX parser does not start", but without success.
This is what we've tried so far:
replaced the file "librfc32.dll" (in C:\Windows\System32 and C:\Windows\SysWOW64) with the new version mentioned in Note 413708.
tested the connection in SM59 - non successful
tested the report query with transaction MDXTEST - non successful
tried to start the mdxparser manually on server - non succesful, error msg: "The application failed to initialise.."
We have the following config:
MS server 2003 SP2 x64 ed.
SAP logon 7.20
MS SQL server 2005
CR 2008
new librfc32.dll version 7200.1.39.6461
Any ideas on what to try next would be highly appreciated!
Cheers, IngA

Hi Ingo.
We have only one application server.
I registered the new version of the file C:\windows\SysWOW64\librfc32.dll with regsvr32.exe successfully. I've also tried to copy the new file to the same directory as the mdxsvr.exe-file is located, but it made no difference.
Should I remove all other copies of librfc32.dll and only keep the one in folder C:\Windows\SysWOW64, or maybe register them all with regsvr32.exe?
--IngA
Edited by: Ingeborg Andreassen on Nov 5, 2010 10:36 AM

Ni::dsc::osdep::PosixError when starting labview

Similar Messages

Maybe you are looking for