LabVIEW doesn't start properly

[FlorinB]

Hello, 

Can someone help me with the problem in the image?

[GerdW]

Hi Florian,

You configured some SCC tool in the LabVIEW options and now that SCC tool isn't available.

Check the LabVIEW settings or your SCC tool…

[FlorinB]

Hi Gerd, 

Thank you for reply! 

Unfortunately I cannot open the LabView interface, it closes automatically after initializing. 

I want to note that I didn't modify anything, just what I installed LabView, I had the problem from the beginning.

How can I change the settings in another way if I can't open it?

[GerdW]

Hi Florin,

1. create a backup of the LabVIEW.ini file
2. Delete the LabVIEW.ini file
3. Start LabVIEW

What happens now?

[FlorinB]

Hi Gerd, 

The same.

[GerdW]

Hi Florin,

---

@FlorinB wrote:

Hi Gerd, 

The same.

---

Now I'm out.

Ask the NI support (as you should have access to due to your recent LabVIEW version)…

[Kyle97330]

The error message shows a path to a VI in vi.lib:

What happens if you re-name the "SourceControl" directory in vi.lib to something else?

It will likely give a different error message (hopefully that provides more information to track down...) and might even let you in to LabVIEW.

[FlorinB]

Hello Kyle, 

Thank you for the reply!

I have made the change, the behavior is almost the same. When I start LabView, it displays the initializations windows and closes automatically. After the third starting, the same error was displayed. What's strange is, the fourth time I opened it, I got the error in the image "Error(2)".

In addition to what has been mentioned so far, I would also like to note the following:
- When I use TestStand and call a LabView vi, it opens for a few seconds and then closes automatically.

- From the path "Documents\LabVIEW Data\LVInternalReports\LabVIEW\25.1.3f3 (64-bit)\reports" I obtained the error file "dmp error" in the attachment.

[Kyle97330]

The message shows something about a directory named "SourceControl_".  Is that what you renamed the directory to?

I wouldn't call that an "error message".  That's a message that comes up after LabVIEW starts while "remembering" that it crashed with a certain VI open that had changes.

The fact that it shows this tells me that likely just renaming it to "SourceControl_" isn't enough.  LabVIEW has a "find missing files" function that checks the entire vi.lib folder and it probably used that to find the renamed folder.  I would go back, and instead of renaming that folder I would just move it to a location that is well outside of any folder LabVIEW might look for files inside of.  Like, put it in a ZIP file on a network drive or something.  Just get rid of it so that LabVIEW can't possibly try loading stuff from it on startup.