Error generated when using Matlab 7.0 with LabVIEW 7.1

The error (1047) states "Server: Inappropriate input array sizen" no matter what the input is. the script works fine without inputs but there seems to be a problem interpreting inputs. I get this error even when I run the scriptnode example for the Matlab script.
Randall Pursley

This is a fixable problem with the older versions of LabVIEW and Matlab, but a new problem with the latest version of Matlab. I have had to 'fix' this problem everytime Matlab upgrades and will probably just have to wait until NI comes out with a new fix to go with Matlab 7.0.
Randall Pursley

Similar Messages

  • Error message when using Spry Data set with XML

    Hi,
    I have what i see as a big problem, might just be me being
    dumm, but here we go.
    When I try to use the feature of spry XML Data Set and insert
    spry table I get error message when trying it in IE 7.
    There are even a problem when I use fireworks automated slide
    show function, where you can choose to use the Spry/XML gallery
    feature.
    The error message I get everytime (incl the auto gallery in
    fireworks) is:
    The tag: "html" doesn't have an attribute: "xmlns:spry" in
    currently active versions.[XHTML 1.0 transitional]
    The tag: "div" doesn't have an attribute: "spry:region" in
    currently active versions.[XHTML 1.0 transitional]
    The tag: "th" doesn't have an attribute: "spry:sort" in
    currently active versions.[XHTML 1.0 transitional]
    and so on.
    What´s wrong?!

    Hello barvid,
    Ok, let's take each problem step by step:
    1. The first error you see in the browser: " Exception while
    loading ..." normally appears when you try to load files that are
    not permitted by the browser security model. This means the XML
    file you try to load is located on a different server than your
    HTML which is not allowed. The browser is not permitting to load
    any files that are not in the same domain as the current page
    because of the complex security risks. You'll have to either get
    the XML file from its original location and save it in your website
    or use a proxy on your web server that should request that file
    from the external server and send it to the browser as an XML from
    the same domain as the HTML origin.
    1.2 The "Exception while loading ..." error you see is a
    generic error and my previous advise is based on my experience. In
    case this is not your scenario you'll have to open the SpryData.js
    and around line 112 you'll see the following code:
    Spry.Debug.reportError("Exception caught while loading " +
    url + ": " + e);
    Please change this line with the following line of code:
    Spry.Debug.reportError("Exception caught while loading " +
    url + ": " + (e.message?e.message:e));
    to obtain a more verbose error message that may clarify the
    reasons of your errors.
    2. The problems you describe are not browser errors but they
    are w3c validation errors. At this point the XHTML standard allows
    every application that define custom namespace attributes to also
    link a DTD to the page so the page to continue to be valid.
    Unfortunately at this point this feature is not correctly supported
    by the FF and IE so we wrote an articles about how you should
    link
    the Spry DTD to your page so the validator understand the
    custom attributes Spry use. You'll find inside the full description
    of the problems and all the technical details you'll need to know
    to solve this issue.
    Regards,
    Cristian

  • Issues when using a Pixelink camera with LabView 9.0

    In my lab, we have a program for video acquisition using LabView and the low level camera functions for Pixelink cameras.  We run into some problems trying to run this program and other demo gui programs that came with the Pixelink SDK.  In our data acquisition program, we have problems with our image coming out all scrambled.  We use the low level functions to obtain a frame from the camera in the from of a vector.  We then reshape the vector into an array and then send the array to a vi that turns it into an image.  When we try to view this image using the standard Labview image viewer, the image comes out all scrambled if the zoom factor is not set to .5 on the image viewer.  The full resolution of the image is supposed to be a 1024x1280 image which when we use the Capture OEM software for the camera provided by Pixelink we can see.  The image that we can see through LabView when we have the correct zoom factor seems to be only the top left quarter of what the entire image is supposed to be.  We also encounter strange problems when we attempt to use the demo programs for labview 8.6 that are provided with the SDK.  When trying to run the simpleGUI.vi, for example, the program connects to the camera just fine.  After you hit play to view an image, the problems start.  The program will play the video for a few seconds until it just freezes up and quits responding.  Labview must be exited and restarted in order for the camera to connect again.  I am not sure if it makes a difference that we are running labview 9.0 on our computers or not.  Any help you have on these issues would be of great help.  Attached are pictures of the scrambled/unscrambled image and of the part of our block diagram for camera control.
    Attachments:
    Incorrectimage.jpg ‏126 KB
    Errorexplanation.jpg ‏543 KB
    correct image.jpg ‏22 KB

    IMAQdx is the driver that National Instruments provides to interface Firewire, GigE and USB cameras (Directshow compliant USB).  This is a licensed driver, so if you don't currently have it, then testing in MAX is not an option. 
    So if I understand correctly, you have the Pixelink software which works fine, but you have Pixelink VI's that are used in LabVIEW, but those do not work correctly?  That to me seems like a driver issue, which I'm not sure how much I can help with since it is not our driver. 
    Do you know what dll's the Pixel link VIs are calling into?  Are they Pixelink dlls?  If so, I would suggest speaking with the manufacturer or perhaps on of our other users has worked with Pixelink before.
    Sorry I can't be much more helpful.
    Tejinder Gill
    National Instruments
    Applications Engineer
    Visit ni.com/gettingstarted for step-by-step help in setting up your system.

  • HELP computer crash when using data translatio​n with labview

    Hi,
    So to explain what I'm doing for starters, I have used DT-Link with DataTrans devices and Labview in the past without any issue. Mainly D/O blocks, A/Os and maybe 1 A/I. So I'm relatively familiar with working with these.
    I began working on a new project that involes a dt9817 using 18 or so D/Os and then they had purchased a 9812(10v) for the 4 A/Is needed. I didn't seem to have any problems setting up the D/Os, in a while loop I referenced the 9812 and put in a write function. Now when I created the A/Is I did it just like I had before for a single A/I. I spent a little time figuring out how to get them to read from the correct port, but eventually figured it out.
    The problem is now that sporadically when the program is running, the computer will go to blue screen and then restart!! The only significant things I have time to see before it restarts are:
    DT9810_x64.sys
    bluescreen error
    code: 50
    I know it has something to do with DT Link as it is almost the only thing in the program and it only goes to bluescreen when the program is running.
    To answer questions:
    Brand new computer. Asus i7 quad core.
    I have tried to repair LV Link multiple times with no success.
    Finally, I'm assuming it is based around a problem with the way I'm sampling the 4 A/I channels, but I can't think of any other way to do it. If some one can help me figure this out, or post an example code for multiple A/I channels into xy graphs I would really appreciate it.
    Thanks in advance,
    Luke

    I just wanted to update this thread. Since having this error I worked out a few things that seem to have made the error more infrequent, however, it is still causing a major issue when the chemists are trying to run and a blue screen is pulled.
    I have gotten to an executable on a few projects and I have seen the error come up on both the development computer and target computers. It has been narrowed down to a problem with the digital outputs, and the LV Link digital output driver. Unfortunately the Data Translation people have been less than helpful, so I was hoping that someone might be able to post some example code to work from.
    This is the crash dump file from the last time I got a blue screen. If it makes a difference, it was taken from a computer with an executable.
    Here is the code that pulls the error.
    Thank you to anyone who can help. I am really stumped at this point.

  • Dreamweaver CC generates one of 3 error messages when using find and replace on Win 8.1 64 bit.

    Dreamweaver CC generates one of 3 error messages when using find and replace is used more than twice in succession. "While executing onLoad in bc_afterSave.htm, the following JavaScript error(s) occurred: At line 188 of file C:\Program Files (x86)\Adobe|Adobe DreamweaverCC|Configuration|Shared|BC\JS\bc_sites.js": out of memory"
    or
    While executing runCommand in File_Save.htm, a JavaScript erroroccurred.
    or
    While exciting getDynamicContent inAdressURL.htm, a Javascript erroroccirred.
    Any thoughts - I end up closing DWCC and reopening. Will work for two additional Find and Replace before the error messaged\s popup again.

    bkaufman43 wrote:
    Thanks Jon. I tried all of those solutions before posting. Same problem. It seems that the problem is tied to DWCC. Do not have the problem when using DW6 on Win8.1. When running DWCC on a Win7 pc, we get the same error message. When running DW6 on Win 7, f&c works fine. It seems to be a bug in DWCC. DWCC works flawlessly on our Macs.
    The same steps apply to DWCC, you just need to choose the CC folders rather than the DWCS4-6 versions that the page talks about. The layout of CC's folders hasn't changed from the older versions which is why, I think, Adobe hasn't updated the troubleshooting page as of yet.
    As Nancy mentions, a 38,500 page site is sort of ridiculously large for a static website, that could be part of the problem, but your response quoted above leads me to think you may have tried the troubleshooting steps in the wrong version of the program. Could you confirm that?

  • Sand Box has stopped working error when using System Exec.vi with wait until completion is true

    I get the following error message in Windows 7 "Sand Box has stopped working" when using System Exec.vi with wait until completion set to true, if I set it to false there is no error message.

    Hello JJVerdi
    mmm well System Exec.vi simulates a DOS command window, can you run the sandbox from the cmd window using the same commands without any errors? 
    you may take a look to this KB, it may be related to your issue:
    http://digital.ni.com/public.nsf/websearch/2393462​BD57B854186256C4F007B706A?OpenDocument
    Regards
    Mart G

  • ERROR MESSAGE WHEN USING PACK COMMAND   Missing file ////presenter.css   Also:  "This course requires JavaScript to be enabled in your browser. Please enable JavaScript, then relaunch the course."  I have Java enabled in all browsers

    ERROR MESSAGE WHEN USING PACK COMMAND   Missing file ////presenter.css    Command then fails
    Also:  "This course requires JavaScript to be enabled in your browser. Please enable JavaScript, then relaunch the course."  I have Java enabled in all browsers
    Thoughts?  Using Presenter 10  Win 8.1  Intel I7  new HP with plenty of memory
                   Thanks

    I had saved one copy as an .asp but then resaved it to .xhtml 
    I'm assuming this is a static web site.  Rename (F2) all your pages with .html or .htm extension. 
    .xhtml is not a valid extension.
    Nancy O.

  • Error message when using FM 'BAPI_BUPA_ADDRESS_CHANGE'.

    I'm continually getting an error message when using FM 'BAPI_BUPA_ADDRESS_CHANGE'. The message being 'Table BAPIADTEL entry to be changed not found in target system'.
    I have looked up this message but all links seem to refer to FM 'BAPI_BUPA_CENTRAL_CHANGE', which I'm not using, and has different parameter settings.
    I'm simply trying to update the telephone number and I'm updating strcuture BAPIADTEL and BAPIADTELX but still the message appears. I know that there is a really simple reason for this, but I have been double-checking everything and experimenting with lots of different areas, but with no effect.
    Has anyone encountered this problem using the specific FM ''BAPI_BUPA_ADDRESS_CHANGE' ?.
    Jason

    Hi Jason,
    In case your database tables had already value for field telephone number, then only the flag should be "U".
    If the telephone number field was empty, and we will try to change it by using the flag as U, it wont work. In this case, we should be using "I".
    I even wrote that before in this post, but somehow I guess the post was locked, and a lot of comments from you and me were not visible apart from the first two. So, I couldnt get any update from you.
    Anyway, its good that its working for you. Thank you for the update.
    Regards,
    Susanta

  • Adobe Air error message when using  PSE 10

    When I try using the tips in PSE 10 I get an error message from Adobe Air stating that it is damaged. Have tried uninstalling and re-installing, but that hasn't helped. I have windows 7

    Okay Jeff, this is as far as I have gotten so far. I'm using Air version 3.2.0.2070.  This is the install log.
    Runtime Installer begin with version 2.6.0.19140 on Windows 7 x86
    Commandline is: -silent -eulaAccepted -programMenu AdobeHelp.air
    Installed runtime (2.6.0.19120) located at C:\Program Files (x86)\Common Files\Adobe AIR
    Invoking Application Installer for combined install
    Launching subprocess with commandline C:\Users\Vette\AppData\Local\Temp\AIRD0CE.tmp\Adobe AIR\Versions\1.0\Adobe AIR Application Installer -runtime C:\Users\Vette\AppData\Local\Temp\AIRD0CE.tmp -silent -withRuntime -url -programMenu -eulaAccepted file:///E:/Adobe%20Photoshop%20Elements%2010/ElementsSTIInstaller/payloads/AdobeHelp/Adob eHelp.air
    Application Installer begin with version 2.6.0.19140 on Windows 7 x86
    Commandline is: -runtime C:\Users\Vette\AppData\Local\Temp\AIRD0CE.tmp -silent -withRuntime -url -programMenu -eulaAccepted file:///E:/Adobe%20Photoshop%20Elements%2010/ElementsSTIInstaller/payloads/AdobeHelp/Adob eHelp.air
    Installed runtime (2.6.0.19120) located at C:\Program Files (x86)\Common Files\Adobe AIR
    Unpackaging file:///E:/Adobe%20Photoshop%20Elements%2010/ElementsSTIInstaller/payloads/AdobeHelp/Adob eHelp.air to C:\Users\Vette\AppData\Local\Temp\flaE4EA.tmp
    Application signature verified
    Unpackaging/validation complete
    No app located for appID 'chc' and pubID '4875E02D9FB21EE389F73B8D1702B320485DF8CE.1'
    Converting unpackaged application to a native installation package in C:\Users\Vette\AppData\Local\Temp\fla71A.tmp
    Native installation package creation succeeded
    Starting silent combined runtime update and app install.
    Updating runtime from version 2.6.0.19120 to version 2.6.0.19140.
    Installing app chc.4875E02D9FB21EE389F73B8D1702B320485DF8CE.1 version 3.5.23 to C:\Program Files (x86)\Adobe  using the source file at file:///E:/Adobe%20Photoshop%20Elements%2010/ElementsSTIInstaller/payloads/AdobeHelp/Adob eHelp.air
    Reinstalling C:\Users\Vette\AppData\Local\Temp\AIRD0CE.tmp\setup.msi
    Installing msi at C:\Users\Vette\AppData\Local\Temp\fla71A.tmp\setup.msi with guid {BD7F1DA3-5EA0-65F8-52B0-5E103FDC045A}
    Application Installer end with exit code 0
    Subprocess app installer succeeded
    Runtime Installer end with exit code 0
    Runtime Installer begin with version 2.6.0.19140 on Windows 7 x86
    Commandline is: -silent "E:\Adobe Photoshop Elements 10\AdobePhotoshopDotcomInspirationBrowser.air"
    Installed runtime (2.6.0.19140) located at C:\Program Files (x86)\Common Files\Adobe AIR
    Invoking Application Installer for combined install
    Launching subprocess with commandline C:\Users\Vette\AppData\Local\Temp\AIR4EA4.tmp\Adobe AIR\Versions\1.0\Adobe AIR Application Installer -runtime C:\Users\Vette\AppData\Local\Temp\AIR4EA4.tmp -silent -withRuntime -url file:///E:/Adobe%20Photoshop%20Elements%2010/AdobePhotoshopDotcomInspirationBrowser.air
    Application Installer begin with version 2.6.0.19140 on Windows 7 x86
    Commandline is: -runtime C:\Users\Vette\AppData\Local\Temp\AIR4EA4.tmp -silent -withRuntime -url file:///E:/Adobe%20Photoshop%20Elements%2010/AdobePhotoshopDotcomInspirationBrowser.air
    Installed runtime (2.6.0.19140) located at C:\Program Files (x86)\Common Files\Adobe AIR
    Unpackaging file:///E:/Adobe%20Photoshop%20Elements%2010/AdobePhotoshopDotcomInspirationBrowser.air to C:\Users\Vette\AppData\Local\Temp\fla634C.tmp
    Application signature verified
    Unpackaging/validation complete
    No app located for appID 'PhotoshopdotcomInspirationBrowser' and pubID '4C35C4D325D350FE0114230CBADCA2DDD0AC8D25.1'
    Converting unpackaged application to a native installation package in C:\Users\Vette\AppData\Local\Temp\fla7325.tmp
    Native installation package creation succeeded
    Starting silent app installation to C:\Program Files (x86)\Adobe. Installing app PhotoshopdotcomInspirationBrowser.4C35C4D325D350FE0114230CBADCA2DDD0AC8D25.1 version 3.07 using the source file at file:///E:/Adobe%20Photoshop%20Elements%2010/AdobePhotoshopDotcomInspirationBrowser.air
    Installing msi at C:\Users\Vette\AppData\Local\Temp\fla7325.tmp\setup.msi with guid {4C184855-B85A-6873-C642-60A58682E721}
    Application Installer end with exit code 0
    Subprocess app installer succeeded
    Runtime Installer end with exit code 0
    Launching subprocess with commandline C:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Resources\Adobe AIR Updater -updatecheck
    Runtime Installer begin with version 2.6.0.19140 on Windows 7 x86
    Commandline is: -updatecheck
    Installed runtime (2.6.0.19140) located at C:\Program Files (x86)\Common Files\Adobe AIR
    Performing pingback request
    Pingback request completed with HTTP status 200
    Starting runtime background update check
    Begin Background update download from http://airdownload.adobe.com/air/3/background/windows/x86/patch/2.6.0.19140/update
    Unpackaging http://airdownload.adobe.com/air/3/background/windows/x86/patch/2.6.0.19140/update to C:\Users\Vette\AppData\Roaming\Adobe\AIR\Updater\Background
    Unpackaging complete
    Download success
    Runtime updated downloaded
    User has selected immediate install of the update
    Starting runtime background update installation
    Launching subprocess with commandline C:\Users\Vette\AppData\Roaming\Adobe\AIR\Updater\Background\updater -update
    Runtime updater successfully launched
    Runtime Installer end with exit code 0
    Runtime Installer begin with version 3.1.0.4880 on Windows 7 x86
    Commandline is: -update
    Installed runtime (2.6.0.19140) located at C:\Program Files (x86)\Common Files\Adobe AIR
    Relaunching with elevation
    Launching subprocess with commandline c:\users\vette\appdata\local\temp\airafa3.tmp\adobe air installer.exe -ei
    Runtime Installer begin with version 3.1.0.4880 on Windows 7 x86
    Commandline is: -stdio
    .\pipe\AIR_704_0 -ei
    Installed runtime (2.6.0.19140) located at C:\Program Files (x86)\Common Files\Adobe AIR
    Starting silent runtime update. Updating runtime from version 2.6.0.19140 to version 3.1.0.4880
    Installing msi at c:\users\vette\appdata\local\temp\airafa3.tmp\setup.msi with guid {FE23D063-934D-4829-A0D8-00634CE79B4A}
    Runtime Installer end with exit code 0
    Elevated install completed
    Runtime Installer end with exit code 0
    Launching subprocess with commandline c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Resources\Adobe AIR Updater -updatecheck
    Runtime Installer begin with version 3.1.0.4880 on Windows 7 x86
    Commandline is: -updatecheck
    Installed runtime (3.1.0.4880) located at c:\Program Files (x86)\Common Files\Adobe AIR
    Performing pingback request
    Pingback request completed with HTTP status 200
    Starting runtime background update check
    Clearing unused background update directory
    Begin Background update download from http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.1.0.4880/update
    Unpackaging http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.1.0.4880/update to C:\Users\Vette\AppData\Roaming\Adobe\AIR\Updater\Background
    Runtime update not available
    Unpackaging cancelled
    Runtime Installer end with exit code 0
    Runtime Installer begin with version 3.1.0.4880 on Windows 7 x86
    Commandline is: -arp:uninstall
    Installed runtime (3.1.0.4880) located at c:\Program Files (x86)\Common Files\Adobe AIR
    Runtime Installer end with exit code 6
    Runtime Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is:
    Installed runtime (3.1.0.4880) located at c:\Program Files (x86)\Common Files\Adobe AIR
    Relaunching with elevation
    Launching subprocess with commandline c:\users\vette\appdata\local\temp\aire7af.tmp\adobe air installer.exe -ei
    Runtime Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is: -stdio
    .\pipe\AIR_4784_0 -ei
    Installed runtime (3.1.0.4880) located at c:\Program Files (x86)\Common Files\Adobe AIR
    Starting silent runtime update. Updating runtime from version 3.1.0.4880 to version 3.2.0.2070
    Installing msi at c:\users\vette\appdata\local\temp\aire7af.tmp\setup.msi with guid {47FA2C44-D148-4DBC-AF60-B91934AA4842}
    Runtime Installer end with exit code 0
    Elevated install completed
    Launching subprocess with commandline c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Resources\Adobe AIR Updater -installupdatecheck
    Runtime Installer end with exit code 0
    Runtime Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is: -installupdatecheck
    Installed runtime (3.2.0.2070) located at c:\Program Files (x86)\Common Files\Adobe AIR
    Performing pingback request
    Pingback request completed with HTTP status 200
    Starting runtime background update check
    Begin Background update download from http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.2.0.2070/update
    Unpackaging http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.2.0.2070/update to C:\Users\Vette\AppData\Roaming\Adobe\AIR\Updater\Background
    Runtime update not available
    Unpackaging cancelled
    Runtime Installer end with exit code 0
    Runtime Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is: -arp:uninstall
    Installed runtime (3.2.0.2070) located at c:\Program Files (x86)\Common Files\Adobe AIR
    Relaunching with elevation
    Launching subprocess with commandline c:\program files (x86)\common files\adobe air\versions\1.0\resources\adobe air updater.exe -eu
    Runtime Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is: -stdio
    .\pipe\AIR_3840_0 -eu
    Installed runtime (3.2.0.2070) located at c:\Program Files (x86)\Common Files\Adobe AIR
    Starting runtime uninstall. Uninstalling runtime version 3.2.0.2070
    Uninstalling product with GUID {47FA2C44-D148-4DBC-AF60-B91934AA4842}
    Runtime Installer end with exit code 0
    Elevated install completed
    Runtime Installer end with exit code 0
    Runtime Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is:
    No installed runtime detected
    Relaunching with elevation
    Launching subprocess with commandline c:\users\vette\appdata\local\temp\airbda4.tmp\adobe air installer.exe -ei
    Runtime Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is: -stdio
    .\pipe\AIR_764_0 -ei
    No installed runtime detected
    Starting silent runtime install. Installing runtime version 3.2.0.2070
    Installing msi at c:\users\vette\appdata\local\temp\airbda4.tmp\setup.msi with guid {47FA2C44-D148-4DBC-AF60-B91934AA4842}
    Runtime Installer end with exit code 0
    Elevated install completed
    Launching subprocess with commandline c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Resources\Adobe AIR Updater -installupdatecheck
    Runtime Installer end with exit code 0
    Runtime Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is: -installupdatecheck
    Installed runtime (3.2.0.2070) located at c:\Program Files (x86)\Common Files\Adobe AIR
    Performing pingback request
    Pingback request completed with HTTP status 200
    Starting runtime background update check
    Begin Background update download from http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.2.0.2070/update
    Unpackaging http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.2.0.2070/update to C:\Users\Vette\AppData\Roaming\Adobe\AIR\Updater\Background
    Runtime update not available
    Unpackaging cancelled
    Runtime Installer end with exit code 0
    Runtime Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is:
    No installed runtime detected
    Relaunching with elevation
    Launching subprocess with commandline c:\users\vette\appdata\local\temp\air2fa8.tmp\adobe air installer.exe -ei
    Runtime Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is: -stdio
    .\pipe\AIR_5396_0 -ei
    No installed runtime detected
    Starting silent runtime install. Installing runtime version 3.2.0.2070
    Installing msi at c:\users\vette\appdata\local\temp\air2fa8.tmp\setup.msi with guid {47FA2C44-D148-4DBC-AF60-B91934AA4842}
    Runtime Installer end with exit code 0
    Elevated install completed
    Launching subprocess with commandline c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Resources\Adobe AIR Updater -installupdatecheck
    Runtime Installer end with exit code 0
    Runtime Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is: -installupdatecheck
    Installed runtime (3.2.0.2070) located at c:\Program Files (x86)\Common Files\Adobe AIR
    Performing pingback request
    Pingback request completed with HTTP status 200
    Starting runtime background update check
    Begin Background update download from http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.2.0.2070/update
    Unpackaging http://airdownload.adobe.com/air/3/background/windows/x86/patch/3.2.0.2070/update to C:\Users\Vette\AppData\Roaming\Adobe\AIR\Updater\Background
    Runtime update not available
    Unpackaging cancelled
    Runtime Installer end with exit code 0
    Application Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is: -playerVersion=11,2,202,233 -sandboxType=remote -securityDomain=airdownload.adobe.com -https=false -fromUserEvent=true -- -url http://www.adobe.com/support/chc/air/350/AdobeHelp.air -- WWW aHR0cDovL3d3dy5hZG9iZS5jb20vc3VwcG9ydC9jaGMv
    Installed runtime (3.2.0.2070) located at c:\Program Files (x86)\Common Files\Adobe AIR
    Begin air file download from http://www.adobe.com/support/chc/air/350/AdobeHelp.air
    Download destination is C:\Users\Vette\AppData\Local\Temp\fla7A97.tmp
    Received download status 200
    Response URL is http://www.adobe.com/support/chc/air/350/AdobeHelp.air
    Download success
    Unpackaging file:///C:/Users/Vette/AppData/Local/Temp/fla7A97.tmp to C:\Users\Vette\AppData\Local\Temp\flaB22B.tmp
    Application signature verified
    Unpackaging/validation complete
    No app located for appID 'chc' and pubID '4875E02D9FB21EE389F73B8D1702B320485DF8CE.1'
    Converting unpackaged application to a native installation package in C:\Users\Vette\AppData\Local\Temp\flaC7B.tmp
    Native installation package creation succeeded
    Starting app installation to C:\Program Files (x86)\Adobe. Installing app chc.4875E02D9FB21EE389F73B8D1702B320485DF8CE.1 version 3.5.23 using the source file at file:///C:/Users/Vette/AppData/Local/Temp/fla7A97.tmp
    Got an unexpected fatal error while in stateInstalling: [ErrorEvent type="error" bubbles=false cancelable=false eventPhase=2 text="Unhandled exception Error: Directory can't be written to" errorID=5006]
    Launching subprocess with commandline c:\Program Files (x86)\Common Files\Adobe AIR\Versions\1.0\Adobe AIR Application Installer -runtime "c:\Program Files (x86)\Common Files" -silent -logToStdout -url -location "C:\Program Files (x86)\Adobe" -desktopShortcut -programMenu file:///C:/Users/Vette/AppData/Local/Temp/fla7A97.tmp
    Relaunching with elevation
    Application Installer begin with version 3.2.0.2070 on Windows 7 x86
    Commandline is: -stdio
    .\pipe\AIR_4952_0 -runtime "c:\Program Files (x86)\Common Files" -silent -logToStdout -url -location "C:\Program Files (x86)\Adobe" -desktopShortcut -programMenu file:///C:/Users/Vette/AppData/Local/Temp/fla7A97.tmp
    Installed runtime (3.2.0.2070) located at c:\Program Files (x86)\Common Files\Adobe AIR
    Unpackaging file:///C:/Users/Vette/AppData/Local/Temp/fla7A97.tmp to C:\Users\Vette\AppData\Local\Temp\fla3260.tmp
    Application signature verified
    Unpackaging/validation complete
    No app located for appID 'chc' and pubID '4875E02D9FB21EE389F73B8D1702B320485DF8CE.1'
    Converting unpackaged application to a native installation package in C:\Users\Vette\AppData\Local\Temp\fla3BF3.tmp
    Native installation package creation succeeded
    Starting silent app installation to C:\Program Files (x86)\Adobe. Installing app chc.4875E02D9FB21EE389F73B8D1702B320485DF8CE.1 version 3.5.23 using the source file at file:///C:/Users/Vette/AppData/Local/Temp/fla7A97.tmp
    Installing msi at C:\Users\Vette\AppData\Local\Temp\fla3BF3.tmp\setup.msi with guid {BD7F1DA3-5EA0-65F8-52B0-5E103FDC045A}
    Application Installer end with exit code 0
    Elevated install completed
    Launching subprocess with commandline C:\Program Files (x86)\Adobe\Adobe Help\Adobe Help.exe
    Application Installer end with exit code 0
    Date: Thu, 12 Apr 2012 17:10:46 -0600
    From: [email protected]
    To: [email protected]
    Subject: Adobe Air error message when using  PSE 10
        Re: Adobe Air error message when using  PSE 10
        created by Jeff A Wright in Downloading, Installing, Setting Up - View the full discussion
    Vetteski65 I would recommend reviewing Troubleshoot AIR installation | Windows - http://helpx.adobe.com/air/kb/troubleshoot-air-installation-windows.ht ml for steps on how to resolve your difficulties.  Please feel free to respond to this thread if you have any questions about the steps listed within the document.  If you could also respond with the specific error message you receive it would be appreciated.
         Replies to this message go to everyone subscribed to this thread, not directly to the person who posted the message. To post a reply, either reply to this email or visit the message page: http://forums.adobe.com/message/4331328#4331328
         To unsubscribe from this thread, please visit the message page at http://forums.adobe.com/message/4331328#4331328. In the Actions box on the right, click the Stop Email Notifications link.
         Start a new discussion in Downloading, Installing, Setting Up by email or at Adobe Forums
      For more information about maintaining your forum email notifications please go to http://forums.adobe.com/message/2936746#2936746.

  • Licence error message when using automation software

    Error message when using Rational Functional Tester 7.0.1.1
    to record a Flex application. The message seemed to come from the
    Flex application.
    I can record a fiew step in the application, then I have the
    message : "Licence are not present. Eith the trial version only
    limited record are allowed". But, my license of my Rational
    Functional Tester application is activated.
    I am using a Flex builder 3 trial version and the trial is
    not over.
    Is there any problem to get the license in the File compiler
    with "D:\apps\IBM\SDP70\FunctionalTester\bin\rft.swc"? That RFT
    file is supposed to be included in the flex application once
    compile

    Does anyone know how to build with automation support in a
    linux environment?
    We simply run an ant script build and have the SDK installed.
    We purchased Flex Builder Professional, but cannot install on Linux
    (we don't want to use the alpha version).
    Thanks for any pointers :)

  • How to generate and use Matlab(R2007) .dll's in Labview

    Is there a step-by-step example on how to generate and use Matlab(R2007)  .dll's in Labview.
    Our experimenal hardware is LabView-controlled and we want to pass
    images/2d intensity arrays to a more complex matlab program that will
    return an array of extracted data which we want to use in LabView again.
    Thank you
    Carsten

    I recommend having a wrapper created around the matlab dll that converts the datatypes for you. There is a lot of fooling around with pointers involved which is very difficult in LabVIEW. btw, this got much more complicated after Matlab 7. Essentially, you need to convert your inputs into mxArrays, and then add those mxArrays to an mxArray list that you pass by pointer into the matlab dll. You also need to create a mxArray list for the outputs from the dll which you will need to extract your data out of before converting it back into a LabVIEW supported datatype. It's a big hassle. We do this pretty often, but we have created a c library that handles all the conversions, so it is feasible for us. Unfortunately, I can't share the library, but hopefully this information will help you get where you want to be.
    Like I said, it would be easier if you can just get a c developer to write a wrapper for you to keep it simple in LabVIEW. Alternatively, you might try getting your m-code to work in Mathscript.
    Chris

  • My Application gets Error 37 when using Serial Port VIs.

    My Application works fine developed with LV 6.1. Then I updated to LV 7.1 and now the Executable of my application gets error 37 when using the old serial port functions. The "serpdrv" file is located in the application directory and is from 02/2002. The application runs well in the development environment after I placed the "serpdrv" file in the LabView directory. I tried to put a line with "serialDevices=..." in the .ini-file of my application but this did not cause an improvement. I also tried to rebuild the EXE with this line in the "labview.ini" file but nothing changes.
    Does anybody have another idea ?
    Many thanks for help
    Thomas

    >Did you actually replace the old serial functions that come with 7.1 with the functions from 6.1?
    Yes. E.g. "open serial driver.vi" uses "open device" with "serpdrv" as device string.
    I had the same problem running my application as VI´s. After the copy of serpdrv into the LV 7.1 directory everything works fine.
    I don´t understand why the application running as a .exe doesn´t find the serpdrv when it is in the same directory....
    Nevertheless many thanks for your answer
    Thomas

  • I'm getting a error message when using Apple Configurator "unable to send ClearPasscode command to device"

    I'm getting a error message when using Apple Configurator "unable to send ClearPasscode command to device"

    Yes, that is correct.  My spreadsheet has the following information in those cells if you want to compare yours on Monday:
    Product Type
    Application
    |
    AdamId:
    <and a 9 digit number>
    I ended up bringing the Macbook Pro home with me after struggling with it for a half hour at the end of a long day. I called and within 5 minutes the problem was corrected.  The technician said they were getting calls all day. 

  • Error 80 when using bluetooth on car radio

    error 80 when using bluetooth on pioneer car radio with my iphone 4 and 5

    me too...did some digging on the internet and appears Error -80 means the car deck is expecting some bluetooth protocols that your iPhones wont give out.  mine was intermittent for last couple years (deck is 12 years old) as of last night i just get error -80 everytime i try to dial out or recieve a call via bluetooth. this issue was intermittent with an iPhone 3G, 4, 4S, 5 and now my current 5S.  im blaming Pioneer not Apple for this
    I ended up buying a new deck for my car...gets installed tomorrow.

  • What causes Run Time Error 10086 when attempting an external calibration with the Calibrate_E_Series funcition.

    I am using Vb6(sp5), NT4, Component Works (latest), and Ni-Daq 6.9.1. The error occurs when using either a PXI-6052E or PXI-6070E. The Self Cal works fine but the external cal code generates this error during the call. The code used is taken directly from the programming example in the NI_DAQ programmers reference for the Calibrate_E_Series function.
    The Error Text is:
    Run-time error '10086':
    The external reference is invalid

    John;
    I found a Knowledge Base about that error you can refer to. The KB, originally, talks about Labview, but, as Labview makes NI-DAQ function calls in the same way any other Software language, you can apply the same concepts when using VB. The link is:
    http://ae.natinst.com/operations/ae/public.nsf/fca7838c4500dc10862567a100753500/2d8abbbb8d45ff74862565f6005c8d7b?OpenDocument
    and the KB number is 18TAPEY5
    in case you prefer to search for it at our home page.
    Hope this helps.
    Filipe
    Applications Engineer
    National Instruments

Maybe you are looking for