Jump to content

Canada's top-tier Telescopes & Accessories
Be as specific as possible when reporting issues and *ALWAYS* include the full version number of the application you are using and your exact *CAMERA MODEL*
NEVER POST YOUR KEY IN ANY PUBLIC FORUM, INCLUDING THE O'TELESCOPE SUPPORT FORUM ::: IF YOU DO YOUR KEY WILL BE DEACTIVATED WITHOUT NOTICE!
  • 0

3.2.1 RC2 not saving settings


Go to solution Solved by admin,

Question

I am setting up a new machine, and my installation of 3.2.1 RC2 works fine, and the settings work, but they're not being saved. So the next time I restart, everything is back to default settings.

I have uninstalled and reinstalled it with a reboot between, but it's still not saving settings.

Any ideas?
 

Link to post
Share on other sites
  • Answers 42
  • Created
  • Last Reply

Top Posters For This Question

Top Posters For This Question

Popular Posts

I understand about classic Windows privileges, but this is the first time since I started using BYE that I have had a settings issue. Also, I have Full Control of the settings subfolder, just as I hav

Right click on the application icon and switch to the security/permissions tab. Assign the account you are logged in all the write/read permissions. This should solve the problem, although it should n

Thank you for sharing this.

Posted Images

Recommended Posts

  • 0
  • Solution
On 11/28/2020 at 6:34 AM, selnekovic said:

Right click on the application icon and switch to the security/permissions tab. Assign the account you are logged in all the write/read permissions. This should solve the problem, although it should not occur in the first place.

1 hour ago, admin said:

Thank you for sharing this.

Here's a workflow for doing this.  I checked the "Modify" option for "Users" for the folder where BYE is installed and is worked after that.  

As mentioned above, this should not happen, but it does.  This workaround will allow BYE/BYE to save settings again.

image.png

Link to post
Share on other sites
  • 0
50 minutes ago, dkerber said:

I tried that with no success; it appears to be a glitch with the RC2 version. I reverted back to 3.2.0, and everything works fine; it even called my previous settings back up (the ones that were in effect before I installed the RC2.

Are you sure you installed in a new folder?

There is no other reason for this, that I'm 100% sure.

Settings are stored in a config file... under appData user folder.

Link to post
Share on other sites
  • 0
28 minutes ago, admin said:

Are you sure you installed in a new folder?

There is no other reason for this, that I'm 100% sure.

Settings are stored in a config file... under appData user folder.

Yes, I'm sure. It defaults to Program Files(x86)/...3.2, and I changed the end of it to "3.2.1". Uninstalling 3.2.1 and reinstalling 3.2.0 worked fine.

 

Link to post
Share on other sites
  • 0
13 hours ago, admin said:

Are you sure you installed in a new folder?

There is no other reason for this, that I'm 100% sure.

Settings are stored in a config file... under appData user folder.

I wonder if the issue is permissions on the AppData folder, rather than the program install folder. I'm not finding any BackyardEOS or OTelescope folders under my User/AppData/Local folder, or any of the other AppData folders as far as I can find.

 

Link to post
Share on other sites
  • 0

I did a little more troubleshooting on this, and found that there is definitely a difference between 3.2.0 Final, and 3.2.1 RC2. I installed 3.2.1 and tried to change the image file type to Raw (from the default Raw + JPG), and found this at the end of the log file:

2020-10-19 08:52:19,717 [Main] INFO  - O'Telescope Dependencies ALREADY REGISTERED!
2020-10-19 08:52:19,727 [Main] ERROR - An error occurred loading a configuration file: Access to the path 'C:\Program Files (x86)\BackyardEOSv3.2\t2s3jcsk.tmp' is denied. (C:\Program Files (x86)\BackyardEOSv3.2\BinaryRivers.BackyardEOS.Start.Camera1.exe.user.config)
2020-10-19 08:52:19,727 [Main] ERROR -    at System.Configuration.MgmtConfigurationRecord.SaveConfigSource(DefinitionUpdate update)
   at System.Configuration.MgmtConfigurationRecord.SaveAs(String filename, ConfigurationSaveMode saveMode, Boolean forceUpdateAll)
   at System.Configuration.Configuration.SaveAsImpl(String filename, ConfigurationSaveMode saveMode, Boolean forceSaveAll)
   at BinaryRivers.Basics.Configurations.SettingManager.SaveCache(Boolean force)
2020-10-19 08:52:19,732 [Main] ERROR - Access to the path 'C:\Program Files (x86)\BackyardEOSv3.2\t2s3jcsk.tmp' is denied.
2020-10-19 08:52:19,732 [Main] ERROR -    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)
   at System.CodeDom.Compiler.TempFileCollection.EnsureTempNameCreated()
   at System.CodeDom.Compiler.TempFileCollection.AddExtension(String fileExtension, Boolean keepFile)
   at System.Configuration.Internal.WriteFileContext..ctor(String filename, String templateFilename)
   at System.Configuration.Internal.InternalConfigHost.StaticOpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext, Boolean assertPermissions)
   at System.Configuration.Internal.InternalConfigHost.System.Configuration.Internal.IInternalConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext, Boolean assertPermissions)
   at System.Configuration.Internal.InternalConfigHost.System.Configuration.Internal.IInternalConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext)
   at System.Configuration.ClientConfigurationHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext)
   at System.Configuration.UpdateConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext)
   at System.Configuration.MgmtConfigurationRecord.SaveConfigSource(DefinitionUpdate update)
2020-10-19 08:52:19,732 [Main] DEBUG - ButtonPlus_MouseClick(btnSave = 'Save')
2020-10-19 08:52:19,772 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2020-10-19 08:52:22,662 [Main] ERROR - An error occurred loading a configuration file: Access to the path 'C:\Program Files (x86)\BackyardEOSv3.2\juy2r5gd.tmp' is denied. (C:\Program Files (x86)\BackyardEOSv3.2\BinaryRivers.BackyardEOS.Start.Camera1.exe.user.config)
2020-10-19 08:52:22,662 [Main] ERROR -    at System.Configuration.MgmtConfigurationRecord.SaveConfigSource(DefinitionUpdate update)
   at System.Configuration.MgmtConfigurationRecord.SaveAs(String filename, ConfigurationSaveMode saveMode, Boolean forceUpdateAll)
   at System.Configuration.Configuration.SaveAsImpl(String filename, ConfigurationSaveMode saveMode, Boolean forceSaveAll)
   at BinaryRivers.Basics.Configurations.SettingManager.SaveCache(Boolean force)
2020-10-19 08:52:22,662 [Main] ERROR - Access to the path 'C:\Program Files (x86)\BackyardEOSv3.2\juy2r5gd.tmp' is denied.
2020-10-19 08:52:22,662 [Main] ERROR -    at System.IO.__Error.WinIOError(Int32 errorCode, String maybeFullPath)
   at System.IO.FileStream.Init(String path, FileMode mode, FileAccess access, Int32 rights, Boolean useRights, FileShare share, Int32 bufferSize, FileOptions options, SECURITY_ATTRIBUTES secAttrs, String msgPath, Boolean bFromProxy, Boolean useLongPath, Boolean checkHost)
   at System.IO.FileStream..ctor(String path, FileMode mode, FileAccess access)
   at System.CodeDom.Compiler.TempFileCollection.EnsureTempNameCreated()
   at System.CodeDom.Compiler.TempFileCollection.AddExtension(String fileExtension, Boolean keepFile)
   at System.Configuration.Internal.WriteFileContext..ctor(String filename, String templateFilename)
   at System.Configuration.Internal.InternalConfigHost.StaticOpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext, Boolean assertPermissions)
   at System.Configuration.Internal.InternalConfigHost.System.Configuration.Internal.IInternalConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext, Boolean assertPermissions)
   at System.Configuration.Internal.InternalConfigHost.System.Configuration.Internal.IInternalConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext)
   at System.Configuration.ClientConfigurationHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext)
   at System.Configuration.UpdateConfigHost.OpenStreamForWrite(String streamName, String templateStreamName, Object& writeContext)
   at System.Configuration.MgmtConfigurationRecord.SaveConfigSource(DefinitionUpdate update)
2020-10-19 08:52:22,712 [Main] DEBUG - IconPlus_MouseClick(iconClose = '')

 

 

Then I uninstalled 3.2.1 and installed 3.2.0, and did the exact same process, finding this in the log file (everything before the first line I quote here was the same between the two instances):

2020-10-19 08:56:13,805 [Main] INFO  - O'Telescope Dependencies ALREADY REGISTERED!
2020-10-19 08:56:13,960 [Main] DEBUG - ButtonPlus_MouseClick(btnSave = 'Save')
2020-10-19 08:56:14,010 [ReadWeatherCenter(Normal)] DEBUG - No weather provider configured.
2020-10-19 08:56:15,705 [Main] DEBUG - IconPlus_MouseClick(iconClose = '')

 

It appears to not like putting a temp file under the program files subdir. HTH!

 

Link to post
Share on other sites
  • 0

I was curious and went trolling to look for where the configuration information is being stored. I had thought that user configuration files were in the directory with the program, but apparently that is just the default copy. That kind of makes sense since MS locks down program files to prevent one program from corrupting another.

I ended up finding my configuration files in AppData\Local\VirtualStore\... I have full control over VirtualStore and child sub-folders. 

I hope this helps.

Link to post
Share on other sites
  • 0
1 hour ago, astroman133 said:

I was curious and went trolling to look for where the configuration information is being stored. I had thought that user configuration files were in the directory with the program, but apparently that is just the default copy. That kind of makes sense since MS locks down program files to prevent one program from corrupting another.

I ended up finding my configuration files in AppData\Local\VirtualStore\... I have full control over VirtualStore and child sub-folders. 

I hope this helps.

What version are you running? I knew from past experience that you generally can't write to the Program Files tree, but it appears that 3.2.1 is trying to do so. Rather than under Virtual Store, I would have thought they would be under User/AppData/Local/BackyardEOS, but I guess it doesn't really matter which it uses as long as it works.

Hoever, I tried this on a different machine, and I'm still seeing a difference in how 3.2.0 and 3.2.1 install themselves. 3.2 is creating the proper directory under both Program Files (x86), and Virtual Store/Program Files (x86). But 3.2.1 only creates the (changed name) directory under Program Files (x86), and NOT the one under Virtual Store/Program Files (x86). Specifically, i told it to install in Program Files (x86)/BackyardEOSv3.2.1, and it did, but did not create the corresponding directory under Virtual Store like 3.2.0 did, and the settings changes are still not sticking. Looks like maybe Guylain is using a different installer builder now, or is using different settings in it.

 

Link to post
Share on other sites
  • 0

Try this

  1. Uninstall all versions for BYE
  2. Delete all BackyardEOS install folder inside "Program Files (x86)"
  3. Delete all "C:\Users\<<username>>\AppData\Local\VirtualStore\Program Files (x86)\BackyardEOS*" config folders.
  4. REBOOT
  5. Re-install 3.2.1.RC3 and try again.

 

Link to post
Share on other sites
  • 0
55 minutes ago, admin said:

Try this

  1. Uninstall all versions for BYE
  2. Delete all BackyardEOS install folder inside "Program Files (x86)"
  3. Delete all "C:\Users\<<username>>\AppData\Local\VirtualStore\Program Files (x86)\BackyardEOS*" config folders.
  4. REBOOT
  5. Re-install 3.2.1.RC3 and try again.

 

Did every step, and same results: no BYE folder under virtual store/program files (x86), and settings not saved.

As variant on the testing, I then installed 3.2.0 without removing 3.2.1, keeping the default location. Now it works: as soon as I start BYE, a BYE folder appears in the virtual store location, and settings are saved.

It looks like there are issues specific to 3.2.1, which according to the log file is attempting to write to the installation Program Files directory, rather than the virtual store one:

2020-10-19 13:38:03,673 [Main] ERROR - Access to the path 'C:\Program Files (x86)\BackyardEOSv3.2\fnoi5scb.tmp' is denied.

It looks like the redirect to Virtual Store isn't working for some reason; IIRC, that's supposed to be automatic, isn't it?

 

Link to post
Share on other sites
  • 0

This is still happening to me with BYE 3.2.1 RC3 where the programs starts with default settings every time I launch it. The initial settings are different from what is in the user config file. Also the modified file timestamp does not change when settings changes are saved.

I was trying to help a friend with a new EOS R6. He needs the latest pre-release to support the R6 but is experiencing the same settings issues.

Any progress on fixing this?

Thanks!

Link to post
Share on other sites
  • 0

No progress, I would have to change the entire setting subsystem.  It's the classic windows privileges.  That code has not changed for 10 years.

One work around is to delete the actual folder under appdata, on startup it should recreate itself that has always done the trick in the pass.  Alternatively re-installing in a new folder also does it.

Link to post
Share on other sites
  • 0

I understand about classic Windows privileges, but this is the first time since I started using BYE that I have had a settings issue. Also, I have Full Control of the settings subfolder, just as I have for previous versions.

Again, this did not happen with 3.2.0, installed to a different folder, but with the same privileges (Full Control) of the Virtual Store subfolder. To me, it seems to be something else!

Link to post
Share on other sites
  • 0

I agree with astroman133: this doesn't feel like a classic windows privileges issue, at least not as I've seen it in the past. Neither completely deleting all versions of BYE folders in program files and app data and reinstalling, nor reinstalling to a different folder, help in this case, and as you said above, they used to correct the issue in older versions.

Are you sure you're building the install package with the exact same settings as you used in 3.2.0? Something sure seems to have changed, even if it's just a typo, like a folder name or privileges requested on install...

 

Link to post
Share on other sites
  • 0

Windows is not longer completely beholden to only the "classic windows privileges".  Additional restrictions at the OS level for Write Access to "protected" directory trees such as %windows% and \Program Files\ and \Program Files (x86)\ have been added (and then in some cases modified or rescinded) over the evolution of Windows OS and the Microsoft response to Heightened Security Conscientiousness.

And sadly, this isn't the only Dev Effort where long-functional approaches seem to hit the proverbial brick wall...  Here's hoping Guylain can scale or blast through it...

Link to post
Share on other sites
  • 0
On 10/27/2020 at 10:26 PM, admin said:

No progress, I would have to change the entire setting subsystem.  It's the classic windows privileges.  That code has not changed for 10 years.

One work around is to delete the actual folder under appdata, on startup it should recreate itself that has always done the trick in the pass.  Alternatively re-installing in a new folder also does it.

You don't have just a single line of code somewhere that defines your config file's location? That could be changed to something else?

Link to post
Share on other sites
  • 0

No, the location is governed by .net/Windows.  I would need to change the entire setting subsystem all together. 

I did have to upgrade .net version in 3.2 due to other issues, that is the only thing that I think would be the cause for this. I'm still unsure what I'll with this one.

Link to post
Share on other sites
  • 0
On 11/28/2020 at 6:34 AM, selnekovic said:

Right click on the application icon and switch to the security/permissions tab. Assign the account you are logged in all the write/read permissions. This should solve the problem, although it should not occur in the first place.

Thank you for sharing this.

Link to post
Share on other sites
  • 0

Thanks for the suggestion, but  your suggestion did not work for me.

I am a member of the Administrators group on my PC, but the Users group did not have permissions as suggested. I changed the Users permissions for BinaryRiv ers.BackyardEOS.Start.Camera1.exeto grant Full control and started BYE 3.2.0 RC3. It still did not save my settings.

Link to post
Share on other sites
  • 0
40 minutes ago, astroman133 said:

Thanks for the suggestion, but  your suggestion did not work for me.

I am a member of the Administrators group on my PC, but the Users group did not have permissions as suggested. I changed the Users permissions for BinaryRiv ers.BackyardEOS.Start.Camera1.exeto grant Full control and started BYE 3.2.0 RC3. It still did not save my settings.

You need to change the permission on the folder where BYE/BYN is installed, not the .exe. 

 

Link to post
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Answer this question...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.


×
×
  • Create New...

Important Information

This site uses cookies to offer your a better browsing experience. You can adjust your cookie settings. By closing this banner, scrolling this page, clicking a link or continuing to browse otherwise, you agree to the use of cookies, our Privacy Policy, and our Terms of Use