11-13-2006 03:01 PM
11-14-2006 01:42 PM
01-07-2008 01:43 PM
01-08-2008 11:25 AM
Hi Jay,
If you had made a back up of the registry, I suggest restoring the backup, just so we can get the laptop speed back for now. Next step would be to download the latest updates for the Sentinel Protection Installer located here: Sentinel Protection Installer v7.4.0 and then add the patch for it here: Security Patch to Sentinel Protection Installer 7.4.0.
If you haven't made a backup of the registry, you can try to rollback your Windows to a previous state using the Windows XP/Vista System Restore functionality, and then follow the step above.
Let me know if this works!
01-08-2008 11:53 AM
01-08-2008 11:56 AM
01-08-2008 01:11 PM
Hi Jay,
I am assuming that you are not the same user as ArtTCG, am I correct in assuming this? If so, would you please let me know what the exact error message is by either just typing it here verbatim, or just taking a screenshot, it would really help in resolving this issue for you. The issue may be due to your firewall settings as well, and I will do my hardest to fix the issue for you, but if you would be able to let me know which version of LabView you have, and how this problem arose etc. it would really help.
Thanks a lot!
01-08-2008 02:41 PM
01-08-2008 02:42 PM
01-08-2008 03:38 PM
Hi Jay,
After researching a bit on this, yes, indeed LabView 8.5 does fix this issue. However, for now, we have a workaround if you do not want to upgrade your software. We will need to modify a particular service setting on your computer to remedy this bug. Apparently what was happening is that the PSP server locator was being started up by two different National Instruments products, and this issue only affects some customers. A remedy has been implemented in LabView 8.5.
If you can browse to Control Panel>Administrative Tools>Services, then navigate to the entry that is labeled "National Instruments PSP Server Locator", double click it, and change the startup type from "Automatic" to "Manual" and press OK. Now, restart your computer and see if you're still getting the error.
I have noticed that this fixes the issue for a lot of users, and it is a good next step to take. I am looking forward to your results.