Fatal Message Error

I have an IPhone and when I download my pict
ures to Photoshop Elements 6.0 I get a Fatal Error message. Ho
w do you fix this??

Hi,
Earlier, this crash was observed under a specific workflow. If the iPhone contains an image that is saved from an email attachment, this crash comes. i.e. if we have mail setup on the iPhone and we save the image from one of the mail attachments and then try to download the photos via APD. This was happening because of mismatch in thumbnail size and actual thumbnail data of the image provided by the device.
Recently, I tried a workflow in which I edited the photo from iPhone itself and I reproduced this crash. On deleting the edited photos, APD would work just fine. This crash is also due to the same above mentioned reason.
Adobe is investigating both the crasher workflows.
At present, the workaround for this is to delete the photos that have been edited from the iPhone itself and that have been saved from an email attachment and then try the download again.
Thanks/Tarun

Similar Messages

Fatal error processing incoming message, Error: 616E

Hi,
after receiving an incoming message, GWIA was not able to process it
correctly, giving the error
Fatal error processing incoming message, Error: 616E
Does anyone know what's this error about? Is the incoming message
malformed or is it an internal GWIA issue?
Frank

Hi Laura,
this has been the only one occurance of the issue. I'm just wondering
what this unknown error code means and whether it makes sense to spent
time on it.
Regards
Frank
In article <[email protected]>,
[email protected] says...
>
> Hi Frank,
>
> How many of these errors are you seeing? Is it always from the same
> source or from multiple sources?
>
> Cheers,
>
>
> --
> Laura Buckley
> Technical Consultant
> IT Dynamics, South Africa
>
> If you find this post helpful and are logged into the web interface,
> please show your appreciation and click on the star below...
> ------------------------------------------------------------------------
> laurabuckley's Profile: https://forums.novell.com/member.php?userid=122
> View this thread: https://forums.novell.com/showthread.php?t=480451

Unable to Log-in *SAP System Message : Error while reading a Dynpro*

Hi,
We are facing issues while logging-in through SAP logon 710.
The system throws an error dialog box with the below message:
SAP System Message : Error while reading a Dynpro
At the OS level Java process server0 is in stop status with exit code -11113. In ABAP WP Table all processes are in wait status.

Hi Please find the contents of std_server.out below.
stdout/stderr redirect
node name   : server0
pid         : 4124
system name : KEC
system nr. : 01
started at : Mon Jul 27 15:44:57 2009
[Thr 5656] MtxInit: -2 0 0
CompilerOracle: exclude com/sapportals/portal/pb/layout/taglib/ContainerTag addIviewResources
CompilerOracle: exclude com/sap/engine/services/keystore/impl/security/CodeBasedSecurityConnector getApplicationDomain
CompilerOracle: exclude com/sap/engine/services/rmi_p4/P4StubSkeletonGenerator generateStub
CompilerOracle: exclude com/sapportals/portal/prt/util/StringUtils escapeToJS
CompilerOracle: exclude com/sapportals/portal/prt/core/broker/PortalServiceItem startServices
CompilerOracle: exclude com/sap/engine/services/webservices/server/deploy/WSConfigurationHandler downloadFile
CompilerOracle: exclude com/sapportals/portal/prt/jndisupport/util/AbstractHierarchicalContext lookup
CompilerOracle: exclude com/sapportals/portal/navigation/cache/CacheNavigationNode getAttributeValue
CompilerOracle: exclude com/sapportals/portal/navigation/TopLevelNavigationiView PrintNode
CompilerOracle: exclude com/sapportals/wcm/service/ice/wcm/ICEPropertiesCoder encode
CompilerOracle: exclude com/sap/lcr/pers/delta/importing/ObjectLoader loadObjects
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readElement
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/InstanceBuilder readSequence
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/TypeMappingImpl initializeRelations
CompilerOracle: exclude com/sap/engine/services/webservices/jaxrpc/encoding/GeneratedComplexType _loadInto
SAP J2EE Engine Version 7.00   PatchLevel 110760.44 is starting...
Loading: LogManager ... 250 ms.
Loading: PoolManager ... 0 ms.
Loading: ApplicationThreadManager ... 47 ms.
Loading: ThreadManager ... 16 ms.
Loading: IpVerificationManager ... 0 ms.
Loading: ClassLoaderManager ... 16 ms.
Loading: ClusterManager ... 93 ms.
Loading: LockingManager ... 32 ms.
Loading: ConfigurationManager ... 1032 ms.
Loading: LicensingManager ... 0 ms.
Loading: CacheManager ... 93 ms.
Loading: ServiceManager ...
Loading services.:
Service runtimeinfo started. (16 ms).
Service cross started. (31 ms).
Service file started. (31 ms).
Service memory started. (31 ms).
Service timeout started. (16 ms).
Service trex.service started. (32 ms).
Service userstore started. (0 ms).
Service jmx_notification started. (15 ms).
Service p4 started. (62 ms).
Service classpath_resolver started. (16 ms).
Service deploy started. (3722 ms).
Service MigrationService started. (31 ms).
Service bimmrdeployer started. (0 ms).
Service log_configurator started. (5177 ms).
Service locking started. (0 ms).
Service http started. (126 ms).
Service naming started. (157 ms).
Service failover started. (16 ms).
Service appclient started. (31 ms).
Service javamail started. (47 ms).
Service ts started. (47 ms).
Service jmsconnector started. (47 ms).
Service licensing started. (15 ms).
Service connector started. (93 ms).
Service iiop started. (94 ms).
Service configuration started. (16 ms).
Service webservices started. (265 ms).
Service dbpool started. (1204 ms).
Service UT started. (0 ms).
Jul 27, 2009 3:45:09 PM         com.sap.security.core.persistence [SAPEngine_System_Thread[impl:5]_54] Fatal: Initialization of ABAP data source (com.sap.security.core.persistence.datasource.imp.R3Persistence) failed: "     Error while reading a dynpro                                        ". This message is critical if it appears during the startup of the AS Java.
Jul 27, 2009 3:45:09 PM ...re.server.ume.service.UMEServiceFrame [SAPEngine_System_Thread[impl:5]_54] Fatal:
service com.sap.security.core.ume.service ================= ERROR =================
Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
     ... 6 more
com.sap.engine.frame.ServiceException: Start of UME service failed. Check help topic "Start of UME Service Failed". Technical details:      Error while reading a dynpro
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:398)
     at com.sap.engine.frame.ApplicationFrameAdaptor.start(ApplicationFrameAdaptor.java:31)
     at com.sap.engine.core.service630.container.ServiceRunner.startApplicationServiceFrame(ServiceRunner.java:214)
     at com.sap.engine.core.service630.container.ServiceRunner.run(ServiceRunner.java:144)
     at com.sap.engine.frame.core.thread.Task.run(Task.java:64)
     at com.sap.engine.core.thread.impl5.SingleThread.execute(SingleThread.java:81)
     at com.sap.engine.core.thread.impl5.SingleThread.run(SingleThread.java:152)
Caused by: com.sap.security.core.persistence.datasource.PersistenceException:      Error while reading a dynpro
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.newPersistenceException(R3PersistenceBase.java:236)
     at com.sap.security.core.persistence.datasource.imp.R3PersistenceBase.init(R3PersistenceBase.java:491)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactoryInstance.<init>(PrincipalDatabagFactoryInstance.java:446)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.newInstance(PrincipalDatabagFactory.java:164)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:117)
     at com.sap.security.core.persistence.imp.PrincipalDatabagFactory.getInstance(PrincipalDatabagFactory.java:63)
     at com.sap.security.core.InternalUMFactory.initializeUME(InternalUMFactory.java:221)
     at com.sap.security.core.server.ume.service.UMEServiceFrame.start(UMEServiceFrame.java:287)
     ... 6 more
[Framework -> criticalShutdown] Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.
Jul 27, 2009 3:45:09 PM             com.sap.engine.core.Framework [SAPEngine_System_Thread[impl:5]_54] Fatal: Critical shutdown was invoked. Reason is: Core service com.sap.security.core.ume.service failed. J2EE Engine cannot be started.

Is a Disk Utility "fatal hardware Error" Always fatal?

Help!
I'm traveling for the next four weeks and have my lap top with me to do work.
Last night I was working fine on my computer when all of a sudden Photoshop wouldn't open files right. I quite out of Photoshop (slow)
Then tried to quit out of everything else (slow) and finally shut down holding the Power button down. I waited a few minutes and tried to reboot.
It was REALLY slow starting back up. (about 15 to 20 minutes). I held the Power key down to turn it off and left it overnight hoping it would figure itself out by morning.
This am the same start up problem happened. I finally got it opened and manuvered to Disk Utility.
IT GAVE ME THIS MESSAGE
This drive has reported a Fatal Hardware Error to Disk utility.
If the drive has not failed completely, Back up as much as you can and
then replace it with a working drive.
HERE IS WHAT I DID EARLIER IN THE EVENING THAT I THINK MADE IT WACKY.
I hadn't installed SUITCASE X1 yet and was using the program Font Book that comes with the computer. It wasn't satifactory so I went ahead and installed Suitcase X1.
FONT BOOK kept showing a ton of open faces.
I carefully (or so I thought) went through Font Books "All fonts" window and got rid of fonts that I didn't see in the system fonts folder. (I think this is where I really may have screwed up)
FYI I am a graphic designer and use many fonts.
I store all the design fonts in a folder in USERS > SHARED> FONTS
I directed SUITCASE to "Manage system fonts"
Every thing was working fine for a few hours.
I was working in QUARK 6 easily and listening to a Podcast. No problems.
When I went to open PHOTOSHOP, it (Photoshop) started running very slow.
and all the things I mentioned above started to happen.
I have the OS10.4 install disk with me so I tried to boot from it.
(I thought maybe it had a utility on it to help fix things or maybe I could copy any important fonts that I accidently trased
(btw do you hold down OPTION C to boot from a CD or APPLE C?
I tried them all)
I couldn't get it to boot from the CD
Have I really wrecked my computer?
Do we think it's a font problem.
Can I fix it. I'm at the beach in NC and there's no techys around!!!!
I am currently typing this email on the laptop so it's not completely dead.
Just super slow and threatening to die.
What should I do??!!!
Did I mention today is my birthday?
PowerbookG4 Mac OS X (10.4.6)

It's either OPTION or C. Unfortunately, the Install CD doesn't give you much access to file operations (no Finder) as Mac OS 9 and earlier did.
If you could start it in Target Disk Mode and mount the drive on another Mac, or boot it from an external drive with a Mac OS X installation on it you could try to recover files that aren't already backed up.

Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph

NOTE: This IS a duplicate post from the Breakpoint. Text slightly changed. The post in Breakpoint can be deleted. All comments should be placed in this thread.
I resolved the "Fatal Internal Error: "image.cpp", line 13192 when trying to insert a cursor to graph", but would like to share to find out if others have seen this and to determine whether this is a bug, or if it's time to redo my PC, or buy a new one..
I have an existing graphs (qt 6) which originally had 2 cursors. This occurred while trying to add the third cursor.
Up until attempting to add the last cursor, the program worked great, and I had been running tests for a while. However, I do recall seeing this problem when creating the original cursors, but not to this extent. Plus I don't remember the original error message from that time.
I needed to add one more cursor to the existing graphs. As soon as I add a new cursor and set it's properties, I get a nasty error message and without warning LV8.2 simply closes itself (well, the only warning was the error message. Tried it 3 times, same result.
Here are the steps:
Shut down the PC, went for a coffee, rebooted the PC. Opened the LV project, opened the VI. Immediately went to the graph properties to add the new cursor by doing the following steps:
Right click graph indicator icon on block diagram.
Select Properties.
Click on cursor tab.
Click on Add
Select Cursor 2 (3rd one, newly created)
Change color
Select cursor as a line
Remove checkmark for "show cursor"
Click OK
I need to do this to 3 other graphs, same steps. And as soon as I get to the step before clicking OK, I get the error message.
I managed to get an additional one done, by immediately saving after each step (yep going in & out of the properties). But I've had this problem before when creating the first two cursors.
Is it a bug? Anyone else seen this? Using LV8.2. And the message is right about LOOSING ALL unsaved work!!!!
Here are more observations:
Tried creating a new one on the second graph. As soon as I clicked on the color, it crashed!
See the error explanation below. It is really clear, now anyone can solve it    LOL!!... According to the error log, there's a bad image out there
.\manager\image.cpp(13192) : DAbort: bad image in ValidateImage
$Id: //labview/branches/Europa/dev/source/manager/image.cpp#47 $
0x007A81E8 - LabVIEW <unknown> + 0
0x007A7BDB - LabVIEW <unknown> + 0
0x00829D74 - LabVIEW <unknown> + 0
0x008546CD - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0081B9C8 - LabVIEW <unknown> + 0
0x0081EB9A - LabVIEW <unknown> + 0
0x0084D9D4 - LabVIEW <unknown> + 0
0x00854663 - LabVIEW <unknown> + 0
0x00C054E6 - LabVIEW <unknown> + 0
0x0085F7A1 - LabVIEW <unknown> + 0
0x00BBACDD - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
0x0085AA46 - LabVIEW <unknown> + 0
0x00C06A2F - LabVIEW <unknown> + 0
I observed the title bar after making changes to the properties. I noticed that 3 out of 4 times, while changing the properties of the graphs to include the cursor, and saving after each & every step, that there were no stars appearing on the title bar to indicate "unsaved changes". Saving was also much slower than usual. I suspect, the program never got to placing the star before saving occurred. However, I am noting everything.
After creating the cursors, saving was and is normal, and the program runs well..   I have run tests without problems.
Does anyone have a clue at what causes this? Has anyone seen this before?
Thanks,
RayR

Hi Donovan,
I can't remember seeing this elsewhere. When I get a chance, I'll create a new (blank) vi with new graphs and will repeat the steps.
I will let you know if I see this in the new vi.
Thanks!
RayR

Berkeley db fatal region error detected run recovery

Hi,
I have initiated d Berkeley DB object.
Then, I am using multithreading to put data into the DB.
Here is how I open the one data handler.
ret = dbp->open(dbp, /* Pointer to the database */
NULL, /* Txn pointer */
db_file_name, /* File name */
db_logical_name , /* Logical db name (unneeded) */
DB_BTREE, /* Database type (using btree) */
DB_CREATE, /* Open flags */
0644); /* File mode. Using defaults */
each threads would put data into the same handler when it needs to.
I am getting "berkeley db fatal region error detected run recovery".
What is the problem? Does it have anything to do with the way the handler is created or whether multiple threads can put data into the DB?
jb

Hi jb,
user8712854 wrote:
I am getting "berkeley db fatal region error detected run recovery".This is a generic Berkeley DB panic message that means something went wrong. When do you get this error? Did you enable the verbose error messages? Are there any other warning/error messages reported? By just posting the way you open the database doesn't help much at all. I reviewed the other questions you asked on the forum, and it seems that you are not following the advices and consult the documentation, but you prefer to open new threads. I advice you to first work on configuring Berkeley DB for your needs and read the following pages in order to understand which Berkeley DB Product best suits your application and how it should be configured for a multithreaded application:
[The Berkeley DB products|http://www.oracle.com/technology/documentation/berkeley-db/db/ref/intro/products.html]
[Concurrent Data Store introduction|http://www.oracle.com/technology/documentation/berkeley-db/db/ref/cam/intro.html]
[Multithreaded applications|http://www.oracle.com/technology/documentation/berkeley-db/db/ref/program/mt.html]
[Berkeley DB handles|http://www.oracle.com/technology/documentation/berkeley-db/db/ref/program/scope.html]
On the other hand, if the code that's calling the Berkeley DB APIs is not too big and is not private, you can post it here so we can review it for you and let you know what's wrong with it.
The procedures you should follow in order to fix a "run recovery" error are described here:
[Recovery procedures|http://www.oracle.com/technology/documentation/berkeley-db/db/ref/transapp/recovery.html]
Thanks,
Bogdan Coman

Adcfgclone.pl errored out with Unzip FAC-50409: Exiting, fatal unzip error

Hi,
while i am doing application cloning i got the following error message:
Beginning application tier Apply - Thu Jul 7 17:03:07 2011
Log file located at /u02/appl/appltest/preprod/prodappl/admin/preprod_cjb112vsa400/log/ApplyAppsTier_07071703.log
| 66% completed Unzip Failed:
/ 66% completed AC-50409: Exiting, fatal unzip error; /u02/appl/appltest/preprod/prodcomn/clone/bin/../appl/AT_inderpdbs/stage/java0.zip failed
ERROR while running Apply...
ERROR: Failed to execute /u02/appl/appltest/preprod/prodcomn/clone/bin/adclone.pl
my zip version is 2.31 and OS is RHEL 5.5 but souse OS is on RHEL3
Please suggest how to resolve this one.

What is the application release?
| 66% completed Unzip Failed:
/ 66% completed AC-50409: Exiting, fatal unzip error; /u02/appl/appltest/preprod/prodcomn/clone/bin/../appl/AT_inderpdbs/stage/java0.zip failedCan you find this zip file (java0.zip)? If yes, can you unzip it manually?
Thanks,
Hussein

Fatal IO error 11 while configuring X

i have installed xorg hal xterm xfce4 packages etc.
but problems come when i run
xterm
comes
xterm xt-error: can't open display: %s
xterm: DISPLAY is not set
and when i run
startx
i can turn to the ugly simple X windows, but when i ctrl+alt+bs and get back, comes
xterm: fatal IO error 11 (resources temporarily unavailable) or KillClient on X server '0:0'
and
display
unable to open X server ' '.
and if i run
startxfce4
messag comes like this
error: cairo 1.4.12 deos not yet support the requested image format:
Depth: 1
Alpha mask: 0x00000000
Red mask: 0x00000000
Green mask: 0x00000000
Blue mask: 0x00000000
xfce4-session: cairo-image-surface.c:199: _cairo_format_from_pixman_format:
Assertion 'NOT_REACHED' failed.
/etc/xdg/xfce4/xinitrc: line 84: 15826 Aborted $xfcesm.
and the following is the xinitrc: line 84
#Run xfce4-session if installed
xfcesm= 'which xfce4 session'
case "x$xfcesm" in ###here's the line 84
x|xno*)
$xfcesm
so, what's the problem? how can i deal with the display is not set

Have you actually configured your xorg.conf as per wiki?
http://wiki.archlinux.org/index.php/Xor … uring_xorg
http://wiki.archlinux.org/index.php/Beg … Fxorg.conf
And could you post your xorg.conf and Xorg.0.log using pastebin? (http://pastebin.archlinux.org/)

SSLException while handshaking: Peer sent alert: Alert Fatal: decrypt error

Hello everybody,
I am tryining to establish a connection from SAP PI 7.0 to an external web service that requires SSL with client authentication. I am using the SOAP adapter for that. The private key of us and the public key of the web service were installed in the VA in the TrustedCAs view. In the corresponding receiver channel configuration I have ticked "Configure Certificate Authetication" and selected appropriate entries in "Keystore Entry" and "Keystore View".
Whenever I send a message through the channel I am getting though an error during the SSL handshake: Decrypt error.
Below is the SSL debug log
ssl_debug(15): Sending v3 client_hello message to services.bloomberg.com:443, requesting version 3.1...
ssl_debug(15): Received v3 server_hello handshake message.
ssl_debug(15): Server selected SSL version 3.1.
ssl_debug(15): Server created new session 81:ED:F8:61:3B:51:8E:70...
ssl_debug(15): CipherSuite selected by server: TLS_RSA_WITH_AES_256_CBC_SHA
ssl_debug(15): CompressionMethod selected by server: NULL
ssl_debug(15): Server does not supports secure renegotiation.
ssl_debug(15): Received certificate handshake message with server certificate.
ssl_debug(15): Server sent a 2048 bit RSA certificate, chain has 3 elements.
ssl_debug(15): ChainVerifier: No trusted certificate found, OK anyway.
ssl_debug(15): Received certificate_request handshake message.
ssl_debug(15): Accepted certificate types: RSA, DSA
ssl_debug(15): Accepted certificate authorities:
ssl_debug(15):   CN=XXXXXXXXXXXXXXXXXXXXXXXX
ssl_debug(15):   CN=VeriSign Class 3 International Server CA - G3,OU=Terms of use at https://www.verisign.com/rpa (c)10,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(15):   CN=VeriSign Class 3 Public Primary Certification Authority - G5,OU=(c) 2006 VeriSign, Inc. - For authorized use only,OU=VeriSign Trust Network,O=VeriSign, Inc.,C=US
ssl_debug(15): Received server_hello_done handshake message.
ssl_debug(15): Sending certificate handshake message with RSA client certificate...
ssl_debug(15): Sending client_key_exchange handshake...
ssl_debug(15): Sending certificate_verify handshake message...
ssl_debug(15): Sending change_cipher_spec message...
ssl_debug(15): Sending finished message...
ssl_debug(15): Received alert message: Alert Fatal: decrypt error
ssl_debug(15): SSLException while handshaking: Peer sent alert: Alert Fatal: decrypt error
ssl_debug(15): Shutting down SSL layer...
My first assumption was that it might be caused by missing public key of other side's server in the TrustedCAs view. Now I have assured that we have this key installed (although I am currious why there is still the "ChainVerifier: No trusted certificate found" message in the log).
Does somebody have an idea what could cause this SSL handshake failure?
Best regards,
Maxim

The XPI inspector gave more understanding of the situation. It shows which certificates the remote server is sending, which client certificate is used for authentication and many other topics. Interesting enough the XPI inspector shows that PI trusts the server key whereas the NWA log at the very same time tells that it doesn't. I have posted an OSS message asking to explain why there is this discrepancy.

I have encountered the new error "Fatal internal error fpinit.cpp line 7398

I get the error message "Fatal internal error fpinit.cpp line 7398".
I use:
TestStand 2.0
LabView 7.1
Vision 7.1
uEye USb Camera
I've included into my TestStand programm some new steps that control the uEye USB Camera.
I use following steps (all steps written in LabView):
- Initialze Camera
- Wait
- Close Camera
- Wait
I have the settings "Load dynamically" in TestStand"
If I use also the setting "Unload after sequence executes" and start the sequence I get somtimes a LabView error after running the Step for the Camera initialization. LabView is sometimes immediatlly closed. This happen at leased after 10 turns/starts of the programm. If I use the loop functions "Loop on selected steps" it happen only sometimes at the first loop. The initialize Camera Step is every time pass, if TestStand try to run the next step I get a error.( Sometimes I get also the message ActiveX Server got lost)
I detected also that sometimes in this case a constant in a other vi is emty.
Normally I use the setting "Unload when sequence file is closed" then I have the problem only sometimes at the first turn.
If the initialize Camera step is succesfull I have no problem with further camera steps.
Regards
Alexander
Attachments:
lvlog02-18-10-09-34-10.txt ‏1 KB
Copy of Error.jpg ‏76 KB
Copy of Error2.jpg ‏42 KB

Hi Alex,
I'd suggest to replace all ctl. with new ones.
Perhaps one of them is corrupt.
You will find a documentation about preferred execution system
in the LabVIEW help. I also attached this files.
Regards
DianaS
Attachments:
help1.gif ‏37 KB
help2.gif ‏11 KB

Solaris Studio 12.3 demangle fatal internal error: information lost in character quoting

Hello,
I have run into a problem with the Solaris Studio 12.3 compiler when building one source file that makes use of the open source Eigen library. The compilation fails with the error:
demangle fatal internal error: information lost in character quoting
CC: fbe failed for CSeasonalComponent.cc
The full command that fails is:
CC -c -o .objs/CSeasonalComponent.o -m64 -g3 -fsimple=1 -O4 -xbuiltin=%all -xlibmil -xlibmopt -xarch=sse3 -xchip=nehalem -nofstore -xalias_level=compatible -features=extensions -errtags +w -erroff=anonnotype,anonstruct,badargtype2w,hidef,notemsource,wbadasg -library=Crun -library=no%Cstd -KPIC -mt -I/usr/local/stdcxx/include -I/usr/include -I/usr/local/include -DSOLARIS -D_POSIX_PTHREAD_SEMANTICS -D_RWSTD_NO_STRING_MUTEX -D_RWSTD_MINIMUM_STRING_CAPACITY=22 -D_RWSTD_NO_LIST_NODE_BUFFER -DBOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS -DEIGEN_MPL2_ONLY -DEIGEN_DONT_USE_RESTRICT_KEYWORD -DNDEBUG -I/export/home/dave/source/local/include -I/usr/local/include/boost-1_54 CSeasonalComponent.cc
The problem goes away if the -g3 flag is removed. Replacing -g3 with -g0 does not help - the same fatal error occurs. (Removing the -g0/-g3 options has the effect of not passing a -dbgfile option to the fbe program, and this appears to be what avoids the problem.)
The information in this question is from a Solaris x86 machine, although the same "demangle fatal internal error: information lost in character quoting" also occurs on SPARC with the same source file and similar (although obviously not identical) compiler options.
The result of running the CC command that fails with the -dryrun option added is this:
### CC: Note: NLSPATH = /opt/solarisstudio12.3/prod/bin/../lib/locale/%L/LC_MESSAGES/%N.cat:/opt/solarisstudio12.3/prod/bin/../../lib/locale/%L/LC_MESSAGES/%N.cat
###     command line files and options (expanded):
### -dryrun -c -o.objs/CSeasonalComponent.o -m64 -g3 -fsimple=1 -O4 -xbuiltin=%all -xlibmil -xlibmopt -xarch=sse3 -xchip=nehalem -nofstore -xalias_level=compatible -features=extensions -errtags=yes +w -erroff=anonnotype,anonstruct,badargtype2w,hidef,notemsource,wbadasg -library=Crun -xcode=pic32 -mt=yes -I/usr/local/stdcxx/include -I/usr/include -I/usr/local/include -DSOLARIS -D_POSIX_PTHREAD_SEMANTICS -D_RWSTD_NO_STRING_MUTEX -D_RWSTD_MINIMUM_STRING_CAPACITY=22 -D_RWSTD_NO_LIST_NODE_BUFFER -DBOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS -DEIGEN_MPL2_ONLY -DEIGEN_DONT_USE_RESTRICT_KEYWORD -DNDEBUG -I/export/home/dave/source/local/include -I/usr/local/include/boost-1_54 CSeasonalComponent.cc
/opt/solarisstudio12.3/prod/bin/ccfe -xarch=amd64 -D__SunOS_5_10 -D__SUNPRO_CC=0x5120 -D__unix -D__SVR4 -D__sun -D__SunOS -D__x86_64 -D__x86_64__ -D__amd64 -D__amd64__ -D_LP64 -D__LP64__ -D__BUILTIN_VA_STRUCT -Dunix -Dsun -D_REENTRANT -D__SUN_PREFETCH -D__SUNPRO_CC_COMPAT=5 -I/usr/local/stdcxx/include -I/usr/include -I/usr/local/include -I/export/home/dave/source/local/include -I/usr/local/include/boost-1_54 -I-xbuiltin -I/opt/solarisstudio12.3/prod/include/CC -I/opt/solarisstudio12.3/prod/include/cc -DSOLARIS -D_POSIX_PTHREAD_SEMANTICS -D_RWSTD_NO_STRING_MUTEX -D_RWSTD_MINIMUM_STRING_CAPACITY=22 -D_RWSTD_NO_LIST_NODE_BUFFER -DBOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS -DEIGEN_MPL2_ONLY -DEIGEN_DONT_USE_RESTRICT_KEYWORD -DNDEBUG -ptf /tmp/ccfe.04.%1.%2 -features=extensions -ptx /opt/solarisstudio12.3/prod/bin/CC -ptk "-dryrun -c -m64 -g3 -fsimple=1 -O4 -xbuiltin=%all -xlibmil -xlibmopt -xarch=sse3 -xchip=nehalem -nofstore -xalias_level=compatible -features=extensions -errtags=yes +w -erroff=anonnotype,anonstruct,badargtype2w,hidef,notemsource,wbadasg -library=Crun -library=no%Cstd -xcode=pic32 -mt=yes -I/usr/local/stdcxx/include -I/usr/include -I/usr/local/include -DSOLARIS -D_POSIX_PTHREAD_SEMANTICS -D_RWSTD_NO_STRING_MUTEX -D_RWSTD_MINIMUM_STRING_CAPACITY='22' -D_RWSTD_NO_LIST_NODE_BUFFER -DBOOST_MATH_NO_LONG_DOUBLE_MATH_FUNCTIONS -DEIGEN_MPL2_ONLY -DEIGEN_DONT_USE_RESTRICT_KEYWORD -DNDEBUG -I/export/home/dave/source/local/include -I/usr/local/include/boost-1_54 " -compat=5 -g -xdebuginfo=macro -xdbggen=no%stabs+dwarf2+usedonly -xF=%none -xbuiltin=%all -pic -xldscope=global -xivdep=loop -xalias_level=layout -xdepend -O4 -errtags -erroff=anonnotype,anonstruct,badargtype2w,hidef,notemsource,wbadasg +w CSeasonalComponent.cc -ptb .objs/CSeasonalComponent.o -o /tmp/ccfe.01.ir -s /tmp/ccfe.02.sd 2> /tmp/ccfe.03.err
/opt/solarisstudio12.3/prod/bin/iropt -Qy -O4 -xarch=sse3 -m64 -xchip=nehalem -xcache=generic -fsimple=1 -g -depend -mt -k -xalias_level=layout -xbuiltin=%all -xlibmopt -xprefetch=auto,explicit -xprefetch_level=1 -xprefetch_auto_type=no%indirect_array_access -xvector=no%lib,simd -F -o /tmp/iropt.05.ir -is /tmp/ccfe.02.sd /tmp/ccfe.01.ir 2> /tmp/iropt.06.err
rm /tmp/ccfe.01.ir
/opt/solarisstudio12.3/prod/bin/c++filt -filt=no%stdlib < /tmp/iropt.06.err >> /tmp/ccfe.03.err
rm /tmp/iropt.06.err
/opt/solarisstudio12.3/prod/bin/stdlibfilt -stderr < /tmp/ccfe.03.err
rm /tmp/ccfe.03.err
/opt/solarisstudio12.3/prod/bin/ir2hf -Qy -g -O4 -xbuiltin=%all -m64 /tmp/iropt.05.ir /tmp/ccfe.02.sd /tmp/ir2hf.07.hf
rm /tmp/ccfe.02.sd
rm /tmp/iropt.05.ir
/opt/solarisstudio12.3/prod/bin/ube -Qy -verbose -iropt -O4 -comdat -m64 -xarch=sse3 -xchip=nehalem -xcache=generic -xannotate=yes -il /opt/solarisstudio12.3/prod/lib/amd64/libm.il -fsimple=1 -ZW -g -xalias_level=layout -PIC -xbuiltin=%all -N -xprefetch=auto,explicit -xprefetch_level=1 -xthreadvar=dynamic -mt -fbe /opt/solarisstudio12.3/prod/bin/fbe -ipo .objs/CSeasonalComponent.o -dbgfile /tmp/ube.09.dbg -S /tmp/ube.08.s /tmp/ir2hf.07.hf
rm /tmp/ir2hf.07.hf
/opt/solarisstudio12.3/prod/bin/fbe -Qy -xarch=amd64 -xchip=nehalem -warn=%none -o .objs/CSeasonalComponent.o /tmp/ube.08.s -dbgfile /tmp/ube.09.dbg
rm /tmp/ube.08.s
rm /tmp/ube.09.dbg
Running the CC command with the -keeptmp option added leaves these files in /tmp:
-rw-rw-r--   1 dave     dev            0 Dec 11 16:20 /tmp/ccfe.1386778859.8273.03.err
-rw-rw-r--   1 dave     dev      45679331 Dec 11 16:21 /tmp/ccfe.1386778859.8273.01.ir
-rw-rw-r--   1 dave     dev            0 Dec 11 16:21 /tmp/iropt.1386778859.8273.06.err
-rw-rw-r--   1 dave     dev       393220 Dec 11 16:21 /tmp/ccfe.1386778859.8273.02.sd
-rw-rw-r--   1 dave     dev      47820727 Dec 11 16:21 /tmp/iropt.1386778859.8273.05.ir
-rw-rw-r--   1 dave     dev      60490992 Dec 11 16:21 /tmp/ir2hf.1386778859.8273.07.hf
-rw-rw-r--   1 dave     dev      22377791 Dec 11 16:21 /tmp/ube.1386778859.8273.09.dbg
-rw-rw-r--   1 dave     dev      8915850 Dec 11 16:21 /tmp/ube.1386778859.8273.08.s
Finally, creating an fbe command similar to the one from the dry run output using the last two files in /tmp with the -V option added as follows:
/opt/solarisstudio12.3/prod/bin/fbe -V -Qy -xarch=amd64 -xchip=nehalem -warn=%none -o .objs/CSeasonalComponent.o /tmp/ube.1386778859.8273.08.s -dbgfile /tmp/ube.1386778859.8273.09.dbg
results in this:
as: Sun Compiler Common 12.3 SunOS_i386 2011/11/16
demangle fatal internal error: information lost in character quoting
I would be happy to provide the /tmp/ube.1386778859.8273.08.s and /tmp/ube.1386778859.8273.09.dbg files to assist with reproduction of this problem if anyone is interested.

The problem with creating a simple test case that doesn't rely on Boost or Eigen is that the error message is so vague that there's no hint about where to start. The pre-processed source of the file that causes the problem is 4.7MB so trying to chop that down without any clue as to what's relevant is going to be very hard.
You could do everyone a favour if future internal error messages contained at least some information about what caused the problem. I know they're not supposed to happen at all, but clearly they occasionally do. For example, instead of:
demangle fatal internal error: information lost in character quoting
something like:
demangle fatal internal error: information lost in character quoting: corrupt symbol is __1cFEigenPPlainObjectBase4n0AGMatrix4CdIBiBiAIBiB___KresizeLike4n0AOGeneralProduct4n0AFBlock4Ckn0AGMatrix4CdIBIB_"""_oops
Then that would give somebody trying to report the problem or change their code to avoid it a starting point for where to look.
Anyway, I've worked around the problem by changing -g3 in the CXXFLAGS in the Makefile to `test $< = CSeasonalComponent.cc || echo -g3` which avoids the error. And hopefully like you say it's a known problem that's already fixed in the next version of Solaris Studio.

Fatal Internal Error : "OMUDClassMgr.cpp". Line 1128

I received the following message:
Fatal Internal Error : "OMUDClassMgr.cpp", 1128
LabVIEW version 8.2.1
I was trying to build an application using the application builder.
Has anyone else had this issue? What needs to be done to fix this.

Hello,
This was reported to R&D (#4ALB7O89) for further investigation. Are you able to reproduce this problem with the same VI? Are you able to build an application with a simple VI?
Regards,
Elizabeth S.
Applications Engineer
National Instruments

Fatal Communication Error

Hello, everyone.
I am fairly new to the world of SQL server, so I apologize for any newbie errors in my question. I am also not sure if this is an SQL, IIS, or Windows Server issue.
The Environment:
One physical server running Hyper-V
Physical server is acting as domain controller, Hyper-v host and DNS server
All servers are part of the same domain.
Server version is 2012 R2 in all instances.
SQL version is 2014 in all instances.
.NET version is 4.5
All software is fully updated.
The Virtual Servers:
SQL Server
IIS Web Server
Test Server with IIS and SQL
The Problem:
The IIS Web Server cannot connect to the SQL Server without the application pool crashing.
The SQL Server logs show the login from the web server was successful.
The web server’s event logs show a “fatal communication error with the Windows Process Activation service.”
Other Facts:
When the IIS server and SQL server are on the same “machine” (the test server mentioned above) there are no issues at all – everything runs normally.
The website code is identical in both cases, as is the SQL configuration, including users and permissions.
If the connection on the test (previously working) is changed to connect to the standalone SQL server, the problem triggers, the app pool crashes, and the error message in the event log is the same as in the standalone web server.
For testing, the firewalls have been turned off on all servers and it makes no difference.
Windows authentication and SQL authentication both have the same results.
Using a standalone UDL file, a connection CAN be made to the SQL server from any other server, including the IIS Web Server where the app. pool crashes.
I realize I am no providing actual examples, but based on the information above, I am hoping to get some direction on where to look for a problem. Most of the information I have found on the error deals with Sharepoint, which is not a variable in my case.
Since the firewalls have been turned off, the problem only happens when attempting to connect to SQL from an outside server, and only happens through IIS, I am at a loss on what else to check.
Thank you in advance for any relevant advice.

Hello,
By your description, it sounds like an issue with the IIS server. The fact you can connect to SQL Server using all methods except through IIS (where it crashes) means that connectivity is good and SQL Server isn't throwing any errors. My other thought is
that there may be an issue with DNS and the way you have the virtual switches configured with the host.
Unfortunately I don't know all that much about IIS or Hyper-V specific host configurations for something such as this. Someone here may be able to help you further, or it could be moved the IIS/Hyper-V specific forums. I'd be willing to continue to help
out from the SQL Server side if that was to become the case.
Sean Gallardy | Blog |
Twitter

ORA-01280: Fatal LogMiner Error in DBA_CAPTURE.

I setup a downstream real time apply replication with oracle instructions. It works fine for a few days. I changed the mount point (file system) of the database files and redo log files for source database, with a regular shutdown and startup. After that, I got error message at DBA_CAPTURE of downstream database:
ORA-01280: Fatal LogMiner Error
And corresponding error in alert log file:
ORA-00600: internal error code, arguments: [krvxbpx20], [1], [242], [37], [16], [], [], []
Thu Apr 2 00:39:02 2009
TLCR process death detected. Shutting down TLCR
Thu Apr 2 00:39:04 2009
Streams CAPTURE C001 with pid=35, OS id=21145 stopped
Thu Apr 2 00:39:04 2009
Errors in file /oracle/admin/hcarp/bdump/hcarp_c001_21145.trc:
ORA-01280: Fatal LogMiner Error.
I am not sure if the source db reboot can cause this. I will appreciate if anybody can let me know
1. What cause of this?
2. How to prevent this from happening?
3. What to do to recover/fix?
====================================
Here is major part of the trace file /oracle/admin/hcarp/bdump/hcarp_c001_21145.trc:
(source DB: DXP1P. Downstream DB: HCARP)
Unix process pid: 21145, image: oracle@fx1db01 (C001)
*** 2009-03-25 17:56:58.472
*** SERVICE NAME:(SYS$USERS) 2009-03-25 17:56:58.453
*** SESSION ID:(413.68) 2009-03-25 17:56:58.453
*** 2009-04-02 00:39:02.554
knlc.c:2619: KRVX_CHECK_ERROR retval 205
*** 2009-04-02 00:39:02.566
Begin knlcDumpCapCtx:*******************************************
Error 1280 : ORA-01280: Fatal LogMiner Error.
Capture Name: REAL_TIME_CAPTURE : Instantiation#: 1
*** 2009-04-02 00:39:02.566
++++ Begin KNST dump for Sid: 413 Serial#: 68
Init Time: 03/25/2009 17:55:35
++++Begin KNSTCAP dump for : REAL_TIME_CAPTURE
Capture#: 1 Logminer_Id: 1 State: CAPTURING CHANGES [ 04/02/2009 00:38:59]
Capture_Message_Number: 0x0003.8ae9479a [15215445914]
Capture_Message_Create_Time: 04/02/2009 00:32:46
Enqueue_Message_Number: 0x0003.8ae27ad3 [15215000275]
Enqueue_Message_Create_Time: 01/01/1988 00:00:00
Total_Messages_Captured: 116442
Total_Messages_Created: 118344 [ 04/02/2009 00:38:59]
Total_Messages_Enqueued: 1457 [ 03/27/2009 12:33:08]
Total_Full_Evaluations: 471
Elapsed_Capture_Time: 55956708 Elapsed_Rule_Time: 17
Elapsed_Enqueue_Time: 141 Elapsed_Lcr_Time: 864
Elapsed_Redo_Wait_Time: 6937736 Elapsed_Pause_Time: 0
++++End KNSTCAP dump
++++ End KNST DUMP
+++ Begin DBA_CAPTURE dump for: REAL_TIME_CAPTURE
Capture_Type: DOWNSTREAM
Version: 10.2.0.4.0
Source_Database: DXP1P
Use_Database_Link: YES
Logminer_Id: 1 Logfile_Assignment: IMPLICIT
Status: ENABLED
First_Scn: 0x0003.8adf5aa5 [15214795429]
Start_Scn: 0x0003.8adf5aa5 [15214795429]
Captured_Scn: 0x0003.8ae8f942 [15215425858]
Applied_Scn: 0x0003.8ae8f942 [15215425858]
Last_Enqueued_Scn: 0x0003.8ae27ad3 [15215000275]
Capture_User: STRMADMIN
Queue: STRMADMIN.STREAMS_QUEUE
Rule_Set_Name[+]: "STRMADMIN"."RULESET$_11"
Checkpoint_Retention_Time: 60
+++ End DBA_CAPTURE dump
+++ Begin DBA_CAPTURE_PARAMETERS dump for: REAL_TIME_CAPTURE
PARALLELISM = 1 Set_by_User: NO
STARTUP_SECONDS = 0 Set_by_User: NO
TRACE_LEVEL = 0 Set_by_User: NO
TIME_LIMIT = -1 Set_by_User: NO
MESSAGE_LIMIT = -1 Set_by_User: NO
MAXIMUM_SCN = 0xffff.ffffffff [281474976710655] Set_by_User: NO
WRITE_ALERT_LOG = TRUE Set_by_User: NO
DISABLE_ON_LIMIT = FALSE Set_by_User: NO
DOWNSTREAM_REAL_TIME_MINE = TRUE Set_by_User: YES
+++ End DBA_CAPTURE_PARAMETERS dump
+++ Begin DBA_CAPTURE_EXTRA_ATTRIBUTES dump for: REAL_TIME_CAPTURE
+++ End DBA_CAPTURE_EXTRA_ATTRIBUTES dump
++ LogMiner Session Dump Begin::
SessionId: 1 SessionName: REAL_TIME_CAPTURE
Start SCN: 0x0000.00000000 [0]
End SCN: 0x0000.00000000 [0]
Processed SCN: 0x0003.8ae947a7 [15215445927]
Prepared SCN: 0x0003.8ae94897 [15215446167]
Read SCN: 0x0003.8ae948b1 [15215446193]
Spill SCN: 0x0000.00000000 [0]
Resume SCN: 0x0000.00000000 [0]
Branch SCN: 0x0000.00000000 [0]
Branch Time: 01/01/1988 00:00:00
ResetLog SCN: 0x0003.8a502ab3 [15205411507]
ResetLog Time: 03/06/2009 23:58:56
DB ID: 1669710455 Global DB Name: DXP1P
krvxvtm: Enabled threads: 1
Current Thread Id: 1, Thread State 0x02
Current Log Seqn: 243, Current Thrd Scn: 0x0003.8ae948b1 [15215446193]
Current Session State: 0x0, Current LM Compat: 0xa200400
Flags: 0x3fa102d0, Real Time Apply is On
+++ Additional Capture Information:
Capture Flags: 325
Logminer Start SCN: 0x0003.8adf5aa5 [15214795429]
Enqueue Filter SCN: 0x0003.8adf5aa5 [15214795429]
Low SCN: 0x0003.8ae9479a [15215445914]
Capture From Date: 01/01/1988 00:00:00
Capture To Date: 01/01/1988 00:00:00
Restart Capture Flag: NO
Ping Pending: YES
Buffered Txn Count: 0
-- Xid Hash entry --
-- LOB Hash entry --
-- No TRIM LCR --
Unsupported Reason: 14
--- LCR Dump not possible ---
End knlcDumpCapCtx:*********************************************
*** 2009-04-02 00:39:02.569
error 1280 in STREAMS process
ORA-01280: Fatal LogMiner Error.
OPIRIP: Uncaught error 447. Error stack:
ORA-00447: fatal error in background process
ORA-01280: Fatal LogMiner Error.
=====================================================
Thanks!

Look up Bug 6022014 at metlink.

Reported Fatal Hardware Error to Disk Utility

I see the following message in my Power Book G4 Disk Utility:
"This drive has Reported Fatal Hardware Error to Disk Utility. If drive has not failed completely, back up as much data as you can and then replace it with a new drive."
I already made a back up my Home folder to my external HD. The install disk utility reports the same and has grey the repair uptions.
The spinning beachball appears constantly when using Safari and iTunes. What should I do?

If your Mac is no longer under the standard 1-yr warranty period or under the 3-yr extended warranty if you purchased the AppleCare extended warranty for your PB, you need to purchase a new internal hard drive that is compatible with your Mac model. This is something you can install yourself or take your Mac to an Apple authorized repair facility to purchase and have a new internal hard drive installed.
The repair facility should include re-installing whichever OX version and all software that was pre-installed and shipped with this Mac when purchased new. If this wasn't Tiger and you purchased a Tiger retail install package, you can re-install the Tiger upgrade yourself and then replace all data from your backup on the new hard drive.

Fatal Message Error

Similar Messages

Maybe you are looking for