MSDE doubts

am having a problem with MSDE. My application uses the MSDE databse.
Sometimes when my application is trying to connect to database (PMP_v3_0),
then the following error is generated:
Description = Cannot open database requested in login 'PMP_v3_0'. Login
fails.
This error is also getting to other databses sometimes:
Cannot open database requested in login 'Insight_v50_0_84711921'. Login
fails.
This eror is only seen some time after the system is rebooted. Why is this
error generated only when system is rebooted?
What is the start up behaviour of MSDE? I have got the following output in
the log file of MSDE when the system is rebooted.
2006-01-26 09:29:29.96 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-01-26 09:29:29.99 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-01-26 09:29:29.99 server All rights reserved.
2006-01-26 09:29:29.99 server Server Process ID is 944.
2006-01-26 09:29:29.99 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2006-01-26 09:29:30.10 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2006-01-26 09:29:31.17 server SQL Server configured for thread mode
processing.
2006-01-26 09:29:31.23 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2006-01-26 09:29:33.34 spid4 Starting up database 'master'.
2006-01-26 09:29:35.73 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-01-26 09:29:35.73 spid5 Starting up database 'model'.
2006-01-26 09:29:35.84 spid4 Server name is 'KRISHNA'.
2006-01-26 09:29:35.87 spid4 Skipping startup of clean database id 4
2006-01-26 09:29:35.95 spid4 Skipping startup of clean database id 7
2006-01-26 09:29:35.95 spid4 Skipping startup of clean database id 8
2006-01-26 09:29:35.96 spid8 Starting up database 'eXpress'.
2006-01-26 09:29:35.96 spid9 Starting up database
'Insight_v50_0_84711921'.
2006-01-26 09:29:36.71 spid5 Clearing tempdb database.
2006-01-26 09:29:40.37 server SQL server listening on 172.20.50.117: 1433.
2006-01-26 09:29:40.37 server SQL server listening on 127.0.0.1: 1433.
2006-01-26 09:29:42.85 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-01-26 09:29:42.85 server SQL Server is ready for client connections
2006-01-26 09:29:43.35 spid5 Starting up database 'tempdb'.
2006-01-26 09:29:44.34 spid4 Recovery complete.
2006-01-26 09:29:44.34 spid4 SQL global counter collection task is
created.
2006-01-26 09:29:45.34 spid51 Starting up database 'eXpress'.
2006-01-26 09:30:11.68 spid56 Starting up database 'vmm_db_v2'.
2006-01-26 09:30:15.56 spid58 Starting up database
'Insight_v50_0_84711921'.
2006-01-26 09:30:16.79 spid58 Error: 15457, Severity: 0, State: 1
2006-01-26 09:30:16.79 spid58 Configuration option 'show advanced
options' changed from 0 to 1. Run the RECONFIGURE statement to install..
2006-01-26 09:30:16.89 spid58 Error: 15457, Severity: 0, State: 1
2006-01-26 09:30:16.89 spid58 Configuration option 'show advanced
options' changed from 1 to 0. Run the RECONFIGURE statement to install..
2006-01-26 09:31:32.03 spid58 Error: 15457, Severity: 0, State: 1
2006-01-26 09:31:32.03 spid58 Configuration option 'show advanced
options' changed from 0 to 1. Run the RECONFIGURE statement to install..
2006-01-26 09:31:32.09 spid58 Error: 15457, Severity: 0, State: 1
2006-01-26 09:31:32.09 spid58 Configuration option 'show advanced
options' changed from 1 to 0. Run the RECONFIGURE statement to install..
2006-01-26 09:41:33.32 spid62 Starting up database 'PMP_V3_0'.
How can i know the start up behaviour of MSDE?. In the logfie i see the
following in the begining:
Skipping startup of clean database id 4
why does MSDE skip the start up of clean database. In some lo files i see
that even though 'PMP_V3_0' is started in the begining, i get the same error
.
Please see the below log file:
2006-01-27 15:15:09.78 server Microsoft SQL Server 2000 - 8.00.760
(Intel X86)
Dec 17 2002 14:22:05
Copyright (c) 1988-2003 Microsoft Corporation
Desktop Engine on Windows NT 5.0 (Build 2195: Service Pack 4)
2006-01-27 15:15:09.79 server Copyright (C) 1988-2002 Microsoft
Corporation.
2006-01-27 15:15:09.79 server All rights reserved.
2006-01-27 15:15:09.79 server Server Process ID is 932.
2006-01-27 15:15:09.79 server Logging SQL Server messages in file
'C:\Program Files\Microsoft SQL Server\MSSQL\LOG\ERRORLOG'.
2006-01-27 15:15:09.87 server SQL Server is starting at priority class
'normal'(2 CPUs detected).
2006-01-27 15:15:11.23 server SQL Server configured for thread mode
processing.
2006-01-27 15:15:11.31 server Using dynamic lock allocation. [500] Lock
Blocks, [1000] Lock Owner Blocks.
2006-01-27 15:15:13.87 spid4 Starting up database 'master'.
2006-01-27 15:15:17.45 server Using 'SSNETLIB.DLL' version '8.0.766'.
2006-01-27 15:15:17.45 spid5 Starting up database 'model'.
2006-01-27 15:15:17.54 spid4 Server name is 'KRISHNA'.
2006-01-27 15:15:17.54 spid4 Skipping startup of clean database id 4
2006-01-27 15:15:17.56 spid4 Skipping startup of clean database id 8
2006-01-27 15:15:17.57 spid8 Starting up database 'eXpress'.
2006-01-27 15:15:17.57 spid9 Starting up database
'Insight_v50_0_84711921'.
2006-01-27 15:15:17.67 spid10 Starting up database 'PMP_V3_0'.
2006-01-27 15:15:19.01 spid5 Clearing tempdb database.
2006-01-27 15:15:23.62 server SQL server listening on 172.20.50.117: 1433.
2006-01-27 15:15:23.62 server SQL server listening on 127.0.0.1: 1433.
2006-01-27 15:15:26.06 server SQL server listening on TCP, Shared Memory,
Named Pipes.
2006-01-27 15:15:26.06 server SQL Server is ready for client connections
2006-01-27 15:15:26.49 spid5 Starting up database 'tempdb'.
2006-01-27 15:15:29.60 spid4 Recovery complete.
2006-01-27 15:15:29.60 spid4 SQL global counter collection task is
created.
2006-01-27 15:15:29.64 spid53 Starting up database 'eXpress'.
2006-01-27 15:15:31.82 spid56 Starting up database 'PMP_V3_0'.
2006-01-27 15:15:59.75 spid67 Starting up database 'vmm_db_v2'.
2006-01-27 15:16:07.12 spid75 Error: 15457, Severity: 0, State: 1
2006-01-27 15:16:07.12 spid75 Configuration option 'show advanced
options' changed from 0 to 1. Run the RECONFIGURE statement to install..
2006-01-27 15:16:07.18 spid75 Error: 15457, Severity: 0, State: 1
2006-01-27 15:16:07.18 spid75 Configuration option 'show advanced
options' changed from 1 to 0. Run the RECONFIGURE statement to install..
2006-01-27 15:17:21.01 spid56 Error: 15457, Severity: 0, State: 1
2006-01-27 15:17:21.01 spid56 Configuration option 'show advanced
options' changed from 0 to 1. Run the RECONFIGURE statement to install..
2006-01-27 15:17:21.10 spid56 Error: 15457, Severity: 0, State: 1
2006-01-27 15:17:21.10 spid56 Configuration option 'show advanced
options' changed from 1 to 0. Run the RECONFIGURE statement to install..
2006-01-27 16:18:04.35 spid70 Error: 15457, Severity: 0, State: 1
2006-01-27 16:18:04.35 spid70 Configuration option 'show advanced
options' changed from 0 to 1. Run the RECONFIGURE statement to install..
2006-01-27 16:18:04.42 spid70 Error: 15457, Severity: 0, State: 1
2006-01-27 16:18:04.42 spid70 Configuration option 'show advanced
options' changed from 1 to 0. Run the RECONFIGURE statement to install..
Why is the database "'PMP_V3_0'." started two times?you see PMP_V3_0 started twice becoz you have enabled auto close option
for this database... disabling auto close might solve your problem