"Unable to open configSource file"

[tksandy]

I recently used the free 30 day trial. After it was over, I got an error saying "unable to open configSource file" and it wouldn't let me use it. I assumed this was the trial running it's course, so I purchased the full version. However, even after a complete reinstall, I can't open the application. This is very frustrating for me, as I've purchased the software and now can't use it.

 

How do I solve this?

[admin]

Try running with admin privileges, it could be a security issue.

[astroman133]

Guylain may have a different suggestion, but I would re-install BYE to a different folder, and re-register it.  If that works I would remove the initial installation folder.

[admin]

Yes, installing in a different folder will/should solve the issue.  Windows messed up (again) the configuration file somehow.

 

This is happening about once 1 month lately, I may have to consider an alternative for storing the user settings, it seems the built-in stuff in .net is not that reliable after all

 

Keep us posted please.

[tksandy]

Thanks. I'll try that later this afternoon when I get home. I appreciate the quick replies

[tksandy]

Hmmmm I'm still giving me the exact same error, even after uninstalling and reinstalling multiple times. Is there anything else that I could try to fix this?

 

I also just tried to install version 3.1.2 to see if that works, and I got the exact same error regardless of what location I installed it in

[admin]

Can you please provide a screen shot of the error.

 

EDIT: Having the same error after installing in a different folder is very odd. .net config files DO NOT cross over to other installation in separate folders, than I'm 100% sure of.

 

Thanks

[tksandy]

[tksandy]

Wooh! That did the trick. Thanks for the help

[admin]

BackyardEOS does not require admin privileges so you must have a odd security policy on your computer. In any event I'm glad that did the trick for you, YEAH!

[s3igell]

It's not that BYE/BYN might explicitly require Admin Priv, but rather that many Windows Installations (because of their own origin and/or upgrade history) expect Read/Write Files such as Config Files to be stored in either ProgramData or User\Name\AppData subdirectories (especially if the Admin/Owner differs from the Current User) rather than the Read-Only Program Files tree.  This is rather confusing and frustrating, but is a legacy of multiple efforts to drive Security in the newer Windows Platforms.

[astroman133]

One big exception to your statement are the .NET app.config and user.config files which must be in the same directory as the executable.  I believe that these files are what sometimes cause problems like the one in this thread.  If Guylain were to change where these files are located, I would expect that it would probably in the User\AppData tree. I would not recommend using Isolated Storage because it is a pain for developers since Debug and Release builds are stored in different folders due to the different signature of the exe file.

[STEVE333]

I had the same "Error message at startup" problem (for the first time) tonight. I have been using BYEOS for two years without any problems until tonight.

I downloaded the newest version of BYE into a new folder, but, the problem persisted.

I then right-clicked on the BYE icon and chose Run as administrator and then the program ran fine.  I now need to choose Run as administrator every time to open BYEOS.  Kind of a pain, but, it works. 

 

Steve

[s3igell]

 I now need to choose Run as administrator every time to open BYEOS.  Kind of a pain, but, it works. 

 

You can setup the Program Item Icon in the Start Menu, and/or the one on the Desktop, to always Run As Administrator.

 

Right-click the Icon; Select Properties; Move to the Shortcut Tab; Select Advanced; Check "Run as Administrator"; Click "OK" to Confirm both levels.

[STEVE333]

You can setup the Program Item Icon in the Start Menu, and/or the one on the Desktop, to always Run As Administrator.

 

Right-click the Icon; Select Properties; Move to the Shortcut Tab; Select Advanced; Check "Run as Administrator"; Click "OK" to Confirm both levels.

Thanks for the tip.  I did as you said and it works great.  Much appreciated.  I hate to have to "think" when I'm outside setting-up/aligning.

 

Steve

[james_sky]

Hey

This worked for me!

Thank You