On Tuesday or Wednesday, being conscientous
about worm patches and all that sort of thing, I downloaded Service Pack 2 for
Windows 2000 onto our server.
Since then, ebase has had trouble --
looked for the host in the wrong places, couldn't locate files, scripts
didn't run, etc. Today, it can't find files at all and gives me only the
database in the form in which we imported it a year ago.
I did a search for all files containing
"*_.*" and found that the service pack uses the same naming convention
ebase does. I'm thinking I have to restore my database from
Monday's backup which isn't really a crisis. Is there some way to
avoid this happening again? How can I make sure my restored database
and the windows upgrade are compatible? Thanks for your help.
Heidi Green
Connecticut Housing Coalition
------------------
Reminder to each recipient: To change your list account preferences, go to
http://email.sparklist.com/scripts/lyris.pl?enter=support and enter the email address you used to subscribe to the ebase support list:: [email protected]
To unsubscribe send a blank email to [EMAIL PROTECTED]
---------------------------------------------------------------------
ebase - Relationship Management for Nonprofits, http://www.ebase.org
---------------------------------------------------------------------
