Read JPEG File gives error in normal user mode

[N sathyendra]

Hi,
 
I have Installed Labview 6.1 and Labview 7.1 In my system. I am using Read JPEG File.vi (labview 7.1) to read the image file. The VI behaves differently when I login into my system (windows XP) as user and differently when I login as Administrator. When I login as user and provide the path of the jpeg file (70kb) it trough’s an error code 1.where as same thing works fine when I login as Administrator. For small Jpeg files (3-20kb) it works fine in both the login. I am attaching the VI and the some jpeg files for your reference.
 
If I uninstall labview 6.1 and labview 7.1 and just install labview 7.1 in the system the Read JPEG File.vi works fine for both logins and for all JPEG Files.
 
Since the client is using both Labview 6.1 and labview 7.1.I need to solve the issue when both versions are present.Any suggestions would be greatly appreciated!

Regards,

sathyendra N

[TCPlomp]

your attachment didn't make it.
When doing a post preview attachments are lost (you have to relink them)

Ton

[devchander]

Hi Satyendra,

Guess the atttachments did not make it through

Are LabVIEW 6.1 and 7.1 installed in different drives on the system??

Does this occur irrespective of the location of the *. jpeg file that you want to read?, or does it occur only when you read this file from certain locations??

[N sathyendra]

Sorry for the inconvenience.

Hi,
 
I have Installed Labview 6.1 and Labview 7.1 In my system. I am using Read JPEG File.vi (labview 7.1) to read the image file. The VI behaves differently when I login into my system (windows XP) as user and differently when I login as Administrator. When I login as user and provide the path of the jpeg file (70kb) it trough’s an error code 1.where as same thing works fine when I login as Administrator. For small Jpeg files (3-20kb) it works fine in both the login. I am attaching the VI and the some jpeg files for your reference.
 
If I uninstall labview 6.1 and labview 7.1 and just install labview 7.1 in the system the Read JPEG File.vi works fine for both logins and for all JPEG Files.
 
Since the client is using both Labview 6.1 and labview 7.1.I need to solve the issue when both versions are present.Any suggestions would be greatly appreciated!

Regards,

sathyendra N

[N sathyendra]

hi devchander ,

Labview 6.1 and 7.1 installed in the same drive c:.

It occurs for most jpeg files irrespective of the file location.

Regards,

sathyendra N

[devchander]

Just see if installing them on different drives solves this problem

[N sathyendra]

I have tried that its not working since i have install labview 6.1 first then labview 7.1.

[Thaison_V]

Hi N sathyendra,

I hope you're doing well.  It's not quite clear why having both of these versions of LabVIEW on the same machine would cause problems related to opening files without administrator rights, but maybe we can narrow things down a bit.  You say that some files seem to work correctly for both log ins, and they tend to be small .jpg files.  Is there exact criteria to which files will open with both logins?  You say generally small .jpg files work.  Have you found if there is a limit in size where this causes a problem?  Does using any other picture file format change this behavior?  Let us know what you find.  I imagine that finding the details of these symptoms might point us to what the root of the problem is.

Thaison V
Applications Engineer
National Instruments

[N sathyendra]

Hi Thaison,

Thanks for your response

Since My client is running some other application which is in Labview 6.1 and he doesn't want to alter anything in that so we are using both the versions on same Machine.some files mean which is less than 30k but i am not sure.In Administrator login all jpeg files open without any issues.In my sample jpeg file the 75KB-FILE.jpeg and 87KB-FILE.jpeg doesn't open in Local login.If you need any other clarification please let me know.

Regards,

sathyendra N

[MattP]

Hello,

If the behavior does not occur for every JPEG file, but only some, it stands to reason that the ones that cause the problem are in a directory with slightly different permissions than the ones that work.  You can test this by logging in as Admin, modifying the folder permissions so all users have full control, then trying to access the JPEG again when logged in as a user.