mssql.mdf

[johnoc]

What is this? It has been happening since 10/29 and causing LabVIEW 2014 to stop responding. Huge issue!!!! What good does it do to submit the issue when LabVIEW stops responding?

[Sam_Sharp]

Sounds like an issue with NI Citadel - the database server used by DSC - perhaps you can try repairing/reinstalling Citadel to see if it fixes the issue? I'd also open up NI Max and check under 'Historical Data' as that will show you the Citadel databases so you can check if there's something wrong there.

It sounds like a file permissions issue - are you logged in as an administrator? Perhaps from NI Max you can 'move' the database location to somewhere you have write access?

[PatrickLye]

"SQL Server databases use two files - an MDF file, known as the primary database file, which contains the schema and data, and a LDF file, which contains the logs. See wikipedia. A database may also use secondary database file, which normally uses a .ndf extension."

Can you open up the Citadel databases with SQL Server Management Studio? This is a  free download if you don't have it. You might have a problem in Security\Logins\One of the users.

I would guess that the user at that point would be the nicitadeluser, as it is on mine if something hasn't been changed.

Check your permissions on that file to see what you have available.

I have 2013 and 2104 installed, but I didn't see that file name at the alternate path in your screenshot. Perhaps this is only on older versions of LabVIEW??

[johnoc]

Thank you both for your replys.

I just uninstalled the "Dataloging and Supervisory Control" module from my development PC. It seems there have been quite a few developers with Citadel issues. I couldn't really find a case where NI actually addressed or solved the issue. Just developers providing workarounds.

Also, when LabVIEW 2014 stopped responding all the time, I was asked if I wanted to submit the logs. I did every time. Apparently, the logs and reports submitted do not point to an issue with NI Citadel.

[johnoc]

Patrick,

LabVIEW 2009 is not even installed on my PC. I have been working in 2014 for quite some time. This problem started on 10/29/2015.

The directory referred to in the log is a location on my machine. The .mdf file is still there. It is a Windows 7 (64 bit) Machine. Thus the "Program Files" folder is the program directory for 64-bit applications. "Program Files (x86)"  contains the 32 bit applications. I have LabVIEW 2012, 2013, and 2014 32 bit versions installed so they are in the Program Files (x86) directory. As I said I do not have LabVIEW 2009 installed so it puzzles me that the dirctory above exists at all.

[PatrickLye]

This is odd.

I've also never had much luck with crash reports, even if I directly gave them to NI support...

Now that you uninstalled DSC does the Citadel database still show up in SQL Server Management Studio? If so can you open it.

Are you planning on reinstalling DSC to see what happens? As I just said I've had problems getting answers to these crash reports before. This was the reason I started watching the forums so closely to see what was going on out there, but oftentimes we just don't have the time we need to test things out and still make a living.

Here is a link that talks to mdf files that are still registered with the system.

http://stackoverflow.com/questions/17931591/mdf-file-not-able-to-attach-at-runtime-mvc4

It looks like you could do some damage if you're not careful.

Sometimes it is such a pain to manually try to repair what installers and uninstallers have done. I try to keep images of my drives at different points just to make it easier to recover. I've even begun getting an image of my development system after running all windows updates on a new machine before installing any NI software. This way I can get back to a clean system, run the current Windows updates, and then load all the NI software again. It would be nice to get all of the NI Software on usb so that it could be loaded on my SSD for a fast reload when NI software cracks up...The NI software loading takes hours...

[Yanhua]

just meet the same question as you. Please open the "Sql Server Configuration Manager" in your start menu, Choose the "SQL Server Services" in the left column, Then you will find the "SQL Server(CITADEL)",change the "Network Service" to "Local System".