Error 1003 when using excel reprt, but not Word

I am trying to use the MS Office Report vi to send my data to an Excel. I am using Labview 7.1.
When I place the VI on the block diagram I get the following message: (Also attached)
Error 1003 occurred at Open VI Reference in ex_RGT_Get
Bookmarks and named cells.vi->Configure MS Office
Report.vi->Confugure MS Office Report.vi.ProxyCaller
Possible Reason(s):
The VI is not executable. (OK Dialog box)
If I click OK, the " Configure MS Office Report pop up window is mostly grayed out . If I select "Basic report for Word" I have no error message.
I am using Excell 2003. The problem is with a laptop computer I am using. I do not see this problem with a desktop computer.
Thanks,
Bill
Attachments:
MS Report 8-24.doc ‏80 KB

Hello Bill,
You are not trying to build an executable, just use the Express VI in a regular development VI, right? If so, this link describes the troubleshooting steps to get rid of this error.
Regards,
Clint M
National Instruments

Similar Messages

Airtunes drops when using Windows XP, but not Mac

We're currently using the AirPort Express as our wireless router, and everything works great from a connection standpoint. No problems with our MacPro or XP laptop.
However, when using XP to play AirTunes, the audio constantly drops out (itunes will pause, and then come back within a few seconds, green light on the APX stays lit). We've tried closing all other programs & processes, and even uploaded the 6.3 firmware for Windows, but still get the drop-outs. Never once had a problem with the Mac, even after the firmware change.
Also tried using a Linksys wireless router as our hub and connecting the APX to the network. same issues.
I haven't been able to find anything on the site about this, anybody else having this problem?
MacPro Mac OS X (10.4.9) Toshiba Laptop w/ Windows XP

I'm experiencing something similar.
I have a TECOM wireless router with a a single win XP PC connected and two airport express stations for playing music remotely.
Green light still on, but iTunes frequently loses sight of the remote speakers after some period of time.
The solution thats often works is to disconnect and reconnect XP to the wifi network. But I'm not really happy with this (boring) method.
If anyone knew a setting that could help...

Photomerge produces white lines when using RAW (PEF) but not TIFF

I just started using PS CC (Mac, v14.1.2) and tried out Photomerge with a set of 40 (4 rows, 10 cols) raw images (Pentax PEF format), resulting in a 0.3 gigapixel image.
When I have them stitched by Photomerge, I see fine white lines at the merge points.
I had enabled all 3 options (blend images together, vignette removal, geometric distortion correction), using cylindrical layout.
When I first convert the PEFs to TIFFs and use Photomerge with the same options, there are no such white lines.
An example of the bad output:
These unwanted lines are, of course, at the edges where the images are getting joined.
Also, when using only a few images (2x2 or 3x3, or even 4x5), I do not get this effect.
I noticed that when using less images, the blend masks' edges are not straight - but they are when I see this issue. This suggests that at some point the merge operation gets overwhelmed and switches to a simpler algorithm, which in turn has this "bug" with RAW images, apparently.
Is this a known issue, and is there a way to get this working right with this many RAW/PEF images?

tempelorg wrote:
csuebele, that link only directs me to http://feedback.photoshop.com/photoshop_family, which is clearly not a bug report form but yet another "open" discussion forum, it seems.
Sigh. How can Adobe charge so much money for their products and not even afford a team of people to look into bugs that users might want to report. Big companies suck.
Although you were probably looking for a standard developer-type bug report form, you still might want to take a closer look at that site. You'll see numbers next to the topics; those are user votes to help get something fixed sooner. While it's one thing to submit a bug report (and from this thread it seems they might already have it), Adobe uses that site to help prioritize which bugs to fix first, based on the user discussion and votes. Because Adobe has to decide not only whether a bug needs to be fixed sooner than other bugs, but sooner or later than certain feature requests. The user discussions and user votes on that site help them decide, although I'm sure there are other internal considerations.
In addition to votes, you'll see that posts on that site can be marked "Acknowledged" or "In Progress" by Adobe. The user votes and status reports are what make that site a little more quantifiable than this forum. Also, it isn't unusual to see Adobe developers and employees in the threads looking for more info or explaining things. So while it might not look like a traditional bug database, it's along those lines but in a way that makes it a little easier for non-technical users to participate in the process.

OJ Pro8000 thin black line appear when using photo paper but not regular paper

When using both my OJPro 8000 and my wife's OJPro8500, thin black lines appear every 7/8" on the paper when using photo paper. This does not happen if I print on regular bond paper.

Anything? It's only happening in Photoshop, other apps print fine.

Idoc with error message when coming from middleware but not in we19

Hi Experts
I am facing a very strange issue !
I have a Z - Idoc type and corresponding inbound function module for creating schedule lines i.e. doing something what me38 does.
When my middleware i.e. Mercator Websphere is sending the idocs, they fail with the error message in the status record as
Field EKET-MENGE (19) does not exist in the screen SAPMM06E 1117.
But when I try processing the same idoc using we19, the scheduling lines are created and the schedule agreement is changed.
Is there any difference between we19 and when idocs come from the middleware ?
Points would be rewareded if useful answers received.
Regards
Shubhankar

Well i think that the problem is with your BDC. there is an option to use standard size in BDC. I think your table control falls short of 19 rows in your program. Please see the thread below and incorporate the same changes in your BDC. I think u might need to record the BDC again.
Re: BDC tabel control for QE01
DATA OPT TYPE CTU_PARAMS.
OPT-DEFSIZE = 'X'.
CALL TRANSACTION 'FB01' USING ITAB OPTIONS FROM OPT.

Getting error 3001 when using Excel Easy Table.vi

When making a call to Excel Easy Table.vi (Report Generation Toolkit) I get a 3001 error.
I have attached an example VI to demonstrate the problem. Please run "Add Table Example.vi" in the attached zip. This sample program is made up of VIs from a larger program, so it made more sense to create a sample program and only include the required VIs than include the entire large program. So that is why the Report class wire comes from a functional global VI.
What is a bit strange is that Excel Easy Table is used to write a summary table at the top of the spreadsheet successfully in "Initialize Report.vi." It is only when I then make the additional call to Excel Easy Table in Add Table Example that I get the 3001 error. If you have any ideas why I'm getting the 3001 error, please let me know.
I'm using LabVIEW 8.6 and RGTK 1.1.4.
Thanks,
Joel
Solved!
Go to Solution.
Attachments:
Add Table Example.zip ‏113 KB

Hey Joel,
I figured out why this error was occuring. After comparing how you were adding the columns in the Report Write Info Table.vi in the Initialize Report.vi to just using the Excel Easy table VI, you hadn't provided a reference to which worksheet it needed to write the data to. I changed your code to include this reference and it worked perfectly without any errors. I have attached a .zip file with those changes so you can look at it.
FYI: Don't try to use this code as a direct replacement with yours. In order for me to reproduce the error, I had to modify several VIs in order to get it to run.
I hope this information helps you with it.
Jim St
National Instruments
RF Product Support Engineer
Attachments:
Add Table Example.zip ‏146 KB

How can I improve the quality of a photo that appears blurry when used in iMovie but not in iPhoto?

A 320 x 240, 35 KB Jpeg file looks crisp and in focus in iPhoto. But as soon as I put it into iMovie and hit full screen, it's blurry and looks terrible. A photo taken with my Nikon D7100, a 3872 x 2582, 2.5 MB Jpeg photo translates to the big screen just fine, with perfect clarity. How can I use this former picture but increase its clarity when it's magnified in iMovie?

Apologies for opening this up again:
I rasterised and embedded the photos, liked what I saw and marked the question as answered, then I zoomed out and lo! The white jaggedy edges are back! This is despite the fact I rotated them to vertical before rasterising them.
It appears that the pixels in the rasterised image are relative to the screen, not relative to the object... so when I rotate the photo it goes back to the original hi-res photo and re-rasterises it to fit the new orientation.
Also doing this has not lowered the filesize at all... It does appear that when you rasterise an image in Illustrator, the new raster is only a veneer, the original (hi-res photo) is still lurking in the background.

I cannot click on tabs in any website, do you know why? I can do it when using Internet Explorer but not firefox.

I have used Mozilla Firefox for years, but all of a sudden I cannot put my curser over a tabs on any website and click on it. What I mean is the top of the websites have words you can click on to go to other pages or in the email system it has tab buttons that allow you look at your inbox or close or save draft, it doesn't allow the curser to click on it. I can go to the tool bar put my curser in that and use the tab button on the key board to tab over to each word or link and then click enter and it will then go to that next page.

Both the Yahoo! Toolbar extension and the Babylon extension have been reported to cause an issue like that. Disable or uninstall those add-ons.
* https://support.mozilla.com/kb/Troubleshooting+extensions+and+themes

PS CS5.1 crashes when using file open but not with bridge or "open as smart object"

I'm using a Mac with Snow Leopard and Photoshop CS5.1 Extended
When i try to open a file largen than ~50MB with double click in finder or with file>open in PS, the program loads the psd and shows it, then 2-3 seconds later PS crashes. If the psd is under ~50MB everything is fine.
If i open it with file>open as smart object or via the mini bridge, everything is fine, and i can work with it.
How can this be fixed?

Make sure you submit your crash report as it helps us track and resolve code for crashing issues.
Submitting Crash Reports: http://adobe.ly/gNJWVY
If you post one of you crash reports here?
Location of Crash Reports:
Users/<your user name>/Library/Logs/CrashReporter

I receive the error "this apple id is valid but not an icloud account" when I try to open icloud on my pc. Help.

I receive the error "this apple id is valid but not an icloud account" when I try to open icloud on my pc. Help.

Music purchased from the iTunes Store is automatically available in iCloud. This is "iTunes in the Cloud" and does not require an iCloud account. The music is stored in the iTunes Store, not in a personal iCloud account.
If you don't have any Apple devices you will not be able to create an account. It wouldn't be any value to you anyway as it syncs data on you computer with your Apple devices. If you don't have any, there is nothing to sync.

I have a macbook air and and hdmi that i have used many times, but not all of a sudden the tv won't recognize the hdmi. The computer flashes when it is plugged into the hdmi but the tv says "no signal" and the airplay displays option says "no device"

I have a macbook air and and hdmi that i have used many times, but not all of a sudden the tv won't recognize the hdmi. The computer flashes when it is plugged into the hdmi but the tv says "no signal" and the airplay displays option says "no device detected" and the drop down bar is grey and locked.

I have a macbook air and and hdmi that i have used many times, but not all of a sudden the tv won't recognize the hdmi. The computer flashes when it is plugged into the hdmi but the tv says "no signal" and the airplay displays option says "no device detected" and the drop down bar is grey and locked.

When I try to make smaller PDF's I get an ''unknown error''message,(Win7 on Acer laptop, but not on my HP Desktop with Win Xp (two separate Acrobats)?

When I try to make smaller PDF's I get an ''unknown error''message,(Win7 on Acer laptop, but not on my HP Desktop with Win Xp (two separate Acrobats
Happens isnce a week or four...

https://www.dropbox.com/s/h20hiaxiuynz6z5/Blendle%20week%2051%202014.pdf?dl=0
https://www.dropbox.com/s/eohk8an2rozwe5w/NatGeo2015.pdf?dl=0
Until a few weeks ago no problems with this kind of files

I have a new keyboard and two of the keys are inverted when I use my Mac -- but not on the Mac at the Apple store. The @ is where the should be and visa-versa. That is, when I type the @ I get and when I type the I get @. I am in Français numérique.

I have a new keyboard and two of the keys are inverted when I use my Mac -- but not when they put that keyboard on the Mac at the Apple Store. The @ is where the < should be and visa-versa. That is, when I type the @ I get < and when I type the < I get @. I am in Français numérique. Thanks

Try a SMC reset, please do it 2-3 times.
SMC RESET
Shut down the computer.
Unplug the computer's power cord and all peripherals.
Press and hold the power button for 5 seconds.
Release the power button.
Attach the computers power cable.
Press the power button to turn on the computer.
PRAM RESET
Shut down the computer.
Locate the following keys on the keyboard: Command, Option, P, and R. You will need to hold these keys down simultaneously in step 4.
Turn on the computer.
Press and hold the Command-Option-P-R keys. You must press this key combination before the gray screen appears.
Hold the keys down until the computer restarts and you hear the startup sound for the second time.
Release the keys.

Error 1003 when running .exe

I am having a problem with error 1003 when I run a built application. I have searched the forums and found many others with this problem, but they encounter the problem while building the application, not while running the built .exe.
I have a top level VI (AutoRun.vi) that calls 3 VIs in sequence. All three are called in the same manner. The first two work fine, but I get this error with the third sub vi. This is how I call the subvi:
Use App.kind, check for "Run Time System" (strip app path twice), or "Development System" (strip app path once)
Build path to combine stripped path and file name of subvi to open
open vi reference
Invokee Node - Open FP
         Activated - T
         State - Standard
Invoke Node - Run VI
         Wait until done - T
          Dispose ReF - F
Invoke Node - Close FP
Close VI Reference
The error I get is:
Error 1003 occurred at Invoke Node in AutoRun.vi
Possible reasons:
LabView: the VI is not executable
I do not get this error while running in the development environment. Only when I run it as a .exe. Also I have had no problems with this code in the past. I just made a small change and now I have this problem. I have gone back to the old code and have the problem with it too.
I build the app by starting the app builder, selecting the top level VI, adding dynamic VIs and select all 3 subvis. The front panel of the second VI is not visible while running.  I have to go in and manualy change the "Remove Panel" in the build settings for this VI from the default yes to no. If I do not do this I get an error while trying to run the built application. I have no idea why this happens either, but making this change fixes the problem. After this I select build.
BTW, I have LabView 7.0

Hello,
Not sure what happened on your end, but if the problem comes back repost and we'll explore it!
Best Regards,
JLS
Best,
JLS
Sixclear

Error 1003 when loading a VI dynamically on LabView Run-time ini file configuration

hi all,
I have a problem with my runtime excutable.
On 4 systems, all running XP it runs fine.
On 2 systems ( one a new install of just LVRT 2011 SP1 ) I have:
Error 1003 when loading a VI dynamically on LabView Real-time
Or more spoecifically the error code is 1003 and the error source is Open VI Reference.
When the RT app runs correctly I get these paths:
Path Sent to Open Vi Reference: Yeast_Grower.exe\Tecan_talk_Control.vi,
Path Returned from Open Vi Refence: C:\Program Files\Yeast_Grower\Yeast_Grower.exe\Tecan_talk_Control.vi,
On a system that does gets the 1003 Open Vi Refence error I have the same Path Sent but of course no path returned as it does not open.
To be sure that the vi Dyanmically called vi is compiled and valid at runtime I also include a copy of in the main.vi.
To be extra sure I have also installed the runtime versions of VISA and DAQmx.
I have compiled it with and without the "Use LV 8 calling hiaracy"
My conclusion as this stage is that either the installation of LVRT 2011SP1 misses something the earlier LVRT installtions make.
or is there a MyApp.ini or LVRT .ini that controls how the RT dyanim calls are handled.
Help very welcome how to solve this puzzle.
thanks
michael

I understand that all the PCs (6 of them) have LV 2011 SP1, runtime or the development system installed. Right?
How many of these PCs have the source code available on them?
-> Only one of them has the source code.
I am not sure I understood 'I also include a copy of in the main.vi'. Does it mean you placed the subvi in the main.vi?
-> I meant I have included in main.vi the actual vi that is called dynamically - but only where it is not called.
Did you try including the sub vi which is called dynamically, as 'Always included' in the EXE build?
-> No, I did not know of this option - but the above I did this by default.
Edit: Did you verify the software versions of LV RT, VISA etc on all the PCs? Are they same?
-> I did verify even added DAQmx just in case
There is lots of material available on this forum for error 1003 and dynamic vi calling. Did you find anything useful to try among the forums threads?
-> I did view many of them.
I did finally find the answer.
I have a subvi (callNet.vi ) in the dynamically called vi (dynamic ) that calls .Net libraries.
Now the thing is that this subvi callNet.vi is coded out by enclosing it in a Disable structure.
In fact this subvi ( callNet.vi) does not even compile - ie it has a broken arrow
however if enclosed in a Disabled structure and disabled, the enclosing vi compiles OK.
However I have discovered that even with the .Net calling subvi (callNet.vi) in the Disabled state of the Disabled structure
the enclosing vi (dynamic.vi ) does NOT run - although it compiles just fine.
Once I installed the .Net libraries (I actually did include them with my app installer ) with the vender's supplied installer
then my app now successfully calls the dynamic vi.
So the Summary and warning is: Even if the dynamic called vi is included in Main.vi and Main.exe runs ( but does not call the dynamic vi - except when called dynamically at later some point ) and even if, in this case, the .Net calling subvi is disabled out ie no .Net calls are made the dynamically called vi will not run when called dynamically.
I hope that is not too confusing. In summary it seems the Disable structure does not entirely disable.
Michael

Error 1003 when using excel reprt, but not Word

Similar Messages

Maybe you are looking for