Load error code 9 - unable to open V7.0 work on V6.1

Work done on Labview version 7.0 was unable to be opened on version
6.1. Please let me know what I need to do.

There is an option in LV 7 to save vi under a previous version. Look
under File - Save With Options - Save for Previous 6.1. This will
save the vi so that it can be opened with LV 6.1.

Similar Messages

ID CS3 "Error Code 5" Unable to open, file damaged beyond recovery. HELP!

System: Apple Dual 500 Mhz PowerPC G4, 1.75 GB SDRAM, Mac OSX 10.4.11.
I have a 36pg ID CS3 document, which is over 2gb because of embedded images. Workflow: create doc using links; when finished, embed all images then unembed to new folder to consolidate. then simply resave the ID CS3 file using the new links. sadly, having embedded, i was unable to save. so, i closed without saving. Now i am unable to open the file.
no problems before embedding, now get "error code 5, unable to open..."
I am painfully aware (now) that this is a bad workflow, as am i aware of several ways to improve this workflow. I do not need advice on a better workflow, i already know i did a stupid thing. i need help on how to recover the damaged file. quick. please. :)
does anyone have a workaround?

Thanks for the tip, Bob. i spoke with a marketing guy at Markzware who asked me to forward it on, he was kind and helpful.

Load error code 3 unable to load front panel

Hi all,
Wrote a vi in 8.6 and saved it for 8.5 for collaborators. When they run it up pops the error code 3 unable to load front panel. Memory full. see attached picture.
Has anyone any suggestions as to how to fix this?
Regards,
leeser
Attachments:
labview error code 3.png ‏51 KB

Hi guys,
Thanks for the comments,
Attached is the code (zipped). Excuse the bulkiness of the block diagrams. It basically controls a rotation stage and makes an avi at specific times/angles. The motor stage is ActiveX controlled.
As I don't have access to the hardware I am writing semi-blind. However, when I did visit them and had a quick look at the code I could get it to work by quickly including the subvis into a new main vi and obviously compiling it in 8.5. (may be onto something here!)
Different versions of the labVIEW -> doing a group a favour; I have v8.6 they have v8.5, wrote it in v8.6 saved it for v8.5. I don't have v 8.5. I also have v 8.2.1 on a different machine. Saved it for v8.2.1 and it opened no problem in 8.2.1. Will send this version on and see how they get on. More likely to be forward compatible???
I agree that the optimal situation is 1) use the same version of labview and/or
2) they get someone to do their coding on-site!!!!
I think the corrupt front panel object could be true given that I could get it to work when the subvis were included in a new main vi on-site.
so versions 8.6, 8.5 and 8.2 attached.....
regards,
Leeser
Attachments:
rotation_control.zip ‏178 KB
rotation_control_v8.6.zip ‏60 KB
NCLA_rot_usb_v8.5 Folder.zip ‏141 KB

ORA-00600: internal error code, arguments: [unable to load XDB library]

hi everybody ;
i have 9.2.0.7 db runs on SLES9 on host A. and i take full rman database backup to make a new database on different host ( host B ) with different file structure. ( sid is the same ) i had already 1 database on host B. after this duplicate now there are 2 database on host B.
i take daily full database rman backup on the new host for my new database and there is no problem. when i try to take extra full export backup i get an error ;
Dynamic link error: libxdb.so: cannot open shared object file: No such file or directory
*** 2010-08-05 09:46:12.868
ksedmp: internal or fatal error
ORA-00600: internal error code, arguments: [unable to load XDB library], [], [], [], [], [], [], []
as i search ; i have to stop the database and listener and set the LD_LIBRARY_PATH variable. how can i make this without make any mistake for the first database runs on Host B.
because 2 database must be up and running on host B. can you explaın these operation step by step ?
thank you ....

craft wrote:
any idea ?
>any idea ?
your database is out off support you should consider to upgrade. ORA-00600 indicate for bug

Failed to Open FR report With Error code 500 - 'unable to process request'

I am running a load test against PBCS service. The service is load-balanced with 2 managed servers : EPMServer0 and EPMServer1
When I put the loads with 60 VUs -- all visiting FR reports, the service runs without error. But when the VU# increased to 90, it began to respond with Error code 500 - 'unable to process request'.
I tried to correlate the FRLogging logs to the errors, and found during the time those error happens, there are logs like this:
>>>>>>>>>>>>>>>>>>>>>>>>>>
[2013-09-27T05:21:29.325+00:00] [EPMServer0] [WARNING] [00365] [oracle.EPMFR.core] [tid: [ACTIVE].ExecuteThread: '5' for queue: 'weblogic.kernel.Default (self-tuning)'] [userId: sysname50134114.PerfUser0439] [ecid: 004tpQ^VFHT7m3RLIYDCif0007a30002bD,0:2:1:1] [APP: FINANCIALREPORTING#11.1.2.0] [SRC_CLASS: com.hyperion.reporting.connection.UserConnection] [SRC_METHOD: openConnection] User authentication information is invalid. Unable to connect to datasource.[[
com.hyperion.reporting.util.HyperionReportException: Error connecting to database connection Vision:Plan1: Failed to sync with user provisioning.com.hyperion.planning.HspRuntimeException
        at com.hyperion.reporting.connection.UserConnection.openConnection(Unknown Source)
        at com.hyperion.reporting.connection.UserConnection.openConnection(Unknown Source)
        at com.hyperion.reporting.connection.UserConnection.<init>(Unknown Source)
        at com.hyperion.reporting.connection.ConnectionManager.getConnection(Unknown Source)
        at com.hyperion.reporting.connection.ConnectionManager.getCube(Unknown Source)
        at com.hyperion.reporting.connection.ConnectionManager.getCube(Unknown Source)
        at com.hyperion.reporting.webviewer.WebDynamicReport.validateDatasources(Unknown Source)
    at jsp_servlet._modules._com._hyperion._reporting._web._reportviewer.__hrhtmlreport._jspService(__hrhtmlreport.java:1999)
        at weblogic.servlet.jsp.JspBase.service(JspBase.java:34)
        at weblogic.servlet.internal.StubSecurityHelper$ServletServiceAction.run(StubSecurityHelper.java:227)
        at weblogic.servlet.internal.StubSecurityHelper.invokeServlet(StubSecurityHelper.java:125)
        at weblogic.servlet.internal.ServletStubImpl.execute(ServletStubImpl.java:301)
        at weblogic.servlet.internal.TailFilter.doFilter(TailFilter.java:26)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at com.hyperion.reporting.webviewer.HRSecurePagesFilter.needAuthentication(Unknown Source)
        at com.hyperion.reporting.webviewer.HRSecurePagesFilter.doFilter(Unknown Source)
        at weblogic.servlet.internal.FilterChainImpl.doFilter(FilterChainImpl.java:56)
        at com.hyperion.reporting.webviewer.FRClusterHelper.doFilter(Unknown Source)
>>>>>>>>>>>>>>>>>>>>>>>>>
It looks like the servlet failed to open the datasource connection while handling the FR requests. But there are several data sources. My questions are:
1) Which datasource is corresponding to the issue? Is it EPMSystemRegistry?
2) What is the recommended configuration for the connection pool max capacity setting? -- current setting for EPMSystemRegistry is 30
3) Whether it could be a connection leak problem as only 90 concurrent end user is visiting and it failed to connect?
Thanks,
Ellick Lu
Type
JNDI Name
Targets
aif_datasource
Generic
jdbc/aif_datasource
EPMServer
calc_datasource
Generic
jdbc/calc_datasource
EPMServer
EPMSystemRegistry
Generic
jdbc/EPMSystemRegistry
EPMServer
odiMasterRepository
Generic
jdbc/odiMasterRepository
EPMServer
planning_datasource
Generic
jdbc/planning_datasource
EPMServer
raframework_datasource
Generic
jdbc/raframework_datasource
EPMServer

It is checking for Database connection in Workspace. Check Editing Database Connections
Can those users login to Planning? Do they have correct security setup (I guess not)
Regards
Celvin
http://www.orahyplabs.com

Load error code 11 when attempting to open .vi from library

Hello,
Recently a colleague sent me a .llb containing a VI and sub-VIs of a program needed for my research. The VI opens correctly but none of the sub-VIs can be found by it and when I attempt to open the sub-VIs I get load error code 11: VI version (6.0) cannot be converted to the current Labview verstion (8.5.1) because is has no block diagram.
I am running Vista with 8.5.1 and attempting to open a library of version 6.0. I do not know what OS the library was compiled on. (Linux is a possibility) The colleague who sent me the program does not know either, as he recieved it from another colleague whom he is no longer in contact with.
I am fairly certain the library was saved with block diagrams, so I do not think that is the source of the error.
Does anyone know what might be a way to get these sub-VIs working?

Okay,
File posted. Someone please tell me if this has a block diagram on it.
Attachments:
Find First Error.vi ‏24 KB

Labview load error code 15 preventing me from opening the VI

I'm having some problems opening a particular VI. I get an error called: "Labview Load Error Code 15; cannot load default data." This VI cannot be opened, but I would like to somehow get into it (some important codes are in it). The Labview version is 6.1 and the system is on a Macintosh G3 with OS 8. Thanks in advance.

It sounds like the VI is corrupt. Are you able to open it another machine or a different version of LabVIEW?

Load error code 3

Hi there!
I'm trying to open VI's of Vision Assistants' plugins into Labview, but I get the message "load error code 3"
I hope somebody helps me!
Gerardo Aragón
I'm using:
Labview Pro 7.1
NI IMAQ Vision 7.1

Gerardo buen día!
Te mando la siguiente liga donde viene explicado el error, que tengas un excelente día!!!
http://forums.ni.com/ni/board/message?board.id=170&message.id=223811
NorSa
NI Applications Engineer Latin America
Para Soporte entra aquí

LabVIEW load error code 10?

Hello..
I have received an .llb file from support at Anritsu, for a Wiltron 56100a Scalar network analyzer. It contains numerous priceless VI's. Unfortunately, when I try to open it, I get an error..
"An error occurred loading VI ''. LabView load error code 10: VI version (3.1) is too old to convert to the current LabView version (6.1)"
Is there any way I can convert this code at all? It would be most valuable! Would it be possible to get ahold of an older labview version, perhaps 4 or 5, convert to that version, then convert to 6.1? We really need these drivers..
Thanks for any suggestions!

Go here
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=0
Click on "become an Enthusiats".
Write a short bio,
Indicate what catagory,
Submit!
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

An error occurred loading VI. LabView load error code 1: LabView load error code %ld: %p"

I have been developing a VI file that has
been working fine, until now. I am using 8.6.
Every time I attempt to open this file
I keep getting:
How do I fix the error code:
Labview: Memory is
full.
An error occurred loading VI. LabView load error code 1:
LabView load error code %ld: %p”
On a separate dialog:
“Not enough memory to complete this
operation.”
I ran VI analyzer which told that the
VI:
One or more errors occurred during
analysis.
Testing errors tab – Vi not loadable
and my file name. At the bottom in the error description I got:
“Error 74. Memory or data structure
corrupt. <my file path> and <file name>.”
Could not be opened.
Is there anything I can do to recover
the file?

Hi kevin_khan,
I went ahead and tried to open it and got the error attached.
Peter T
Applications Engineer
National Instruments
Attachments:
test.png ‏14 KB

LabVIEW load error cod %ld: %p

All of the sudden, when I tried to open a VI, I got an error message that said, "LabVIEW: Resource not found. An error occured loading VI 'VI name.vi". LabVIEW load error code 1: LabVIEW load error code %ld: %p". I tried to revert that particular VI to the previous version through source control, but that didn't help. Does anyone know what I need to do to fix this? Thanks!
Kudos and Accepted as Solution are welcome!

It was fine, and now I can't open the VI. It is possible that I forcefully closed the VI a few times with ctrl+alt+del. The name.vi is the host vi for an fpga application. It interacts with user, calls .NET DLL to communite with a DUT, pass data to/from FPGA, etc.
I had already looked at the link that you posted. Not sure does it apply to me.
Kudos and Accepted as Solution are welcome!

Why I get Labview load error code 16?

"Labview load error code 16 preventing me from opening the VI"
"I'm having some problems opening a particular VI. I get an error called: "Resource not found"; "Labview Load Error Code 16; Could not load data space link information." This VI cannot be opened, but I would like to somehow get into it (some important codes are in it). The Labview version is 7, the size of vi is about 1.08 Mb, and the system is on a Windows 98. Thanks in advance."

Hello James,
Thank you for contacting National Instruments.
Try opening the VI with another version of LabVIEW. You can also try placing the VI as a subVI and then viewing its block diagram.
You're also welcome to post your VI, and we can try to open it up here.
I hope this helps!
Matthew C
Applications Engineer
National Instruments

LabVIEW load error code 1: LabVIEW load error code %Id: %p

One of my VI crashed while trying to save some data to file, I then tried to save the VI afterwards, but message with Out of Memory popped up again and the IV closed down. So now I can´t open my VI, then I try I get the "LabVIEW load error code 1: LabVIEW load error code %Id: %p" message and I have been given no opportunity to recover an older version of the VI then I close down and open LabVIEW again!!! So my VI is lost or what?
This is a huge problem for me, hope someone can help...
Regards
Jesper

Hi Jesper
For the future you should be good with LabVIEW 2012 (Normally realeased after NI Week in Austin in beginning of August). From what I know about this problem it have not been mentioned to be solved in a fixpack before release of LabVIEW 2012.
If you are reading in large files that uses more memory than avaliable and do wan't to avoid LabVIEW from crashing then you could add more RAM to your PC. If you are using Windows 32-bit you could try to edit the boot.ini file for Windows to allow Windows to allocate more memory to LabVIEW as explained in the following article:
Extending Virtual Memory Usage for 32-bit Windows
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/enable_lrg_ad_aware/
You could also try upgrading to Windows 64-bit this will allow much larger memory operations, and Windows 64-bit will let LabVIEW allocate more memory.
To use Source Code Control on your computer you will need:
1) A Source Code Control server with space to store the backup VI's and previous versions on (this can be your own PC). All Source Code Control providers that follow the Microsoft Source Code Control API. We have a list of tools that we have been tested that can be found here (note that some is free and other is not):
Which Third-Party Source Control Providers Can I Use with LabVIEW 8.0 and later?
http://digital.ni.com/public.nsf/websearch/26EC5904169430CE8625706E00743997?OpenDocument
2) After installing the server you need to configure LabVIEW to communicate with this server. In the article below under the section "Configuring LabVIEW to Call the Microsoft SCC API" you can see how to do this:
Software Configuration Management and LabVIEW
http://zone.ni.com/devzone/cda/tut/p/id/4114
3) You are good to go. Source Code Control uses the two most know functions "Commit / Check out." When you Check out a document you will be able to edit it, and when you then commit the changes then it will be saved with a new version number on the server. For each commit you will be able to select "Revert to previous version" to go back and restore a previous commited VI. You can use these functions on the VI it self or as I prefer from the Project Explorer.
Bisides the advantage of being able to restore previous versions, Source Code Control is also a great tool if your are multiple users working on the same project. You will i.e. be able to be 2 or more developers working on the same VI at the same time and then merging your changes to one VI when you are finished.
Best Regards
Anders Rohde
Applications Engineer
National Instruments Denmark

Error code: MapiExceptionJetDatabaseCorruption: Unable to mount database. (hr=0x80004005, ec=-338)

We are on Exchange 2007
We have one database that will not mount. Whenever we try to mount we get the below error
Exchange is unable to mount the database that you specified. Specified database: EXG01\SG3-DB\SG3-DB; Error code: MapiExceptionJetDatabaseCorruption: Unable to mount database. (hr=0x80004005, ec=-338)
I ran the eseutil /mh against the DB & found the database to be in clean shutdown state. I moved all the log files and chk files to another location and tried mounting the DB but the very same error.
Initiating FILE DUMP mode...
         Database: SG3-DB.edb
        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,12
Engine ulVersion: 0x620,12
Created ulVersion: 0x620,12
     DB Signature: Create time:06/07/2011 00:22:54 Rand:482525 Computer:
         cbDbPage: 8192
           dbtime: 3942751903 (0xeb019e9f)
            State: Clean Shutdown
     Log Required: 0-0 (0x0-0x0)
    Log Committed: 0-0 (0x0-0x0)
   Streaming File: No
         Shadowed: Yes
       Last Objid: 877765
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
Please help us on how to clear this error and mount the database.

We are on Exchange 2007
We have one database that will not mount. Whenever we try to mount we get the below error
Exchange is unable to mount the database that you specified. Specified database: EXG01\SG3-DB\SG3-DB; Error code: MapiExceptionJetDatabaseCorruption: Unable to mount database. (hr=0x80004005, ec=-338)
I ran the eseutil /mh against the DB & found the database to be in clean shutdown state. I moved all the log files and chk files to another location and tried mounting the DB but the very same error.
Initiating FILE DUMP mode...
         Database: SG3-DB.edb
        File Type: Database
   Format ulMagic: 0x89abcdef
   Engine ulMagic: 0x89abcdef
Format ulVersion: 0x620,12
Engine ulVersion: 0x620,12
Created ulVersion: 0x620,12
     DB Signature: Create time:06/07/2011 00:22:54 Rand:482525 Computer:
         cbDbPage: 8192
           dbtime: 3942751903 (0xeb019e9f)
            State: Clean Shutdown
     Log Required: 0-0 (0x0-0x0)
    Log Committed: 0-0 (0x0-0x0)
   Streaming File: No
         Shadowed: Yes
       Last Objid: 877765
     Scrub Dbtime: 0 (0x0)
       Scrub Date: 00/00/1900 00:00:00
Please help us on how to clear this error and mount the database.

What can I do about "LabVIEW load error code 38: Failed to uncompress part of the VI."

While attempting to load an executable LabVIEW application for LabVIEW 2009 SP1 on a Windows-XP machine when the following pop-up message occurs. "LabVIEW: Memory or data structure corrupt. An error occurs in loading VI 'NI_Gmath.lblib: Backward Bracket Search.VI'. LabVIEW load error code 38: Failed to uncompress part of the VI. The VI is most likely corrupt." What seems odd is that the same LabVIEW application loads fine when logged on as a privileged user account, but fails to load on a private user account.
Attachments:
2012-07-18 LabVIEW Load error code 38.jpg ‏1314 KB

Here's a thought:
So when something is decompressed, a temp folder is often used.
I have no idea why LabVIEW would be decompressing anything, but I suspect it is trying to put the decompressed file into a temp folder where the user does not have write permissions.
In the .ini file for your executable, you can add a line that specified the location of the temp folder to use:
tmpdir=C:\Temp
On my Win7 machine, the location is:
C:\Users\MyUserName\AppData\Local\Temp
On WinXP, it is probably:
C:\Documents And Settings\YourUserName\local settings\temp
Try changing the tmpdir key in your ini file to something to C:\Temp and see if that helps.
- john

Load error code 9 - unable to open V7.0 work on V6.1

Similar Messages

Maybe you are looking for