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

Unhandled Error


seajay0_0

Question

Having been using BYE v3.0.3.successfully for some months, I am now getting a consistent BackyardEOS.Start error  whenever I try to start. Whatever I do, I cannot get rid of this now, even after reboot! I can connect to my camera using the Canon utility or ATP. The error occurs even if I disconnect the camera via USB. I have uninstalled BYE and reinstalled again, but still get the same.

 

Is there some corrupted file that doesn’t get uninstalled that I can manually delete? I’m using Win7 on an i7 machine.

 

Can you help at all?

 

Thanks

 

Christopher Jenkins

post-3114026-141893877186_thumb.jpg

Link to comment
Share on other sites

  • Answers 2
  • Created
  • Last Reply

2 answers to this question

Recommended Posts

unofficial answer from a user; 

 

That sounds like an XML error, complaining about a corrupt xml structure. The ".config" files in C:\Program Files (x86)\BackyardEOSv3 are XML. Perhaps one of those is corrupt. Do they all go away on an uninstall?

 

The dialog pic you posted mentions a specific .config file that is "bad". If that file still exists after an uninstall, I would try deleting it before re-install.

 

 

 

 

 

Link to comment
Share on other sites

unofficial answer from a user; 

 

That sounds like an XML error, complaining about a corrupt xml structure. The ".config" files in C:\Program Files (x86)\BackyardEOSv3 are XML. Perhaps one of those is corrupt. Do they all go away on an uninstall?

 

The dialog pic you posted mentions a specific .config file that is "bad". If that file still exists after an uninstall, I would try deleting it before re-install.

 

 

 

 

 

This has been resolved directly with user.  Windows somehow corrupted the config file.

 

The simplest resolution is to install in a separate folder when this occurs.

 

Regards,

 

 

Link to comment
Share on other sites

Archived

This topic is now archived and is closed to further replies.


×
×
  • 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