I restarted the Zope server from the Control Panel inside Zope and it took a long time untill it was back up again. About 20 seconds. During these 20 seconds, I started to suspect that the service wasn't working, so I manually pressed the "Start" on the Zope Server inside the Control panel in windows. I couldn't. Below is the traceback I got. I suspect that it means that the Zope server is already running and that I can't start it again (see error and Fs.lock stuff). It turned out that the server was actually running since people on the intranet was using it at the same time as I was struggling with getting the service running. Now the server is running fine, but if I go into the Services in Administrative Tools of the Control Panel, the service ZopeSite is "turned off". So from a quick look on the Win2000 server you can't tell whether the Zope Server actually is running, unless you open a web browser. Strange. It's not a production server and I guess the w2k needs a robust restart with a little kick in the machines direction. Here's the Traceback I got when I tried to start it because I thought it was started: C:\Program Files\Zopesite>start.bat C:\Program Files\Zopesite>"C:\Program Files\Zopesite\bin\python.exe" "C:\Program Files\Zopesite\z2.py" -D Traceback (innermost last): File "C:\Program Files\Zopesite\z2.py", line 554, in ? exec "import "+MODULE in {} File "<string>", line 1, in ? File "C:\PROGRA~1\Zopesite\lib\python\Zope\__init__.py", line 110, in ? DB=ZODB.FileStorage.FileStorage(Globals.BobobaseName) File "C:\PROGRA~1\Zopesite\lib\python\ZODB\FileStorage.py", line 262, in __ini t__ lock_file(f) File "C:\PROGRA~1\Zopesite\lib\python\ZODB\lock_file.py", line 115, in lock_fi le raise error, ( ZODB.POSException.StorageSystemError: Could not lock the database file. There m ust be another process that has opened the file. <p> C:\Program Files\Zopesite>