LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Error after install of DSC 8.2.1

After upgrading to Labview 8.2.1 with the DSC 8.2.1, I run into an error.  I believe the error is because I already had SQL Server 2005 Express Edition installed when I installed DSC 8.2.1.  Here is the error message that I get when I did the first reboot after the install. 

"NI MSDE NT Security Setup Error
NI MSDE Setup is unable to setup relational database.  NI MSDE is not accessable or currently logged user doesn't have sysadmin permissions.  Please log on as user with sysadmin permissions and run msdesetup.exe again."

I tried logging into SQL Server Express as my normal user with sysadmin privledges and running C:\Program Files\National Instruments\Shared\Citadel\msdesetup.exe but the error is the same. 

Any ideas how I can set up the relational database for DSC?

Thanks for the help.
Joe Losco
0 Kudos
Message 1 of 2
(4,713 Views)

Joe:

While the LabVIEW DSC module setup is executing, it performs an install of Microsoft’s MSDE SQL Server 2000. The install may appear to have completed successfully, but after reboot of the PC, the above error message may be displayed. This error message most likely indicates that a problem was encountered while Setup was registering SQL Server Performance Monitor counters. This is entirely a Microsoft registry related issue.

The following registry key stores the Extensible counters information:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows NT\CurrentVersion\Perflib\009

If you receive this error message, there are a few troubleshooting options that can be taken to try and address the problems with the registry key.

  1. To resolve the corrupted registry problem, run the following command:
    "lodctr /r: PerfStringBackup.ini"
  2. If you are using Microsoft Windows 2000 or later, you can try to repair the registry by running Windows Setup and choosing the Upgrade option. By choosing the Upgrade option, you retain all your applications and settings. Note that you must reapply any Windows service packs that you applied before you performed the upgrade.
  3. Verify the permissions on the above listed registry key. Ensure that, at a minimum, the local Administrators group and the local System account have Full Control permissions.

I would also suggest that you check out the DSC readme file. I hope this helps.

Regards,

Rudi N.

Message Edited by Rudi N on 04-24-2007 05:42 PM

Message Edited by Rudi N on 04-24-2007 05:43 PM

Message Edited by Rudi N on 04-24-2007 05:43 PM

0 Kudos
Message 2 of 2
(4,689 Views)