09-03-2009 08:32 AM
I have recently re-released an application exe with some minor tweaks to run with LabVIEW 2009 runtime engine instead of the LabVIEW 8.6 runtime engine with which this has run successfully for over a year.
After deploying the application on a Win XP PC the program ran ok.
Subsequently shutting down the PC and turning the PC ON again running the program, it would not find some excel templates for report generation.
Closing the VI and rebooting the PC caused the Desktop and its Icons to reset as if a new user had logged on and all of the LAN and Administrator rights were missing.
This has also happened with a smaller deployed application on a different PC.
Re-instating all of the user and and network rights has worked, can any one help so I do not have to keep doing this?
09-03-2009 10:00 PM
Is there anything in your application that could be in any way trying to interact directly with Windows?
I really doubt that LabVIEW could cause the issues you are seeing unless somehow they were programmed that way in you application.
Any chance that your IT department as decided to install some software that causes the PC to restore user settings to some default environment that they mandate everytime it reboots?
09-04-2009 03:02 AM
Thanks for the reply.
Our IT department alway blames new installations first and asks us the engineering department to look into it as well.
Subsequent to my post yesterday I have found new problems with our engineering network drive. This could be the cause of our problem which I have got the IT department looking into now (reluctantly).
They do sysnchronise user logon settings to the network and critical files used for production I will get them to check the default user accounts.
I have been using the LabVIEW 2009 development suite for over 3 weeks now and have also tried the deployed software on my PC with no problems.
09-04-2009 09:56 AM - edited 09-04-2009 09:58 AM
Gareth C wrote:This could be the cause of our problem which I have got the IT department looking into now (reluctantly).
Ha, is that ever the truth. I think when people go into IT, they eventually forget that computers are supposed to be able to do useful productive things. They also forget that the reason that they have a job is because people need to do useful things with computers that aren't necessarily the e-mail, MS Word, MS Excel only boxes that they want to lock down and deploy identically to every user. They forget that they actually work for the users rather than the other way around. I also think they sometimes make changes to their systems just for the sake of change rather than to actually improve on any real computer problem. They have to justify their existence for some reason besides just unlocking user's passwords.
09-30-2009 04:17 AM
Hi Gareth,
Did the IT department manage to sort this problem out in the end? Please let us know if you are still having this problem
Many Thanks,
09-30-2009 06:09 AM
Hi Andrew
I have had no problems with subsequent LabVIEW 2009 Runtime and VI exe Installations. The IT department had to manually reboot the Engineering server as they could not remote access it and the fault diagnosis logs were not logging the known errors. They have had some UPS problems over the past few weeks and varying server reboots since our Mains Distribution Boards were Electrically Tested. This is what we think caused the problem.
09-30-2009 07:02 AM
Everybody always blames software first.... And it seldom ever is a software problem. We need to fight back and claim that all problems are hardware. 😄
PS. Well said RavensFan