I am running my shared database on Windows Home Server. DVDP is in the startup programs list, so that it becomes available whenever the server is booted.

However, DVDP does not respond cleanly to a windows shutdown request, so that when it restarts, you get the warning suggesting that the database be repaired.

This is a serious bug. I am requesting that Invelos fix DVDP such that it responds properly to the internal Windows shutdown message sent to all applications, and safely close the database to prevent corruption. Perhaps I should have made this a trouble ticket - I'll do that now. Done.

For completeness, this is latest version of DVDP running on Windows Home Server 2011 (x64) in shared database mode.

Quoting Mithi:

Quote:
Same thing came up recently in the Frequency of local db errors (need for DB Repair)? thread.

So it isn't only you, it really is a DVD Profiler issue and yes this absolutely has to be fixed.

cya, Mithi

Thanks for the corroboration.

Quoting StaNDarD:

Quote:
Do you have the backup notification on closing activated? This might prevent DVDP from closing.

Good tip. I'll check. That would be a good workaround, but DVDP should require no user intervention to respond to an official "Get outta Dodge" message from Windows. Thanks, I'll report back the results.

Yep, also confirming this happens.

Quoting GSyren:

Quote:
It's actually a bit worse than that. Even if you shut down Profiler manually, it keeps running for a while in the background. How long probably depends on how fast your computer is. If it has been idling for a long time, memory seems to have been swapped out, so first it starts to add memory in chunks, and only after that does Profiler actually start to shut down.

So even if you exit Profiler and then shut down Windows, you can still get the same problem. I check with Task Manager to make sure that Profiler has run its course before I shutdown/reboot. I've seen it run for up to a minute on my machine.

This happens to me as well.  I try to give it a fwe minutes after closing DVDP before shutting down or restarting.

Quoting ruineddaydreams:

Quote:
confirmed. i always shut down dvdp manually before restarting or shutting down to prevent the need for database repair

So do I but, to be fair to DVDP, I have to treat Outlook the same way and it's not like Microsoft are rushing to 'repair' that or even consider it a significant problem!

Quoting mreeder50:

Quote:
Come on gang, it only takes one click in the upper right corner on the X to quit a program. Shutting down Windows without quitting your running programs seem a little like getting bashed in the head with a hammer to go to sleep instantly. It may work, but there are consequences.  

Well, as pointed out, quitting the program doesn't help unless one waits for the background process to finish. And Windows is designed to let programs shut down cleanly.

Quoting mreeder50:

Quote:
You (general you) could set up a bat file with built-in delays to allow processes to stop and finally at the end, shutdown Windows.

This would go overly complicated since you would have tho create a shutdown script (and I mean shutdown, not log out script) with a loop function that would monitor DVDP process and when the error level is correct (DVDP process has been stopped) it would continue the shutdown process. I'm not even sure if this is possible with .bat scripts used in 90' (I remember they have some limitations with for-loop and error levels).

I understood that this bug is an issue if you run DVDP on server as a service when nobody is logged in and automatic reboot is initiated by, for example Windows update. In normal desktop user situations (user logged in) you can just close DVDP, make sure that the process has been shutdown and reboot.