[Zope] HELP! My Zclass just disappeared and I am getting *weird* console errors!

[Dieter Maurer]

Darin Lee writes:
 > I have been working on a ZClass based product for the past month or so=
 -
 > somehow I just clicked the wrong button combination (I was adjusting '=
views'
 > mappings) and my zclass is no longer addable via the factory. Instead,=
 I get
 > the following error:
 >=20
 > Error Type: NameError
 > Error Value: global name 'EZPortal' is not defined
Do you know this name?
Is it the name of the disappeared ZClass?

 > ...
 > Zope console errors follow:
 >=20
 > --------------------------------------------------
 > Zope console is returning the following message, although I'm unsure i=
f it's
 > related or not:
 > 2001-11-25T06:38:39 ERROR(200) ZODB setklassstate failed
 > Traceback (innermost last):
 >   File E:\PROGRA~1\ZOPEDE~1\lib\python\ZODB\Connection.py, line 582, i=
n
 > setklass
 > state
 >     (Info:       >?)
 >   File E:\PROGRA~1\ZOPEDE~1\lib\python\ZODB\FileStorage.py, line 588, =
in
 > load
 >     (Object: E:\Program Files\ZopeDevelopment\var\Data.fs)
 >   File E:\PROGRA~1\ZOPEDE~1\lib\python\ZODB\FileStorage.py, line 564, =
in
 > _load
 >     (Object: E:\Program Files\ZopeDevelopment\var\Data.fs)
 > KeyError:       >?
 > .....
 > ------
 > 2001-11-25T06:38:39 ERROR(200) ZODB Couldn't load state for
 > '\x00\x00\x00\x00\x0
 > 0\x00=3D\x89'
 > Traceback (innermost last):
 >   File E:\PROGRA~1\ZOPEDE~1\lib\python\ZODB\Connection.py, line 519, i=
n
 > setstate
 >=20
 >   File E:\PROGRA~1\ZOPEDE~1\lib\python\ZODB\FileStorage.py, line 588, =
in
 > load
 >     (Object: E:\Program Files\ZopeDevelopment\var\Data.fs)
 >   File E:\PROGRA~1\ZOPEDE~1\lib\python\ZODB\FileStorage.py, line 564, =
in
 > _load
 >     (Object: E:\Program Files\ZopeDevelopment\var\Data.fs)
 > KeyError:       =3D=EB
 > ....
That does not sound good....

  Usually, Zope does not use keys like that.

  I would expect that somehow the content of your "Data.fs" had been
  corrupted.

  But I do not have a precise idea....


At your place, I would probably try the following:

  *  make a backup copy of "Data.fs"

  *  use "tranalyser" to analyse "Data.fs" and truncate it to
     a time when the problem has not yet been there.

     This will eradicate all changes after this time but
     recover your work until then.

  *  Think about a proper backup strategy (e.g. daily backing up "Data.fs=
")
     in order to prevent panic when the problem should reoccur


Dieter