CITADEL DATABASE NOT CONFIGURED AS A RELATIONAL DATABASE

[Ignacio]

Hi Alison:
That's precisely my problem: I don't know if there's something I can do about it...
I've tried this configuration on three machines with the same result.
I'm waiting the next package of CDs that I should receive because of the support program bought...

I don't know if there's something else I can try, I'd appreciate it very much!

TKS

Ignacio

[akokot]

Hi Ignacio,

I tried your VI in a Windows XP machine with LV and LV DSC 8.2.1. All works as expected. I can't see any problem using your configuration. So,  probably this is not a LV bug. I have some questions about your system:

1 - Do you have any other NI software installed in your machine? If you have, what are the programs and the versions?

2 - What are your OS? What language is it? There are some know issues with some localized windows versions.

3 - Are you using the Autodeploy Variables option in LV project? You should deploy your variables every time you make a change in the library.

4 - Have you tried another LV version? Like 8.0 or 8.2


Best Regards
Alisson Kokot

[Ignacio]

Hi Alisson:
Answering your questions,
I have installed every one of softwares that are included  in the NI DEVELOPER SUITE 2007,  last  update  (before LV 8.5) (LabWindows CVI, TestStand, etc.)
My OS is windows 2000 in spanish,
I'm using auto deploy, but even when I disable this function an I perform the deployment manually, is the same result
I've tried LV 8.2, with the same result

I hope this is a known issue with Win 2000 in spanish; in that case, what can I do?

TKS!

Ignacio

[VRspace4]

I am experiencing the same problem and have spent the last few days pulling my hair out trying different approaches but still no luck.

Basically, I'm getting the same error message when using the Alarm and Event Query. I'm running LabVIEW 8.2 with DSC 8.2 on a Windows XP SP2 platform.

Please help as my dead line for this phase is coming up.

- James

[VRspace4]

I finally got it to work. LabVIEW requires Microsoft's SQL Server Desktop Engine 2000 (MSDE 2000) which you can find from Microsoft's website and it weighs around 42.3MB.

http://www.microsoft.com/downloads/details.aspx?familyid=413744D1-A0BC-479F-BAFA-E4B278EB9147&displaylang=en


You need a little trick to install the MSDE because during the setup it will require you to have a SA password otherwise the setup would not continue. There is no user interface for you choose the password, so you have to do it by command prompt. Run cmd.exe from Start->Run and then go into the MSDE setup folder that you just extracted  - the default folder is C:\MSDERelA. From there, run this command:

setup SAPWD="YouPassword"

After the installation is complete, don't forget to restart your computer. You'll notice that there will be a new icon in your task tray that looks like a server machine or a gray box with a little status icon. If it isn't already running - denoted by a green PLAY button, double click on the icon and press Start/Continue. Now fire up your LabVIEW project or Measurement & Automation Explorer to test it.

Good luck,
James Pham

[Ignacio]

Thanks a lot James!, I'll try this and I tell... Hope it works!

Ignacio

[akokot]

Hi James,

You are right, LabVIEW DSC uses the MSDE to log data. But it's already installed with DSC. If you look at the DSC CD you will see a folder named MSDE. Thus, I don't think you need to install it again from Microsoft website. You are running WXP SP2 and the MSDE run as a service in startup. You need to verify if it is running in each machine startup.

Ignacio,

Do you have the icon in task tray like James described? If it isn't there, you have to enable it to run in startup. To start it, you can go to Control Panel>>Administrative Tool>>Services and start the service MSSQLSERVER.

To run the service in startup, go to msconfig and set the MSSQLSERVER to run in startup.

Best Regards,
Alisson Kokot

[Ignacio]

Hi everybody,
first of all thank you for you answers and your hints for solving my problem.
Finally I found what was happening... the SQLServer was not installed correctly. I couldn't realize this because apparently everything was working properly, but when James talked about the SQLServer I started investigating that issue and found the problem. Now it is working properly

Thanks again!

Ignacio von Unger