1 Topic by lornashaw

  • lornashaw
  • Member
  • Offline
  • Registered: 23-01-2012
  • Posts: 44

Topic: bug report on startup

Since upgrading a networked version of Recorder, one of the networked PCs is refusing to open Recorder, coming up with an error message instead:

exception class   : EApplicationSettingsError
exception message : The Object Sheet File Path setting is missing or incorrect. Recorder is not installed properly and cannot start.

Recorder is working fine on the other two computers that it is networked to.

Does anyone have any ideas as to how to overcome this?

thank you
Lorna

Post's attachments

Error-73507550870354.txt 10.38 kb, 4 downloads since 2013-07-26 

You don't have the permssions to download the attachments of this post.

2 Reply by stuart_k

  • stuart_k
  • Member
  • Offline
  • Registered: 29-01-2013
  • Posts: 24

Re: bug report on startup

I have just received the same error - We upgraded our live environment with 6.18.1.260 yesterday and tried to create a new workstation to it.  It is this workstation that has the above error.

Did anything change in the upgrade to the workstation setup?? (we upgraded from 6.15)

Thanks

Stuart

3 Reply by charliebarnes

  • charliebarnes
  • Veteran
  • Offline
  • From: Greater Lincolnshire
  • Registered: 07-09-2008
  • Posts: 1,396

Re: bug report on startup

Sounds like a registry/path setting (The "Object Sheet File Path" is the path to the shared Object Sheet folder where map polygon layers are stored.)

The recorder system check program might help - see http://forums.nbn.org.uk/viewtopic.php?id=4016

Charlie Barnes
Information Officer
Greater Lincolnshire Nature Partnership

charliebarnes's Website

4 Reply by stuart_k (edited by stuart_k 09-08-2013 07:16:14)

  • stuart_k
  • Member
  • Offline
  • Registered: 29-01-2013
  • Posts: 24

Re: bug report on startup

Using the fix in the help program seems to have resolved the issue.  Not sure why this happened (although I did wonder if the workstation application had not uninstalled properly).  Will need to try running the workstation set up on a clean client machine and see if I get the same error.

Many thanks for your help.