WealthLabDev.pdb not loaded
Author: Ben_Zurich
Creation Date: 4/8/2016 12:45 PM
profile picture

Ben_Zurich

#1
We have not used one of our PC's for several weeks, and now, when starting WL6 again, the program does not load.

When I start WL6 from the .NET environment, I learn that

WealthLabDev.pdb could not be loaded


But as far as I know, this file is not necessary and it is missing from our two other PC's running WL6, without producing this error.

What's wrong here? (see attachment)
profile picture

Eugene

#2
This is not a Wealth-Lab issue. From a logical standpoint, since you're trying to load the program under debugger there must be an option to uncheck in the debugger/IDE. I guess that you have reconfigured Visual Studio to load symbol files and forgot about it. Hope this helps to disable that option (Module Load Messages -> Off):

Error Message : Cannot find or open the PDB file
profile picture

Ben_Zurich

#3
Thank you. I have done this but unfortunately this wasn't the problem. The exception that occurs is:

QUOTE:
An unhandled exception of type 'System.TypeInitializationException' occurred in WealthLabDev.exe

Additional information: The type initializer for 'WealthLabPro.MainModule' threw an exception.
profile picture

Eugene

#4
This is a startup crash. Most likely it's caused by the custom DLLs you've deveoped.

Here's an all-encompassing guide on what to do when Wealth-Lab crashes on start: General troubleshooting procedure, follow from step 4. Pay attention to step 8 (remove all custom DLLs).
profile picture

Ben_Zurich

#5
Thank you, Eugene. In fact, it was a problem with the WealthLabConfig.txt file, which we solved now.
profile picture

Eugene

#6
I wonder what was the reason. Have you determined which line may have caused it, or do you still have a copy of the file?
profile picture

Ben_Zurich

#7
Another person has changed the country specifications on this particular PC.

This has caused the calendar date being in the wrong format in WealthLabConfig.txt
profile picture

Eugene

#8
Got it. This bug has been partially fixed in v6.8 (AFAIR). You seem to be using an older unsupported version 6.6 in one of your installations.